Apple Pay is a button, not a project.
On a supported device, Apple Pay renders as a one-tap sheet on the same checkout as everything else. The customer authenticates with Face ID or Touch ID, the payment runs on a device token rather than the real card number, and your side sees the same order and the same receipt as a typed card.
Four steps, most of them invisible.
- [ 01 ]
DETECT
The checkout shows the Apple Pay button only on devices that can actually pay with it.
- [ 02 ]
TAP
The sheet opens with the amount and the merchant name; the customer picks a card.
- [ 03 ]
AUTHENTICATE
Face ID or Touch ID confirms — this is the strong authentication step, so no separate 3-DS challenge.
- [ 04 ]
SETTLE
The payment runs on a device token and settles to EUR in the same batch as your card takings.
What the customer sees
A black Apple Pay button at the top of the method list, on the same page as the card form. Tapping it opens the native sheet with the amount, the merchant name, and their stored cards. There is no form to fill, no address to type, and no redirect to a second page — which is precisely why it converts on mobile.
- [ 01 ]Shown only where it can be used — never a dead button
- [ 02 ]The native sheet, with the amount and your merchant name
- [ 03 ]No typing, no redirect, no separate authentication step
What you receive
The same thing a typed card produces: euros in the day's payout, one order reference, one receipt. The difference is on the customer's side, not yours — you don't handle a different settlement path, a different refund flow, or a different reconciliation model because someone paid with a wallet.
- [ 01 ]Identical order, receipt, and payout to a typed card
- [ 02 ]Refunds handled against the order, back through the same wallet
- [ 03 ]Nothing extra to reconcile — the method is a field on the record
What it takes to switch on
A toggle on the methods screen. Domain verification for the checkout domain is handled as part of enabling it, and the button then appears automatically for every customer whose device supports it. There is no SDK to install and nothing to maintain when Apple changes the sheet.
Apple Pay — questions merchants ask.
No. Enabling Apple Pay on the methods screen covers the domain verification and the certificate handling. The button appears on supported devices from that point on.
No separate challenge. The device's own authentication — Face ID, Touch ID, or the passcode — is the strong customer authentication step, which is a large part of why wallet payments convert better than typed cards.
The button isn't shown. The checkout presents the methods that customer can actually use, so a Windows desktop sees cards, USDC, and transfer without a dead Apple Pay button taking up the top of the list.
Yes, exactly like a card refund — full or partial, issued against the order with a required reason. The funds travel back over the same route to the card behind the wallet.
Often switched on together.
Google Pay
One-tap · Device tokenThe same one-tap treatment as Apple Pay, on Android and Chrome, through the same order and receipt.
[ 02 ]Card payments
Visa · MastercardThe default rail, with 3-D Secure 2.0 and strong customer authentication handled inside the flow.
[ 03 ]Saved cards
Vault · One-clickReturning customers pay in a tap; the card lives in our vault and yours stores a reference.
Take a payment on every one of them.
A sandbox merchant, API keys, and a checkout with all of these switched on — so you can run each method end to end before you commit to anything.
Request sandbox access