LogoLogo
HomeBlogLoginSignup
  • Get started
  • Guides
  • Reference
  • Getting Started
    • Welcome
    • Quickstart
    • Plan your integration
    • Support
  • Developers
    • Concepts
    • Environments
    • Authentication
    • Pagination
    • Request identification
    • Date & Time
    • Rate limit
    • Webooks
      • Authentication
      • Content and Structure
      • Events
        • Collecting document
        • Collecting document refund
        • Payment document
        • Payment document refund
        • Transfer document
  • Reference
    • API Reference
Powered by GitBook
On this page

Was this helpful?

  1. Developers

Webooks

PreviousRate limitNextAuthentication

Last updated 4 months ago

Was this helpful?

Most of the 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 .

Technical details

All registered endpoints must be configured to receive an 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.

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

webhooks