Payment method eligibility
Understand when cards, wallets, and Direct Debit appear at checkout.
Choose a payment rail
RevKeen evaluates the purchase, merchant provider configuration, and the customer's device before showing payment methods. A method enabled in settings is not a promise that every session can use it.
| Method | Customer experience | Important boundary |
|---|---|---|
| Card | Hosted card entry, CVV, and 3-D Secure when the gateway requires it | Keep a usable card fallback for wallet-ineligible customers. |
| Apple Pay | Native wallet sheet on an eligible HTTPS origin and device | Offered for one-off and recurring/trial/usage/mixed carts when the merchant enables it. Still blocked for Direct Debit-first / card-fallback sessions. |
| Google Pay | Wallet button above the card form when it is switched on, the gateway account allows it, and the customer's browser and device support it | Available to all merchants; each merchant turns it on or off in Settings → Checkout Appearance. Evaluated independently; an Apple Pay block does not hide or enable Google Pay. |
| Direct Debit | Bank authority and scheduled collection | Submission or mandate activation does not mean funds have settled. |
Apple Pay is offered on recurring, trial, usage, and mixed carts when the merchant enables it in Settings → Checkout Appearance and the NMI processor supports Digital Wallet Recurring. The wallet sheet is configured as a recurring/vault credential (not a one-shot sale token). Hosted checkout still blocks Apple Pay when:
blocked_reason | When it applies |
|---|---|
card_fallback_only | Default method is Direct Debit and card is only a fallback. |
Google Pay does not use that Apple Pay block list. Confirm it on a supported Android/Chrome combination with the merchant's wallet rail enabled. A method present in settings is not a session-level promise.
Checkout journey
- Resolve the product, Cart, session, or invoice link on the server.
- Review customer details, line items, currency, discounts, and the amount due.
- Select an eligible method. Saved-card access can require email verification.
- Complete card authentication or Direct Debit mandate steps.
- Show the returned status. Fulfil only after your server confirms the appropriate payment or collection event.
Hosted checkout and hosted invoice pages share payment capabilities but represent different purchases: a checkout creates a purchase; an invoice link pays an existing receivable. A successful card payment and a pending Direct Debit collection must have different confirmation copy.
Troubleshooting
- Apple Pay is missing: check the merchant Appearance wallet toggle, the Direct Debit-first setting, NMI Apple Pay / processor activation (including Apple Pay ToS in the merchant portal), Safari/iOS HTTPS, and device eligibility.
- Google Pay is missing: check that Google Pay is switched on in Settings → Checkout Appearance (merchants can turn it off there), that it is available on the merchant's gateway account (RevKeen support can confirm), and that the customer is on a supported browser and device over HTTPS. Customers on unsupported devices see the card form only. On embedded checkout, also see the embedded wallet item below.
- Only card is offered, or a Direct Debit-only link is refused: check whether shipping charges are on. When shipping is charged on a checkout that requires a delivery address, checkout offers card only. See Shipping charges.
- A wallet closes or fails: retain the order context and offer another eligible method. Reconcile the payment state before retrying.
- An embedded wallet is unavailable: check HTTPS, registered origins, iframe payment permissions, and browser support; offer the hosted URL.
- Direct Debit says pending: show the collection date and status rather than a paid receipt. See Direct Debit from checkout.
Next: Choose a checkout integration.
Owner: david · Reviewed 6 Sep 2026