Last updated
Was this helpful?
Last updated
Was this helpful?
All the calls to our Bank Account Validation APIs will contain an Authorization
field on the header used to ensure request integrity and to authenticate yourself since you will use your own secret key (API Signature) to generate and encrypt a hash.
It has to be created using HMAC-SHA-256 (RFC 2104) encoding and the payload must include the following details:
+ +
JSONPayload
Use your to generate the Authorization value
The Authorization
field on the header of the requests will contain the string "D24 " concatenated to the hash generated, in the following format:
Authorization: "D24 " + HMAC256(X-Date + X-Login + JSONPayload)
Example:
Authorization: D24 223a9dd4784726f1536c926da7dc69155a57612c5c3c1e1b429c367a5eee67cf
The is your login API Key, it can be retrieved from the Merchant Panel by going to Settings -> API Access -> Cashout credentials -> API Key.
The is the date in ISO8601 Datetime with Timezone. Format expected: ISO8601 Datetime with Timezone: yyyy-MM-dd'T'HH:mm:ssZ
. E.g.: 2020-06-21T12:33:20Z
.
The Authorization
value is case sensitive and must include all the above mentioned values.
The JSONPayload
is the exact same JSON you sent in the body of the request.
In case the JSONPayload
value is empty (for example in the status or payment methods endpoints), use an empty string ("") instead.
The JSONPayload
should be converted to UTF-8 before hashing it to prevent Invalid Signature error when sending characters with different encodings.
Check the examples in the different languages on how to properly calculate the Signature.
You can also check the code of our SDKs in and to see how it is calculated.
Learn how to calculate and send the Signature header value to verify requests integrity