Skip to main content
Airport Lounge Access is coming soon and is not currently available through the Reap API.

​
Four parties, one flow

You

Purchase pass inventory, issue passes to your cardholders, monitor stock and usage and receive webhook notifications

Reap

Reviews every purchase, holds the inventory pool, creates each pass on the lounge network and keeps pass status in step with the card

The lounge network

Admits the cardholder at lounges in the Priority Pass network and reports every visit back to Reap

The cardholder

Receives the pass inside your app and scans the QR code or barcode at the lounge door

​
The pass journey

Inventory is purchased in batches and passes are issued one card at a time. Redemption and expiry then run for as long as each pass lives. The flow is the same for every client, whether you operate through the Reap dashboard or a direct API integration. The working with passes guide walks each stage of the journey in order.

​
The spending control model

The prepaid inventory pool is the spending cap. A pass can only be issued while stock remains, every successful issuance draws the pool down by exactly one, and a failed creation never draws it down at all.
Passes enter the pool only through an approved purchase, so exposure is agreed before a single pass reaches a cardholder. Counters never fall below zero. When one pass remains, only one issuance can succeed. Approved purchases are invoiced to your business and every pass carries its recorded cost.

​
The plan

One plan is available today. LOUNGE_PP_1PA is a single use pass that covers one lounge visit and stays valid for 365 days from issuance. Pricing is configured for your business during onboarding. A redeemed pass is complete, so issue a new pass from your inventory when a cardholder needs another visit.

​
Who does what

Reap operates the whole flow behind the Reap API. It reviews and approves every inventory purchase, holds the pool and creates each pass on the lounge network at the moment of issuance. It records lounge visits against the right pass, keeps pass status synchronised with the card lifecycle and delivers webhook notifications and audit records throughout.

​
Before you start

  1. Airport Lounge Access enabled for your business by your Reap team, since requests made before enablement are rejected
  2. The lounge plan configured for your business
  3. Cards issued through Reap, because every pass attaches to an existing card
  4. A registered webhook endpoint for the purchase decision and pass creation events

​
Next steps

Working with passes

Purchase inventory, issue passes and track lounge visits

Lifecycle and events

The four pass statuses, the card operations that move them and the webhook events