SberPay

Overview

Introduction

SberPay is a payment method which allows you to process payments in Russian roubles by using bank accounts in Russia. This method supports purchases and refunds. In addition, the implementation of credential-on-file purchases is in development.

This article provides information about working with the SberPay 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

Payment method type bank payments
Payment instruments bank accounts
Countries and regions RU
Payment currencies RUB
Currency conversion –
One-time purchases +
Credential-on-file purchases +
Full refunds +
Partial refunds –
Payouts –
Chargebacks –
Notes –
Onboarding and access fee refer to your EtoPlatezhi account manager

Interaction diagram

Payment processing by using the SberPay method involves the merchant's web service, one of EtoPlatezhi interfaces, the EtoPlatezhi payment platform, and technical facilities of the provider service.



Operations support

Various platform interfaces can be used to process payments and perform operations using the SberPay method. Purchases can be processed by using Payment Page, Gate and Dashboard (using payment links). At the same time, regardless of the interfaces used, amount limitations are applicable. Refer to your EtoPlatezhi account manager for more information.

Processing scenarios

To perform a purchase by using the SberPay method, you need to redirect the customer to the provider service.

Figure 1. Purchase by using Payment Page


Figure 2. Purchase 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.

Purchases by using Payment Page

General information

To process a purchase through Payment Page by using the SberPay method, the merchant's web service is required to send a request with all required parameters and signature to the EtoPlatezhi URL and receive a callback with the result. The full sequence and special aspects of purchase processing are provided below.



Figure 3. Purchase processing by using Payment Page: step-by-step description
  1. A customer initiates a purchase in the web service.
  2. The web service sends the request for opening Payment Page to the specified EtoPlatezhi 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 SberPay method.
  8. The payment platform receives the request for processing the payment by using the SberPay method.
  9. The payment platform processes the request and sends it to the provider service.
  10. The request is processed on the provider service side.
  11. The data for redirecting the customer to the provider service is sent from the provider service to the payment platform.
  12. The data for redirecting the customer is sent from the payment platform to Payment Page.
  13. The customer is redirected to the provider service.
  14. The customer completes all required payment steps.
  15. The purchase is processed in the provider service.
  16. The result information is displayed to the customer in the provider service.
  17. The customer is redirected to Payment Page.
  18. The provider 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.

Information about the formats of requests and callbacks used for processing payments by using the SberPay method via Payment Page is presented further in this section; general information about working with the Payment Page API is presented in Interaction concepts.

Request format

There are several things you need to consider when sending purchase requests by using the SberPay method:

  1. The following parameters required for any payment must be specified:
    • project_id—project identifier obtained from EtoPlatezhi 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. The following parameters required for any payment must be specified: project_id, payment_id, payment_currency, payment_amount, customer_id.
  3. Additionally, it is required to specify the phone number of the customer in the customer_account_number parameter.
  4. The currency of the payment can only be RUB.
  5. If you need to have the payment form displayed with the SberPay method selected, set the force_payment_method parameter to sberpay.
  6. Additionally, any other parameters available for working with Payment Page can be used (details).
  7. After all target parameters are specified, generate a signature (details).

Thus, a correct request for opening the payment form using the SberPay method must contain the project identifier, basic payment information (identifier, amount, and currency code), customer identifier, phone number and signature, as well as possible additional parameters.

{
   "project_id": 120,
   "payment_id": "580",
   "payment_amount": 1000,
   "payment_currency": "RUB",
   "customer_id": "customer1",
   "customer_account_number": "+71231234567",
   "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg=="
}
Figure 4. Example of sufficient data in a purchase request
{
   "project_id": 120,
   "payment_id": "580",
   "payment_amount": 1000,
   "payment_currency": "RUB",
   "customer_id": "customer1",
   "customer_account_number": "+71231234567",
   "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg=="
}

Callback format

The SberPay method uses the standard format for callbacks to deliver purchase results. For more information, see Handling callbacks (details).

The following is the example of a callback with information about a 1,000.00 RUB purchase made in the 129103 project.

