What it is
Apple Pay is a mobile wallet and contactless payment feature from Apple. Customers add credit, debit, or prepaid cards to the Wallet app and pay with Face ID, Touch ID, or a double-click. For merchants it is a payment method at checkout, not a bank, not a card network, and not a standalone merchant account.
- Mobile wallet built into Apple devices.
- Cards stored in the Wallet app.
- Authenticate with Face ID, Touch ID, or double-click.
- A checkout method, not an account or network.
Where it is mainly used
Apple Pay is available in many countries and regions, with very high adoption among US iPhone users. Any merchant can accept it as long as their payment service provider supports Apple Pay, and it works in store, in apps, and on the web in Safari and other browsers.
- Strong in the United States and many regions.
- High adoption among iPhone users.
- Works in store, in apps, and on the web.
- Availability depends on your PSP support.
How customers pay at checkout
On the web or in an app the customer taps the Apple Pay button, confirms with biometric or passcode, and the payment is authorized in one step. In store they hold the device near a contactless terminal. The merchant never receives the actual card number; Apple uses a device-specific token.
- One-tap Apple Pay button at checkout.
- Authorize with Face ID, Touch ID, or passcode.
- In store via contactless NFC terminals.
- Merchant gets a token, not the real card number.
How merchants access it (and local-entity caveat)
Merchants do not open an Apple Pay account; they enable Apple Pay through their PSP, gateway, or e-commerce platform, and register a merchant identifier in the Apple Developer account for direct integrations. Because it rides on existing cards and processors, no new local entity is needed beyond what your PSP already requires.
- Enabled via your PSP, gateway, or platform.
- Direct builds register a merchant ID in Apple Developer.
- No separate Apple Pay merchant account.
- No new local entity beyond your PSP.
PSP / aggregator route
Almost every major PSP and platform (Stripe, Adyen, Square, Shopify, Braintree, etc.) supports Apple Pay, so the normal route is to toggle it on inside your existing provider. Direct integration uses the Apple Pay APIs and a payment processing certificate, typically handled by your PSP.
- Toggle on inside your existing PSP.
- Supported by Stripe, Adyen, Square, Shopify, Braintree.
- Direct API needs a merchant ID and cert.
- Usually no extra contract with Apple.
Pricing and settlement: what to verify
Apple does not charge merchants extra fees for Apple Pay; you pay your normal card-processing rates through your PSP. Published pricing is for initial screening only; confirm the provider's official pricing page or a written quote before you go live. Confirm that your PSP supports Apple Pay in your target regions, the settlement timing, and any requirement for the Apple Pay mark and guidelines on your site.
- No extra Apple fee; normal card rates apply.
- Confirm PSP regional support.
- Check settlement timing with your processor.
- Follow Apple Pay mark and UX guidelines.
Public contact route
Apple does not offer a merchant sales email for Apple Pay; integration help is via the Apple Developer site and Apple Support. Use the official Apple Pay pages and the merchant support article; in-store terminal setup goes through your payment provider.
- Apple Pay overview: https://www.apple.com/apple-pay/
- Developer / merchants: https://developer.apple.com/apple-pay/
- Merchant support: https://support.apple.com/en-us/HT204274
- No public sales email found; use the official website contact page or LocalPayMap consultation.
Technical and pricing fields to verify
Use this structured checklist before you ask for a quote or implementation access. Unknown fields are intentionally marked as “to be confirmed” instead of being treated as unavailable.
| Pricing model | wallet acceptance or psp priced |
|---|---|
| Pricing basis | official pricing page or public terms |
| Fee range | To be confirmed |
| FX markup | to be confirmed |
| Chargeback fee | To be confirmed |
| Payout fee | To be confirmed |
| Reserve policy | To be confirmed |
| API / checkout route | api or hosted checkout |
| SDK languages | to_be_confirmed |
| Sandbox | likely supported verify in docs |
| Webhooks | likely supported verify in docs |
| Idempotency | to be confirmed |
| PCI scope | to be confirmed |
| 3-D Secure | To be confirmed |
| Recurring billing | to be confirmed |
| Marketplace split | to be confirmed |
| Partial refund | to be confirmed |
| Preauth / capture | To be confirmed |
Official links to open
Public pricing signals are for initial screening only. Actual quotes can vary by country, industry, transaction volume, settlement currency, integration route, and contract terms.
Questions merchants ask
Do I need an Apple Pay merchant account?
No. You enable Apple Pay through your existing PSP or gateway. Apple does not open merchant accounts for Apple Pay; it works on top of the cards and processors you already use.
Does Apple Pay cost extra?
Apple does not charge merchants a separate Apple Pay fee. You pay your normal card-processing rates from your PSP. Published pricing is for initial screening only; confirm the provider's official pricing page or a written quote before you go live.
Can customers pay on my website with Apple Pay?
Yes, on the web in Safari and supported browsers, and in iOS/macOS apps, using the Apple Pay button and the customer's stored cards.
Is Apple Pay available outside the US?
Yes, in many countries and regions. Your ability to accept it depends on whether your PSP supports Apple Pay in each market you sell into.
What do I need for a direct integration?
A merchant identifier and a payment processing certificate in your Apple Developer account, plus a PSP that decrypts the token. Most merchants let their PSP handle this.
Do I see the customer's card number?
No. Apple Pay sends a device-specific token and never shares the real card number with your systems, which reduces your card-data exposure.