WB Wallet

Overview

Introduction

WB Wallet is a payment method which allows you to process payments in Russian rubles by using e-wallets in Russia. This method supports purchases and refunds.

This article provides information about working with the WB Wallet 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 digital wallet payments
Payment instruments digital wallets
Countries and regions RU
Payment currencies RUB
Currency conversion on the EtoPlatezhi side
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 WB Wallet 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 WB Wallet method. Purchases can be processed by using Payment Page, Gate and Dashboard (using payment links), refunds—by using Gate and Dashboard. At the same time, regardless of the interfaces used, the following properties and limitations are applicable.

The following properties and limitations apply to the WB Wallet method.

Amounts, RUB Times ¹
minimum maximum base threshold
Purchases 1.00 600,000.00 1 minute 3 hours
Refunds – – – –
Note:
  1. The base and threshold times are defined as follows:
    • The base time is the average estimated time between the moment a payment is initiated in the payment platform to the moment the payment result is sent to the web service. The base time evaluation is made on the assumption of normal operation of all technical facilities and communication channels and typical customer behaviour (if any input from the customer is required). Use the base time to estimate when to react to the absence of payment result callbacks or when to check payment status (details).
    • The threshold time is the maximum possible time between the moment a payment is initiated in the payment platform to the moment the web service receives the callback with the payment result. A payment is automatically assigned the decline status if it wasn't processed within the threshold time. For individual customisation of the threshold time limit, contact EtoPlatezhi technical support.

Processing scenarios

To perform a purchase by using the WB Wallet method, you need to redirect the customer to the WB Wallet service, while to make a refund, you need to receive a request from the customer and notify the customer about the result of the refund via the web service.

Figure 1. Purchase by using Payment Page
Figure 2. Purchase by using Gate
Figure 3. Refund 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 purchases via 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 WB Wallet 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 4. 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 WB Wallet method.
  8. The payment platform receives the request for processing the payment by using the WB Wallet 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 provider service sends the data for confirming the purchase to the customer.
  12. The customer completes all required payment steps.
  13. The purchase is processed in the provider service.
  14. The result information is displayed to the customer in the provider service.
  15. The customer is redirected to Payment Page.
  16. The provider service sends a notification about the result to the payment platform.
  17. The payment platform sends the payment result callback to the web service.
  18. The payment platform sends the result information to Payment Page.
  19. 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 WB Wallet 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 WB Wallet 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 necessary to specify the phone number of the customer, associated with the WB Wallet account in the customer_account_number parameter.
  4. If you need to have the payment form displayed with the WB Wallet method selected, set the force_payment_method parameter to wildberries.
  5. Additionally, any other parameters available for working with Payment Page can be used (details).
  6. After all target parameters are specified, generate a signature (details).

Thus, a correct request for opening the payment form using the WB Wallet 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": "79991234567",
   "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg=="
}
Figure 5. 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": "79991234567",
   "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg=="
}

Callback format

The WB Wallet 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 10.00 RUB purchase made in the 129103 project.

Figure 6. Example of callback data indicating that the purchase has been processed
{
    "payment": {
        "date": "2025-11-13T08:34:42+0000",
        "method": "wildberries",
        "sum": {
            "amount": 1000,
            "currency": "RUB"
        },
        "id": "testwb1",
        "type": "purchase",
        "status": "success",
        "description": ""
    },
    "customer": {
        "id": "1"
    },
    "account": {
        "number": "***4471"
    },
    "project_id": 129103,
    "operation": {
        "provider": {
            "id": 18791,
            "payment_id": "a103d070-ab7628f82a8f",
            "auth_code": ""
        },
        "id": 5026717010142355,
        "type": "sale",
        "status": "success",
        "date": "2025-11-13T08:34:42+0000",
        "sum_initial": {
            "amount": 1000,
            "currency": "RUB"
        },
        "created_date": "2025-11-13T08:34:29+0000",
        "request_id": "3d55427b78f80c0da8e8-05026718",
        "sum_converted": {
            "amount": 1000,
            "currency": "RUB"
        },
        "code": "0",
        "message": "Success"
    },
    "signature": "gw3d4qL5Yu1n/YhIhpMXZHnLbnLZ/ziI0LO8TPslOfA=="
}

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

