> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reap.global/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Offer airport lounge visits as a built in benefit on the cards you issue

<Note>
  Airport Lounge Access is coming soon and is not currently available through the Reap API.
</Note>

## Four parties, one flow

<CardGroup cols={2}>
  <Card title="You">
    Purchase pass inventory, issue passes to your cardholders, monitor stock and usage and receive webhook notifications
  </Card>

  <Card title="Reap">
    Reviews every purchase, holds the inventory pool, creates each pass on the lounge network and keeps pass status in step with the card
  </Card>

  <Card title="The lounge network">
    Admits the cardholder at lounges in the Priority Pass network and reports every visit back to Reap
  </Card>

  <Card title="The cardholder">
    Receives the pass inside your app and scans the QR code or barcode at the lounge door
  </Card>
</CardGroup>

## 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.

```mermaid theme={null}
flowchart LR
    A["Purchase<br/>request"] --> B["Reap<br/>review"]
    B -->|"Approved"| C["Inventory<br/>pool"]
    B -->|"Rejected"| R["Reason via<br/>webhook"]
    C --> D["Pass issued<br/>to a card"]
    D --> E["Cardholder scans<br/>at the lounge"]
    E --> F["Visit recorded<br/>on the pass"]
```

The [working with passes](/airport-lounge-access/working-with-passes) guide walks each stage of the journey in order.

## The spending control model

<Check>
  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.
</Check>

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

<Tabs>
  <Tab title="What Reap provides">
    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.
  </Tab>

  <Tab title="What you build">
    You call the rewards endpoints from your existing integration and register a [webhook endpoint](/webhooks/overview) for the purchase decision and pass creation events. The pass returns a raw QR payload and a barcode string rather than an image, so your app generates the scannable QR code from the payload and renders both to the cardholder. You decide when to purchase stock and when to issue a pass. The same flow also runs through the Reap dashboard, so a benefit can launch before any integration work begins.
  </Tab>

  <Tab title="How the pieces interact">
    <Steps>
      <Step title="Request a batch of passes">
        You request a batch of passes and Reap reviews and decides the purchase.
      </Step>

      <Step title="Receive approved inventory">
        Approved passes land in your inventory pool and appear in your counters.
      </Step>

      <Step title="Issue a pass">
        You issue a pass to a card and Reap creates it on the lounge network within seconds.
      </Step>

      <Step title="Present and redeem the pass">
        The cardholder scans the pass at the lounge and the network reports the visit to Reap.
      </Step>

      <Step title="Update the pass lifecycle">
        Reap records the visit, updates the pass and expires or disables passes as the card and the calendar require.
      </Step>
    </Steps>
  </Tab>
</Tabs>

## 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](/cards/overview)
4. A registered [webhook endpoint](/webhooks/overview) for the purchase decision and pass creation events

## Next steps

<CardGroup cols={2}>
  <Card title="Working with passes" href="/airport-lounge-access/working-with-passes">
    Purchase inventory, issue passes and track lounge visits
  </Card>

  <Card title="Lifecycle and events" href="/airport-lounge-access/lifecycle-and-events">
    The four pass statuses, the card operations that move them and the webhook events
  </Card>
</CardGroup>