1️⃣Validation

Upon receiving a Payment Message creation request, the DCM platform performs a comprehensive verification and validation of the request's key attributes. If any issues are detected, the system provides a response detailing the identified errors.

Error list:

Сode 400:

• "INVALID_DEBTOR_ACCOUNT"

• "INVALID_CREDITOR_ACCOUNT"

• "INVALID_NONCE"

• "INVALID_ENCRYPTED_KEY"

• "INVALID_DEBTOR_NAME"

• "INVALID_DEBTOR_ID"

• "INVALID_DEBTOR_PHONE"

• "INVALID_CREDITOR_ID"

• "INVALID_CREDITOR_NAME"

• "INVALID_CURRENCY"

• "UNSUPPORTED_CURRENCY"

• "ORDER_NOT_FOUND"

• "SENDER_COUNTERPARTY_NOT_FOUND"

• "RECEIVER_COUNTERPARTY_NOT_FOUND"

• "EXTERNAL_ID_IS_ALREADY_TAKEN"

• "ORDER_IS_EXPIRED"

• "INVALID_EXTERNAL_ID"

• "INVALID_AMOUNT"

• "INVALID_PURPOSE"

• "INVALID_CREATION_DATE"

• "INVALID_CREATION_TIME"

• "CREATION_DATE_IS_NOT_PAST"

• "INVALID_REQUEST"

Code 401:

• "AUTHORIZATION_FAILED"

Code 500

• "INTERNAL_ERROR"

Examples of the Most Common error Responses:

Duplicate Payment Message with the same Order Details

If it exists, response:

{
    “error”: “payment message with provided order id already exists”,
    “payment_message_guid”: “10f6e03c-7769-4d83-a600-fa642f856105"
}

Duplicate Payment Message with the Same JTI

If it exists, response:

{
    “error”: “payment message with provided jti already exists”,
    “payment_message_guid”: “fc436ab7-0cc0-47fb-801e-4ab86f3c5e00"
}

Upon successful creation, the DCM platform sends cascading callbacks in JWT format to all involved participants:

• Callback: "Pay-in" — sent to the Recipient Bank.

• Callback: "Pay-out" — sent to the Initiator Bank.