Skip to main content

Digital wallets

Digital wallets let customers pay with credentials stored in a wallet account or on a supported device. Customers authenticate through the wallet instead of entering payment details directly in checkout, which can reduce friction and provide an additional layer of payment security.

Wallet availability and behavior depend on the customer device, browser, country, currency, selected checkout version, and your Cleverbridge account configuration. Review the individual wallet guide for setup requirements, supported transaction types, subscription behavior, and refund handling.

Do all digital wallets use the same flow?​

No. The wallets share a high-level payment lifecycle, but the customer interaction and the point at which the order is finalized differ by method.

WalletDocumented interactionImportant difference
Apple PayAn Apple Pay sheet opens over the checkout.The customer selects a card and authorizes through the Apple Pay experience without a full-page redirect.
Google PayA Google Pay sheet opens from the express checkout area.Additional cardholder authentication can be requested for an eligible transaction.
AlipayThe customer leaves the Cleverbridge checkout to authorize in Alipay and then returns.This is a redirect-and-return flow rather than an embedded payment sheet.
PayPal StandardThe customer is redirected to PayPal to choose a funding source and authorize the payment.The documented subscription flow uses a customer-approved PayPal Billing Agreement.
PayPal ExpressThe customer authorizes with PayPal, returns with a token, and then completes the order on Cleverbridge.Wallet authorization occurs before the final Cleverbridge order-submission step.
Amazon PayLegacy reference only.Cleverbridge no longer offers Amazon Pay for new purchases.

Shared payment lifecycle​

At a high level, an active digital-wallet payment follows these stages:

Digital wallet payment lifecycle
  1. Cleverbridge displays the wallet when it is configured and the checkout context is eligible.
  2. The customer selects the wallet.
  3. The wallet opens as an in-page sheet or through a redirect.
  4. The customer selects an available funding source and completes any authentication requested by the wallet or card issuer.
  5. Cleverbridge receives the payment result and continues or completes the order.
  6. After a successful payment, Cleverbridge confirms the order and sends the applicable customer communication and delivery information.

The method article is authoritative for the ordering of these stages. Do not treat the shared lifecycle as a single exact flow for every wallet.

Wallet authentication confirms the customer's intent to use the selected wallet or funding source. The underlying card issuer or payment service can still decline the payment, so a completed biometric, passcode, or login step does not by itself mean that the Cleverbridge order is paid.

   

The PaidOrderNotification format does not change based on the digital wallet used for the payment. Continue to use the standard notification fields and your configured notification processing.

Explore this section


Did you find this doc useful?