- HTTP webhooks — Teel POSTs HMAC-signed events to a URL you register. See Subscriptions and Deliveries for the management endpoints, and the Webhooks guide for the verifier samples + retry rules.
- WebSocket — Connect to
wss://api.teel.finance/ws, authenticate in-band with your Auth0 access token, and receive the same events on an open socket. See the Webhooks guide for the client snippet.
Provider webhooks (architecture — internal)
The section below describes how Teel handles inbound webhooks from payment providers (Borderless, Conduit, TransFi, etc.) — this is internal architecture, not something you configure. If you’re integrating as a partner, you only care about the outbound modes above.How It Works
Teel manages webhook integrations with all underlying providers on your behalf. When a provider sends a status update, Teel processes it and forwards the relevant event to your application via WebSocket and any registered HTTP webhook subscriptions.Common Behavior
All webhook handlers follow the same pattern:- Verify signature (where applicable)
- Parse the JSON request body
- Look up the transaction in the database
- Update transaction status
- Broadcast status update via WebSocket
- Auto-trigger offramp when onramp completes (where applicable)
Listening for Events
Rather than configuring individual provider webhooks, connect to the Teel WebSocket to receive all status updates in a unified format. See the Webhooks & Real-Time Updates guide for details.Responding to Webhooks
Return a200 OK response to acknowledge receipt. If a non-2xx response is returned, the provider may retry the webhook.