Apple Pay

Apple Pay is supported both on the web and in iOS apps. In both environments, Apple Pay can be integrated using the SDK and without the SDK.

​

Prerequisites

To enable Apple Pay transactions, the system is directly integrated with Apple. As a result, it transmits decoded device tokens to payment services instead of encrypted gateway tokens. Please note that not all payment services support decoded Apple Pay tokens, and they may require this feature to be activated. Contacting your payment service provider to enable this feature is recommended.

​

Web (Embed)

On the web, Apple Pay can be easily integrated both with and without Embed. In both offerings, the need to sign up for an Apple Developer account has been removed, reducing additional financial and maintenance costs.

​

Mobile (iOS)

On mobile apps, Apple Pay can be easily integrated both with and without the SDK. In both offerings, signing up for an Apple Developer account and creating an Apple merchant ID and processing certificate is required.

​

Recurring payments

Recurring payments are supported on Apple Pay in a similar way to how recurring payments are supported for regular card payments.

1. Take the first payment with the Apple Pay token and store: true, with merchant_initiated and is_subsequent_payment set to false and a payment_source such as recurring. This stores the Apple Pay payment method.
2. Charge later payments with the stored payment method id, the same payment_source, and merchant_initiated and is_subsequent_payment set to true.

A stored Apple Pay payment method has no cryptogram, because the cryptogram only exists for the original payment on the buyer’s device. Later payments rely on the recurring flags and the scheme transaction ID from the first payment instead, so payment services may decline a later payment that’s sent with the flags of a first payment.