Figure 5. Example of callback data indicating that the purchase has been processed
 {
        "customer": {
            "id": "f4d68g5f"
        },
        "project_id": 129103,
        "payment": {
            "id": "testtoo0003",
            "type": "purchase",
            "status": "success",
            "date": "2025-06-19T10:39:26+0000",
            "method": "sberpay",
            "sum": {
                "amount": 100000,
                "currency": "RUB"
            },
            "description": ""
        },
        "operation": {
            "sum_initial": {
                "amount": 100000,
                "currency": "RUB"
            },
            "sum_converted": {
                "amount": 100000,
                "currency": "RUB"
            },
            "code": "0",
            "message": "Success",
            "provider": {
                "id": 18301,
                "payment_id": "71b83839-4514220488",
                "auth_code": ""
            },
            "id": 5023372010140727,
            "type": "sale",
            "status": "success",
            "date": "2025-06-19T10:39:26+0000",
            "created_date": "2025-06-19T10:37:20+0000",
            "request_id": "9d8138a67b35b0402779e9f40beffd7f3-05023373"
        },
        "signature": "KmV6HLSQFVZTR3lZKYDHh5fbbraumHyfOunD9MiP+PA=="
    }
}

Useful links

The following articles can be useful when implementing purchases via Payment Page:

COF purchases by using Payment Page

General information

COF purchases using SberPay is a way of making COF purchases with debit requests or making recurring transactions using stored credentials. For more information about COF purchases, see On-demand COF purchase. Registration of a COF purchases is 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 EtoPlatezhi 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.

Information about the formats of requests used for processing payments by using the SberPay method via Payment Page is presented further in this section; general information about working with the Payment Page API is presented in Interaction concepts.

Request format

There are several things you need to consider when sending purchase requests for registering COF purchases by using the SberPay method:

  1. You must specify the necessary parameters required for any payment.
  2. Additionally, it is required to specify the phone number of the customer in the customer_account_number parameter.
  3. The currency of the payment can only be RUB.
  4. To register a COF purchase, you must specify a recurring object containing the registration attribute and an explanation of the nature of the services provided in the payment_description parameter.

    When using the EtoPlatezhi JavaScript library, the recurring object in such a request can constitute a JSON object that includes the register register with the value true. In other cases, the recurring object, as well as the request body as a whole, must be specified as a URL string obtained from the original JSON object using URL-encoding conversion.

  5. If you need to have the payment form displayed with the SberPay method selected, set the force_payment_method parameter to sberpay.
  6. Additionally, any other parameters available for working with Payment Page can be used (details).
  7. After all target parameters are specified, generate a signature (details).

Thus, a correct request for opening the payment form using the SberPay method must contain the project identifier, basic payment information (payment identifier, amount, and currency code), customer identifier, registration parameter and signature, as well as possible additional parameters.

{
   "project_id": 120,
   "payment_id": "580",
   "payment_amount": 100000,
   "payment_currency": "RUB",
   "customer_id": "customer1",
   "customer_account_number": "+71231234567",
   "recurring": {"register":true},
   "payment_description": "example reason",
   "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg=="
}
Figure 6. Example of sufficient data in a purchase request
{
   "project_id": 120,
   "payment_id": "580",
   "payment_amount": 100000,
   "payment_currency": "RUB",
   "customer_id": "customer1",
   "customer_account_number": "+71231234567",
   "recurring": {"register":true},
   "payment_description": "example reason",
   "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg=="
}

Useful links

The following articles can be useful when implementing purchases via Payment Page:

Purchases by using Gate

General information

To process a purchase through Gate by using the SberPay method, the merchant's web service is required to do the following:

  1. Send a request with all the required parameters and signature to the EtoPlatezhi URL.
  2. Receive an intermediate callback from the payment platform and redirect the customer to the provider service.
  3. Receive the final callback from the payment platform.

The full sequence and special aspects of purchase processing are provided below.



Figure 7. Purchase processing by using Gate: step-by-step description
  1. A customer initiates a purchase by using the SberPay method in the web service.
  2. The web service sends the request for processing the purchase by using Gate to the specified EtoPlatezhi 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).
  6. The payment platform performs further processing of the request (with parameter consistency check) and sends it to the provider service.
  7. The request is processed on the provider service side.
  8. The provider service sends the redirection data to the payment platform.
  9. The payment platform sends the callback with the redirection data to the web service.
  10. The customer is redirected to the provider service.
  11. The customer completes all required payment steps.
  12. The purchase is processed in the provider service.
  13. The result is displayed to the customer.
  14. The customer is redirected to the web service.
  15. The provider 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.

Information about the formats of requests and callbacks used for processing payments by using the SberPay method via Gate is presented further in this section. General information about working with the Gate API is presented in Interaction concepts.

Request format

