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

# Set Up a User for Agentic Payment

> Start with Connect the account for Reap API onboarding, or Enrol the card for approved external, then create the passkey.

Setup runs once per user and the whole journey happens directly in the chat. After it completes every purchase needs only one passkey tap. Users on a general assistant first connect your service to that assistant while users in a purpose built agent start directly at sign in.

<Note>
  Start from the step that matches your Reap integration model.

  Clients using Reap APIs for user onboarding, identity verification, and account creation must begin with "Connect the account".

  Clients whose users and accounts have already been onboarded and provisioned through an approved external flow may begin with "Enrol the card".
</Note>

<Steps>
  <Step title="Connect the account" icon="user-plus">
    <Accordion title="For Reap API onboarding clients" description="External clients skip this step and begin at Enrol the card">
      The user signs in to an existing account or creates and verifies a new one directly in the chat.

      * Your application registers the user with [`POST /users/`](https://docs.reap.global/api-reference/users/create-user)
      * Your application advances identity verification with [`POST /users/id/application`](https://docs.reap.global/api-reference/users/advance-the-user-application) using the method configured on your project
      * Reap reports each status change through the [`user-application-status-updated`](https://docs.reap.global/api-reference/user-application-status-updated) webhook
      * Your application creates the account with [`POST /accounts/`](https://docs.reap.global/api-reference/accounts/create-account) once the status reaches `APPROVED`
    </Accordion>
  </Step>

  <Step title="Enrol the card" icon="credit-card">
    The user enrols the card once on a secure card surface so every purchase pays with a single use token instead of the card number.

    * Your application starts enrolment with `POST /agentic/enrolments` and receives the secure surface session
    * Reap stores the card in a PCI compliant vault and provisions a network token
  </Step>

  <Step title="Create the passkey" icon="fingerprint">
    The user creates the payment passkey inside the same secure surface session and setup is complete.

    * Reap binds the passkey to the user device inside the same session so no separate tokenise or passkey endpoint exists
    * Reap confirms the finished setup through the `enrolment-completed` webhook
    * One biometric tap now approves each future purchase and the card network recognises the passkey as the user proof of consent
  </Step>
</Steps>

## Card programmes

<Note>
  Reap programme cards enrol with an existing card ID. BIN sponsorship clients with no Reap card object use the same secure passthrough where the PAN travels from the cardholder to the vault and never touches Reap or the agent.
</Note>

## Next steps

<Card title="Make a one time purchase" icon="shopping-bag" href="/agentic-payment/one-time-purchases">
  Run the first purchase from quote to verified order
</Card>