Specifics of working with the API
Key aspects of working with DCM platform API requests:
Every API request initiated by the Bank includes a unique
url_host
(separate for testing and production environments) and acounterparty_guid
obtained by the Bank during the integration with the DCM platform.The date and time format complies with the ISO 8601 standard, for example:
2021-09-30T21:43:26+00:00
.All API requests sent to or from the DCM platform include the
Cx-Authorization
header in JWT format, which contains:Header: parameters
alg
,type
,kid
Body: parameters
iat
,jti
The JWT is signed with the private key of the party initiating the request. For requests to the DCM platform, the Bank's private key is used, while for requests from the DCM platform, the DCM platform's private key is used.
When receiving a request from the Bank, the DCM platform verifies it using the public key published by the Bank
When receiving a request from the DCM platform, the Bank verifies it using the platform’s public key
API requests that contain personal information about transaction participants (
POST/payment_message
andСallback
) require not only theCx-Authorization
header but also data transformation into JWT format signed with the private key and included in the request.
The recipient bank's private key is used to decrypt personal information. A detailed description of the data encryption and decryption process is provided in the "Data Encryption" section.
DCM platform does not have access to client data or tools for decrypting such data.
Last updated