Ruble payments in ISO 20022 format

Prepare an ISO 20022 payment instruction, sign it, and submit it to the bank. After submission, track the payment processing status.
Tokens required. You need an access_token to submit payments. Get one on the “Getting tokens” screen.
1

Build and sign a pain.001.001.raif payment message

Edit the XML freely. The value in InstdAmt determines the payment outcome: .00 → ACSC, .01 → RJCT, .02 → ATTN, .03 → RJCT (for a different reason).

pain.001.001.raif
Request body
About the signature. A signature confirms the authority to submit a payment instruction. In production, before sending a payment to the bank, make sure the document is signed by an authorized employee and that the signature is valid.
2

Send the message

First build and sign the document in step 1, then confirm that it is ready to send.

3

Track statuses

Statuses progress: PDNGFSGNACSP → a final status within 20–30 seconds. Resending the same MsgId returns DBLC. A missing MsgId returns NPMT.

Submitted payment messages

MsgIdPaymentsCtrlSumStatus
No messages yet.

All payment endpoints

Each endpoint is available for independent calls. Click a card to expand request parameters.