Payment with user redirection to the ACS server

Information for developers is available inGoogle documentation.
The payment page must be designed in accordance with brand guidelines.

When submitting a request to Google Pay, use the following parameters:

gateway: sberbank;
gatewayMerchantId: <name of your organization in the payment gateway system> .

If, in case of payment with Google Pay, the payment page is located on the merchant's side, the interaction scheme looks as follows.

	One-phase payment	Two-phase payment
1	The customer creates an order on the website of the online store and selects Google Pay payment method.
2	The online store system generates a payment request to Google Pay payment.
3	The Google Pay system generates the encrypted payment data.
4	The online store system receives the encrypted payment data.
5	The online store system generates a request to the payment gateway for Google Pay payment, indicating the received encrypted payment data: payment.do; Notably, the `preAuth` parameter either is not passed or has the value `false`.	The online store system generates a request to the payment gateway for Google Pay payment, indicating the received encrypted payment data: REST interface payment.do; Notably, the `preAuth` parameter is passed in the request with value `true`.
6	The payment gateway decrypts the received token and checks the card whether it is tokenized or not.
7	If the card is enrolled in 3-D Secure, the payment gateway sends a response to the payment request that contains a redirect link to the ACS server.
8	The user is redirected to the ACS website. There are two ways to redirect to ACS: normal and lightweight (see below). Standard To redirect to ACS the merchant must send to the customer to the address specified in the acsUrl parameter with the request body MD=mdorder&PaReq=pareq&TermUrl=redirect, where: `mdOrder` – unique order number in the payment gateway system, `pareq` – parameter from the response to the payment request, `redirect`- parameter from the response to the payment request (URL user is to be redirected to from ACS). The request must be in POST format. Depending on the connection scheme used, the Customer after being authenticated on ACS will be redirected to the Payment Gateway or to the Store. Simplified In order for the Customer to get to the ACS page, the Merchant redirects him to the Payment Gateway page with the following URL pattern: `https://api.3dsec.sberbank.ru/payment/acsRedirect.do?orderId=<order number>` where «<order number>» is the unique number of the Customer's order. Please remember to include api. before the domain name. Next, the Payment Gateway redirects the Customer (without additional actions on the part of the Customer) to the ACS of the bank, where the Customer is authenticated.
9	The user goes to the ACS site and authenticates.
10	After successful authentication, the user is redirected from the ACS website to the payment gateway page.
11	The user goes to the payment gateway page.
12	The payment gateway returns the payment result.
13	The Merchant requests from the Payment Gateway the status of order payment: getOrderStatusExtended.do.
14	Not applicable	To debit funds from the Customer's account, the Merchant needs to send to the Payment Gateway an order completion request: deposit.do.
15	Not applicable	The payment gateway returns the result of processing the request. The order status is not returned. To get the status of the order, an order status request should be sent to the gateway: getOrderStatusExtended.do.