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 Google 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.
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 Google Pay public keys.
Before submitting an Google Pay transaction using the Authorize.Net API, follow these steps to integrate Google's Google Pay SDK. For the most part, it is the same as the steps in the Google Pay integration tutorial. However, there are a few differences, explained below.