# Google Pay {#pm_googlepay} An article about the payment method which allows you to process payments in different currencies by using Google services in different countries and supports one-time one-step and two-step purchases, credential-on-file purchases, refunds, payment card verification, and payouts. **Parent topic:**[Digital wallet payments](en_pm_ewallet.md) ## Overview {#en_pm_googlepay_overview} An article about the payment method which allows you to process payments in different currencies by using Google services in different countries and supports one-time one-step and two-step purchases, credential-on-file purchases, refunds, payment card verification, and payouts. ### Introduction {#section_i11_bg5_1xb .section} Google Pay is a payment method which allows to process payments in different currencies by using Google Pay services in different regions.This method supports one-time one-stepand two-step purchases, credential-on-file purchases, refunds, payment card verification and payouts. This article provides information about working with the Google Pay method: general insights are presented in the Overview section, while information about the actions required to process payments and perform other actions is presented in the sections that follow. ### General information {#section_tbf_2zk_ggb .section} |Payment method type|digital wallet payments| |Payment instruments|payments cards| |Countries and regions|the list is available at the [link](https://support.google.com/pay/answer/9023773?hl=en&ref_topic=7625138#zippy=)| |Payment currencies|all currencies supported by American Express, Mastercard, and Visa payment systems in supported regions| |Currency conversion|on the Ecommpay side| |One-time purchases|+| |Credential-on-file purchases|+| |Full refunds|+| |Partial refunds|+| |Payouts|+| |Card verification|+| |Chargebacks|+| |Special considerations|- for payments with Google Pay, American Express, Visa, and Mastercard can be supported. For more information, contact your Ecommpay account manager. - to perform purchases by using Gate, the merchant is required to do the following: - perform the necessary [setup](https://developers.google.com/pay/api/web/guides/setup) required by Google and follow the [integration checklist](https://developers.google.com/pay/api/web/guides/test-and-deploy/integration-checklist) - apply for the registration in Google service and receive the Google merchant ID - call the Google Pay API directly from the web service for more information on these points, refer to your Ecommpay key account manager - purchases can be processed by customers using devices that do and do not support the Google Pay app, in the second case the 3‑D Secure 2 authentication is possible depending on the issuer - for payments with this method via the 5th generation of Payment Page, collecting customer data by the Google Pay service is supported \([details](pm_googlepay.md#section_p5j_fgl_ggb)\) - all merchants must adhere to the Google Pay APIs [Acceptable Use Policy](https://payments.developers.google.com/terms/aup) and accept the terms defined in the [Google Pay API Terms of Service](https://payments.developers.google.com/terms/sellertos) - for payments with this method via Payment Page, conversion when the customer selects the currency is supported \([details](en_pp_currency_choice.md)\) - An Google Pay branded payment button can be embedded into the interface of the web service to ensure the capability of processing express checkout payments, in which case the interaction between the web service and the platform will differ from the one described in this article \([details](en_pp_embedded_payment_buttons.md)\) | |Obtaining access to the payment method and access fee|refer to your Ecommpay key account manager, additional information available in the [Ecommpay shop](https://ecommpay.com/shop/payment-methods/google-pay/)| ### Interaction diagram {#section_tsp_gzk_ggb .section} Payment processing by using the Google Pay payment method requires merchant's web service, one of Ecommpay interfaces, and the Ecommpay payment platform, as well as the Google Pay and the issuer bank services. ![](images/pm/en_googlepay_functional_new.svg) ### Operations support {#section_rnx_4cl_ggb .section} Various platform interfaces can be used to process payments and perform operations using the Google Pay method. Purchases can be processed by using Payment Page, Gate and Dashboard \(using payment links\), refunds and payouts—by using Gate and Dashboard. ### Processing scenarios {#section_fgt_sdl_ggb .section} To perform a purchases by using the Google Pay method, a customer needs to register a payment card in Google Payapp at one of the supported devices first. Then to perform a purchase, it is required to request the tokenized card details from the Google Pay service by using Google Pay API. When processing a purchase by using Payment Page, Ecommpay establishes all interactions with the Google Pay service, when processing a purchase by using Gate, interaction with the Google Pay service is on the merchant web service side.To perform a refund, you need to receive a request from a customer and notify the customer about the result of the refund via the web service. To process a payout, you need to notify the customer via the web service. ![](images/pm/eng_googlepay_interfaces_pp.svg "Purchase by using Payment Page") ![](images/pm/eng_googlepay_interfaces_gate.svg "Purchase by using Gate without 3‑D Secure 2 authentication") ![](images/pm/eng_googlepay_interfaces_gate_3ds.svg "Purchase by using Gate with 3‑D Secure 2 authentication") ![](images/pm/eng_googlepay_interfaces_gate_refund.svg "Refund by using Gate") ![](images/pm/eng_googlepay_interfaces_gate_payout.svg "Payout by using Gate") Scenarios for performing operations via the main interfaces of the payment platform correspond to those presented in the diagrams. Similarly, when additional features \(such as payment links\) are used, scenarios for performing operations also correspond to the specifics of those features. ## One-time purchases by using Payment Page {#en_pm_googlepay_pp_purchase} ### General information {#section_gtg_vxk_m2b .section} To process a purchase through Payment Pageby using the Google Pay method, the merchant's web service is required to send a request with all required parameters and signature to the Ecommpay URL and receive a callback with the result. In case of a two-step purchase, it might be required, at a later point, to confirm the capture of the held funds.The full sequence and special aspects of one-step purchase processing are provided below. ![](images/pm/eng_googlepay_uml_pp.svg) 1. A customer initiates a purchase in the web service. 2. The web service sends the request for opening Payment Page to the specified Ecommpay URL. 3. The request for opening Payment Page is sent to the payment platform. 4. The payment platform receives the request and validates the required parameters and signature. 5. Payment Page is generated based on the project and request parameters. 6. Payment Page is displayed to the customer. 7. The customer selects the payment card method and clicks the `Google Pay` button. If the `Google Pay` button is displaying among other payment methods on the first page, the customer just clicks the button. 8. The payment platform receives the request for opening the Google Pay app or the Google Pay payment form. 9. The payment platform sends the request for opening the payment form with the customer masked card details stored in the Google account to the Google Pay service. 10. The Google Pay service processes the request and generates a payment form with the list of cards available for the customer. 11. The Google Pay app or form is displayed to the customer with masked card details: - when processing a purchase on web sites by using mobile Google Chrome or in apps supporting payments with Google Pay, the Google Pay app opens - in other cases the Google Pay form is displayed in any mobile or desktop browser 12. The customer selects the specific card and confirms the purchase. 13. The Google Pay service redirects the customer to Payment Page 14. The customer data is processed on the Google Pay service side. 15. The Google Pay service sends the token of the encrypted card details to the payment platform. 16. The payment platform sends the payment request to the card organisation service. 17. The purchase is processed in the card organisation service. 18. The card organisation service sends a notification about the result to the payment platform. 19. The payment platform sends the payment result callback to the web service. 20. The payment platform sends the result information to Payment Page. 21. The result information is displayed to the customer on Payment Page. In case of a two-step purchase, the process of placing the authorisation hold via Payment Page using the Google Pay method is identical to the workflow sequence of a one-step purchase, with the exception that instead of an immediate debiting of funds an authorisation hold is initiated and executed. Information about the formats of requests and callbacks used for processing payments by using the Google Pay method via Payment Page is presented further in this section; general information about working with the Payment Page API is presented in [Interaction concepts](en_pp_interaction_organisation.md). ### Request format {#section_p5j_fgl_ggb .section} There are several things you need to consider when sending purchase requests by using the Google Pay method: 1. The following parameters required for any payment must be specified: - `project_id`—project identifier obtained from Ecommpay during integration - `payment_id`—payment identifier unique within the project - `payment_currency`—payment currency code in the ISO-4217 alpha-3 format - `payment_amount`—payment amount in the smallest currency unit - `customer_id`—customer identifier unique within the project 2. To specify the type of purchase that is different from the default one set for the specific project, pass `sale` \(for immediate withdrawal of funds during one-step purchase processing\) or `auth`\(to place an authorisation hold during two-step purchase processing\) in the `operation_type` parameter. 3. You can choose the way of displaying the `Google Pay` button on Payment Page. There are several ways: - Displaying the `Google Pay` button on the page for entering card details. The customer must first select the Bank cards method on the page for selection a payment method among other payment methods. This option is set by default. - Displaying the `Google Pay` button on the page for selection a payment method among other payment methods. To set this option, contact Ecommpay technical support. - Displaying the `Google Pay` button on the page for entering card details by passing the page for the payment method selection. The customer does not need to select the Bank cards method. To set this option, pass the code `card` in the `force_payment_method` parameter. - Displaying only the `Google Pay` button on Payment Page. To set this option, pass the code `google_pay_host` in the `force_payment_method` parameter. 4. To collect specific customer data on the Google Pay service side \(in cases when the 5th generation of Payment Page is used and such data collection is not configured for all payments within the project; [details](en_PP_Gathering_customer_data.md)\), pass the `payment_methods_options` parameter with a list of the of the requested data in the `billing_contact_fields` array included in the `google_pay_host` object. The following information can be requested: - `email`—the customer's email address - `name`—the customer's first and last name - `phone`—the customer's phone number - `postal_code`—the postal code from the customer's address - `billing_address`—the customer's billing address For example, to collect the customer's email address and phone number, pass the `payment_methods_options` parameter as follows. ``` {#codeblock_csj_dkz_5gc .language-json} "payment_methods_options": {"google_pay_host":{"billing_contact_fields":["email","phone"]}} ``` ``` {#codeblock_oql_sd1_vgc .language-json} "payment_methods_options": {\"google_pay_host\":{\"billing_contact_fields\":[\"email\",\"phone\"]}} ``` 5. Additionally, any other parameters available for working with Payment Page can be used \([details](en_PP_Parameters.md)\). 6. After all target parameters are specified, generate a signature \([details](en_platform_signature.md)\). Thus, a correct request for opening the payment form using the Google Pay method must contain the project identifier, basic payment information \(identifier, amount, and currency code\), customer identifier and signature. ```language-json { "project_id": 120, "payment_id": "580", "payment_amount": 1000, "payment_currency": "USD", "customer_id": "customer1", "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg==" } ``` **Warning:** In order to enhance the quality of payment processing and ensure compliance with industry standards, starting from January 15, 2026, merchants in certain business categories must specify the `booking_info` parameter containing information about the start and end dates of the booked service \([details](en_pp_additional_data.md)\), for each initiated [card purchase](en_pm_cardpayments.md). This requirement applies to merchants with [Merchant Category Codes \(MCC\)](en_glossary.md) 3000–3999, 4411, 4511, 4722, 5962, 6513, 7011, 7012, 7512, 7519, and 7922. ### Callback format {#section_dpx_2hl_ggb .section} In the Google Pay method, the callbacks that deliver purchase results use the standard format described in [Handling callbacks](en_platform_callbacks.md). Note that unlike other payment methods, in the Google Pay method, callbacks containing information about purchases processed with the inclusion of the 3‑D Secure authentication procedure contain the ECI indicator code in the `operation.eci` parameter \([details](en_ECI_codes.md)\); also in this case the service code of the payment method is specified as `card` in the `payment.method` parameter. At the same time callbacks containing information about purchases processed without the inclusion of the 3‑D Secure authentication procedure do not contain the ECI indicator code and the service code can be specified as `card` or `etoken-google`. The callbacks containing information about processed purchases include the token of the card in the `token` parameter of the `account` object. When the service code of the method is specified as `etoken-google` the token can be only used for initiating payouts, and when the code is `card` the token can be used for initiating both purchases and payouts. The following is the example of a callback with an information about a `1,000.00 USD` purchase made in the `688` project by using `431422******0056` payment card without 3‑D Secure authentication. ```language-json { "project_id": 688, "payment": { "id": "TEST_154356886034722221", "type": "purchase", "status": "success", "date": "2019-04-11T11:22:36+0000", "method": "etoken-google", "sum": { "amount": 100000, "currency": "USD" }, "description": "TEST_154356886034722221" }, "account": { "number": "431422******0056", "token": :"a989f5ef7ab159dd5c33260e4201d13dbfcdc75" }, "operation": { "id": 2000015, "type": "sale", "status": "success", "date": "2019-04-11T11:22:36+0000", "created_date": "2019-04-11T11:22:20+0000", "request_id": "2b36e68d4d9fc8839d5d65ee6273dfdebbd", "sum_initial": { "amount": 100000, "currency": "USD" }, "sum_converted": { "amount": 100000, "currency": "USD" }, "provider": { "id": 1381, "payment_id": "d1b9-3qfl-9rns-1ql9aokzi2v8", "date": "2019-04-11T11:22:34+0000", "auth_code": "" }, "code": "0", "message": "Success" }, "signature": "Xkf7nUDleg8wcLltroCvNOMq751VtZcgrz6Nax...==" } ``` The following is the example of a callback with an information about a `1,000.00 USD` purchase made in the `688` project by using `431422******0056` payment card with 3‑D Secure authentication. ```language-json { "project_id": 688, "payment": { "id": "TEST_154356886034722221", "type": "purchase", "status": "success", "date": "2019-04-11T11:22:36+0000", "method": "etoken-google", "sum": { "amount": 100000, "currency": "USD" }, "description": "TEST_154356886034722221" }, "account": { "number": "431422******0056", "token": :"a989f5ef7ab159dd5c33260e4201d13dbfcdc75" }, "operation": { "id": 2000015, "type": "sale", "status": "success", "date": "2019-04-11T11:22:36+0000", "created_date": "2019-04-11T11:22:20+0000", "request_id": "2b36e68d4d9fc8839d5d65ee6273dfdebbd", "sum_initial": { "amount": 100000, "currency": "USD" }, "sum_converted": { "amount": 100000, "currency": "USD" }, "provider": { "id": 1381, "payment_id": "d1b9-3qfl-9rns-1ql9aokzi2v8", "date": "2019-04-11T11:22:34+0000", "auth_code": "" }, "code": "0", "message": "Success", "eci": "02" }, "signature": "Xkf7nUDleg8wcLltroCvNOMq751VtZcgrz6Nax...==" } ``` The following is the example of a callback for a declined purchase with 3‑D Secure authentication. ```language-json { "project_id": 688, "payment": { "id": "TEST_154356886034722222", "type": "purchase", "status": "decline", "date": "2019-04-11T11:24:51+0000", "method": "etoken-google", "sum": { "amount": 100100, "currency": "USD" }, "description": "TEST_154356886034722222" }, "account": { "number": "431422******0056" }, "operation": { "id": 2000000383, "type": "sale", "status": "decline", "date": "2019-04-11T11:24:51+0000", "created_date": "2019-04-11T11:24:35+0000", "request_id": "0eef294c20a7d72abd0fb20f3753ee674b51fbe", "sum_initial": { "amount": 100100, "currency": "USD" }, "sum_converted": { "amount": 100100, "currency": "USD" }, "provider": { "id": 1381, "payment_id": "1rvp-fc2k-cnp9-h41ocauwn6fr", "date": "2019-04-11T11:24:50+0000", "auth_code": "" }, "code": "20000", "message": "General decline", "eci": "00" }, "signature": "cQbMiD0pON9eJc5ZugNK0iT5SwHc0feItZRcAB...==" } ``` ### Useful links {#section_xpz_thl_ggb .section} The following articles can be useful when implementing purchases via Payment Page: - [Interaction concepts](en_pp_interaction_organisation.md)—about the interaction with the payment platform by using Payment Page. - [Signature generation and verification](en_platform_signature.md)—about the procedure of generating and verifying signatures in requests and callbacks. - [Payment processing](en_platform_payment_model.md)—about the types, processing models, and possible statuses of supported payments and operations. - [One-time one-step purchase](en_platform_sms_model.md)—about processing of one-time one-step purchases by using Payment Page. - [Handling operation processing information](en_platform_payment_info_codes.md)—about error and response codes that are used in the payment platform to record information about performing of operations. ## One-time purchases by using Gate {#en_pm_googlepay_gate_purchase} ### General information {#section_lsx_3jl_ggb .section} In order to process purchases by using the Google Pay method via Gate, the merchant must adhere to the Google Pay API [Acceptable Use Policy](https://payments.developers.google.com/terms/aup) and accept the terms defined in the [Google Pay API Terms of Service](https://payments.developers.google.com/terms/sellertos). At the same time, the web service is required to the following: 1. Perform the necessary [setup](https://developers.google.com/pay/api/web/guides/setup) required by Google and follow the [integration checklist](https://developers.google.com/pay/api/web/guides/test-and-deploy/integration-checklist) 2. Apply for the registration in Google service and receive the Google merchant ID 3. Fill in the [Google Pay API integration support request form](https://services.google.com/fb/forms/googlepayAPIsupport/) and take the next steps in accordance with the communications from Google. It may be necessary to provide additional integration information to Google You should also keep in mind that payments using the Google Pay method can be processed in accordance with two scenarios: - via the Google Pay app \(when installed on the customer's compatible device\) - without using the Google Pay app, like a typical card payment \(when the app is not installed on the customer's device or the device is not compatible with it\). In the first case, the purchase is processed without 3‑D Secure authentication, and in the second case, it can be carried out both with and without the authentication. To resolve such situations on the web service side, it is necessary to configure a response to callbacks with information about customer redirection and support the two possible scenarios. When processing a purchase in the Google Pay method without 3‑D Secure authentication, the merchant web service is required to do the following: 1. Integrate the `Google Pay` button following the Google Pay [brand guidelines](https://developers.google.com/pay/api/web/guides/brand-guidelines) and implement the receiving of the token of customer card from Google Pay. 2. Send a request to Google Pay service for payment form or app opening with the list of saved cards that are available to a customer. 3. Send a request to Google Pay service for receiving the token of the card selected by a customer. 4. Send a request with all the required parameters and signature to the Ecommpay URL. 5. Receive the final callback with the payment result from the payment platform. When processing a purchase in the Google Pay method with 3‑D Secure, the merchant web service is required to do the following: 1. Integrate the `Google Pay` button following the Google Pay [brand guidelines](https://developers.google.com/pay/api/web/guides/brand-guidelines) and implement the receiving of the token of customer card from Google Pay. 2. Send a request to Google Pay service for payment form or app opening with the list of saved cards that are available to a customer. 3. Send a request to Google Pay service for receiving the token of the card selected by a customer. 4. Send a request with all the required parameters and signature to the Ecommpay URL. 5. Get the callback from the platform with data to redirect the customer to the authentication page. 6. Redirect the customer to the authentication page to pass 3‑D Secure. 7. Send the payment completion request with the result of authentication to the payment platform. 8. Receive the final callback with the payment result from the payment platform. The full sequence and special aspects of purchase processing are provided below. ![Purchase workflow in Gate](images/pm/eng_googlepay_uml_gate.svg) 1. A customer initiates a purchase by using the Google Pay method in the web service. 2. The request for opening the Google Pay app or the Google Pay payment form that display masked card details stored in the customer Google account is sent to the Google Pay service. 3. The Google Pay service processes the request and generates a payment form with the list of cards available for the customer. 4. When processing a purchase on web sites by using mobile Google Chrome or in apps supporting payments with Google Pay, the Google Pay app opens with masked card details is displayed to the customer. 5. The customer selects the specific card and confirms the purchase. 6. The Google Pay service redirects the customer to the result loading page in the merchant web service. 7. The customer data is processed on the Google Pay service side. 8. The Google Pay service sends the token that represents encrypted card details. 9. The web service sends the request for processing the purchase through Gate by using the card token received from Google Pay to the specified Ecommpay URL. 10. The payment platform receives the request for processing the purchase by using Gate. 11. The payment platform validates the required parameters and signature in the request. 12. The payment platform sends the response to the web service with information about the receipt of the request and its validity \([details](en_gate_interaction_organisation.md)\). 13. The payment platform performs further processing of the request \(with parameter consistency check\) and sends it to the card organisation service. 14. The payment is processed on the card organisation side. 15. The card organisation service sends the payment result notification to the payment platform. 16. The payment platform sends the payment result callback to the web service. 17. The customer receives the payment result information from the web service. ![Purchase workflow in Gate](images/pm/eng_googlepay_uml_gate_3ds.svg) 1. A customer initiates a purchase by using the Google Pay method in the web service. 2. The request for opening the Google Pay app or the Google Pay payment form that display masked card details stored in the customer Google account is sent to the Google Pay service. 3. The Google Pay service processes the request and generates a payment form with the list of cards available for the customer. 4. When processing a purchase using devises that do not support payments with Google Pay the payment form of Google Pay is displayed to the customer in any mobile or desktop browser with masked card details. 5. The customer selects the specific card and confirms the purchase. 6. The Google Pay service redirects the customer to the result loading page in the merchant web service. 7. The customer data is processed on the Google Pay service side. 8. The Google Pay service sends the token that represents encrypted card details. 9. The web service sends the request for processing the purchase through Gate by using the card token received from the Google Pay service to the specified Ecommpay URL. 10. The payment platform receives the request for processing the purchase by using Gate. 11. The payment platform validates the required parameters and signature in the request. If the purchase is performed from the web browser and not from the Google Pay app, the 3‑D Secure authentication is also performed. 12. The payment platform sends the response to the web service with information about the receipt of the request and its validity \([details](en_gate_interaction_organisation.md)\). 13. The payment platform performs further processing of the request \(with parameter consistency check\) and sends it to the card organisation service. 14. The request is processed and the necessity of 3‑D Secure authentication is checked on the card organisation side. 15. The data for redirection of the customer to the authentication page is sent to the payment platform from card organisation. 16. The payment platform sends the callback with the redirection data to the web service. Further information on the formats for callbacks with the data for redirection of the customer to the authentication page is provided in the corresponding section [3‑D Secure authentication](en_gate_payment_3ds.md). 17. Merchant web service redirects the customer to the authentication page. 18. Customer is redirected to the authentication page and passes the 3‑D Secure authentication. 19. Card organisation service performs customer authentication. 20. Customer is redirected to the web service loading page. 21. The web service sends the payment completion request through Gate to the specified Ecommpay URL. 22. The payment platform receives the payment completion request. 23. The payment platform validates the required parameters and signature in the request. 24. The payment platform sends the response to the web service with information about the receipt of the request and its validity \([details](en_gate_interaction_organisation.md)\). 25. The payment platform performs further processing of the request \(with parameter consistency check\) and sends it to the card organisation service. 26. The payment is processed on the card organisation service side. 27. The card organisation service sends the payment result notification to the payment platform. 28. The payment platform sends the payment result callback to the web service. 29. The customer receives the payment result information from the web service. To initiate a payment session on the side of the merchant's web service, you need to implement integration with the Google Pay service according to its [documentation](https://developers.google.com/pay/api/web/guides/tutorial?hl=en). A range of supplementary features supported by the service can be used in such integrations including the functionality of collecting customer data. Information about the formats of requests and callbacks used for interacting with the Ecommpay payment platform to process payments by using the Google Pay method via Gate is presented further in this section. General information about working with the Gate API is presented in [Interaction concepts](en_gate_interaction_organisation.md). ### Request format {#section_osx_3jl_ggb .section} There are several things you need to consider when sending requests for starting the payment session by using the Google Pay method: 1. To initiate each purchase, send a separate POST requestto one of the following endpoints: - [/v2/payment/googlepay/sale](https://api-developers.ecommpay.com/api-specification/google-pay/post-v2-payment-googlepay-sale) for one-step purchases - [/v2/payment/googlepay/auth](https://api-developers.ecommpay.com/api-specification/google-pay/post-v2-payment-googlepay-auth) for two-step purchases 2. Each request must include the following objects and parameters: - Object `general`—general purchase information: - `project_id`—project identifierobtained from Ecommpay during integration - `payment_id`—payment identifierunique within the project - `signature`—request signaturegenerated after all required parameters are specified \(details—in the [Signature generation and verification](en_platform_signature.md)\) - Object `payment`—payment information: - `amount`—payment amount in the smallest currency unit - `currency`—payment currency codein the ISO-4217 alpha-3 format - `cryptocurrency_type`—the indicator that specifies the type of the cryptocurrency, required for Mastercard and Visa payments involving cryptocurrencies. This parameter should be assigned one of the following values: - `cbdc`—a central bank digital currency or tokenized deposit issued by a central bank, reserve bank, or other national monetary authority; - `stablecoins_fiat_backed`—a fiat-backed digital asset with reserves held by a licensed financial institution; - `native_tokens`—a digital currency native to a specific blockchain, required for transactions within its network, including fee payments; - `other`—a non-fiat digital asset that does not fit other types or cannot be classified at the time of transaction initiation. - Object `customer`—customer information: - `id`—customer identifierunique within the project - `ip_address`—customer IP addressrelevant for the initiated payment - Object `etoken` — information about token that represents card details received from the Google Pay service: - `token`—token with card encrypted details 3. Other mandatory parameters may be required. It depends on the tokenization type that is used in a request to the Google Pay service. For information about what type of tokenization you need to perform purchase in a project, contact Ecommpay technical support. To use `PAYMENT_GATEWAY` tokenization type, customer email is required to specify in the `email` parameter of the `customer` object. To use `DIRECT` tokenization type, the following parameters must be specified in the `etoken` object: - `google_merchant_id`—merchant ID in the Google Pay service - `google_tokenization_type`—the `DIRECT` tokenization type 4. Additionally, any other parameters included in the specification can be used. Thus, a correct purchase request by using the Google Pay method with the `PAYMENT_GATEWAY` tokenization type must contain the project identifier, basic payment information \(identifier, amount, and currency code\), customer identifier, IP address and email, as well as signature. ```language-json { "general": { "project_id": 626, "payment_id": "ORDER_ID_gev_S01_0.20111200_1554473913", "signature": "xWOlMksKctAKeYADt8W6F98D/ZFgyNqOYw...==" }, "customer": { "id": "123", "email": "googlepay@example.com", "ip_address": "192.0.2.0" }, "payment": { "amount": 10000, "currency": "USD" }, "etoken": { "token": "..." // as received from Google Pay } } ``` ```language-json { "general": { "project_id": 626, "payment_id": "ORDER_ID_gev_S01_0.20111200_1554473913", "signature": "xWOlMksKctAKeYADt8W6F98D/ZFgyNqOYw...==" }, "customer": { "id": "123", "email": "googlepay@example.com", "ip_address": "192.0.2.0" }, "payment": { "amount": 10000, "currency": "USD" }, "etoken": { "token": "..." // as received from Google Pay } } ``` Thus, a correct purchase request by using the Google Pay method with the `DIRECT` tokenization type must contain the project identifier, basic payment information \(identifier, amount, and currency code\), customer identifier and IP address, merchant ID and tokenization type, as well as signature. ```language-json { "general": { "project_id": 688, "payment_id": "ORDER_89218100_1554981739", "signature": "aRZiZZc0w5RVnuCxC7KSm50Pfwsj/8fqy2XlAJ...==" }, "customer": { "id": "123", "ip_address": "192.0.2.0" }, "payment": { "amount": 10000, "currency": "USD" }, "etoken": { "token": "...", // as it is received from Google Pay "google_merchant_id": "12345678901234567890", "google_tokenization_type": "DIRECT" } } ``` ```language-json { "general": { "project_id": 688, "payment_id": "ORDER_89218100_1554981739", "signature": "aRZiZZc0w5RVnuCxC7KSm50Pfwsj/8fqy2XlAJ...==" }, "customer": { "id": "123", "ip_address": "192.0.2.0" }, "payment": { "amount": 10000, "currency": "USD" }, "etoken": { "token": "...", // as it is received from Google Pay "google_merchant_id": "12345678901234567890", "google_tokenization_type": "DIRECT" } } ``` **Warning:** In order to enhance the quality of payment processing and ensure compliance with industry standards, starting from January 15, 2026, merchants in certain business categories must specify the `booking_info` object containing information about the start and end dates of the booked service \([details](en_gate_additional_data.md)\), for each initiated [card purchase](en_pm_cardpayments.md). This requirement applies to merchants with [Merchant Category Codes \(MCC\)](en_glossary.md) 3000–3999, 4411, 4511, 4722, 5962, 6513, 7011, 7012, 7512, 7519, and 7922. ### Payment completion request format {#section_e1f_hxm_rnb .section} There are several things you must consider when using payment completion requests in the Google Pay method: 1. To complete each purchase, send a separate POST request to the [/v2/payment/card/3ds\_result](https://api-developers.ecommpay.com/api-specification/card-payments/post-v2-payment-card-3ds-result) endpoint. 2. Each request must include the following objects and parameters: - Object `general`—general purchase information: - `project_id`—project identifierobtained from Ecommpay during integration - `payment_id`—payment identifierunique within the project - `signature`—request signaturegenerated after all required parameters are specified \(details—in the [Signature generation and verification](en_platform_signature.md)\) - One of the following parameters: - `pares`—the 3‑D Secure authentication result you obtain from the payment platform - `cres`—the 3‑D Secure authentication result you obtain from the Access Control Server Thus, a correct payment completion request by using the Google Pay method must contain the project and payment identifiers, authentication result, as well as signature. ```language-json { "general": { "project_id": 580, "payment_id": "TEST_15427033321774", "signature": "96c+hWk1zweuGKwDJXZw7ew6ow3RpGYv4U...==" }, "pares": "eJzVWdfvq8iy/iujOY/1...Dfn76en3N+f/A1fJrSU=" } ``` ### Two-step purchase debiting request format {#section_zpl_x34_nkb .section} There are several things you need to consider when sending debiting requests by using the Google Pay method: 1. To initiate each debiting, send a separate POST request to one of the following endpoints: - [/v2/payment/googlepay/capture](https://api-developers.ecommpay.com/api-specification/google-pay/post-v2-payment-googlepay-capture)—when the service code of the method is specified as `etoken-google` in the callback containing information about authorisation hold - [/v2/payment/card/capture](https://api-developers.ecommpay.com/api-specification/card-payments/post-v2-payment-card-capture)—when the service code of the method is specified as `card` in the callback containing information about authorisation hold 2. Each request must include the following objects and parameters: - Object `general`—general purchase information: - `project_id`—project identifierobtained from Ecommpay during integration - `payment_id`—payment identifierunique within the project - `signature`—request signaturegenerated after all required parameters are specified \(details—in the [Signature generation and verification](en_platform_signature.md)\) - Object `payment`—payment information: - `amount`—payment amount in the smallest currency unit - `currency`—payment currency codein the ISO-4217 alpha-3 format 3. The amount and currency must match the values in the authorisation request. 4. Additionally, any other parameters included in the specification can be used. Thus, a correct purchase request by using the Google Pay method must contain the project identifier, basic payment information \(identifier, amount, and currency code\), as well as signature. ```language-json { "general": { "project_id": 580, "payment_id": "TEST_15427033321774", "signature": "96c+hWk1zweuGKLXHChlDZrjJXZw7ew6ow3RpGYv4U...==" }, "payment": { "amount": 1000, "currency": "USD" } ``` ### Two-step purchase cancellation request format {#section_p2j_dm4_nkb .section} There are several things you need to consider when sending purchase cancellation requests by using the Google Pay method: 1. To initiate each cancellation, send a separate POST request to one of the following endpoints: - [/v2/payment/googlepay/cancel](https://api-developers.ecommpay.com/api-specification/google-pay/post-v2-payment-googlepay-cancel-etoken)—when the service code of the method is specified as `etoken-google` in the callback containing information about authorisation hold - [/v2/payment/card/cancel](https://api-developers.ecommpay.com/api-specification/card-payments/post-v2-payment-card-cancel)—when the service code of the method is specified as `card` in the callback containing information about authorisation hold 2. Each request must include the following objects and parameters: - Object `general`—general purchase information: - `project_id`—project identifierobtained from Ecommpay during integration - `payment_id`—payment identifierunique within the project - `signature`—request signaturegenerated after all required parameters are specified \(details—in the [Signature generation and verification](en_platform_signature.md)\) 3. Additionally, any other parameters included in the specification can be used. Thus, a correct purchase request by using the Google Pay method must contain the project and payment identifiers, as well as signature. ```language-json { "general": { "project_id": 580, "payment_id": "TEST_15427033321774", "signature": "9DRrl+Se5mDLXHChlDZrjJXZw7ew6ow3RpGYv4U...==" } ``` ### Callback format {#section_dpx_2hl_ggb .section} In the Google Pay method, the callbacks that deliver purchase results use the standard format described in [Handling callbacks](en_platform_callbacks.md). Note that unlike other payment methods, in the Google Pay method, callbacks containing information about purchases processed with the inclusion of the 3‑D Secure authentication procedure contain the ECI indicator code in the `operation.eci` parameter \([details](en_ECI_codes.md)\); also in this case the service code of the payment method is specified as `card` in the `payment.method` parameter. At the same time callbacks containing information about purchases processed without the inclusion of the 3‑D Secure authentication procedure do not contain the ECI indicator code and the service code can be specified as `card` or `etoken-google`. The callbacks containing information about processed purchases include the token of the card in the `token` parameter of the `account` object. When the service code of the method is specified as `etoken-google` the token can be only used for initiating payouts, and when the code is `card` the token can be used for initiating both purchases and payouts. The following is the example of a callback with an information about a `1,000.00 USD` purchase made in the `688` project by using `431422******0056` payment card without 3‑D Secure authentication. ```language-json { "project_id": 688, "payment": { "id": "EPb940-4dab6", "type": "purchase", "status": "success", "date": "2019-04-11T11:22:36+0000", "method": "etoken-google", "sum": { "amount": 100000, "currency": "USD" }, "description": "Successful purchase with 3DS" }, "account": { "number": "431422******0056", "token": :"a989f5ef7ab159dd5c33260e4201d13dbfcdc75" }, "operation": { "id": 2000015, "type": "sale", "status": "success", "date": "2019-04-11T11:22:36+0000", "created_date": "2019-04-11T11:22:20+0000", "request_id": "2b36e68d4d9fc8839d5d6d701b22c5957ebbd", "sum_initial": { "amount": 100000, "currency": "USD" }, "sum_converted": { "amount": 100000, "currency": "USD" }, "provider": { "id": 1381, "payment_id": "gmftho8c-d1b9-3qfl-9rns-1ql9aokzi2v8", "date": "2019-04-11T11:22:34+0000", "auth_code": "HOSTOK" }, "code": "0", "message": "Success" }, "signature": "Xkf7nUDleg8wcLltroCvNOMq751VtZE+JBsJEy2SQ==" } ``` The following is the example of a callback with an information about a `1,000.00 USD` purchase made in the `688` project by using `431422******0056` payment card with 3‑D Secure authentication. ```language-json { "project_id": 688, "payment": { "id": "EPb940-4dab6", "type": "purchase", "status": "success", "date": "2019-04-11T11:22:36+0000", "method": "etoken-google", "sum": { "amount": 100000, "currency": "USD" }, "description": "Successful purchase with 3DS" }, "account": { "number": "431422******0056", "token": :"a989f5ef7ab159dd5c33260e4201d13dbfcdc75" }, "operation": { "id": 2000015, "type": "sale", "status": "success", "date": "2019-04-11T11:22:36+0000", "created_date": "2019-04-11T11:22:20+0000", "request_id": "2b36e68d4d9fc8839d5d65e701b22c5957ebbd", "sum_initial": { "amount": 100000, "currency": "USD" }, "sum_converted": { "amount": 100000, "currency": "USD" }, "provider": { "id": 1381, "payment_id": "gmftho8c-d1b9-3qfl-9rns-1ql9aokzi2v8", "date": "2019-04-11T11:22:34+0000", "auth_code": "HOSTOK" }, "code": "0", "message": "Success", "eci": "02" }, "signature": "Xkf7nUDleg8wcLltroCvNOMq7wdefE+JBsJEy2SQ==" } ``` The following is the example of a callback for a purchase declined due to insufficient funds on card. ```language-json { "project_id": 688, "payment": { "id": "TEST_154356886034722222", "type": "purchase", "status": "decline", "date": "2019-04-11T11:24:51+0000", "method": "etoken-google", "sum": { "amount": 100100, "currency": "USD" }, "description": "TEST_154356886034722222" }, "account": { "number": "431422******0056" }, "operation": { "id": 2000000383, "type": "sale", "status": "decline", "date": "2019-04-11T11:24:51+0000", "created_date": "2019-04-11T11:24:35+0000", "request_id": "0eef294c20a7d72abd0fb20f3753ee674b51fbe", "sum_initial": { "amount": 100100, "currency": "USD" }, "sum_converted": { "amount": 100100, "currency": "USD" }, "provider": { "id": 1381, "payment_id": "1rvp-fc2k-cnp9-h41ocauwn6fr", "date": "2019-04-11T11:24:50+0000", "auth_code": "" }, "code": "20000", "message": "General decline", "eci": "00" }, "signature": "cQbMiD0pON9eJc5ZugNK0iT5SwHc0feItZRcAB...==" } ``` ### Useful links {#section_xsx_3jl_ggb .section} The following articles can be useful when implementing purchases via Gate: - [Interaction concepts](en_gate_interaction_organisation.md)—about the interaction with the payment platform by using Gate. - [Signature generation and verification](en_platform_signature.md)—about the procedure of generating and verifying signatures in requests and callbacks. - [Payment processing](en_platform_payment_model.md)—about the types, processing models, and possible statuses of supported payments and operations. - [One-time one-step purchase](en_platform_sms_model.md)—about processing of one-time one-step purchases by using Gate. - [Handling operation processing information](en_platform_payment_info_codes.md)—about error and response codes that are used in the payment platform to record information about performing of operations. ## COF purchases by using Payment Page {#en_pm_googlepay_pp_recurring} ### General information {#section_gtg_vxk_m2b .section} The Google Pay payment method provides the ability to perform COF purchases—regular on-demand payments. For more information about COF purchases, see [On-demand COF purchase](en_platform_recurring_model.md). Registration of a COF purchases is also available by using Payment Page. For registration the web service must send a request containing the required parameters and signature, as well as data for registering a COF purchase in the `recurring` object, to the Ecommpay URL and accept a callback with the result. In the callback about registering a COF purchase, you will get its ID, which you need to use to make or cancel regular payments via Gate. For more information, see the section [COF purchases by using Gate](pm_googlepay.md). Information about the formats of requests and callbacks used for processing payments by using the Google Pay method via Payment Page is presented further in this section; general information about working with the Payment Page API is presented in [Interaction concepts](en_pp_interaction_organisation.md). ### Request format {#section_p5j_fgl_ggb .section} There are several things you need to consider when creating requests to open a payment form for registering COF purchases by using the Google Pay method: 1. The following parameters required for any payment must be specified: - `project_id`—project identifier obtained from Ecommpay during integration - `payment_id`—payment identifier unique within the project - `payment_currency`—payment currency code in the ISO-4217 alpha-3 format - `payment_amount`—payment amount in the smallest currency unit - `customer_id`—customer identifier unique within the project 2. To register a COF purchase, you must specify a `recurring` object containing the registration attribute and the necessary information. To register regular payments, the request must contain information about the frequency, amount, and beginning and end time of regular payments. The full list of parameters that can be passed in the `recurring` object is shown in the [COF purchase registration](en_pp_recurring.md) section. 3. If you need to have payment form displayed with the Google Pay method selected, set the `force_payment_method` parameter to: - `google_pay_host`—to open Payment Page with pre-selected payment method Google Pay - `card`—for the ability of payment by using either a payment card or Google Pay. In this case customer can chose the payment method on Payment Page 4. Additionally, any other parameters available for working with Payment Page can be used \([details](en_PP_Parameters.md)\). 5. After all target parameters are specified, generate a signature \([details](en_platform_signature.md)\). Thus, a correct request for opening the payment form using the Google Pay method must contain the project identifier, basic payment information \(identifier, amount, and currency code\), customer identifier and signature. ```language-json { "project_id": 120, "payment_id": "580", "payment_amount": 100000, "payment_currency": "USD", "customer_id": "customer1", "force_payment_method": "google_pay_host", "recurring": {"register":true,"type":"R","expiry_year":2025,"expiry_month":"01","period":"D","time":"10:00:00","start_date":"15-11-2020","scheduled_payment_id":"A2323"}, "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg==" } ``` ### Callback format {#section_dpx_2hl_ggb .section} The Google Pay method uses the standard format for callbacks to deliver COF purchase registration results. For more information, see [Handling callbacks](en_platform_callbacks.md). Note that unlike other payment methods, in the Google Pay method, callbacks containing information about purchases processed with the inclusion of the 3‑D Secure authentication procedure contain the ECI indicator code in the `operation.eci` parameter \([details](en_ECI_codes.md)\); also in this case the service code of the payment method is specified as `card` in the `payment.method` parameter. At the same time callbacks containing information about purchases processed without the inclusion of the 3‑D Secure authentication procedure do not contain the ECI indicator code and the service code can be specified as `card` or `etoken-google`. The callbacks containing information about processed purchases include the token of the card in the `token` parameter of the `account` object. When the service code of the method is specified as `etoken-google` the token can be only used for initiating payouts, and when the code is `card` the token can be used for initiating both purchases and payouts. The following is the example of a callback with an information about a COF purchase registration made by a customer in the `208` project. ```language-json { "project_id": 208, "payment": { "id": "payment", "type": "purchase", "status": "success", "date": "2018-11-20T08:44:46+0000", "method": "etoken-google", "sum": { "amount": 300, "currency": "USD" }, "description": "payment" }, "account": { "number": "431422******0056" }, "recurring": { "id": 1000030038, "currency": "USD", "valid_thru": "-0001-11-30T00:00:00+0000" }, "operation": { "id": 1000034, "type": "recurring", "status": "success", "date": "2018-11-20T08:44:46+0000", "created_date": "2018-11-20T08:44:41+0000", "request_id": "07fd7ade7cf010", "sum_initial": { "amount": 300, "currency": "USD" }, "sum_converted": { "amount": 300, "currency": "USD" }, "provider": { "id": 1381, "payment_id": "2548950091", "date": "2020-11-20T08:44:45+0000", "auth_code": "" }, "code": "0", "message": "Success" }, "signature": "x2tsnvLCRyr9a8+I3RipuPWUod5c89cDSQ6cRq...==" } ``` ### Useful links {#section_xpz_thl_ggb .section} The following articles can be useful when implementing purchases via Payment Page: - [Interaction concepts](en_pp_interaction_organisation.md)—about the interaction with the payment platform by using Payment Page. - [Signature generation and verification](en_platform_signature.md)—about the procedure of generating and verifying signatures in requests and callbacks. - [Payment processing](en_platform_payment_model.md)—about the types, processing models, and possible statuses of supported payments and operations. - [Handling operation processing information](en_platform_payment_info_codes.md)—about error and response codes that are used in the payment platform to record information about performing of operations. ## COF purchases by using Gate {#en_pm_googlepay_gate_recurring} ### General information {#section_lsx_3jl_ggb .section} The Google Pay payment method provides the ability to perform COF purchases—regular on-demand payments. For more information about COF purchases, see [On-demand COF purchase](en_platform_recurring_model.md). Information about the formats of requests and callbacks used for processing payments by using the Google Pay method via Gate is presented further in this section. General information about working with the Gate API is presented in [Interaction concepts](en_gate_interaction_organisation.md). ### COF purchase registration {#section_qhf_wsn_j3b .section} To register a COF purchase by using Gate, the merchant is required to send a request for purchase with all the required parameters \(including the `register` parameter of the `recurring` object, set to the value `true`\) to the Ecommpay URL and get the callback with the payment result from the payment platform. To register a regular payment the request should also contain information about the frequency, amount, start and end dates of regular payments. The COF purchase registration callback contains its identifier, which can be used to process or cancel regular payments. For more information about purchase processing by using Gate, see [One-time purchases by using Gate](pm_googlepay.md). ### Format of requests for registration of COF purchases {#section_osx_3jl_ggb .section} There are several things you need to consider when sending requests for registering COF purchases by using the Google Pay method: 1. To register each COF purchase, send a separate POST request to one of the following endpoints [/v2/payment/googlepay/sale](https://api-developers.ecommpay.com/api-specification/google-pay/post-v2-payment-googlepay-sale) or [/v2/payment/googlepay/auth](https://api-developers.ecommpay.com/api-specification/google-pay/post-v2-payment-googlepay-auth). 2. The following objects and parameters must be specified in the request: - Object `general`—general purchase information: - `project_id`—project identifierobtained from Ecommpay during integration - `payment_id`—payment identifierunique within the project - `signature`—request signaturegenerated after all required parameters are specified \(details—in the [Signature generation and verification](en_platform_signature.md)\) - Object `payment`—payment information: - `amount`—payment amount in the smallest currency unit - `currency`—payment currency codein the ISO-4217 alpha-3 format - `cryptocurrency_type`—the indicator that specifies the type of the cryptocurrency, required for Mastercard and Visa payments involving cryptocurrencies. This parameter should be assigned one of the following values: - `cbdc`—a central bank digital currency or tokenized deposit issued by a central bank, reserve bank, or other national monetary authority; - `stablecoins_fiat_backed`—a fiat-backed digital asset with reserves held by a licensed financial institution; - `native_tokens`—a digital currency native to a specific blockchain, required for transactions within its network, including fee payments; - `other`—a non-fiat digital asset that does not fit other types or cannot be classified at the time of transaction initiation. - Object `customer`—customer information: - `id`—customer identifierunique within the project - `ip_address`—customer IP addressrelevant for the initiated payment - Object `recurring`—COF purchase information: - `register`—payment registration as a COF purchase - `type`—type of the COF purchase: `R` \(for Regular payment\), `C` \(for OneClick payment\), or `U` \(for Autopayment\), for more information, refer to [Overview](en_Gate__saved_cards_payments_type.md) - `scheduled_payment_id`—identifier assigned to the payment within which scheduled debits are performed; it must differ from the identifier of the payment made to register a COF purchase and must be unique within the project - `start_date`—the start date of regular payments, in the `DD-MM-YYYY` format \(must be at least one day later than the date of registration\) - `amount`—amount of debiting - `period`—regular payment performing period - `interval`— regular payment performing interval - `time`—regular payment performing time in the `hh:mm:ss (UTC0)` format 3. Additionally, any other parameters included in the specification can be used. Thus, a correct COF purchase registration request by using the Google Pay method must contain the project identifier, basic payment information \(identifier, amount, and currency code\), customer identifier and IP address, the registration parameter and the conditions for regular payments, as well as signature. ```language-javascript { "general": { "project_id": 208, "payment_id": "TEST_15427007172789", "signature": "DH0v2pZnkK9hwytQ6/ZtDSQh+wwx/OqrWdbltzO5GMSkzd0Iq6lM2...==", }, "customer": { "id": "123", "ip_address": "192.0.2.0" }, "payment": { "amount": 1000, "currency": "USD" }, "recurring": { "register": true, "type": "R", "amount": 1000, "interval": 1, "cycle": "week", "start_date": "21-11-2018" } } ``` ### Format of requests for COF purchase processing {#section_isb_3xn_j3b .section} After the payment is registered, the funds are debited according to the specified regular payment conditions. You initiate COF purchase by sending a `recurring` request to the payment platform. There are several things you must consider when processing COF purchases performing by using the Google Pay method: - To process each COF purchase, send a separate POST request to one of the following endpoints: - [/v2/payment/googlepay/recurring](https://api-developers.ecommpay.com/api-specification/google-pay/post-v2-payment-googlepay-recurring)—when the service code of the method is specified as `etoken-google` in the callback containing information about a registered COF purchase - [/v2/payment/card/recurring](https://api-developers.ecommpay.com/api-specification/card-payments/post-v2-payment-card-recurring)—when the service code of the method is specified as `card` in the callback containing information about a registered COF purchase - The following objects and parameters must be specified in the request: - Object `general`—general purchase information: - `project_id`—project identifierobtained from Ecommpay during integration - `payment_id`—payment identifierunique within the project - `signature`—request signaturegenerated after all required parameters are specified \(details—in the [Signature generation and verification](en_platform_signature.md)\) - Object `payment`—payment information: - `amount`—payment amount in the smallest currency unit - `currency`—payment currency codein the ISO-4217 alpha-3 format - `cryptocurrency_type`—the indicator that specifies the type of the cryptocurrency, required for Mastercard and Visa payments involving cryptocurrencies. This parameter should be assigned one of the following values: - `cbdc`—a central bank digital currency or tokenized deposit issued by a central bank, reserve bank, or other national monetary authority; - `stablecoins_fiat_backed`—a fiat-backed digital asset with reserves held by a licensed financial institution; - `native_tokens`—a digital currency native to a specific blockchain, required for transactions within its network, including fee payments; - `other`—a non-fiat digital asset that does not fit other types or cannot be classified at the time of transaction initiation. - Object `customer`—customer information: - `id`—customer identifierunique within the project - `ip_address`—customer IP addressrelevant for the initiated payment - Object `recurring`—COF purchase information: - `id`—registered COF purchase identifier - Additionally, any other parameters included in the specification can be used. Thus, a correct purchase request by using the Google Pay method must contain the project identifier, basic payment information \(identifier, amount, and currency code\), customer identifier and IP address, COF purchase identifier, as well as signature. ```language-javascript { "general": { "project_id": 208, "payment_id": "TEST_15427007172789", "signature": "DH0v2pZnkK9hwytQ6wx/OqrWdbltzO5GMSkzd0Iq6lM2...==", }, "customer": { "id": "123", "ip_address": "192.0.2.0" }, "payment": { "amount": 1000, "currency": "USD" }, "recurring": { "id": 1234567890 } } ``` ### Format of request for cancellation of COF purchases {#section_rrj_cyj_k3b .section} Until the expiration date of COF purchases performing, you can cancel it. Also, to change the conditions of COF purchases, you must cancel it and send a request to register a new one. There are several things you must consider when cancelling COF purchases by using the Google Pay method: 1. To cancel each purchase, send a separate POST request to one of the following endpoints: - [/v2/payment/googlepay/recurring/cancel](https://api-developers.ecommpay.com/api-specification/google-pay/post-v2-payment-googlepay-recurring-cancel)—when the service code of the method is specified as `etoken-google` in the callback containing information about a registered COF purchase - [/v2/payment/card/recurring/cancel](https://api-developers.ecommpay.com/api-specification/card-payments/post-v2-payment-card-recurring-cancel)—when the service code of the method is specified as `card` in the callback containing information about a registered COF purchase 2. Each request must include the following objects and parameters: - Object `general`—general purchase information: - `project_id`—project identifierobtained from Ecommpay during integration - `payment_id`—payment identifierunique within the project - `signature`—request signaturegenerated after all required parameters are specified \(details—in the [Signature generation and verification](en_platform_signature.md)\) - Object `recurring`—COF purchase information: - `id`—registered COF purchase identifier 3. Additionally, any other parameters included in the specification can be used. Thus, a correct purchase request by using the Google Pay method must contain the project, payment and COF purchase identifiers, as well as signature. ```language-javascript { "general": { "project_id": 208, "payment_id": "TEST_15427007172789", "signature": "DH0v2pZnkK9hwytQ6/ZtDzO5GMSkzd0Iq6lM2v8...==", }, "recurring": { "id": 1234567890 } } ``` ### Callback format {#section_wsx_3jl_ggb .section} The standard format for callbacks is used to deliver the results of actions with COF purchases. For more information, see [Handling callbacks](en_platform_callbacks.md). The following is the example of a callback with an information about a COF purchase registration for a customer in the `208` project. The title of the payment method is specified as `etoken-google` in the `payment.method` parameter. ```language-json { "project_id": 208, "payment": { "id": "payment", "type": "recurring", "status": "success", "date": "2018-11-20T08:44:46+0000", "method": "etoken-google", "sum": { "amount": 300, "currency": "USD" }, "description": "payment" }, "account": { "number": "431422******0056" }, "recurring": { "id": 1000030038, "currency": "USD", "valid_thru": "-0001-11-30T00:00:00+0000" }, "operation": { "id": 1000034, "type": "recurring", "status": "success", "date": "2018-11-20T08:44:46+0000", "created_date": "2018-11-20T08:44:41+0000", "request_id": "07fd7ade7cf010", "sum_initial": { "amount": 300, "currency": "USD" }, "sum_converted": { "amount": 300, "currency": "USD" }, "provider": { "id": 1381, "payment_id": "2548950091", "date": "2020-11-20T08:44:45+0000", "auth_code": "" }, "code": "0", "message": "Success" }, "signature": "x2tsnvLCRXZMyr9a8+I3RipuPWUod5c89cDSQ6cRq...==" } ``` The following is the example of a callback after COF purchase cancellation. ```language-json { "project_id": 208, "payment": { "id": "payment", "type": "recurring", "status": "success", "date": "2018-11-20T08:44:46+0000", "method": "etoken-google", "sum": { "amount": 300, "currency": "USD" }, "description": "payment" }, "account": { "number": "431422******0056" }, "recurring": { "id": 1000030038, "currency": "USD", "valid_thru": "-0001-11-30T00:00:00+0000" }, "operation": { "id": 1000034, "type": "recurring_cancel", "status": "success", "date": "2018-11-20T08:44:46+0000", "created_date": "2018-11-20T08:44:41+0000", "request_id": "07fd7ade7cf010", "sum_initial": { "amount": 300, "currency": "USD" }, "sum_converted": { "amount": 300, "currency": "USD" }, "provider": { "id": 1381, "payment_id": "2548950091", "date": "2020-11-20T08:44:45+0000", "auth_code": "" }, "code": "0", "message": "Success" }, "signature": "x2tsnvLCRXa8+I3RipuPWUod5c89cDSQ6cRq...==" } ``` The following is the example of a callback with an information about a declined registration of a COF purchase. ```language-json { "project_id": 208, "payment": { "id": "payment", "type": "recurring", "status": "success", "date": "2018-11-20T08:44:46+0000", "method": "etoken-google", "sum": { "amount": 300, "currency": "USD" }, "description": "payment" }, "errors": [ { "code": "2701", "message": "Rules Failed Code", "description": "fatal: RULES_FAILED_CODE" } ], "recurring": { "id": 1000700, "currency": "USD", "valid_thru": "-0001-11-30T00:00:00+0000" }, "operation": { "id": 1000034, "type": "recurring", "status": "decline", "date": "2018-11-20T08:44:46+0000", "created_date": "2018-11-20T08:44:41+0000", "request_id": "07fd7ade7cf010", "sum_initial": { "amount": 300, "currency": "USD" }, "sum_converted": { "amount": 300, "currency": "USD" }, "provider": { "id": 1381, "payment_id": "2548950091", "date": "2020-11-20T08:44:45+0000", "auth_code": "" }, "code": "2701", "message": "Rules Failed Code" }, "signature": "x2tsnvLCRXZMX8Kwyr9a8+I3RipuPWUod5c89cDSQ6cRq...==" } ``` ### Useful links {#section_xsx_3jl_ggb .section} The following articles can be useful when implementing purchases via Gate: - [Interaction concepts](en_gate_interaction_organisation.md)—about the interaction with the payment platform by using Gate. - [Signature generation and verification](en_platform_signature.md)—about the procedure of generating and verifying signatures in requests and callbacks. - [Payment processing](en_platform_payment_model.md)—about the types, processing models, and possible statuses of supported payments and operations. - [Handling operation processing information](en_platform_payment_info_codes.md)—about error and response codes that are used in the payment platform to record information about performing of operations. ## Refunds by using Gate {#en_pm_googlepay_gate_refund} ### General information {#section_lsx_3jl_ggb .section} To perform a refund through Gate by using the Google Pay method, send a request with all required parameters and signature to the Ecommpay URL and receive a callback with the result.The full sequence and special aspects of refund performing are provided below. ![](images/pm/eng_googlepay_uml_gate_refund.svg) 1. A customer initiates a refund. 2. The web service sends the request for performing the refund by using Gate to the specified Ecommpay URL. 3. The payment platform receives the request. 4. The payment platform validates the required parameters and signature in the request. 5. The payment platform sends the response to the web service with information about the receipt of the request and its validity \([details](en_gate_interaction_organisation.md)\). 6. The payment platform performs further processing of the request \(with parameter consistency check\) and sends it to the card organisation service. 7. The refund is processed on the side of the card organisation service. 8. The card organisation service sends the result notification to the payment platform. 9. The payment platform sends the result callback to the web service. 10. The customer receives the refund result information from the web service. Information about the formats of requests and callbacks used for performing refunds by using the Google Pay method via Gate is presented further in this section. General information about working with the Gate API is presented in [Interaction concepts](en_gate_interaction_organisation.md). ### Request format {#section_osx_3jl_ggb .section} There are several things you need to consider when sending refund requests by using the Google Pay method: 1. To initiate each refund, send a separate POST request to one of the following endpoints: - [/v2/payment/googlepay/refund](https://api-developers.ecommpay.com/api-specification/google-pay/post-v2-payment-googlepay-refund)—when the service code of the method is specified as `etoken-google` in the callback containing information about a registered COF purchase - [/v2/payment/card/refund](https://api-developers.ecommpay.com/api-specification/card-payments/post-v2-payment-card-refund)—when the service code of the method is specified as `card` in the callback containing information about a registered COF purchase 2. The following objects and parameters must be specified in any request: - Object `general`—general refund information: - `project_id`—project identifierobtained from Ecommpay during integration - `payment_id`—identifier of the payment that needs to be refunded - `signature`—request signaturegenerated after all required parameters are specified \(details—in the [Signature generation and verification](en_platform_signature.md)\) - Object `payment`—refund information: - `description`—refund description or comment - `amount`—refund amount in the smallest currency unit \(required for a partial refund\) - `currency`—refund currency codein the ISO-4217 alpha-3 format \(required for a partial refund\) - Object `customer`—customer information: - `ip_address`—customer IP addressrelevant for the initiated refund 3. Additionally, any other parameters included in the specification can be used. Thus, a correct refund request by using the Google Pay method must contain the project and payment identifiers, description of the refund, the customer IP address, signature, and, if necessary, currency code and refund amount. ```language-json { "general": { "project_id": 210, "payment_id": "test_payment", "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA==" }, "payment": { "description": "test refund", "amount": 1000, "currency": "USD" }, "customer": { "ip_address": "192.0.2.0" } } ``` ```language-json { "general": { "project_id": 210, "payment_id": "test_payment", "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA==" }, "payment": { "description": "test refund", "amount": 1000, "currency": "USD" }, "customer": { "ip_address": "192.0.2.0" } } ``` ### Callback format {#section_wsx_3jl_ggb .section} The Google Pay method uses the standard format for callbacks to deliver refund results. For more information, see [Handling callbacks](en_platform_callbacks.md). The following is the example of a callback with an information about a `30,00 USD` refund for the customer account `541333******0019` in the `208` project. The service code of the payment method can be specified as `etoken-google` or `card`, depending on the purchase for which the refund is processed. ```language-json { "project_id": 208, "payment": { "id": "TEST_123456", "type": "purchase", "status": "refunded", "date": "2020-03-30T08:54:23+0000", "method": "etoken-google", "sum": { "amount": 0, "currency": "USD" }, "description": "payment for 30.0 USD" }, "account": { "number": "541333******0019", "type": "mastercard", "card_holder": "LEE OONG", "expiry_month": "09", "expiry_year": "2020" }, "customer": { "id": "907680850" }, "operation": { "id": 57299000036261, "type": "refund", "status": "success", "date": "2020-03-30T08:54:24+0000", "created_date": "2020-03-30T08:54:22+0000", "request_id": "122809a-c43c08a4b6ee7d73bfaaf7f", "sum_initial": { "amount": 3000, "currency": "USD" }, "sum_converted": { "amount": 3000, "currency": "USD" }, "code": "0", "message": "Success", "provider": { "id": 120, "payment_id": "353197036", "auth_code": "000000", "endpoint_id": 120, "date": "2020-03-30T08:54:23+0000" } }, "signature": "8y41YTzCAy0N/mV+tkJmB6OsGYLUYAyAIp3U/3x7jymU...==" } ``` The following is the example of a callback with information about a declined refund. ```language-json { "project_id": 208, "payment": { "id": "TEST_1234567", "type": "purchase", "status": "success", "date": "2020-03-27T17:41:04+0000", "method": "etoken-google", "sum": { "amount": 2000, "currency": "EUR" }, "description": "35121367" }, "account": { "number": "541333******0019", "type": "mastercard", "card_holder": "LEE OONG", "expiry_month": "09", "expiry_year": "2028" }, "customer": { "id": "LEE OONG" }, "operation": { "id": 42809000016421, "type": "refund", "status": "decline", "date": "2020-03-27T17:41:04+0000", "created_date": "2020-03-27T17:41:03+0000", "request_id": "b869d91-ff913d9c5ae5ba1bb6c3457c30e91", "sum_initial": { "amount": 1400, "currency": "EUR" }, "sum_converted": { "amount": 1400, "currency": "EUR" }, "code": "10000", "message": "General decline" }, "signature": "8ql4yC3p2RiYbNXN15+64voxMYBrBQJmcKmL...==" } ``` ### Useful links {#section_xsx_3jl_ggb .section} The following articles can be useful when implementing refunds via Gate: - [Interaction concepts](en_gate_interaction_organisation.md)—about the interaction with the payment platform by using Gate. - [Signature generation and verification](en_platform_signature.md)—about the procedure of generating and verifying signatures in requests and callbacks. - [Payment processing](en_platform_payment_model.md)—about the types, processing models, and possible statuses of supported payments and operations. - [Purchase refunds](en_Gate_Refund.md)—about performing of refunds by using Gate. - [Handling operation processing information](en_platform_payment_info_codes.md)—about error and response codes that are used in the payment platform to record information about performing of operations. ## Payouts by using Gate {#en_pm_googlepay_gate_payout} ### General information {#section_lsx_3jl_ggb .section} To process a payout through Gateby using the Google Pay method, send a request with all required parameters and signature to the Ecommpay URL and receive a callback with the result.The full sequence and special aspects of payout processing are provided below. ![](images/pm/en_googlepay_uml_gate_payout.svg) 1. A customer initiates a payout by using the Google Pay method in the web service. 2. The web service sends the request for processing the payout by using Gate to the specified Ecommpay URL. 3. The payment platform receives the request. 4. The payment platform validates the required parameters and signature in the request. 5. The payment platform sends the response to the web service with information about the receipt of the request and its validity \([details](en_gate_interaction_organisation.md)\). 6. The payment platform performs further processing of the request \(with parameter consistency check\) and sends it to the card organisation service. 7. The payout is processed on the side of the card organisation service. 8. The card organisation service sends the result notification to the payment platform. 9. The payment platform sends the result callback to the web service. 10. The customer receives the payout result information from the web service. Information about the formats of requests and callbacks used for processing payouts by using the Google Pay method via Gate is presented further in this section. General information about working with the Gate API is presented in [Interaction concepts](en_gate_interaction_organisation.md). ### Request format {#section_osx_3jl_ggb .section} There are several things you need to consider when sending payout requests by using the Google Pay method: 1. To initiate each payout send a separate POST request to the [/v2/payment/card/payout/token](https://api-developers.ecommpay.com/api-specification/card-payments/post-v2-payment-card-payout-token) endpoint. 2. Each request must include the following objects and parameters: - Object `general`—general payout information: - `project_id`—project identifierobtained from Ecommpay during integration - `payment_id`—payment identifierunique within the project - `signature`—request signaturegenerated after all required parameters are specified \(details—in the [Signature generation and verification](en_platform_signature.md)\) - Object `payment`—payment information: - `amount`—payout amount in the smallest currency unit - `currency`—payout currency codein the ISO-4217 alpha-3 format - Object `customer`—customer information: - `id`—customer identifierunique within the project - `first_name`—customer first name - `middle_name`—customer middle name or patronymic - `last_name`—customer last name - `ip_address`—customer IP addressrelevant for the initiated payout - Object `card`—card information: - `card_holder`—full name of the cardholder - `token`—token of the card received from Ecommpay in the parameter included in a callback with information about a processed purchase. 3. In the case of a payout to Visa card issued in Canada, the request must contain the `recipient` object with the payout recipient's address data: - `country`—recipient's country code in ISO 3166-1 alpha-2 - `city`—recipient's city - `address`—recipient's address - if the specified country code is [CA](references/en/countries/CA.md) or [US](references/en/countries/US.md), also pass the `state` parameter that provides information about the recipient's state, province, or any other region 4. In the case of a payout processed as part of the Visa Money Transfer program to a card issued in Brazil or Qatar, the request must contain the sender's phone number in the `phone` parameter of the `sender` object. 5. In the case of a payout that originates from a physical person and that is processed as part of the programs supported for the Mastercard MoneySend service, the request must contain the information about the payout recipient's name in the `first_name` and `last_name` parameters of the `recipient` object and the information about the payout sender in the `sender` object: - number of the sender's payment instrument—`pan` for the sender's card or `wallet_id` for the sender's electronic wallet - `first_name`—sender's first name - `last_name`—sender's last name - `address`—sender's address - `city`—sender's city - `zip`—sender's postal code - `country`—sender's country code in ISO 3166-1 alpha-2 - if the specified country code is [CA](references/en/countries/CA.md) or [US](references/en/countries/US.md), also pass the `state` parameter that provides information about the sender's state, province, or any other region 6. Additionally, any other parameters included in the specification can be used. Thus, a correct payout request by using the Google Pay method must contain the project identifier, basic payment information \(identifier, amount, and currency code\), customer information, full name of the card holder, as well as token and signature. ```language-json { "general": { "project_id": 210, "payment_id": "test_payment", "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA==" }, "payment": { "amount": 1000, "currency": "USD" }, "customer": { "id": "customer123", "first_name": "John", "middle_name": "Jr", "last_name": "Jonson", "ip_address": "192.0.2.0" }, "card": { "card_holder": "John Johnson" }, "token": "a989f5ef7ab159dd5c3016eee7563736f" } ``` ```language-json { "general": { "project_id": 210, "payment_id": "test_payment", "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA==" }, "payment": { "amount": 1000, "currency": "USD" }, "customer": { "id": "customer123", "first_name": "John", "middle_name": "Jr", "last_name": "Jonson", "ip_address": "192.0.2.0" }, "card": { "card_holder": "John Johnson" }, "token": "a989f5ef7ab159dd5c3016eee7563736f" } ``` ### Callback format {#section_dpx_2hl_ggb .section} The Google Pay method uses the standard format for callbacks to deliver payout results. For more information, see [Handling callbacks](en_platform_callbacks.md). The following is the example of a callback with information about a `1.00 EUR` payout made in the `123` project. ```language-json { "payment": { "method": "card", "sum": { "amount": 100, "currency": "EUR" }, "id": "test_id", "type": "payout", "status": "success", "date": "2023-11-07T07:37:27+0000", "description": "Test payout" }, "customer": { "id": "Test", "ip": "192.0.2.0", "first_name": "Test", "last_name": "Test" }, "account": { "number": "1234******4567", "token": "a9608ce50413260e4201d13dbfcdc75", "type": "visa", "card_holder": "TEST TEST", "expiry_month": "01", "expiry_year": "2031" }, "project_id": 123, "rrn": "331140338636", "testdebet": "credit", "opeation": { "last_processor_message": "Success" }, "operation": { "created_date": "2023-11-07T07:37:22+0000", "request_id": "d22a4c02f61ed9a82140045-00049491", "sum_initial": { "amount": 100, "currency": "EUR" }, "sum_converted": { "amount": 100, "currency": "EUR" }, "code": "0", "message": "Success", "provider": { "id": 414, "payment_id": "0040000018267721", "auth_code": "408112", "endpoint_id": 414, "date": "2023-11-07T07:37:24+0000" }, "id": 49490010084733, "type": "payout", "status": "success", "date": "2023-11-07T07:37:27+0000" }, "signature": "TL2BLpOE/xAVCmYf8SIUXYqmlF1WHtaHQ==" } ``` The following is the example of a callback with information about a declined payout. ```language-json { "payment": { "method": "card", "sum": { "amount": 100, "currency": "EUR" }, "id": "test_id", "type": "payout", "status": "decline", "date": "2023-11-07T07:38:27+0000", "description": "Test payout" }, "customer": { "id": "Test", "ip": "192.0.2.0", "first_name": "Test", "last_name": "Test" }, "account": { "number": "1234******4567", "token": "a9608ce50413260e4201d13dbfcdc75", "type": "visa", "card_holder": "TEST TEST", "expiry_month": "01", "expiry_year": "2031" }, "project_id": 123, "rrn": "", "testdebet": "credit", "opeation": { "last_processor_message": "Decline" }, "operation": { "created_date": "2023-11-07T07:38:22+0000", "request_id": "d22a4c02f61ed9a82140045-00049492", "sum_initial": { "amount": 100, "currency": "EUR" }, "sum_converted": { "amount": 100, "currency": "EUR" }, "code": "20000", "message": "General decline", "provider": { "id": 414, "payment_id": "0040000018267721", "auth_code": "", "endpoint_id": 414, "date": "2023-11-07T07:38:24+0000" }, "id": 49490010084733, "type": "payout", "status": "decline", "date": "2023-11-07T07:38:27+0000" }, "signature": "TL2BLpOE/xAVCmYf8SIUXYqmlF1WHtaHA==" } ``` ### Useful links {#section_xsx_3jl_ggb .section} The following articles can be useful when implementing payouts via Gate: - [Interaction concepts](en_gate_interaction_organisation.md)—about the interaction with the payment platform by using Gate. - [Signature generation and verification](en_platform_signature.md)—about the procedure of generating and verifying signatures in requests and callbacks. - [Payment processing](en_platform_payment_model.md)—about the types, processing models, and possible statuses of supported payments and operations. - [Payouts](en_Gate_payout.md)—about processing of payouts by using Gate. - [Handling operation processing information](en_platform_payment_info_codes.md)—about error and response codes that are used in the payment platform to record information about performing of operations. ## Payouts by using Dashboard {#en_pm_googlepay_dash_payout} When working with Dashboard, you can process payoutsby using the Google Pay method using batch requests.Each batch can contain one or more payout requests. To process a number of payouts, prepare and upload a file with information about all target payouts, send a batch request, and verify that the payouts have been processed. Use a CSV file structured according to the requirements presented in the [Mass payments data](en_dbl_payments.md) section.The payout parameters must comply with the [requirements](pm_googlepay.md) \(you do not have to generate a signature because it is specified by Dashboard\). More information about processing payouts by using Dashboard is presented in a [separate section](en_dbl_payments.md). ## Payment card verification {#en_pm_googlepay_acc_ver} ### General information {#section_lsx_3jl_ggb .section} To perform a payment card verification through the Google Pay method, merchant's web service sends a request with all the required parameters and signature to Ecommpay URL, and receives a callback with the result. Payment card verification processing for this method is the same as standard processing sequence which is provided in the section [Payment instrument verification](en_gate_account_verification.md). ### Format of request for payment card verification {#section_osx_3jl_ggb .section} There are several things you need to consider when sending payment card verification requests by using the Google Pay method: 1. To initiate each verification, send a separate POST request to the [/v2/payment/googlepay/account\_verification](https://api-developers.ecommpay.com/api-specification/google-pay/post-v2-payment-googlepay-account-verification) endpoint. 2. Each request must include the following objects and parameters: - Object `general`—general purchase information: - `project_id`—project identifierobtained from Ecommpay during integration - `payment_id`—payment identifierunique within the project - `signature`—request signaturegenerated after all required parameters are specified \(details—in the [Signature generation and verification](en_platform_signature.md)\) - Object `payment`—payment information: - `amount`—payment amount in the smallest currency unit - `currency`—payment currency codein the ISO-4217 alpha-3 format - Object `customer`—customer information: - `id`—customer identifierunique within the project - `ip_address`—customer IP addressrelevant for the initiated payment - `etoken`—token received from the Google Pay information: - `token`—token received from the Google Pay after customer identification 3. The payment amount must be zero. 4. Additionally, any other parameters included in the specification can be used. Thus, a correct purchase request by using the Google Pay method must contain the project identifier, basic payment information \(identifier, amount, and currency code\), customer identifier and IP address, Google Pay token information, as well as signature. ```language-json { "general": { "project_id": 238, "payment_id": "TEST_15427033321774", "signature": "96c+hWk1zweuGKwDRrl+DZrjJXZw7ew6ow3RpGYv4U...==" }, "customer": { "ip_address": "192.0.2.0" }, "payment": { "amount": 0, "currency": "USD" }, "etoken": { "token": "..." } } ``` ```language-json { "general": { "project_id": 238, "payment_id": "TEST_15427033321774", "signature": "96c+hWk1zweuGKwDRrl+DZrjJXZw7ew6ow3RpGYv4U...==" }, "customer": { "ip_address": "192.0.2.0" }, "payment": { "amount": 0, "currency": "USD" }, "etoken": { "token": "..." } } ``` ### Callback format {#section_wsx_3jl_ggb .section} The Google Pay method uses the standard format for callbacks to deliver results. For more information, see [Payment instrument verification](en_gate_account_verification.md). ### Useful links {#section_xsx_3jl_ggb .section} The following articles can be useful when implementing purchases via Gate: - [Interaction concepts](en_gate_interaction_organisation.md)—about the interaction with the payment platform by using Gate. - [Signature generation and verification](en_platform_signature.md)—about the procedure of generating and verifying signatures in requests and callbacks. - [Payment processing](en_platform_payment_model.md)—about the types, processing models, and possible statuses of supported payments and operations. - [One-time one-step purchase](en_platform_sms_model.md)—about processing of one-time one-step purchases by using Gate. - [Handling operation processing information](en_platform_payment_info_codes.md)—about error and response codes that are used in the payment platform to record information about performing of operations. ## Testing {#en_pm_googlepay_testing} ### General information {#section_zqw_xfw_xjb .section} For the Google Pay method, it is possible to test one-step and two-step purchases by using Payment Page and Gate, as well as payment card verification by using Gate. To enable and disable testing, as well getting assistance with setting up a test project, refer to Ecommpay technical support. When performing a test payment, take into account that you must specify the identifier of the test project in the requests, and the interfaces of the payment forms emulator of Payment Page and the 3‑D Secure 2 authentication page may differ from the production environment. At the same time to process a test payment it is necessary to use verified payment cards previously registered in the Google Pay service. This does not influence the processing of real payments by using such cards, but allows to perform full-fledged testing. In order to test purchases by using Gate it is necessary to prepare the web-service for interaction with the Google service \(more information is presented in the section [One-time purchases by using Gate](pm_googlepay.md)\). ### Statuses of test payment and operations {#section_j1z_1s5_zjb .section} The final status of test payments and operations is determined by the amount specified in the request. Test one-step and two-step purchases: - `1000` amount to get the `success` status - `2000`, `5000` or `10001` amount to get the `decline` status Test payment card verification: - `0` amount to get the `success` status - any other amount to get the `decline` status ### One-step purchases by using Payment Page {#section_wlk_dgw_xjb .section} To perform a test one-step purchase by using Payment Page, do the following: 1. Send a correct test request for Payment Page opening to the payment platform. 2. If the `card` or `google_pay_host` method was not specified in the request—select the method on the emulator page. 3. If the authentication page is displayed pass the 3‑D Secure 2 authentication. 4. Receive the final callback with information about the payment result. More information about processing purchases by using the Google Pay method via Payment Page is provided in the [One-time purchases by using Payment Page](pm_googlepay.md) section. ### One-step purchases by using Gate {#section_uvm_ngw_xjb .section} To perform a test one-step purchase by using Gate, do the following: 1. Send a correct test request for purchase to the payment platform. 2. If you receive the callback with the 3‑D Secure 2 authentication redirection data: 1. Perform the redirection and pass the 3‑D Secure 2 authentication. 2. Send the payment completion request. It is required to use the cres parameter and specify the following value in the request: ``` ewogICAiYWNzUmVmZXJlbmNlTnVtYmVyIiA6ICJBQ1NFbXUyIiwKICAgImFjc1RyYW5zSUQiIDogIjAwMDAwMDAwLTAwMDUtNWE1YS04MDAwLTAxNmRiNjMzNzZlYiIsCiAgICJtZXNzYWdlVHlwZSIgOiAiQ1JlcyIsCiAgICJtZXNzYWdlVmVyc2lvbiIgOiAiMi4xLjAiLAogICAidGhyZWVEU1NlcnZlclRyYW5zSUQiIDogIjZmMmM3OGFkLTFjOWMtNTI2ZC04MDAwLTAwMDAwMDAwMTA2YiIsCiAgICJ0cmFuc1N0YXR1cyIgOiAiWSIKfQ ``` 3. Receive the final callback with information about the payment result. More information about processing purchases by using the Google Pay method via Gate is provided in the [One-time purchases by using Gate](pm_googlepay.md) section. ### One-step purchases by performing authorization hold via Payment Page and capture or cancellation via Gate {#section_w25_jkz_cqb .section} To perform a test one-step purchase by performing authorization hold via Payment Page and capture or cancellation via Gate, do the following: 1. Send a correct test request for Payment Page opening to the payment platform. 2. If the `card` or `google_pay_host` method was not specified in the request—select the method on the emulator page. 3. If the authentication page is displayed pass the 3‑D Secure 2 authentication. 4. Accept a callback with information about successful authorization hold. 5. Send a capture or cancellation request. 6. Receive the final callback with information about the result. More information about processing purchases by using the Google Pay method via Gate is provided in the [One-time purchases by using Payment Page](pm_googlepay.md) and [One-time purchases by using Gate](pm_googlepay.md) sections. ### One-step purchases by performing authorization hold and capture or cancellation via Gate {#section_jfx_3lz_cqb .section} To perform a test one-step purchase by performing authorization hold and capture or cancellation via Gate, do the following: 1. Send a correct test request for Payment Page opening to the payment platform. 2. If you receive the callback with the 3‑D Secure 2 authentication redirection data: 1. Perform the redirection and pass the 3‑D Secure 2 authentication. 2. Send the payment completion request. It is required to use the cres parameter and specify the following value in the request: ``` ewogICAiYWNzUmVmZXJlbmNlTnVtYmVyIiA6ICJBQ1NFbXUyIiwKICAgImFjc1RyYW5zSUQiIDogIjAwMDAwMDAwLTAwMDUtNWE1YS04MDAwLTAxNmRiNjMzNzZlYiIsCiAgICJtZXNzYWdlVHlwZSIgOiAiQ1JlcyIsCiAgICJtZXNzYWdlVmVyc2lvbiIgOiAiMi4xLjAiLAogICAidGhyZWVEU1NlcnZlclRyYW5zSUQiIDogIjZmMmM3OGFkLTFjOWMtNTI2ZC04MDAwLTAwMDAwMDAwMTA2YiIsCiAgICJ0cmFuc1N0YXR1cyIgOiAiWSIKfQ ``` 3. Accept a callback with information about successful authorization hold. 4. Send a capture or cancellation request. 5. Receive the final callback with information about the result. More information about processing purchases by using the Google Pay method via Gate is provided in the [One-time purchases by using Gate](pm_googlepay.md) section. ### Payment card verification by using Gate {#section_qwb_tlz_cqb .section} To process a test payment card verification by using Gate, send a valid test request for a verification to the payment platform and receive a final callback with information about the verification result. More information about performing payment card verification by using the Google Pay method via Gate is provided in the [Payment card verification](pm_googlepay.md) section. ## Analysis of payments results {#en_pm_googlepay_dash_analysis} To analyse information about payments made with the Google Pay method and other methods, you can use: - Dashboardinterface toolkitwith various lists and analytic panels. - Reports in CSV file format, available via the **Reports** section \(one-time and periodically\). - Data in JSON format, sent by program requests to a specified URL by using the Data API interface. If you have any questions, refer to the documentation \([Dashboard](en_dbl_about.md) and [Using Data API](en_dbl_api_protocol.md)\) and Ecommpay technical support.