Figure 7. Example of callback data indicating that the purchase has been declined
{
    "payment": {
        "date": "2025-11-13T08:33:49+0000",
        "method": "wildberries",
        "sum": {
            "amount": 1000,
            "currency": "RUB"
        },
        "id": "testwb",
        "type": "purchase",
        "status": "decline",
        "description": ""
    },
    "customer": {
        "id": "1"
    },
    "account": {
        "number": "578954******5254"
    },
    "project_id": 129103,
    "operation": {
        "provider": {
            "id": 18791,
            "payment_id": "",
            "auth_code": ""
        },
        "id": 5008838010142407,
        "type": "sale",
        "status": "decline",
        "date": "2025-11-13T08:33:49+0000",
        "sum_initial": {
            "amount": 1000,
            "currency": "RUB"
        },
        "created_date": "2025-11-13T08:33:46+0000",
        "request_id": "b5ee59190f3ceae5ffee-05008839",
        "sum_converted": {
            "amount": 1000,
            "currency": "RUB"
        },
        "code": "20000",
        "message": "General decline"
    },
    "signature": "9m4ZK9fWYHIeIR/tRzo/bGP14gSQWtaiKNuEA=="
}

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 WB Wallet 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 and callbacks used for processing payments by using the WB Wallet 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 WB Wallet method:

  1. You must specify the necessary parameters required for any payment.
  2. Additionally, it is necessary to specify the phone number of the customer, associated with the WB Wallet account in the customer_account_number parameter.
  3. 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.

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

Thus, a correct request for opening the payment form using the WB Wallet 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": "79991234567",
   "recurring": {"register":true},
   "payment_description": "example reason",
   "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg=="
}
Figure 8. 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": "79991234567",
   "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 WB Wallet 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 the final callback from the payment platform.

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

Figure 9. Purchase processing by using Gate: step-by-step description
  1. A customer initiates a purchase by using the WB Wallet 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 data for confirming the purchase to the customer.
  9. The customer completes all required payment steps.
  10. The purchase is processed in the provider service.
  11. The result is displayed to the customer.
  12. The customer is redirected to the web service.
  13. The provider service sends the payment result notification to the payment platform.
  14. The payment platform sends the payment result callback to the web service.
  15. 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 WB Wallet 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 WB Wallet method:

  1. To initiate each purchase, send a separate POST request to the /v2/payment/wallet/wildberries/sale endpoint. This endpoint belongs to the group /v2/payment/wallet/{payment_method}/sale.
  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—account information:
      • number—phone number of the customer, associated with the WB Wallet account
  3. Additionally, any other parameters included in the specification can be used.

Thus, a correct purchase request by using the WB Wallet 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"
  },
  "account": {
    "number": "79991234567"
  },
  "customer": {
    "id": "customer123",
    "ip_address": "192.0.2.0"
  }
}
Figure 10. 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"
  },
  "account": {
    "number": "79991234567"
  },
  "customer": {
    "id": "customer123",
    "ip_address": "192.0.2.0"
  }
}

Final callback format

The WB Wallet 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 10.00 RUB purchase made in the 129103 project.

Figure 11. Example of callback data indicating that the purchase has been processed
{
    "payment": {
        "date": "2025-11-13T08:34:42+0000",
        "method": "wildberries",
        "sum": {
            "amount": 1000,
            "currency": "RUB"
        },
        "id": "testwb1",
        "type": "purchase",
        "status": "success",
        "description": ""
    },
    "customer": {
        "id": "1"
    },
    "account": {
        "number": "***4471"
    },
    "project_id": 129103,
    "operation": {
        "provider": {
            "id": 18791,
            "payment_id": "a103d070-ab7628f82a8f",
            "auth_code": ""
        },
        "id": 5026717010142355,
        "type": "sale",
        "status": "success",
        "date": "2025-11-13T08:34:42+0000",
        "sum_initial": {
            "amount": 1000,
            "currency": "RUB"
        },
        "created_date": "2025-11-13T08:34:29+0000",
        "request_id": "3d55427b78f80c0da8e8-05026718",
        "sum_converted": {
            "amount": 1000,
            "currency": "RUB"
        },
        "code": "0",
        "message": "Success"
    },
    "signature": "gw3d4qL5Yu1n/YhIhpMXZHnLbnLZ/ziI0LO8TPslOfA=="
}

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

Figure 12. Example of callback data indicating that the purchase has been declined
{
    "payment": {
        "date": "2025-11-13T08:33:49+0000",
        "method": "wildberries",
        "sum": {
            "amount": 1000,
            "currency": "RUB"
        },
        "id": "testwb",
        "type": "purchase",
        "status": "decline",
        "description": ""
    },
    "customer": {
        "id": "1"
    },
    "account": {
        "number": "578954******5254"
    },
    "project_id": 129103,
    "operation": {
        "provider": {
            "id": 18791,
            "payment_id": "",
            "auth_code": ""
        },
        "id": 5008838010142407,
        "type": "sale",
        "status": "decline",
        "date": "2025-11-13T08:33:49+0000",
        "sum_initial": {
            "amount": 1000,
            "currency": "RUB"
        },
        "created_date": "2025-11-13T08:33:46+0000",
        "request_id": "b5ee59190f3ceae5ffee-05008839",
        "sum_converted": {
            "amount": 1000,
            "currency": "RUB"
        },
        "code": "20000",
        "message": "General decline"
    },
    "signature": "9m4ZK9fWYHIeIR/tRzo/bGP14gSQWtaiKNuEA=="
}

