Signed events, secret rotation, retries, auto-pause and replay.
Your systems need to know when a transfer completes or an account is credited, without asking every few seconds. Webhooks tell you, as it happens.
Every event is signed with HMAC-SHA256 in a Bridge-Signature header, so you can prove it came from us. Failed deliveries retry with backoff, an endpoint that keeps failing is paused instead of hammered, and anything you missed can be replayed.
When you rotate the signing secret, the old and new secrets overlap for a window, so a rotation never drops an event.
Give us a URL and choose the events it should receive.
Check the Bridge-Signature header against your secret before trusting the body.
Return 2xx and process in the background. Failures retry with backoff.
Request any event again, or a range of them, after an outage.
New and old secrets both verify during the overlap window.
Every delivery is signed so you can verify it came from Bridge.
Failed deliveries try again, spacing out as they fail.
An endpoint that keeps failing is paused, and you're told.
Ask for events again after a deploy or an outage.
Swap secrets without dropping a single event.
Send a test event to check your endpoint before going live.
Illustrative businesses, not customers. Figures are made up to show the flow.
A wallet app in Lagos · Fintechs & neobanks
The app polled for incoming transfers every minute and still showed balances late. Customers kept topping up twice.
Balances update as money lands, and a repeated event never credits twice.
A marketplace's engineering team in Abuja · Marketplaces
Every deploy took the webhook receiver down for a few minutes, and the team lost events.
Deploys stop losing events.
A payroll platform in Lagos · Payroll & HR platforms
A developer accidentally committed the webhook secret. The team needs a new one without missing a payout event.
The leaked secret is retired without a single dropped event.
Compute HMAC-SHA256 of the raw body with your secret and compare it to the Bridge-Signature header, in constant time.
Yes, after a retry. Use the event's reference to process each one once.
Deliveries retry with backoff. If it keeps failing it's paused, and you can replay what you missed.
We'll come back with what's live for you today, and what's next.
Bridge