Apple Pay
Offer Apple Pay to your merchants: what you set up, how it runs over the card processor, and how to test it.
Apple Pay runs over the card processor of the project: an Apple Pay payment is a card payment with a device token instead of a card number. You don't need a separate processor contract. The merchant's customers pay on the hosted payment page, or in the merchant's own checkout.
How it works
- The customer chooses Apple Pay and approves the payment on their device.
- Apple returns an encrypted payment token to Ginger. Ginger decrypts it and sends the payment to the card processor of the project, with the device account number and the cryptogram.
- The processor authorises the payment like a card payment. A cryptogram replaces 3-D Secure.
Apple Pay works with every card processor: Silverflow, Elavon, Rapyd, Shift4 and IPG. Through Silverflow, the payment method details include the Payment Account Reference (PAR).
Set it up
Allow the payment method
Give the merchant and the project permission for Apple Pay, as for any payment method. See Merchant hierarchy.
Check the card contract
The project needs a working card contract, with the card brands the merchant accepts. One-click and recurring Apple Pay payments follow the merchant's card settings. See Processor contracts.
Add the apple-pay contract, for host-to-host only
When a merchant runs Apple Pay in its own app or checkout and sends the payment data to Ginger (host to host), add the
apple-pay contract with additional_: the extra domain for its Apple Pay data. For Apple Pay on the hosted
payment page, you don't need this contract. See the apple-pay fields of
Update a project contract in the API reference.
Test
Apple Pay works in test mode: a project in active-testing sends its Apple Pay payments to the test environment of
the processor. Ask your Ginger contact which Apple Pay cards and devices to test with.
For your merchants
The integration is in the payment acceptance docs: Apple Pay in your own checkout and Apple Pay recurring payments.