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

# Agentic Payment

> Delegate a purchase to an AI agent while the user keeps control of every spend.

Agentic Payment lets an end user hand a purchase to an AI agent while a passkey approved mandate caps every spend. The user asks for an item in chat. The agent handles the checkout. One biometric tap approves the amount and no card number appears anywhere in the flow.

## Three parties, one flow

<CardGroup cols={3}>
  <Card title="The end user" icon="user">
    Makes the request in your app or any assistant experience you provide, approves each purchase with a passkey and remains in control
  </Card>

  <Card title="You" icon="building">
    Integrate the Reap Agent Enabler Module directly into your application and give the agent connect, enrol, quote, mandate, checkout and confirm capabilities
  </Card>

  <Card title="Reap" icon="shield-check">
    Powers the module underneath with UCP checkout quotes, passkey mandates, single use network tokens, checkout execution, issuer grade verification, webhooks and audit records
  </Card>
</CardGroup>

Product discovery stays with you as the agent developer. The module enters the flow at the quote.

## The safety model

<Check>
  The passkey signed mandate acts as the authorisation. The user can never spend more than the approved mandate amount.
</Check>

Credentials are issued only after the user approves the mandate with a biometric tap. Each mandate authorises a single use network token per charge scoped to the approved mandate cap, merchant and validity window. This holds whether the mandate covers one purchase or a recurring cycle. The passkey replaces the human in the loop step for most purchases.

The module operates behind the Reap API. The agent execution identity is registered in the Visa Agent Registry and enrolled in the Trusted Agent Protocol. Supported merchants can verify checkout traffic through a signed identity instead of treating it as bot traffic.

## Who does what

<Tabs>
  <Tab title="What Reap provides">
    Reap operates the Agent Enabler Module behind a single API. The module vaults the card on a secure surface, provisions network tokens, captures passkey mandates, opens checkout quotes on UCP merchants, executes the real merchant checkout, relays issuer challenges, verifies every order against the card authorisation and retains the full audit trail.
  </Tab>

  <Tab title="What you build">
    You own the chat surface and the branding. You integrate the functionality directly into your application through the current Reap API endpoints. You own product discovery. You register a webhook endpoint and surface the human in the loop challenge in chat when one fires.

    An example call sequence shows the shape of a full integration. Every call goes from your application straight to the current Reap API endpoints.

    * [`POST /users/`](https://docs.reap.global/api-reference/users/create-user), [`POST /users/id/application`](https://docs.reap.global/api-reference/users/advance-the-user-application) and [`POST /accounts/`](https://docs.reap.global/api-reference/accounts/create-account) sign the user in or create and verify a new account
    * `POST /agentic/enrolments` opens the secure enrolment surface and binds the payment passkey
    * `POST /quotes` opens a checkout quote for the chosen item
    * `POST /mandates` creates the mandate and triggers the passkey approval
    * `POST /checkouts` hands the quote reference and mandate to checkout execution
    * `POST /checkouts/id/escalation/respond` relays the user decision when a challenge fires
    * `GET /orders/id` pulls the verified order so the agent can confirm it back to the user
  </Tab>

  <Tab title="How the pieces interact">
    1. The user registers their card once on a secure Reap hosted surface
    2. The agent finds the product and locks the quoted price
    3. The user approves a merchant spend cap with one passkey tap
    4. Reap completes the merchant checkout, reconciles the final total under the cap, and pays with a single use network token
    5. Reap matches the order to the card authorisation on its own rails and returns the verified outcome

    Your application holds the credentials and the agent never calls Reap directly. The agent never receives raw credentials or issuer secrets.
  </Tab>
</Tabs>

## Next steps

<CardGroup cols={2}>
  <Card title="How agentic payment works" icon="sitemap" href="/agentic-payment/how-it-works">
    Follow the full journey from platform registration to the verified order
  </Card>

  <Card title="Set up a user" icon="user-check" href="/agentic-payment/setup">
    Walk the one time setup across account, card and passkey
  </Card>
</CardGroup>