The Authorize.Net Accept Mobile SDKs allow mobile developers to provide credit card payment functionality in their mobile applications, without having to pass sensitive card data back to their application backend servers. The SDKs allow you to accept the input of credit card data directly, or tie in to Apple Pay or Android Pay to leverage your mobile operating system's secure payment framework.
For in-person payments using a mobile point-of-sale application, see the In-Person SDK.
The three payment options work similarly, using a three-step process. Only step 1 differs, depending on which in-app solution you implement.
The
opaqueData
element.
The Accept Mobile SDK for iOS or Android enables you to build your payment app without worrying about card data passing through your server. You retain complete control of the user experience.
When you send the payment data to Authorize.Net, you use a public client key to secure it.
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 credit card data. See our API Reference for an example of a payment transaction.
If you have not already done so, you must create an Authorize.Net transaction key. This key is used to create a transaction-specific signature at your server. The signature is cross-checked by Authorize.Net servers when a transaction request is received, ensuring that no transaction is initiated by the consumer without your approval.
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 obtain an Apple merchant ID before you can generate the Certificate Signing Request (CSR) that Apple requires.
You must submit a Certificate Signing Request (CSR) to Apple in order to receive a necessary payment entitlement certificate.
The Apple Merchant ID that you enter must be identical to the one that you created at the Apple site. If it is different, Authorize.Net will not be able to to decrypt the payment data.
You must submit the CSR to Apple in order to receive the required payment entitlement certificate.
To process an Apple Pay transaction, use
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 is contained in the Tokenization Information section.
Before you can use Android Pay with Authorize.Net, you must sign up for the service in the Authorize.Net Merchant Interface.
Google will send your app a unique Base64-encrypted message via the Android API. Google requires an identifier and public key in order to encrypt sensitive payment credentials. You must already have an Authorize.Net API login ID and transaction key before generating Android Pay public keys.
Before submitting an Android Pay transaction using the Authorize.Net API, follow these steps to integrate Google's Android Pay SDK. For the most part, it is the same as Google's Android Pay integration tutorial. However, there are a few differences, explained below.