Webhook Configurations (Transfer Center)
Use this page as the Transfer Center entry for outbound webhooks: what they are for, where to configure HTTPS endpoints in the product, and where to read full technical detail.
What webhooks do here
Your server receives HTTPS POST callbacks when Transfer Center–related events occur (for example transfer or invoice lifecycle changes—see the catalog in the main guide). Configure URLs and secrets in the Dashboard so Swirepay can reach your environment reliably.
Configure in the dashboard
Set up webhook URLs and verification steps using:
- Webhooks guide — signing, retries, event types, payloads, and troubleshooting.
That guide applies across Payment Center, Transfer Center, and Inventory; Transfer-specific events appear alongside the others.
Using APIs after configuration
Once webhooks are enabled, your integration should:
- Verify signatures using the shared guide’s instructions.
- Return 2xx quickly and process work asynchronously when possible.
- Reconcile state using GET APIs if a delivery is missed (webhooks are at-least-once).
Related Transfer Center APIs (optional triggers)
Some flows expose explicit “notify” operations for a single resource (for example a transfer session or vendor invoice). See the API reference for details; they are not a substitute for dashboard webhook configuration.