Data syncing
How Data syncing works in Paycux, what it is for, and the smallest setup that gets it running.
Introduction
Data syncing is part of the Paycux platform. This page explains what it does, when to reach for it, and the smallest working setup you can ship.
Everything below applies to both environments. Build and test in staging, then promote the same configuration to production without changing your code — only the API key and client ID differ.
Sync using the events API
Sync using the events API is handled by Data syncing rather than by your application code. Paycux exposes it through the same API surface as the rest of the platform, so the client you already configured needs no additional setup.
Configuration lives in the dashboard and is versioned per environment. Change it in staging, confirm the behaviour, then apply the same change to production.
Sync using webhooks
Webhooks deliver each event to your endpoint over HTTPS with a signature header. Verify the signature before you trust the body, and respond with a 2xx status within thirty seconds.
Delivery is at-least-once, so make your handler idempotent — key it on the event ID and ignore an ID you have already processed. Failed deliveries retry with exponential backoff for twenty-four hours.
API vs. webhooks
API vs. webhooks is delivered as an event you can subscribe to. Events carry the object as it looked after the change, plus the actor that caused it.
Subscribe to the specific event types you handle rather than all of them — a wildcard subscription turns every new event type into unexpected traffic.