Here are some answers to questions you may have about transactions with Google Pay:

Besides the original fields for a credit or debit card payment transaction, the Google Pay DPAN transaction has three additional fields:

• cryptogram: 3DS cryptogram information (previously called 3DS_criptogram).
• eci: Electronic Commerce Indicator (previously called ECI_Indicador). This field is sent only for Visa transactions and indicates the result of the authentication attempt made by the 3DS system.
• paymentOrigin (optional): Identifies the type of card used for payment. To enable this field in Google Pay (DPAN) transactions or FPAN transactions and receive the information in the Create payment endpoint payload, open a ticket with VTEX Support.

In the VTEX Admin, go to Orders > Transactions to check if a transaction has been made with Google Pay.

The paymentOrigin, panType, and cryptogram fields aren't sent in standard credit or debit card transactions (without using a digital wallet).

The paymentOrigin field is always sent with the "Google Pay" value. Payment transactions using other payment methods don't have the paymentOrigin field in the payload.

No. The card CVV is sent in certain FPAN-type transactions. DPAN payment transactions do not require the card CVV number.

Transactions processed in subscription or recurring operations do not use the card CVV as well.

To run a DPAN test transaction, follow these steps:

1. Add a new card in the Google Pay digital wallet app or via redirection from the bank app (Android).

2. Open the Chrome browser using the same Android device you used to add the card.

3. Simulate buying a product, and on the checkout screen, select the option to pay using Google Pay.

   Make sure to select the card that displays the actual card image, as it defines the transaction will use DPAN. If you select the card displaying the flag image, the transaction will use the FPAN method.

4. Complete the payment and check the DPAN transaction data in your system.