Callbacks security
How to verify callbacks authenticity
For security reasons, when sending and receiving data and information to and from an external endpoint (i.e. real-time webhooks, external resources) we recommend verifying the callback authenticity by signing the payload with the shared secret (SHA256 HMAC) and comparing the result with the X-CommerceLayer-Signature callback header. In details:
Read the X-CommerceLayer-Signature header and get the encrypted signature.
Rebuild the signature according to the SHA256 HMAC algorithm, using the payload body and the provided shared secret.
Compare your signature with the one you got from the header.
If the two signatures match, you can proceed safely — if not, you can't trust the callback.
Example
This is a sample script in Node.js that you can use as a reference to check the signature:
When verifying the callback authenticity, make sure to read the raw body of the payload and NOT the parsed one.
Do you prefer to use Next.js or Express.js to verify the signature? Check the linked code samples from our Examples open-source repository on GitHub.
IP ranges
All the external requests (i.e. real-time webhooks, external resources) are sent from a set of dedicated IP addresses. When you receive requests to your endpoints, please make sure their source IP is included in the following lists:
eu-west-1
54.246.59.198
99.81.212.137
54.74.119.33
Source IPs for customers with organization localized in the EU region.
us-east-1
3.220.172.67
34.202.177.238
52.0.55.171
Source IPs for customers with organization localized in the US region.
In case there are any changes to the list of IPs above, they will be communicated widely in advance through all our channels.
Last updated