Skip to main content
The answers below reflect the status of the capability today and say when something is planned rather than live.
Checkout coverage is confirmed for UCP merchants. Support for guest checkout, login required flows, and custom integrations remains unconfirmed and is subject to change.
No. Every purchase requires the user’s approval on a Reap-hosted page before any charge. Passkey-approved mandates on the roadmap will replace the per-purchase approval with a spending cap the user sets once.
A quote locks the payable amount for a short window and the checkout pays the quoted amount. When a quote expires before the checkout opens, your application creates a fresh quote and the user sees the new price before approving.
Not yet. Recurring purchases are on the roadmap: one approval will create a standing mandate and each cycle will charge under it within an approved ceiling. See recurring purchases for the planned behavior.
Never in your application or the agent. The user enters or selects the card on the Reap-hosted approval page, and the details travel from the cardholder to the secure surface. Card enrollment on the roadmap will vault the card once and pay later purchases with single-use credentials.
The user completes any issuer authentication inside the hosted approval page as part of paying. Relaying challenges into the chat for in-conversation approval is on the roadmap.
The checkout reports its lifecycle status and, once completed, the merchant order reference and the final charged amount. Matching each order to the card authorization on Reap’s rails is on the roadmap.
This capability currently supports Reap Card and Visa cards. Support for additional card types and payment networks may be introduced in the future.

​
Next steps

Make a one-time purchase

The full request flow from product search to the completed order