This article will guide merchants through enabling your Authorize.net account for Google Pay (formerly Android Pay).

Understanding Google Pay:

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.

The Authorize.net Accept Mobile SDKs for 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 Google Pay services on your customer's phone.

Requirements for Google Pay with Authorize.net:

• Your Authorize.net account is on a supported processor.
• You must generate your Authorize.net API Login ID and Transaction Key.
• You must enable the service in the Authorize.net Merchant Interface.
• Your app must meet the Google Pay Developer requirements.
• You must generate a Google Pay public key.

How Google Pay Transactions Work:

When a customer checks out in your app or on the web, Google 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. Google Pay passes the tokenized card information to Authorize.net.

Cost of Using Google Pay:

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

To see the fees on your Authorize.net account, follow the steps below:

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

Supported Processor Connections for Google Pay on Authorize.net:

Authorize.net supports Google Pay on the following processors:

• Chase Paymentech
• FDC Nashville
• Global Payments
• NAB EPX
• TSYS
• Vantiv

To find 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. Under the Payment Methods section, the Processor name will be listed.

Enabling Google Pay in the Merchant Interface:

Account Owners can follow these 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 Google Pay section.
5. Enter your KeySet ID from Google.
6. Click Generate Public Key.
7. Then click Download next to the Key generated.

Developer and Integration Resources:

More information can be found in the Developer Documentation and API Reference Guide:

• Developer Documentation
• API Reference Guide

Google Pay FAQs

Why should merchants use Google Pay?

• Google Pay doesn’t send the actual credit or debit card number with the payment. Instead, it uses a virtual account number to represent the account information, keeping card details safe.
• Provides a fast, secure checkout experience for Android device holders, eliminating the need to enter credit card information during checkout.
• Opens your business to millions of Android users who already have an Android device with a credit card on file for payments.
• Existing merchants get unified reporting from all their transactions—online, mobile, in-app, and more—all in one place.

Merchant already uses in-app payments with Android device. Is this solution relevant to them?

• Yes. Google Pay offers frictionless payments as customers do not have to enter their payment/card information and simply use their Android device.
• Yes, using tokenization with Google Pay enhances security and helps reduce overall fraud risk.
• Yes, if you want all of your transactions—online, in-app, etc.—in one place. Using Authorize.net and Google Pay provides unified reporting.

Will enabled or disabled Card Types impact Google Pay?

Yes, just like with any other submission type, there is a check against the card type the merchant has enabled on their Authorize.net account. If a card type like American Express is not enabled, we would respond back with RRC 17 - The merchant does not accept this type of credit card.

Will AVS and Card Code be checked?

If the Address information is passed, then the AVS (Address Verification System) check will be done and work as it normally does. Card Code/CAVV (Cardholder Authentication Verification Value) check cannot be done as CCV (Card Code Verification) information cannot be stored and will not be passed in the transaction/token data.

Will Google Pay transactions pass through Advance Fraud Detection Suite (AFDS)?

Yes, the transactions will pass through and can trigger AFDS filters.

Can tokenized transactions like Google Pay be refunded?

Yes, merchants can refund tokenized transactions the same way and using the same limits as normal credit card transactions.

How does Google Pay work with Authorize.net?

Google Pay can be used with our Accept Mobile Android SDK.

SDK Scenario:

1. The developer will send a call to Google’s native SDK to retrieve an encrypted BLOB (Binary Large Object) which identifies the customer’s payment information.
2. Send the encrypted payment data to their server.
3. Their server will then construct a transaction request using the Authorize.Net API, placing the encrypted payment information they received in Step 2 in the opaqueData element.

What are the minimum required payment fields for Google Pay transactions?

• Opaque Data (which contains the following):
  • Data Descriptor
  • Data Value (encrypted data)
• Card Number
• Expiration Date
• Amount

What transaction types are supported?

• Authorization and Capture
• Authorization Only

Are there Google Pay specific Reason Response Codes?

Yes, and our guides and documentation are being updated to reflect them.