Apple Pay: Global's digital wallet
Tokenised card-on-file wallet baked into every iPhone, iPad, Mac and Apple Watch.
How the Apple Pay flow works
Apple Pay is a device-based wallet that stores tokenised versions of the consumer's existing debit and credit cards. It does not create new payment credentials — it replays the underlying card through the same networks (Visa, Mastercard, Amex, domestic schemes), but with a device account number and per-transaction cryptogram.
Online (Apple Pay on the Web) the shopper taps an Apple Pay button, reviews the amount and shipping in the native sheet, and authorises with Face ID, Touch ID or device passcode. In-app SDKs behave the same way.
In-person, the device generates a contactless NFC transaction against a standard EMV contactless terminal. Consumers see far higher approval rates than raw card entry because Apple Pay is treated by issuers as strong customer authentication.
Merchants receive the transaction as a standard card auth — same acquirer, same interchange band, same settlement — but with tokenised PAN and cryptographic proof of device presence.
Typical use cases
- Any consumer checkout where Apple share is meaningful, especially high-friction mobile flows.
- One-tap checkout for guest and repeat buyers — huge conversion lift over manual card entry.
- In-person contactless at retail, transit and F&B.
- Subscription and in-app purchase flows on iOS where the native sheet reduces abandonment.
Consumer reach
Every consumer on a supported Apple device with a compatible issuer card — over a billion devices globally.
Adoption is deepest in the US, UK, Canada, Australia and Western Europe.
Wallet share continues to grow as issuers push provisioning during card issuance.
Who should accept Apple Pay
- Any merchant with a mobile-heavy shopper base, particularly on iOS.
- Merchants suffering high card-entry abandonment; Apple Pay materially improves guest-checkout conversion.
- Physical retail, transit and hospitality where contactless is the expected UX.
Operational detail
The operational half of every method profile — settlement, refunds, disputes, PSP coverage and licensing — is reserved for Payment Methods List founding partners. It's the part vendor sites won't publish and the part that actually decides whether Apple Pay works for your stack.
Settlement time
When Apple Pay balances actually clear from the wallet operator to a merchant account, how top-up float and P2P legs distort the timeline, cut-offs on the operator side, and which PSPs pass funds through same-day vs. hold a reserve.
Book a founding-partner call →Refund mechanics
How Apple Pay refunds flow back to the payer's wallet balance vs. their funding source, partial-refund support, time windows before a refund becomes an off-platform transfer, and the exact PSP API calls used when the wallet has no native reversal.
Book a founding-partner call →Chargeback exposure
Whether Apple Pay supports scheme-style chargebacks, the operator-run dispute program that sits alongside, actionable reason codes, evidence formats accepted, and observed net loss rates versus cards on the same basket.
Book a founding-partner call →PSP coverage matrix
Which acquirers, MoRs and wallet-aggregators actually process Apple Pay in Global today, whether coverage is direct or piggy-backed on a scheme rail, effective pricing bands, and where the operator has restricted new merchant onboarding.
Book a founding-partner call →KYC & licensing notes
What a merchant needs to legally accept Apple Pay in Global, whether the wallet operator or the PSP is the regulated entity, KYC and AML obligations that flow down to the merchant, and cross-border MoR options.
Book a founding-partner call →