⛔Error reference guide

This page contains a list of all potential errors that may occur while working with the API.

GET/merchants/order/nbu/json

DCM platform checks the existence of an order using the provided order_id. If the order is not found, DCM platform returns an appropriate error:

{
    "error": "func GetMerchantsOrderNbuJSONHandler() failed. Error: failed to get order by ID: get order by guid err: order not found"
}

---

POST/payment_message

When receiving a request to create a Payment Message, DCM platform performs the following checks:

1. Verifies the existence of a Payment Message with matching order details.

If such a Payment Message exists, the response is:

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

1. For the existence of a Payment Message with an identical JTI.

If such a Payment Message exists, the response is:

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

---

GET Method to Retrieve Payment Message Status

When processing a request to retrieve the status, DCM platform verifies the existence of the Payment Message with the specified details. If the DCM platform is not found, the error returned is:

{
    "error": "not found"
}