Use case summary
Returning customers pay with a saved card, and new ones can use Apple Pay or Google Pay, either on hosted checkout or placed on your own site through host-to-host integration. Card and wallet data are handled within PCI DSS-compliant infrastructure, or decrypted on your side if your setup requires it. Result: a purchase takes one confirmation, and the flow stays under your domain.
- Payment Manager
- Developers & CTO
Why wallets are easy for customers and hard to add
On mobile, the card form is the slowest part of checkout: sixteen digits, an expiry date, a security code, and often a billing address, typed on a small screen by a customer who had already decided to buy.
Express wallets remove that step, but adding them takes work. Each wallet has its own certification, token handling, and domain verification, and some PSPs support them only through their own hosted page, which adds a redirect and limits where the button can appear.
Wallet support also affects routing. When only one PSP can process your wallet tokens, all wallet volume goes to that provider, outside the routing rules that apply to the rest of your card traffic.
How to set up one-click payments
Apple Pay and Google Pay can be switched on in hosted checkout or built into your own pages, and in both cases the payments stay inside your routing.
- 1
Switch on express methods in the checkout builder
In the checkout's Methods settings, turn on Express methods and select Apple Pay and Google Pay. The methods available come from the payment scheme connected to your merchant account.
- 2
Place the buttons on your own site if you prefer
Host-to-host Apple Pay and Google Pay put the wallet button wherever you want it on your site, styled within Apple's and Google's guidelines, with no redirect to an external payment page.
- 3
Keep wallet payments in your routing
Corefy is a certified Google Pay participating processor and runs its own Apple Pay token decrypt service. Direct integrations with both wallets give wallet traffic more independence and more routing options.
- 4
Decrypt tokens on your side if your setup requires it
For host-to-host flows, you can decrypt Apple Pay and Google Pay tokens yourself, using your own certificates and credentials.
- 5
Reach customers on other devices
Apple Pay can be shown on Android and Windows devices as a QR code the customer scans with an iPhone or iPad. The option can be switched on or off, so you can test its effect on conversion.
- 6
Remember cards for returning customers
Tokenized card credentials let returning customers pay without entering their details again, and the same card can be charged for recurring payments.
Explore 4 ways to put Apple Pay into your checkout and get a pre-launch checklist.
What you get
Customers pay in one step on the devices they use most, and wallet payments follow the same rules as the rest of your traffic.
Faster checkout on mobile
Customers confirm with Face ID, Touch ID, or their phone's lock screen and skip the card form, which removes the longest step of a mobile checkout.
Wallet buttons wherever you want them
With host-to-host integration, you can place Apple Pay and Google Pay on product pages, in the cart, or at checkout, under your own domain and with no redirect in the flow.
Control over who processes wallet volume
Direct wallet integrations let you decide which provider handles your largest mobile payment method, based on its pricing and performance.
Repeat payments without typing
Saved card credentials and wallets let a returning customer complete a repeat purchase, top-up, or subscription payment without entering card details again.
Grand Cru Concepts added Apple Pay and Google Pay without extra engineering
Grand Cru Concepts, a software publisher running high-volume consumer products across the US and Canada, launched on Corefy's hosted checkout and later added its own method selection interface. Apple Pay and Google Pay were added alongside ACH, Interac e-Transfer, and crypto, each through the same steps: connect credentials, configure routing, go live, with no additional engineering for each method. As of May 2026, the stack ran at a 79% approval rate across all active providers, with no declines attributed to downtime.