Apple Pay
Learn more about Apple Pay and its payment workflow.
Apple Pay is a mobile wallet solution available to all users of Apple devices.
| Payment type | Available in | Supported currencies | Features | Integrations | API endpoint | API prefix |
|---|---|---|---|---|---|---|
| Wallet | All countries | AUD, CHF, CZK, DKK, EUR, GBP, NOK, PLN, SEK, USD, HUF, RON, BGN, HRK, ISK |  Authorize Direct Charge Reversal Refund Partial Refund Chargeback Recurring
Payout
Pay later
Unzer Secured B2C customer B2B customer | Payment Pages UI Components Direct API PHP SDK Java SDK Plugins | /types/ApplePay | apl |
Advantages
- Payment security: All Apple Pay transactions use two-factor authentication (2FA) from your customer’s Apple device. The use of Touch ID or Face ID gives a payment experience that is both secure and convenient.
- Exempt from 3DS step up flows: The native use of 2FA with every Apple Pay transaction means that your customer will never be required to leave your page to authorize the payment in their banking app or webpage.
- Multiple Payment Options: Your customers can pay with any card they have stored in their Apple Pay wallet. This includes all major credit card brands.
Assets
UnzerOne integration
You can now integrate Apple Pay easily without the need to add the various merchant certificates and keys. This is now handled by Unzer.
| Integration type | Integration for Apple Pay (updated procedure with Unzer Apple Pay certification) |
|---|---|
| UI Components |  |
| Payment Pages | |
| Direct Integration | |
| Plugins | |
Payment workflow
The following diagram explains the workflow for Apple Pay payments in the Safari browser.
Step 1: Create a ApplePay payment type resource using the encrypted Apple Pay Payment Token you receive from Apple.
A resource ID is generated in the response and is used in the workflow to complete the payment.
Step 2:
(Option 1): Make a charge transaction with the ApplePay resource that you created.
(Option 2): Make an authorize transaction with the ApplePay resource you created.
Step 3:
(Option 1): Forward the customer to the redirectUrl that is displayed in the charge response.
(Option 2): Forward the customer to the redirectUrl that is displayed in the authorize response.
Step 4:
(Option 1): Once the customer makes the payment at Apple Pay, redirect the customer to the returnURL specified in the initial charge call. The merchant needs to query the result and show it to the customer by redirecting him to the final shop result page.
(Option 2): Once the customer authorizes the payment at Apple Pay, redirect the customer to the returnURLspecified in the initial authorize call. The merchant need to query the result and show it to the customer by redirecting him to the final shop result page.
Step 5: After the transaction, display the result to the customer in the front end of the online shop.
Step 6: (Option 2 only) When you are ready to capture the authorized payment, create a charge using the paymentId from the authorize response.
Integration options
Use pre-built forms and quickly integrate with minimum work on the client side
Start integrating
Use pre-built, configurable all-in-one pages with your own mix of payment methods
Start integrating