Enable Agentic Payments on your project
Agentic Payments is not generally available. Contact Reap to enable it for your project in the sandbox. Calls to the agentic endpoints fail until the capability is enabled.
Identify your customer
Each checkout carries an
owner with your own reference for the customer and an optional email. Use a stable identifier from your system so purchases associate with the same customer over time.Let the hosted page collect the card
The user enters or selects a card on the hosted approval page when they approve a purchase. Card details travel from the cardholder to the secure surface and never touch your application or the agent.
On the roadmap
A one-time setup will replace the per-purchase card step:- An enrollment vaults the card once on a secure Reap-hosted surface, and later purchases pay with single-use credentials instead of the card number
- Users onboarded through the Reap API will enroll a Reap-issued card by its card id. Create a user, Advance the user application, and Create an account cover that onboarding journey today
- Cards issued under a Reap BIN sponsorship will enroll through the same secure passthrough
- A payment passkey created during enrollment will let the user approve purchases with one biometric tap
Test cards
Seamless Reap-issued card enrollment viacardId is not yet available. Use these test cards on the hosted card entry page to run the full payment flow in the sandbox. They behave like real cards but never move money. Reap adds more cards and networks as it supports them.
These cards only work through the Agentic Payments API and are declined everywhere else.
One-time passwords
The card verification step may ask for a one-time password. Enter456789. The same code works whether you choose email or SMS delivery.
Next steps
Make a one-time purchase
Run the first purchase from product search to the completed order