ISO 20022 payments
The simulator follows the production cycle: XML pain.001 → signature → submit to /iso20022/signed → track statuses through pain.002. The sandbox validates the XSD schema and signature structure.
Tokens required. You need an
access_token to submit payments. Get one on the “Getting tokens” screen.1
Build and sign pain.001.001.raif
Edit the XML freely. Cents in InstdAmt determine the payment outcome: .00 → ACSC, .01 → RJCT, .02 → ATTN, .03 → RJCT (different reason).
pain.001.001.raif — тело запроса
Ctrl+Enter / ⌘+Enter — send
About the signature. The sandbox checks the signature structure —
ds:Signature in SgntrSt, GOST algorithms, and XPath Filter subtract — but not cryptography. Production uses GOST R 34.10-2012.2
Send the message
POST /v2/transfers/iso20022/signed Authorization: Bearer [access_token — get it in scenario 1] Content-Type: application/xml
The synchronous response is pain.002: PDNG accepted, RJCT rejected with a reason in AddtlInf.
3
Track statuses
Statuses progress: PDNG → FSGN → ACSP → terminal in 20–30 seconds. Resending the same MsgId returns DBLC. A missing MsgId returns NPMT.