Apple Pay allows customers to make secure purchases using a credit or debit card associated with a supported Apple mobile device. Businesses can accept Apple Pay on newer versions of iOS and Safari, making it quick and easy for customers to buy on both mobile and the web.

Behind the scenes, Apple uses a tokenization service and encrypts the customer's card number, assigning it a device-specific identifier called a DPAN. Braintree and the processing banks then use this DPAN in place of the real card number in order to securely handle transactions.


Where your business is domiciled dictates your ability to accept Apple Pay. Most merchants located in the following regions – contingent on their processing settings – can accept Apple Pay transactions from eligible customers with the indicated card types:

  • APAC - Visa, Mastercard, American Express*
  • Australia - Visa, Mastercard, American Express*
  • Canada - American Express*
  • Europe - Visa, Mastercard, American Express*
  • New Zealand - Visa, Mastercard, American Express*
  • United States - Visa, Mastercard, American Express, Discover

*To be eligible to accept Apple Pay with American Express in this region, you must be processing with your own Amex account.

If you are unsure of your setup, contact our Accounts team for assistance.

Discover on Apple Pay

Merchants domiciled in the United States who have integrated with Apple Pay can accept Discover cards from their customers without any additional integration work. If you are using split shipments or recurring billing on Apple Pay, you'll need to contact Discover to set up the proper permissions in order to avoid declines.

Customer compatibility

Device requirements

To pay with Apple Pay, customers must have devices with the following specifications.

For in-app purchases:

  • iOS 8+
  • Touch ID

For mobile web purchases:

  • iOS 10+
  • Touch ID

For desktop web purchases:

  • An iPhone or Apple Watch that can authorize the payment
  • macOS Sierra 10.12+
  • Safari

Location requirements

At this time, our merchants can accept Apple Pay from customers in the following countries:

  • Australia
  • Canada
  • Denmark
  • Finland
  • France
  • Hong Kong
  • Ireland
  • Italy
  • Japan*
  • New Zealand
  • Poland
  • Russia*
  • Singapore
  • Spain
  • Sweden
  • Switzerland
  • United Kingdom
  • United States

*While customers in these locations will be able to make purchases using Apple Pay, merchants domiciled in these locations either can't accept Apple Pay via Braintree, or are not eligible to onboard with Braintree.


Apple Pay transactions process and settle just like credit card transactions, but have their own unique payment type logo in the Control Panel so they can be easily identified.


There are no additional fees for processing Apple Pay transactions—pricing for Apple Pay is the same as your other credit card transactions.


Chargebacks, retrievals, and prearbs on Apple Pay transactions behave in the same way as your credit card disputes, and should be responded to according to your merchant account setup. If you’re unsure how to handle a dispute, contact our Disputes team.

Fraud tools

Apple uses a tokenization system to encrypt card information and reduce the risk of fraud. As a result, our Basic Fraud Tools are not compatible with Apple Pay. We do still recommend collecting and passing billing address information, at miniumum billing postal code, and passing that billing postal code with all Apple Pay transactions as a best practice.

Recurring billing and vaulting

Apple Pay cards can be vaulted and used for recurring billing or split shipment transactions. If you plan to use Apple Discover cards for these purposes, you must first contact Discover directly to obtain the proper permissions.


Before getting started, you'll need to work with us and Apple to configure your Apple Pay certificates and Merchant IDs. Then you can complete your client (iOS and/or JavaScript v3) and server integrations. Full instructions are available in our developer docs.

Certificate renewal

Apple Pay certificates expire after 25 months. To avoid any disruptions in processing, your developer will need to generate a new certificate, and upload it to the Control Panel before your current one expires. For full instructions on certificate renewal, see our developer docs.

Still have questions?

If you can’t find an answer, contact our Support team

← Back to Previous Page