Funds deposit (makeDeposition)

Operation for sending a transfer to a Yandex.Money Wallet, a bank account in rubles, a bank card, or a mobile phone account.

The payment recipient is defined in the value of the dstAccount parameter. Data required for depositing in the appropriate way is transmitted in the paymentParams parameters. This includes the recipient's agreement with the Yandex.Checkout terms (pof_offerAccepted). You need to place the link to the offer on your side:


Before sending the money to the user, the ability to deposit the funds must be checked using the testDeposition request. This request lets you check whether the amount specified can be transferred to the appropriate user, including:

  • Whether the user ID is correct and exists (the account number or phone number).
  • What limits are applied.
  • Whether this operation is allowed.

When a testDeposition request is received, the deposit is not made.

Verification of recipient's passport information

In requests to debit to a bank account or bank card, the recipient's personal data must be passed. Before making the deposit, Yandex.Money verifies this data against the database of active passports of the Ministry of Internal Affairs (as required by the legislation of the Russian Federation).

If everything is in order, the Yandex.Money service will returns status=0.

If the data does not pass verification, the Yandex.Money service returns status=3, a deposition error (error=48) with an explanation, and a errorDepositionNotification notification.

Interaction format

Described in the Protocol for deposits to Wallets. See Interaction format

Address for sending requests

Request parameters




Mandatory parameters
dstAccount YMAccount

Identifier of the transfer recipient.

Depends on where you send the transfer:

clientOrderId ClientTransactionNumber

Operation ID. Must be unique for the Counterparty over the entire history of operations. Recommended values: a positive integer in decimal notation.

requestDT xs:dateTime

The date and time the operation request was formed on the Counterparty's side, according to their system.

amount CurrencyAmount

The transfer amount. For example: 12.34.

currency CurrencyCode

Currency code of the transfer. Possible value—643 (Russian ruble).

agentId xs:long

Counterparty ID issued by Yandex.Money.



up to 128 characters

The reason for making the transfer.
Optional parameters
paymentParams xs:complexType

Request element for transmitting additional payment parameters. Possible values are described in the sections Transfer to bank card, Transfer to bank account, and Transfer to mobile phone account.

Response parameters of the Yandex.Money service




status xs:int

Result of executing the operation. The value of this field should be used on the Counterparty's side to make a decision about the request state. See Request status codes

error xs:int

Code of the request execution error. Additional explanation of the status.

clientOrderId ClientTransactionNumber

The value of the clientOrderId request parameter.

processedDT xs:dateTime

Time when the request was processed, according to the Yandex.Money server. For a successful transfer, this is the actual time when money was transferred.

balance xs:decimal

The difference between the security amount that the Counterparty has transferred to the gateway account in Yandex.Money, and the amount of money that Yandex.Money has transferred to users at the request of the Counterparty. This parameter is passed in the response only for the makeDeposition request, and only if the transfer was successful.

techMessage xs:string

Optional field. May contain an additional explanation for refusals to accept the payment. This text contains technical information and should not be displayed in any user interface.

When making a transfer to a bank account, card, or mobile phone, the reason for refusing to accept the payment is only contained in the response to the makeDeposition request.

identification xs:string

This field contains information about the status of the Wallet in the Yandex.Money service. Only present for deposits to Yandex.Money Wallets.

Possible values:

  • anonymous — no identification;
  • reviewed — simplified identification;
  • identified — full identification.

More about user statuses


Request examples
Request to check transfer possibility
<testDepositionRequest agentId="123"
                         contract="Winnings in Sphera game"/>
Request to transfer specifying paymentParams
<makeDepositionRequest agentId="200225"
Examples of responses
Response about deposit possibility
<testDepositionResponse clientOrderId="12345"
Response about successful deposit
<makeDepositionResponse clientOrderId="12345"

Rules for forming and processing requests

  1. Each transfer must be formed with a unique ID value (clientOrderId).
  2. If the response Success (status=0) is received for the deposit operation, it means the transfer was completed successfully. In some cases of a successful transfer, Yandex.Money might return the error field in the response with an additional explanation of the operation status.
  3. If the request was sent with a previously processed ID (clientOrderId) and the values of the mandatory parameters (clientOrderId, dstAccount and amount) match the previous attempt, Yandex.Money returns the result of processing the previously sent request.
  4. If the request was sent with a previously processed ID (clientOrderId) and the values of mandatory parameters (clientOrderId, dstAccount and amount) differ from the first attempt, Yandex.Money declines this request and returns status=3, error=26 in the response.
  5. The Yandex.Money service processes a received request immediately. If a request can't be handled within a few seconds, the response processing (status=1) is returned. In this case, the result of the operation is unknown, and the merchant should repeat the request with the same data to get a final response. We recommend retrying as follows: the first retry after 1 minute, the next three with an interval of 5 minutes, and then not more than once every 30 minutes. We recommend the same retry attempts if the response from the Yandex.Money service is not received, or if the response contains HTTP status 500.
  6. If there is no response from Yandex.Money, or if the response is indefinite (for example: HTTP status 500), the counterparty's system should repeat the request with the same data until the final response is received. We recommend using the same retry attempts as in the previous point.
  7. The status of a transaction in progress (status=1) may change either to Success (status=0) or Declined (status=3).
  8. If the transfer was declined by the Yandex.Money service, the response returns status=3 and error with the code of the reason for refusal. In some cases the techMessage field may be included, which contains additional information in the form of text in any format. This text is intended for analysis by technical specialists and shouldn't be shown in any user interface.
  9. If the transfer is refused with the error status=3 error=45, the Counterparty's system should deposit accepted transfers to the Yandex.Money account and confirm that the balance increased (by sending a balance request), then make the transfers with new transaction IDs (clientOrderId).
  10. The response status=3 error=21 means that the requested operation is not allowed for this Counterparty.
  11. The response status=0 error=43 means that the transfer was successful and the Counterparty's balance was reduced by the transfer amount, and the Yandex.Money service sent the recipient an SMS message or email with instructions for receiving the money.

See also

Transfer to a Yandex.Money wallet

Transfer to bank card

Transfer to bank account

Transfer to mobile phone balance

Reports on accepted and returned transfers