1️⃣Сallback "Pay-in"
After the successful order creation and payment confirmation by the customer via DCM platform, the bank generates a Payment Message. Based on this message, DCM platform sends a "Pay-in" callback to the Merchant in JWT format.
Callback Structure
{
"payment_message_external_id": "string",- Unique identifier for the payment (generated by the paying bank)
"payment_message_guid": "string", - Unique identifier for the payment message
"callback_guid": "string", - Unique identifier for the callback
"amount": "number", - Payment amount
"currency": "string", - Payment currency
"sender_account_iban": "string", - Payer's IBAN account
"receiver_account_iban": "string", - Receiver's IBAN account
"order_id": "string", - Unique order identifier
"ref_found": "bool",- Technical attribute indicating if the payment purpose matched
"ref_number": "string",- Unique identifier of the order (generated by the Merchant)
"amount_matched": "bool", - Technical attribute indicating if the payment amount matched
"purpose": "string", - Payment purpose (provided by the Merchant)
"status": "success/reject", - Callback status
"reason": "string" - Error description if the status is "reject"
}
The Merchant authorizes the callback request using DCM platform's JWKS, accessible via the provided link - https://api-lz5r45.tpn-api.dcm.systems/api/v1/.well-known/jwks.json
Response
Code "2хх" - DCM platform sends a “Pay-out” callback in JWT format with:
status "Success"
reason "Payment message is approved by the receiver's bank. Merchant is informed by the callback"
Code "4хх" - DCM platform sends a “Pay-out” callback in JWT format with:
status "Reject"
reason "No response on the callback from the merchant""
Code "5хх" - DCM platform sends retries according to the retry policy (10 retries). After 10 unsuccessful attempts, the "Pay-out" callback is sent to the Initiator Bank with the same response as Code 4xx.
Last updated