Wallet checkout, one tap instead of a keyboard.
Apple Pay, Google Pay and mobile wallet acceptance through the same Flowa Pay integration you use for cards, with tokenized credentials and device authentication replacing manual card entry.
The fastest checkout is the one nobody types into
On a phone, manual card entry is where checkouts are abandoned. A wallet replaces the card form with a biometric confirmation the customer has already set up, and presents a tokenized credential rather than a raw card number. For the merchant it is the same payment object, the same webhooks and the same reconciliation as any other card transaction.
From request to reconciled
Offer
The wallet button appears only on devices and browsers where the wallet is actually available, so customers are never shown a method they cannot complete.
Authenticate
The customer confirms on their device with biometrics or a device passcode. Authentication happens in the wallet, not in your interface.
Tokenize
The wallet returns a tokenized credential rather than the underlying card number.
Authorize
The tokenized credential is routed and authorized through the same acquiring routes and the same routing rules as any other card transaction.
Report
Wallet payments appear in reporting as their own method, so you can compare wallet and manual-card approval and conversion side by side.
What digital wallets covers
Apple Pay
Wallet acceptance in supported browsers and native apps, available through supported acquiring partners and routes.
Google Pay
Wallet acceptance on supported devices and browsers, through the same integration and the same routing rules.
Mobile wallets
Additional device and market wallets where they are supported on your acquiring route. Availability is confirmed per merchant during onboarding.
Wallet-based checkout
Wallet buttons on the hosted payment page and in embedded checkout, with capability detection so they render only where they will work.
Tokenized wallet payments
Wallet credentials arrive tokenized, so your systems never receive the underlying card number.
Mobile-first conversion
No card form, no address typing, and a payment step that completes in a single confirmation.
One integration
Wallets reuse the card payment object, webhooks, refund API and reconciliation. There is no separate wallet pipeline to build or operate.
Reporting by method
Wallet volume, approval rate and conversion are reported separately from manually entered cards.
Why teams choose it
- Less friction on mobile. The payment step becomes a confirmation rather than a form.
- Tokenized by default. The credential presented is a token, not a card number.
- Nothing new to operate. Same payment object, same webhooks, same refunds, same reconciliation as cards.
- Honest availability. Buttons render only where the wallet is genuinely available on the device and the route.
How you connect
- Hosted payment page: wallet buttons rendered and handled for you.
- Embedded checkout: wallet buttons as drop-in components on your own page.
- API: request the wallet method directly and handle the device-side flow yourself.
What you can accept
- Apple Pay
- Google Pay
- Device and market mobile wallets where supported
Availability depends on merchant category, jurisdiction, underwriting and the applicable payment or acquiring partner.
How it is controlled
- Wallet credentials are tokenized by the wallet before they reach Flowa Pay.
- Customer authentication happens on the customer's own device.
- Wallet transactions follow the same encryption, access control and monitoring as all card traffic.
Flowa Pay provides the payment technology and orchestration layer. Acquiring, scheme settlement and regulated payment services are provided by licensed acquiring and payment partners under their own authorisations.
Common questions
No. Wallets run through the same Flowa Pay payment object and the same webhooks as card payments. Enabling a wallet is configuration, not a new integration.
Wallet availability depends on your acquiring route, your market and your merchant category, and is confirmed during onboarding. We do not enable a wallet that your route cannot actually process.
No. A wallet-tokenized card settles through the same acquiring route, in the same settlement cycle, and reconciles the same way.
The button is not rendered. The customer sees the other methods you have enabled, so nobody reaches a dead end.
Ready to put digital wallets to work?
Talk to our team about your corridors, your volumes and the routes that fit your business.