Useful links

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

COF purchases by using Gate

General information

COF purchases using WB Wallet 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 WB Wallet 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 WB Wallet 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": "79991234567"
  },
  "recurring": {
    "register": true
  }
}
Figure 13. 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": "79991234567"
  },
  "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 WB Wallet method:

  1. To process each purchase, send a separate POST request to the /v2/payment/wallet/wildberries/recurring endpoint, which belongs to the group /v2/payment/wallet/{payment_method}/recurring.
  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—account information:
      • number—phone number of the customer, associated with the WB Wallet account
    • 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 WB Wallet 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": "79991234567"
  },
  "recurring": {
    "id": 1234567890
  }
}
Figure 14. 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": "79991234567"
  },
  "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 WB Wallet 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 15. 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 WB Wallet service.
  7. The refund is processed on the side of the WB Wallet service.
  8. The WB Wallet 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 WB Wallet 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 WB Wallet method:

  1. To initiate each refund, send a separate POST request to the /v2/payment/wallet/wildberries/refund endpoint, which belongs to the group /v2/payment/wallet/{payment_method}/refund.
  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
      • amount—refund amount in the smallest currency unit (required for a partial refund)
      • currency—refund currency code in the ISO-4217 alpha-3 format (required for a partial refund)
    • 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 WB Wallet 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.

{
  "general": {
    "project_id": 210,
    "payment_id": "test_payment",
    "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA=="
  },
  "payment": {
    "description": "test refund",
    "amount": 1000,
    "currency": "RUB"
  },
  "customer": {
    "ip_address": "192.0.2.0"
  }
}
Figure 16. 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",
    "amount": 1000,
    "currency": "RUB"
  },
  "customer": {
    "ip_address": "192.0.2.0"
  }
}

Callback format

The WB Wallet 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 10.00 RUB refund made in the 129103 project.

Figure 17. Example of callback data indicating that the refund has been processed
{
    "payment": {
        "date": "2025-11-27T13:57:38+0000",
        "method": "wildberries",
        "sum": {
            "amount": 0,
            "currency": "RUB"
        },
        "id": "TEST_PAYMENT_596610",
        "type": "purchase",
        "status": "refunded",
        "description": "TEST_PAYMENT_596610"
    },
    "customer": {
        "id": "1"
    },
    "project_id": 129103,
    "operation": {
        "provider": {
            "id": 17361,
            "payment_id": "7e357cc72-4c57cb3d824b",
            "auth_code": ""
        },
        "id": 35054010177128,
        "type": "refund",
        "status": "success",
        "date": "2025-11-27T13:57:38+0000",
        "sum_initial": {
            "amount": 1000,
            "currency": "RUB"
        },
        "created_date": "2025-11-27T13:57:34+0000",
        "request_id": "5c6b1cb2338f47f239784-00035055",
        "sum_converted": {
            "amount": 1000,
            "currency": "RUB"
        },
        "code": "0",
        "message": "Success"
    },
    "signature": "byAApq7igpmeGgQGZjoonzaPgHX7PUGaBQ=="
}

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

Figure 18. Example of callback data indicating that the refund has been declined
{
    "payment": {
        "date": "2025-11-13T08:37:57+0000",
        "method": "wildberries",
        "sum": {
            "amount": 1000,
            "currency": "RUB"
        },
        "id": "testwb1",
        "type": "purchase",
        "status": "success",
        "description": ""
    },
    "customer": {
        "id": "1"
    },
    "account": {
        "number": "***4471"
    },
    "project_id": 129103,
    "operation": {
        "provider": {
            "id": 18791,
            "payment_id": "",
            "auth_code": ""
        },
        "id": 5026717010142359,
        "type": "refund",
        "status": "decline",
        "date": "2025-11-13T08:37:57+0000",
        "sum_initial": {
            "amount": 1000,
            "currency": "RUB"
        },
        "created_date": "2025-11-13T08:37:55+0000",
        "request_id": "3cc806ee3b7e672b5cf578-05026718",
        "sum_converted": {
            "amount": 1000,
            "currency": "RUB"
        },
        "code": "20000",
        "message": "General decline"
    },
    "signature": "3fPVj6Q+M6wyPm6AH8vN0RHnC6Q7UxQ=="
}

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 WB Wallet 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 WB Wallet 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.