...
PDF Download:
| View file | ||
|---|---|---|
|
Introduction
Insert excerpt
Note: The Android App for Google Pay is now called Google Wallet. Google Wallet can be used anywhere that accepts Google Pay.
Adding a Card to Google Pay™
The customer creates a Google Wallet account and adds payment methods to the wallet.
The payment methods are stored in Google Servers. A list of payment methods is provided when the service is invoked.
Google severs return the payment payload when the payment method is used for a transaction. The payment payload is decrypted, and the specific values required for the authorization are passed to MerchantE by the merchant or Gateway provider for processing.
Making a Purchase using Google Pay™
...
A customer checks out on the Merchant website and uses Google Pay as payment.
Google Pay is invoked, and the available payment methods are provided. The encrypted payment payload and unencrypted details are provided to the Merchant or Gateway provider.
The encrypted payment payload and transaction details are sent to the Merchant or Gateway provider for decryption.
The payment payload with the decrypted wallet details is sent to MerchantE for transaction Processing. The transaction is executed, and the results are sent back to the Merchant or Gateway Provider.
The Merchant sends the transaction receipt to the customer.
Steps to Implement
MerchantE offers two ways to add Google Pay as a payment option.
...
The initial Google Pay request should contain the following the values.
Field | Value |
|---|---|
gateway | merchante |
gatewayMerchantId | Google Pay MID |
Google Pay Configuration
https://developers.google.com/pay/api/web/guides/test-and-deploy/integration-checklist
...
The following fields are used to send payment data directly to the payment gateway for processing.
Field | Description | Example | Required? | Length | Format |
profile_id | ID issued by MerchantE | 94100008819100000003 | Required | 20 | N |
profile_key | EAPI password assigned by MerchantE | oyFnzBewkLQEkGispfAoIjNoTuTwtcbv | Required | 32 | AN |
transaction_type | D, where D denotes a sale. | D | Optional | 1 | AN |
card_number | Payment card number | 4012301230158 | Conditional | 5 – 22 | N |
moto_ecommerce_ind | Acceptable values are 5, 6, 7, and A. Recurring transactions will require 2. | 5 | Required | 1 | AN |
cavv | This contains a data value generated by the issuer to enable cardholder validation for 3D Secure transactions. | BwABBJaSmIZUMzSVMpKYAAAAAAA%3D | Conditional - Used for Visa and Discover. | 40 | AN |
tac |
| TWsyTEhIakRyQWRNakd4SkhoeHI%3D | Conditional – Used for AMEX. | 30 | AN |
ucaf_auth_data | This is a variable length issuer generated security field up to 32 bytes in length. | ucaf:jJJLtQa+Iws8AREAEbjsA1MAAAA | Conditional - Used for Mastercard. | 0-32 | AN |
xid | This field contains a value assigned to a SET or 3D Secure transaction as a unique transaction identifier. | b1h4MTVGa2JXMzFhSEhOU3FqSjA%3D | Conditional - Used for AMEX. | 0 or 40 | AN |
requesterapp_name | Product Identifier | GGL001 | Conditional - Mandatory for Google Pay. |
| AN |
token_requestor_id | Hex-encoded device manufacturer identifier. | 544553544456 | Conditional- Mandatory for AMEX. | 0 or 11 | AN |
recurring_pmt_num | Payment number of the transaction. Initial and subsequent recurring transactions should pass 1. | 1 | Conditional | 2 | N |
Example Request/Response
Tokenized
...