⏺️p2p order (to request)

Methods described on this page:

  • POST /create_p2p_order

  • GET /order_status

Upon receiving a request from the client to generate a QR code and deeplink for funding their own account, the bank must create a P2P order by sending a request using the POST /create_p2p_order method.

POST/create p2p order

Endpoint: POST/api/v1/p2p/orders

Payload:

{ 
"jti": "1234567890", 
"creditor": { 
"account": "UA41003506518366713636167" 
}, 
"expires_at": "2025-12-31T23:59:59Z", // optional  
"amount": 1500.75, // optional  
"currency": "UAH", 
"external_id": "112663",
"purpose": "Replenishment of own account",
"type": "link" [enam: phone/ link]
}

Response 2Ρ…Ρ… OK

Response 4Ρ…Ρ… ERROR

Upon receiving a request to create an order, the DCM platform verifies it and, in case of any issues, provides details of the errors in the response.

Errors list

Code 400:

  • "INVALID_DEBTOR_ACCOUNT"

  • "INVALID_Π‘REDITOR_PHONE"

  • "INVALID_TYPE"

  • "INVALID_CURRENCY"

  • "UNSUPPORTED_CURRENCY"

  • "INVALID_EXTERNAL_ID"

  • "EXTERNAL_ID_NOT_UNIQUE"

  • "EXPIRES_AT_IS_NOT-FUTURE_DATE"

  • "INVALID_PURPOSE"

  • "INVALID_REQUEST "

Code 401:

  • "AUTHORIZATION_FAILED"

Code 500:

  • "INTERNAL_ERROR"

The DCM platform allows retrieving information about the status of a P2P order using the GET /order_status request.

GET/order_status

Endpoint: GET /api/v1/p2p/orders/:order_guid

Response 2Ρ…Ρ… OK (same as POST/create_order)

Error list:

Code 400:

  • "INVALID_ORDER_GUID"

Code 401:

  • "AUTHORIZATION_FAILED"

Code 404:

  • "ORDER NOT FOUND"

Code 500:

  • "INTERNAL_ERROR"

Previousp2p by deeplink or QR codeNextPay request initiation

Last updated