The Authorize.net Accept Mobile SDKs for Apple Pay and Google Pay enable mobile developers to integrate payment card payment 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 or Google Pay services on your customer's phone.
For information about in-person payments using a mobile point-of-sale application, see the In-Person SDK.
Use a public client key to secure payment data sent to Authorize.net.
Use the Accept Mobile SDK to dispatch the payment data and receive a secure payment nonce (one-time-use token). For sample code, see our GitHub page for either iOS or Android.
The secure payment nonce can be used anywhere in the Authorize.net API in place of payment card data. See our API Reference for an example of a payment transaction.
You must create an Apple merchant ID before you can generate the Certificate Signing Request (CSR) that Apple Pay requires. See Apple's documentation on setting up Apple Pay requirements for details.
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.
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.
See 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.
To process an Apple Pay transaction, use the createTransactionRequest
API call with the opaqueData
field instead of payment information such as a payment card, bank account, or customer profile. For more information on submitting the payment request, see the Apple Pay section of the API Reference Guide.
marketType=0
in the createTransactonRequest
API call. If you do not submit the marketType
field, the payment gateway will use its default transaction type setting.transactionType
to authCaptureTransaction
or authOnlyTransaction
.You can identify Apple Pay transactions in the Transaction Detail view of the Authorize.net Merchant Interface.
The Transaction Details lightbox appears. Apple Pay information appears in the Tokenization Information section.
The Google Pay API enables merchants to accept payments from Google Pay users without entering payment information manually.
Google Pay supports transactions paid through American Express, Discover, JCB, Mastercard, and Visa payment cards. For authorizations, Google Pay also supports the following authorization methods:
PAN_ONLY
for receiving personal account numbers (PAN) from Google PayCRYPTOGRAM_3DS
for receiving network tokens and cryptograms from Google PayMerchants using Google Pay can pass billing information with their transactions for AVS checks. Contact your Merchant Service Provider to confirm the minimum billing address requirements that they set.
The integration steps for the Google Pay SDK are based on the steps listed in the Google Pay integration tutorial. The details below explain how to use your Authorize.net account to request and use Google Pay payment network tokens.
Google Pay uses the Authorize.net account's payment gateway ID to identify the merchant. See What is My Payment Gateway ID? for instructions on finding the payment gateway ID.
In the Google Pay integration tutorial, Step 2 explains how to set the payment tokenization method. For the parameters
object, set the gateway
field to authorizenet
, and set the gatewayMerchantId
field to your Authorize.net account's payment gateway ID.
See below for an example of how the fields would appear in the JavaScript code.
After obtaining a payment network token from Google Pay, encode the token's blob using Base64:
Submit a createTransactionRequest
API call. Set the dataDescriptor
field to COMMON.GOOGLE.INAPP.PAYMENT
, and set the dataValue
field to the Base64-encoded blob.
See the Google Pay section of the API Reference for a sample API request.
The integration steps for the Google Pay SDK are based on the steps listed in the Google Pay integration tutorial. The details below explain how to use your Authorize.net account to request and use Google Pay payment network tokens.
Google Pay uses the Authorize.net account's payment gateway ID to identify the merchant. See What is My Payment Gateway ID? for instructions on finding the payment gateway ID.
In the Google Pay integration tutorial, Step 2 explains how to set the payment tokenization method. For the parameters
object, set the gateway
field to authorizenet
, and set the gatewayMerchantId
field to your Authorize.net account's payment gateway ID.
See below for an example of how the fields would appear in the JavaScript code.
After obtaining a payment network token from Google Pay, encode the token's blob using Base64:
Submit a createTransactionRequest
API call. Set the dataDescriptor
field to COMMON.GOOGLE.INAPP.PAYMENT
, and set the dataValue
field to the Base64-encoded blob.
See the Google Pay section of the API Reference for a sample API request.