Skip to main content
Registration happens once at the platform level, setup once per user, and the purchase flow repeats for every order. A single recurring mandate covers all subsequent cycles.

​
Three phases

Agent registration happens once at platform level

Reap registers the agent execution identity with the relevant agent registry and enrols it in the applicable trusted agent protocol before any user session begins. Every client inherits this registration automatically, with no integration work or user action required.

Setup happens once per user

The user connects an account, enrols the card into a PCI compliant vault and creates the payment passkey in one secure surface session. The setup guide walks this journey.

The purchase loop repeats for every order

The agent quotes the item, the user approves a mandate with one passkey tap and Reap executes the checkout through to the verified order.
This capability currently supports Reap Card and Visa cards. Support for additional card types and networks may be introduced in the future.

​
The purchase path

​
Inside the purchase loop

  • The agent finds the item through your product discovery and POST /quotes opens the merchant checkout with a priced proposal and a quote reference
  • The user approves the cap, merchant and validity with a passkey biometric and POST /mandates captures the signed approval
  • Reap runs the real checkout with POST /checkouts, reconciles the live total against the quote before any charge and pays with a single use network token
  • Reap relays an occasional issuer challenge for an in chat approval and most purchases do not require this step
  • Reap verifies the order against the card authorisation on its own rails and the agent confirms it back to the user

​
The machinery behind the flow

  • POST /users/ registers the end user and records terms acceptance
  • POST /users/id/application advances identity verification with the configured method
  • POST /accounts/ creates the account once verification is approved
  • POST /agentic/enrolments opens the secure surface session that vaults the card, provisions the network token and binds the payment passkey
  • POST /quotes opens the merchant checkout for the chosen item and returns the priced proposal
  • POST /mandates creates the mandate and triggers the passkey approval on the secure surface
  • POST /checkouts runs the checkout from the quote reference and the mandate
  • POST /checkouts/id/escalation/respond relays the user response to the card issuer when a challenge fires
  • GET /orders/id returns the verified order with the full record of consent evidence, mandate, credential lifecycle, order and authorisation
  • user-application-status-updated fires when the verification status changes
  • enrolment-completed fires when the card is vaulted, the network token is provisioned and the passkey is created
  • mandate-approved fires when the passkey approval is captured and the mandate becomes active
  • checkout-completed fires when the order is placed and the merchant order reference is returned
  • checkout-escalated fires when a challenge needs the user and the checkout pauses
  • order-completed fires when the order is verified and matched to the authorisation event on the Reap rails
These guides stay at the level of names and purpose. Field level detail belongs to the API Reference.

​
Next steps

Set up a user

Connect the account, enrol the card and create the passkey

Make a one time purchase

One quote, one passkey tap and one verified order

Set up recurring purchases

One approval that stands for every later cycle