Overview

This article guides you through enabling Apple Pay on your Authorize.net account. It explains how Apple Pay works with Authorize.net, the requirements you must meet, supported processors, and the step-by-step process for enrollment and how it appears in the classic Merchant Interface. This article applies to merchants processing on a supported Authorize.net processor connection who wish to accept Apple Pay in a mobile application or on the web.

Understanding Apple Pay

Apple Pay uses payment network tokenization. If your processor does not support payment network tokenization, or if Authorize.net does not support your payment processor's tokenization interface, you cannot sign up for Apple Pay through Authorize.net.

The Authorize.net Accept Mobile Software Development Kits (SDKs) for Apple Pay enable mobile developers to integrate payment card functionality into their mobile applications without passing sensitive card data back to their application servers. For example, you can accept payment card data directly, or use the Apple Pay services on your customer's phone.

How Apple Pay Transactions Work

When a customer checks out in your app or on the web, Apple Pay tokenizes the customer's credit card information. This token is then used for the transaction, eliminating the need for the customer to enter their credit card information. Apple Pay passes the tokenized card information to Authorize.net.

Requirements for Apple Pay with Authorize.net

• Your Authorize.net account must be on a supported processor.
• You must generate your Authorize.net Application Programming Interface (API) Login Identifier (ID) and Transaction Key.
• You must have your Apple Merchant Identifier (ID).
• You must enable the service in the Merchant Interface.
• You must generate a Certificate Signing Request (CSR) file to upload to Apple.
• You must submit the generated CSR file to Apple.

Supported Processor Connections for Apple Pay

Authorize.net supports Apple Pay on the following processors:

• Chase Paymentech
• Global Payments
• TSYS
• FDC Nashville
• NAB EPX
• Worldpay (Vantiv Core)

Finding Your Processor on Authorize.net

1. Sign in to the Merchant Interface.
2. Select Account from the main toolbar.
3. Choose Merchant Profile from the menu on the left.
4. Locate the Processor name listed under the Payment Methods section.

Cost of Using Apple Pay

Authorize.net does not charge any separate or additional fee for using Apple Pay. Please check your Apple Pay account for any fees that Apple may charge.

Viewing Fees on Your Authorize.net Account

1. Sign in to the Merchant Interface.
2. Select Account from the main toolbar.
3. Click Merchant Profile in the main left side menu.
4. Click Fees to the right of Payment Gateway in the Payment Methods section.

Obtaining an Apple Merchant Identifier

A Merchant Identifier (ID) uniquely identifies you to Apple Pay as a merchant who is able to accept payments. A Merchant Identifier never expires, and you can use the same one for multiple apps. Refer to Apple's "Create a Merchant Identifier" documentation for details.

Enabling Apple Pay in the Merchant Interface

Note: Only Account Owners can complete the following enrollment steps.

1. Sign in to the Merchant Interface.
2. Click Account from the main toolbar.
3. Click Digital Payment Solutions from the menu on the left.
4. Click Sign Up in the Apple Pay section.
5. Enter your Apple Merchant ID/Identifier in the Apple Merchant ID field.
6. Click the Generate Apple CSR button. This will create and download the Certificate Signing Request (CSR) file to use with your Apple account.
7. Complete the enrollment process by submitting your CSR to Apple.

You must submit a Certificate Signing Request (CSR) to Apple in order to receive a payment processing certificate. The certificate enables Authorize.net to decrypt the payment data in your Apple Pay requests.

Submitting a CSR File to Apple

Refer to Apple's documentation on setting up Apple Pay requirements for details. Use the CSR that you created in Authorize.net instead of creating a new CSR.

Common Questions

• What is Apple Pay and how does it work with Authorize.net?
  • Apple Pay uses payment network tokenization to protect your customer's card information. When a customer checks out, Apple Pay tokenizes the credit card information, and the token is used for the transaction. Apple Pay passes the tokenized card information to Authorize.net, so your customers do not need to enter their card details.
• Which processors support Apple Pay through Authorize.net?
  • Apple Pay is supported on Chase Paymentech, Global Payments, TSYS, FDC Nashville, NAB EPX, and Worldpay (Vantiv Core).
• What if my processor is not listed as supported?
  • If your processor does not support payment network tokenization, or if Authorize.net does not support your processor's tokenization interface, you cannot sign up for Apple Pay through Authorize.net.
• Does Authorize.net charge a fee for using Apple Pay?
  • No. Authorize.net does not charge any separate or additional fee for using Apple Pay. Any fees would come from Apple directly, so please check your Apple Pay account for details.
• How can I view fees on my Authorize.net account?
  • Sign in to the Merchant Interface, select Account, click Merchant Profile, and then click Fees to the right of Payment Gateway in the Payment Methods section.
• What is an Apple Merchant Identifier and how do I get one?
  • A Merchant Identifier uniquely identifies you to Apple Pay as a merchant who can accept payments. It never expires and can be used for multiple apps. You can create one by following Apple's "Create a Merchant Identifier" documentation.
• What is a Certificate Signing Request (CSR) and why do I need to submit one to Apple?
  • A CSR is a file you submit to Apple in order to receive a payment processing certificate. The certificate enables Authorize.net to decrypt the payment data contained in your Apple Pay requests.
• Who can enroll my Authorize.net account in Apple Pay?
  • Only Account Owners can complete the Apple Pay enrollment steps in the Merchant Interface.
• Should I generate a new CSR through Apple?
  • No. Use the CSR generated within Authorize.net when submitting to Apple. Do not create a new CSR through Apple.
• Where can developers find integration information for Apple Pay?
  • Additional details are available in the Authorize.net Developer Documentation and Application Programming Interface (API) Reference Guide. See the Additional Resources section below.

Glossary

• API: Application Programming Interface
• CSR: Certificate Signing Request
• ID: Identifier
• SDK: Software Development Kit

Additional Resources

• Authorize.net Developer Documentation
• Authorize.net API Reference Guide
• Apple: Create a Merchant Identifier
• Apple: Setting Up Apple Pay Requirements