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 | Hosted checkout blocks it for recurring, trial, usage, mixed carts, and Direct Debit-first/card-fallback sessions. |
| Google Pay | Wallet option when the gateway, browser, and merchant enable it | 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 blocked in hosted checkout when any of these is true:
blocked_reason | When it applies |
|---|---|
card_fallback_only | Default method is Direct Debit and card is only a fallback. |
usage | The purchase contains a usage/metered product or line. |
trial | A product has trial_period_days greater than zero. |
mixed_cart | One-off is combined with recurring or usage on the same checkout. |
recurring | The remaining items are recurring automatic billing. |
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.
The hosted checkout V13 experience and invoice V6 experience 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 recurring/trial/usage/mixed content, the Direct Debit-first setting, provider activation, device eligibility, and origin configuration.
- 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.