🔍Receiver search

Methods described on this page:

• POST /link_creditor

• Callback "Creditor linked"

If the phone number is not found in the alias database, the DCM platform sends a request to participating banks to search for the recipient associated with this number and obtain the client’s consent to link it as an alias. The request is sent in JWT format using the POST /link_creditor method.

POST/link creditor

Payload:

{ 
"phone": "[phone]", 
"account": "UA41003506518366713636167", // optional
"pay_request_guid": "b5a8-e79a45160a8b-d1f54a9f-50d3-4a16" 
}, 

Response 202 OK is provided immediately and indicates that the recipient exists as a client of the bank.

Response 400 "USER_NOT_FOUND" is provided immediately and indicates that the recipient is not found in the bank. After receiving the POST /link_creditor request and confirming the existence of the client (as indicated by the 202 OK response to the DCM platform), the bank must obtain the client's consent to link their phone number and IBAN account for receiving P2P transfers.

If the linking is successful, the bank initiates a callback to the DCM platform with information about the alias creation using the "Creditor linked" callback method.

Callback "Creditor linked"

Endpoint: POST/api/v1/p2p/callbacks Payload (if Success)

{ 
"type": "creditor_linked",
"data": {
"pay_request_guid": "b5a8-e79a45160a8b-d1f54a9f-50d3-4a16" 
"creditor": {
"phone": "[phone]", 
"account": "UA41003506518366713636167", // optional
"pay_request_guid": "b5a8-e79a45160a8b-d1f54a9f-50d3-4a16" 
    }
  }
}

If the client refuses to link the IBAN account to the phone number (or does not respond to the request), the bank initiates a callback to the DCM platform with the corresponding status.

Payload (if Failure)

{ 
"type": "linking_declined",
"data": {
"pay_request_guid": "b5a8-e79a45160a8b-d1f54a9f-50d3-4a16"
 }
}