Skip to Content
Developer Portal preview — pages marked Draft describe the intended design and are not yet available.
Go to Syper Console
EssentialsWebhooks

Webhooks

How Syper notifies your systems when something happens.

DraftDescribes the intended design. Not yet available — names, fields and behaviour may change.

Many Syper operations complete asynchronously — a payment settles, a card is authorised, an account is verified. Webhooks tell your server when that happens so you don’t have to poll.

How it works

  1. You register an HTTPS endpoint for an environment.
  2. When an event occurs, Syper sends an HTTP POST with the event type and payload — for example payment.completed.
  3. Your endpoint verifies the signature, records the event, and responds quickly with a 2xx.
  4. If delivery fails, Syper retries with backoff.

Rules for receivers

  • Verify signatures before trusting a payload.
  • Deduplicate — the same event may be delivered more than once.
  • Don’t assume order — fetch the latest object state if order matters.
  • Respond fast and process in a background job.

Building a receiver: see Webhooks integration. Event types and payloads: see the Webhooks API.

Last updated on