SDK Integration

Choose your integration approach

Pipes move records between your application and the tools your customers already run, without you writing a connector per tool. You publish a schema; Paycux handles the transport, retries and mapping.

Each pipe is scoped to one organization and one direction. Model a two-way sync as two pipes so failures on one side cannot stall the other.

AUsing the Node runtime client

The Paycux CLI wraps the same API the SDKs use. Authenticate once, then run commands against whichever environment you select.

1paycux login
2paycux env use staging
3paycux organizations list

BUsing the feature_flags access token claim

Access tokens are JWTs signed with a rotating key. Verify them against the JWKS endpoint for your client rather than a pinned public key, so rotation never causes an outage.

1https://api.paycux.com/sso/jwks/client_01M4KXD1PZXFWGWE9ZKPCQRAQ

Cache the key set and re-fetch on an unknown key ID. Reject any token whose issuer, audience or expiry does not match what you expect.