There are several things you need to consider when sending purchase requests by using the SberPay method:

  1. To initiate each purchase, send a separate POST request to the /v2/payment/sberpay/sale endpoint.
  2. Each request must include the following objects and parameters:
    • Object general—general purchase information:
      • project_id—project identifier obtained from EtoPlatezhi during integration
      • payment_id—payment identifier unique within the project
      • signature—request signature generated after all required parameters are specified (details—in the Signature generation and verification) (details)
    • Object payment—payment information:
      • amount—payment amount in the smallest currency unit
      • currency—payment currency code in the ISO-4217 alpha-3 format
    • Object customer—customer information:
      • id—customer identifier unique within the project
      • ip_address—customer IP address relevant for the initiated payment
    • Object account—customer account information:
      • number—customer phone number
  3. The currency of the payment can only be RUB.
  4. Additionally, any other parameters included in the specification can be used.

Thus, a correct purchase request by using the SberPay method must contain the project identifier, basic payment information (identifier, amount, and currency code), customer identifier, IP address and phone number, signature, as well as possible additional parameters.

{
  "general": {
    "project_id": 210,
    "payment_id": "test_payment",
    "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA=="
  },
  "payment": {
    "amount": 1000,
    "currency": "RUB"
  },
  "customer": {
    "id": "customer123",
    "ip_address": "192.0.2.0"
  },
  "account": {
    "number": "+71231234567"
  }
}
Figure 8. Example of sufficient data in a purchase request
{
  "general": {
    "project_id": 210,
    "payment_id": "test_payment",
    "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA=="
  },
  "payment": {
    "amount": 1000,
    "currency": "RUB"
  },
  "customer": {
    "id": "customer123",
    "ip_address": "192.0.2.0"
  },
  "account": {
    "number": "+71231234567"
  }
}

Formats of intermediate callbacks for customer redirection

Each payment made with the SberPay method requires redirection of customers from the merchant's web service to the provider service. To redirect a customer it is necessary to receive an intermediate callback from the payment platform and use the information included in the redirect_data object. The format of such callbacks is standard (details), and the following objects and parameters are included in the redirect_data object:

  • body—object with data to be sent in the request body
  • method—parameter specifying the HTTP method for sending the request (GET or POST)
  • url—parameter containing a link for redirection
Figure 9. redirect_data example
  "redirect_data": {
    "body": {},
    "method": "GET",
    "url": "https://www.example.com/pay"
  }

Final callback format

The SberPay method uses the standard format for callbacks to deliver purchase results. For more information, see Handling callbacks (details).

The following is the example of a callback with information about a 1,000.00 RUB purchase made in the 129103 project.

Figure 10. Example of callback data indicating that the purchase has been processed
 {
        "customer": {
            "id": "f4d68g5f"
        },
        "project_id": 129103,
        "payment": {
            "id": "testtoo0003",
            "type": "purchase",
            "status": "success",
            "date": "2025-06-19T10:39:26+0000",
            "method": "sberpay",
            "sum": {
                "amount": 100000,
                "currency": "RUB"
            },
            "description": ""
        },
        "operation": {
            "sum_initial": {
                "amount": 100000,
                "currency": "RUB"
            },
            "sum_converted": {
                "amount": 100000,
                "currency": "RUB"
            },
            "code": "0",
            "message": "Success",
            "provider": {
                "id": 18301,
                "payment_id": "71b83839-4514220488",
                "auth_code": ""
            },
            "id": 5023372010140727,
            "type": "sale",
            "status": "success",
            "date": "2025-06-19T10:39:26+0000",
            "created_date": "2025-06-19T10:37:20+0000",
            "request_id": "9d8138a67b35b0402779e9f40beffd7f3-05023373"
        },
        "signature": "KmV6HLSQFVZTR3lZKYDHh5fbbraumHyfOunD9MiP+PA=="
    }
}

The following is the example of a callback with information about a declined purchase.

Useful links

The following articles can be useful when implementing purchases via Gate:

COF purchases by using Gate

General information

COF purchases using SberPay is a way of making COF purchases with debit requests or making recurring transactions using stored credentials. For more information about COF purchases, see On-demand COF purchase.

Information about the formats of requests used for processing payments by using the SberPay method via Gate is presented further in this section. General information about working with the Gate API is presented in Interaction concepts.

COF purchase registration

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 EtoPlatezhi 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. Note that if you specify any other value in the register parameter, a one-time payment will be made, and recurring payments will not be registered.

The COF purchase registration callback contains the identifier of the COF purchase, which can be used to make regular payments.

For more information about purchase processing by using Gate, see Purchases by using Gate.

