Start from checkout
Direct Debit on checkout links, checkout sessions, and the site embed
Hosted checkout is a charge surface. When the customer selects Direct Debit on a checkout link or session, RevKeen can collect the checkout amount after the mandate is Active and advance notice has been given.
Hosted checkout is multi-rail. When those rails are enabled, the customer can pay by card, Direct Debit, or a wallet. Pay by Bank is not a live checkout rail. See Checkout.
Checkout link or session, no usable mandate
- The customer opens the checkout URL and selects Direct Debit.
- Checkout continues into hosted mandate setup in the same session.
- They authorise the mandate. RevKeen records the authorisation against the checkout.
- If amount, date, and frequency are known, they receive a combined confirmation and first-collection notice. Otherwise confirmation now and advance notice later.
- Checkout completes into a pending Direct Debit confirmation. That is not payment succeeded.
- After Active and the notice period, RevKeen submits one collection for that checkout.
Do not describe mandate submission as payment. Use wording such as Set up Direct Debit and confirm order or Set up Direct Debit and schedule £X.
Checkout link or session, Active mandate already
Checkout skips the mandate page, tells the customer Direct Debit is approved, sends a separate advance notice, and then collects. Guest checkout resolves the customer only inside the merchant on the signed checkout session. A matching email at another merchant never authorises mandate reuse.
Embed on your site
The public embed at https://releases.revkeen.com/embed/v1/checkout.js mounts mandate capture on your site. Bank details are not stored in the browser.
Embed capture is mandate setup. It does not collect an amount by itself. To charge, send the customer through an invoice, a checkout link or session with an amount, or an eligible subscription collection after notice.
Card PAN collection stays on RevKeen-hosted checkout. The embed is not a card iframe. See Embed.
Guest identity
Checkout captures email first. RevKeen derives the merchant from the signed checkout session and looks up customers and mandates only for that merchant. Completing Direct Debit in checkout does not log the customer into the customer portal. Confirmation emails may include an optional portal link for later status.
After checkout
| State | Meaning |
|---|---|
| Mandate submitted | Instruction received. Checkout is not paid. |
| Mandate Active | Eligible to collect after notice. |
| Collection scheduled | Notice has been or will be sent. |
| Collection succeeded | The checkout or invoice can move to paid. |
If a one-off collection fails, checkout replaces the scheduled state with a clear failure message. For an ordinary unpaid collection (Bacs code 0), checkout offers Pay by card only when the business has Card enabled. Choosing it switches to the existing card form; it does not charge the customer automatically. For every other failed-collection outcome, checkout asks the customer to contact the business. Checkout never shows the raw Bacs reason code or silently changes payment method. The customer also gets a collection-failed email. See Emails and notices.
If checkout receives a Direct Debit state it does not recognise, it does not open bank-detail setup. The customer is asked not to re-enter bank details and to refresh the page or contact the business instead.