Apple Pay on Payment Pages

Apple Pay allows cardholders to securely use the payment methods stored in their Apple Wallet to perform online transactions.

When a customer uses Safari on a supported Mac, iPhone, or iPad and selects Apple Pay on your Hosted Checkout (HCO) Payment Page, they will be presented with Apple's native payment sheet. From there, they can authorize the payment instantly using Face ID, Touch ID, or their device passcode.

🚧
Processor Limitation
Apple Pay is currently only available for merchants using Chase Paymentech as their payment processor.

1. Enabling Apple Pay in the RPM

By default, Apple Pay is disabled on your Hosted Checkout Payment Pages. An RPM user with the Merchant Admin role must enable it manually.

Log in to the Realtime Payment Manager (RPM).
Navigate to your Payment Page Settings.
Under the Payment Types section, locate the Apple Pay settings.
You must review and accept the “Apple Pay Platform Web Merchant Terms and Conditions”.
Check the box to enable Apple Pay and save your changes.

Note: When previewing your Payment Page from the RPM settings, the Apple Pay button will only be visible if you are actively using the Safari browser.

2. Cardholder Requirements for Apple Pay

For the Apple Pay option to appear on the Hosted Checkout page for a customer, their setup must meet Apple's strict environmental requirements. If the Apple Pay button is hidden during checkout, one or more of the following conditions are not being met:

Device: The customer is using a supported Apple device (Mac, iPhone, iPad, or Apple Watch).
Browser: The customer is browsing your payment page using a compatible version of Safari.
OS: A supported version of iOS, macOS, or watchOS is installed.
Apple ID: The customer is signed into iCloud with a valid Apple ID.
Wallet: A credit card from a supported issuer is added to their Apple Wallet. (If no card is present, Apple will prompt the user to add one).

If all conditions are met, the customer will be able to select the Apple Pay radio button and launch the Apple Pay authorization sheet directly over the HCO page.

3. Transaction Details & DPAN Tokens

When a transaction is processed via Apple Pay, Apple does not send the customer's actual credit card number to the gateway. Instead, it sends a tokenized 16-digit number called a Device Primary Account Number (DPAN).

Because of this tokenization:

The last 4 digits displayed on the receipt and in your RPM transaction list will correspond to the DPAN, not the physical credit card.
Because the DPAN is device-specific, the exact same physical credit card will generate a completely different DPAN if the customer uses a different Apple device to check out.

Viewing Wallet Info in the RPM

You can easily identify Apple Pay transactions within your RPM dashboard.

Open the Transaction Details for a specific payment.
Look for the Alternative Payment Method row.
The Wallet Provider field will indicate that a digital wallet was used, and it will list the specific APM name and ID.

4. Testing Apple Pay in the Demo Environment

The E-xact Demo environment is fully connected to the Apple Pay Sandbox, allowing you to safely test your Apple Pay integration without processing real money.

To test Apple Pay, you will need:

An Apple device that supports Apple Pay.
A valid iTunes Connect account managed under an Apple Developer Account. (You do not personally need to own the Developer account, as long as someone in your organization grants you access).

To provision test cards and prepare your sandbox environment, please refer directly to Apple's official documentation: Apple Pay Sandbox Testing Guide