Thus, a correct COF purchase registration request by using the SberPay method must contain the project identifier, basic payment information (payment identifier, amount, and currency code), customer identifier and IP address, the registration parameter and the conditions for regular payments, as well as signature.

 {
  "general": {
    "project_id": 208,
    "payment_id": "TEST_15427007172789",
    "signature": "DH0v2pZnkK9hwytOqrWdbltzO5GMSkzd0Iq6lM2...==",
  },
  "customer": {
    "ip_address": "192.0.2.0",
    "id": "123"
  },
  "payment": {
    "amount": 1000,
    "currency": "RUB",
    "description": "example reason"
  },
  "account": {
    "number": "+71231234567"
  },
  "recurring": {
    "register": true
  }
}
Figure 11. Example of sufficient data in a COF purchase registration request
 {
  "general": {
    "project_id": 208,
    "payment_id": "TEST_15427007172789",
    "signature": "DH0v2pZnkK9hwytOqrWdbltzO5GMSkzd0Iq6lM2...==",
  },
  "customer": {
    "ip_address": "192.0.2.0",
    "id": "123"
  },
  "payment": {
    "amount": 1000,
    "currency": "RUB",
    "description": "example reason"
  },
  "account": {
    "number": "+71231234567"
  },
  "recurring": {
    "register": true
  }
}

Format of requests for COF purchase processing

Once a COF payment has been registered, to initiate the recurring payment, you must send a request to the payment platform with the COF purchase ID, which you previously received in the callback after registering the COF purchase.

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 SberPay method:

  1. To process each purchase, send a separate POST request to the /v2/payment/sberpay/recurring endpoint.
  2. Each request must include the following objects and parameters:
    • Object general—general purchase information:
      • project_id—project identifier obtained from EtoPlatezhi during integration
      • payment_id—payment identifier unique within the project
      • signature—request signature generated after all required parameters are specified (details—in the Signature generation and verification) (details)
    • Object payment—payment information:
      • amount—payment amount in the smallest currency unit
      • currency—payment currency code in the ISO-4217 alpha-3 format
    • Object customer—customer information:
      • ip_address—customer IP address relevant for the initiated payment
    • Object account—customer account information:
      • number—customer phone number
    • Object recurring—COF purchase information:
      • id—registered COF purchase identifier
  3. The currency of the payment can only be RUB.
  4. Additionally, any other parameters included in the specification can be used.

Thus, a correct purchase request by using the SberPay method must contain the project identifier, basic payment information (payment identifier, amount, and currency code), customer IP address, COF purchase identifier, as well as signature.

 {
  "general": {
    "project_id": 208,
    "payment_id": "TEST_15427007172789",
    "signature": "DH0v2pZnkK9hwytQ6bltzO5GMSkzd0Iq6lM2...==",
  },
  "customer": {
    "ip_address": "192.0.2.0"
  },
  "payment": {
    "amount": 1000,
    "currency": "RUB"
  },
  "account": {
    "number": "+71231234567"
  },
  "recurring": {
    "id": 1234567890
  }
}
Figure 12. Example of sufficient data in a COF purchase processing request
 {
  "general": {
    "project_id": 208,
    "payment_id": "TEST_15427007172789",
    "signature": "DH0v2pZnkK9hwytQ6bltzO5GMSkzd0Iq6lM2...==",
  },
  "customer": {
    "ip_address": "192.0.2.0"
  },
  "payment": {
    "amount": 1000,
    "currency": "RUB"
  },
  "account": {
    "number": "+71231234567"
  },
  "recurring": {
    "id": 1234567890
  }
}

Useful links

The following articles can be useful when implementing purchases via Gate:

Refunds by using Gate

General information

To perform a refund through Gate by using the SberPay method, send a request with all required parameters and signature to the EtoPlatezhi URL and receive a callback with the result. The full sequence and special aspects of refund performing are provided below.



Figure 13. Refund performing by using Gate: step-by-step description
  1. A customer initiates a refund.
  2. The web service sends the request for performing the refund by using Gate to the specified EtoPlatezhi 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).
  6. The payment platform performs further processing of the request (with parameter consistency check) and sends it to the provider service.
  7. The refund is processed on the side of the provider service.
  8. The provider 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 SberPay method via Gate is presented further in this section. General information about working with the Gate API is presented in Interaction concepts.

Request format

