Configuring Apple Pay on Payment Pages

Overview

This article takes you through the setup process of Apple Pay on a Hosted Checkout Payment Page.

Apple Pay allows cardholders to use the payment method stored in their Apple wallet to perform online payments.

If cardholders are using Safari on their Mac, iPhone, or iPad and they select the Apple Pay button on the HCO Payment Page, they will see Apple’s payment sheet where they can authorize the payment using their fingerprint, or device password.

Before using this feature, please review Apple’s Web Merchant Terms and Conditions.

Apple Pay Data Flow for HCO

1.png

Enabling Apple Pay on a Payment Page

An RPM user with the Merchant Admin role has the option to enable Apple Pay in the Payment Types section of the Payment Page Settings. By default, the feature is disabled. The “Apple Pay Platform Web Merchant Terms and Conditions” must be reviewed and accepted for the feature to be enabled.

 

The following screenshot from the Payment Page Settings shows the check marks that a Merchant Admin has to accept in order to use Apple Pay:

2.png

 

Please note that when Apple Pay is enabled on the Payment Page Settings, the Apple Pay button will be visible on a preview only if the RPM user is using the Safari browser).

Testing using Payeezy Gateway Demo environment

The Exact Demo environment is connected to Apple Pay Sandbox and can be used to test the Apple Pay feature.

The tester must have the following setup:

Please refer to Apple Pay Sandbox documentation on how to prepare for testing and add Test cards:
​​https://developer.apple.com/apple-pay/sandbox-testing/

Setup and requirements to be met by the cardholder 

Once Apple Pay is set up a cardholder can perform an Apple Pay transaction with the Apple Pay button on HCO only if all of the following conditions are met:

  • A supported Apple device is used (Supported devices).
  • A valid Apple ID is used to sign in to the Apple device (Signing in to iCloud).
  • An Apple Pay compatible version of the Safari browser is used by the cardholder and it is compatible with the merchant’s website.
  • A supported version of an Apple Operating System is correctly installed in the Apple device (iOS, watchOS, macOS).
  • A credit card from a supported card issuer is successfully added to the Apple Wallet and can be used for the transaction (supported card issuers). In case there is no card added to the Apple Wallet, the customer is then given the option to add a new card.

To learn more about the cardholder Apple Pay setup process, please refer to:

Cardholder payment processing flow via an HCO Payment Page

If Apple Pay is correctly configured for the HCO Payment Page by the merchant and if the cardholder meets the technical requirements listed above, they will be able to select the Apple Pay radio button. If the Apple Pay button is not visible, that means one, or several, technical requirements are not being met by the cardholder.

3.png

After the Apple Pay radio button is selected, a new Apple Pay button will appear on the HCO Payment Page:

4.png

 

When the cardholder clicks on the Apple Pay button, they will be presented with the Apple Pay sheet, which appears on top of the Payment Page. From this screen it is possible for the cardholder to select or add a credit card and billing address.5.png

 

If the transaction is canceled, the cardholder will return to the HCO payment page. If the cardholder authorizes the transaction, it will be processed and the rest of the screen/receipt flow will be the same as it is for regular credit card transactions (i.e., it will be defined by the merchant integration options on the HCO Payment Page Settings; for more information, please refer to the Hosted Checkout Payment Pages Integration Manual).

Real Time Payment Manager (RPM) Transaction Details

In the RPM transaction details, the “Wallet Provider” field can be used to determine if the transaction was processed using a digital wallet.

In the RPM Transaction details, a new row of information has been added to describe the Alternative Payment Method used in the transaction, including the name of the APM and its ID (shown below).

6.png

Notes on Apple Pay

Apple Wallet uses a tokenized version of the cardholder’s credit card to perform payments. This token is a 16-digit number called the “DPAN” (Device Primary Account Number). One consequence of this is that the last four digits of the DPAN used in an Apple Pay transaction in the RPM transaction list do not correspond to the actual last four digits of the cardholder’s credit card. Since the DPAN is related to the device, the same credit card will generate a different DPAN in each Apple device.

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk