Platform
Webhook
Definition
An HTTP callback mechanism by which one system notifies another of events. Standard infrastructure in B2B iGaming integrations.
Why it matters
Webhooks are how the various components of an iGaming technology stack communicate event-by-event. When a player wins a slot spin, the RGS sends a webhook to the PAM updating the balance. When a deposit completes, the PSP sends a webhook to the operator confirming the transaction. When an integrity alert fires, the trading system sends a webhook to compliance tooling. The webhook architecture supports asynchronous, scalable, near-real-time event propagation across the stack.
The reliability of webhook infrastructure matters. A missed webhook for a winning spin creates a player-balance discrepancy that needs reconciliation. A missed payment webhook creates an FTD without bonus credit. Modern integrations include redundancy, acknowledgment protocols, and reconciliation processes to catch any missed webhooks and resolve discrepancies. The integration complexity around webhooks is one reason platform switching is so disruptive: every webhook flow with every supplier has to be re-built against the new platform.
Frequently asked questions
Are webhooks the same as API calls?
They're complementary. APIs are typically the calling system requesting data or action from the called system. Webhooks are the called system pushing notifications to the calling system without being asked. Both are HTTP-based, but the direction of initiation is different.
Why do webhook failures matter so much in iGaming?
Because each webhook represents a financial event (a bet, a win, a deposit, a withdrawal). Missed webhooks create financial discrepancies that must be detected and resolved. The cumulative effect of even a small webhook failure rate can be substantial reconciliation work and potential player-experience issues.