There are several things you need to consider when sending refund requests by using the SberPay method:

  1. To initiate each refund, send a separate POST request to the /v2/payment/sberpay/refund endpoint.
  2. Each request must include the following objects and parameters:
    • Object general—general refund information:
      • project_id—project identifier obtained from EtoPlatezhi during integration
      • payment_id—identifier of the payment that needs to be refundedpayment identifier
      • signature—request signature generated after all required parameters are specified (details—in the Signature generation and verification)
    • Object payment—refund information:
      • description—refund description or comment
    • Object customer—customer information:
      • ip_address—customer IP address relevant for the initiated refund
  3. Additionally, any other parameters included in the specification can be used.

Thus, a correct refund request by using the SberPay method must contain the project and payment identifiers, description of the refund, the customer IP address and signature.

{
  "general": {
    "project_id": 210,
    "payment_id": "test_payment",
    "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA=="
  },
  "payment": {
    "description": "test refund"
  },
  "customer": {
    "ip_address": "192.0.2.0"
  }
}
Figure 14. Example of sufficient data in a refund request
{
  "general": {
    "project_id": 210,
    "payment_id": "test_payment",
    "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA=="
  },
  "payment": {
    "description": "test refund"
  },
  "customer": {
    "ip_address": "192.0.2.0"
  }
}

Callback format

The SberPay method uses the standard format for callbacks to deliver refund results. For more information, see Handling callbacks.

The following is the example of a callback with information about a 100.00 RUB refund made in the 1037 project.

Figure 15. Example of callback data indicating that the refund has been processed
{
    "project_id": 1037,
    "payment": {
        "id": "62153051",
        "type": "purchase",
        "status": "refunded",
        "date": "2024-06-15T13:21:51+0000",
        "method": "sberbank",
        "sum": {
            "amount": 10000,
            "currency": "RUB"
        },
        "description": "Test sale"
    },
    "customer": {
        "id": "1234"
    },
    "operation": {
        "id": 63,
        "type": "refund",
        "status": "success",
        "date": "2024-06-15T14:23:56+0000",
        "created_date": "2024-06-15T14:22:51+0000",
        "request_id": "ea2e5888a65cf1b1f2b5-00000003",
        "sum_initial": {
            "amount": 10000,
            "currency": "RUB"
        },
        "sum_converted": {
            "amount": 10000,
            "currency": "RUB"
        },
        "code": "0",
        "message": "Success",
        "provider": {
            "id": 1782,
            "payment_id": "7C035795EJ562523A",
            "date": "2024-06-15T14:23:51+0000"
        }
    },
    "signature": "uU6LOpEjEqxeqJ2GsDkDnaY+1p1m4aS5zTPkJA=="
}

The following is the example of a callback with information about a declined refund.

Figure 16. Example of callback data indicating that the refund has been declined
{
    "project_id": 1037,
    "payment": {
        "id": "59375393",
        "type": "purchase",
        "status": "success",
        "date": "2024-06-15T14:23:56+0000",
        "method": "sberbank",
        "sum": {
            "amount": 10000,
            "currency": "RUB"
        },
        "description": "Test sale"
    },
    "customer": {
        "id": "1234"
    },
    "operation": {
        "id": 84,
        "type": "refund",
        "status": "decline",
        "date": "2024-06-15T14:23:56+0000",
        "created_date": "2024-06-15T14:23:56+0000",
        "request_id": "776d5d3e602912e88858c922e34e5-00000001",
        "sum_initial": {
            "amount": 10000,
            "currency": "RUB"
        },
        "sum_converted": {
            "amount": 10000,
            "currency": "RUB"
        },
        "code": "20000",
        "message": "General decline",
        "provider": {
            "id": 1782,
            "payment_id": "",
            "date": ""  
        }
    },
    "signature": "qjVnKRZX51lrxh5kqCzurbJbQQSAeFwqH7H9gk7gUYI3A=="
}

Useful links

The following articles can be useful when implementing refunds via Gate:

Refunds by using Dashboard

When working with Dashboard, you can perform single and mass refunds by using the SberPay method.

  • To perform a single refund, select the target purchase, open its information tab, specify the amount of the refund, send a request and verify that the refund has been performed.

  • To perform a mass refund, prepare and upload a file with information about all target refunds, send a batch request, and verify that the refunds have been performed.

    Use a CSV file structured according to the requirements presented in the Mass payments data section. The refund parameters must comply with the requirements (you do not have to generate a signature because it is specified by Dashboard).

More information Information about performing refunds by using Dashboard is presented in a separate section.

Analysis of payments results

To analyse information about payments made with the SberPay method and other methods, you can use:

  • Dashboard interface toolkit with 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 available by using the Data API interface.

If you have any questions, refer to the documentation (Dashboard and Using Data API) and EtoPlatezhi technical support.