Skip to main content
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.
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”.

Connect the account

The user signs in to an existing account or creates and verifies a new one directly in the chat.

Enrol the 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

Create the passkey

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

​
Card programmes

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.

​
Next steps

Make a one time purchase

Run the first purchase from quote to verified order