Apple Pay

Overview

Apple Pay is a Wallet payment method, enabling users to make secure payments, authenticate and approve payments via their Apple Pay payment app.

It is a card payment using the token services provided by the card scheme. The transactions are authenticated with Touch ID or Face ID and uses the 3DS.

Supported card schemes:

• Visa
• Mastercard
• Dankort
• Maestro
• American Express

Functionalities

Pre-auth Apple Pay

Apple Pay supports Netaxept’s pre-auth functionality as described on this page. Please note that for Apple Pay the pre-authorization needs to be initialized using the Process API call. For details, see "Step 1: Initiating a pre-authorization payment" -> "2. Process Call" in this section.

Activation

You are responsible for activating this payment method in Netaxept Admin and ensuring that all information is entered correctly.

1. Go to Netaxept Admin -> Options -> Agreement -> Choose Apple Pay.
2. Add a Merchant ID and domain (this is not sent to Apple and is just for reference).
3. Click “Generate CSR” button and agreement is added – Merchant specific certificate will be generated.
4. Click “Edit” on Apple Pay agreement and copy the CSR.
5. Go to your Apple Dev account and create the certificate with the CSR. Note the expiration date for the certificate to ensure you create a new one before it expires.
6. Copy the payment processing certificate.
7. Go back to Netaxept Admin and click edit the agreement.
8. Upload your certificate from Apple Pay in PEM File section and click “Save”.

Sharing Apple Pay agreement with your partners

To avoid the process of adding an agreement for each sub-merchant separately, you can automatically distribute your Apple Pay agreement to your selected sub-merchants by following below steps:

1. Click "Share" next to your Apple Pay agreement on the partner you have added the Apple Pay agreement.
2. Enter merchantID from which the agreement should be copied.
3. Upload a Comma Separated Value (CSV) file with merchantId and currencyCode (NNNNNN, CCC) to which the agreement should be distributed to.

Payment flow

Apple Pay is available in both test and production environments.

Test: https://test.epayment.nets.eu Production: https://epayment.nets.eu

High level sequence diagram

Register call

1. The paymentMethodActionList-parameter should specify Apple Pay
2. The parameter PaymentData should be added and contain the encrypted Payment Data from Apple Pay in Json: {"paymentData”: {"version":"EC_v1","data":"4………….}

https://epayment.nets.eu/Netaxept/Register.aspx?
merchantId=xxxxxx
&token=xxxxxx
&orderNumber=123456

Terminal call

Terminal call is skipped as payment data is already collected in the Register call.

Process call

Works as regular card payments, see Netaxept API.

Query Call

Query call works as on the normal case. Below is an example query response with ApplePay info within the Wallet tag.

<PaymentInfo xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<MerchantId>MerchantId</MerchantId>
<QueryFinished>2017-10-25T07:00:56.0454551+02:00</QueryFinished>
<TransactionId>TransactionId</TransactionId>

Subscription-based payments

Subscription-based payments Netaxept supports Recurring and Unscheduled Credential-on-File (UCOF) payments for Apple Pay. You can process subscriptions, memberships, and other recurring transactions seamlessly following the same flow as you do for standard card payments.

Recurring payments

Initial payment

You need to add the following parameters in the Register request for the first transaction:

• recurringType must be set to S.

After successful authorization, you must use the Query request on the specific transaction to retrieve the token from the panHash parameter, which will be returned in the response. You must store and use this payment token reference for all subsequent transactions in this payment flow.

Subsequent payments

Please make sure that all subsequent Register requests include the following data:

• panHash must be filled with the payment token generated in the initial transaction.
• serviceType must be set to A.
• recurringType must be set to M.
• recurringTransactionType must be set to 1.

For more details on how to use the API parameters above, refer to the API reference.

Unscheduled Credential-on-File (UCOF) payments

Initial payment

You need to add the following parameters in the Register request for the first transaction:

• recurringType must be set to S.

After successful authorization, you must use the Query request on the specific transaction to retrieve the token from the panHash parameter, which will be returned in the response. You must store and use this payment token reference for all subsequent transactions in this payment flow.

Subsequent payments

Please make sure that all subsequent Register requests include the following data:

• panHash must be filled with the payment token generated in the initial transaction.
• serviceType must be set to A.
• recurringType must be set to M.
• recurringTransactionType must be set to 1.

For more details on how to use the API parameters above, refer to the API reference.