Skip to main content
The answers below reflect the status of the module today. Anything not yet live sits in the final entry and is clearly labelled.
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. The approved mandate cap is the hard spending limit of the mandate. A total above the cap fails the payment and the user must approve a new mandate with a passkey tap.
A total that drifts from the quote but stays within the cap moves the checkout to requires_new_quote and the purchase proceeds under the same approved mandate once a new quote is generated. A total above the cap fails and needs a fresh approval.
No. One passkey tap approves the standing mandate and each later cycle charges under that approval as long as the repriced total stays within the cap per charge. The user can pause, resume or cancel at any time and charges stop instantly. Recurring behaviour in each cycle is still being tested in the sandbox and may change.
Most purchases do not require the step because the passkey approval at the mandate already authenticated the user. An occasional challenge pauses the checkout through the checkout-escalated webhook and the user approves it in the chat within five minutes.
No. The card sits in a PCI compliant vault and every purchase pays with a single use network token. For BIN sponsorship clients the PAN travels from the cardholder to the vault and never touches Reap or the agent.
Reap matches every order against the card authorisation event on its own rails. The full trail of consent evidence, mandate, credential lifecycle, order and authorisation stays queryable and disputable.
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

Set up your first user

Walk the one time setup across account, card and passkey