Paycux Emulate
How Paycux Emulate works in Paycux, what it is for, and the smallest setup that gets it running.
Paycux Emulate
Paycux Emulate is handled by Paycux Emulate 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.
Installation
Install the SDK with your package manager, then read the API key from the environment rather than hard-coding it.
1npm install @paycux/node
CLI
The Paycux CLI wraps the same API the SDKs use. Authenticate once, then run commands against whichever environment you select.
1paycux login2paycux env use staging3paycux organizations list
Using from Any Language
Using from Any Language is handled by Paycux Emulate 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.
Programmatic API (Node.js)
Programmatic API (Node.js) is handled by Paycux Emulate 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.
Seed Data
Seed Data is handled by Paycux Emulate 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.
Testing Your Login Flow End-to-End
Verify the setup end to end before you hand it to a customer. Run the flow from a private browser window so no existing session masks a broken step.
- 1Open the connection in the dashboard and confirm its status reads Active.
- 2Start the flow from your application, not from the provider, so the redirect URI is exercised.
- 3Sign in as a test user and confirm the profile arrives with an email address.
- 4Check the connection's event list — a successful sign-in appears within a few seconds.
JWT Templates (custom claims)
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.