Most of transactions at Trio's integration are asynchronous, which means that we have some process in background to finish and commit the transaction. In order to effective communicate with external systems and customers we use webhooks.

The webhooks can be configured through our API.

All registered endpoints must be configured to receive a HTTP POST with JSON payload. We have a default timeout configured of 3 seconds waiting a 2XX HTTP status code in order to mark the payload as delivered.

We have a special failure schema, our systems will try 5 times, with a retry configure for 16 seconds for the first failure and doubling the time each failure: 16s, 32s, 104s, 208s, etc.

We recommend that all registered endpoints uses the HTTPS protocol to secure the in-transit payload.

To verify that a webhook was actually sent by Trio, every payload is signed with a signature that is passed through as the HTTP header X-Webhook-Signature. The signature is encoded and can be replicated by applying HMAC-SHA-256 to the body of the webhook with your specific webhook key, which can be found in your webhook settings page.

Have you seen our video tutorials on YouTube?