Going to production
Sandbox and production are separate partner records with separate credentials, origins and companies. Moving means Payroo's review of your integration and a production record; your code does not change, your configuration does.
What you need to show
Payroo reviews the sandbox run of your integration before issuing a production record. Have these done on sandbox:
| Area | Expected | How Payroo sees it |
|---|---|---|
| Credential custody | the credential lives only in your server's secret store; never in a browser, repository, log or URL | your word, and the audit shows every mint from your server addresses |
| Origins | the exact origins of every page that mounts a component, no wildcards, no paths | your production record is created with them |
| Content-Security-Policy | frame-src for the API origin; connect-src for it in the native shell |
you confirm |
| Session route | mints only for users signed in to your product, with the components and scopes the page needs, and the real assurance |
the audit's sessions.create rows |
| Idempotency and concurrency | a fresh Idempotency-Key per attempt, the same key on retry; If-Match on every pay run write; 409 revision_conflict handled by reloading |
the audit shows no idempotency_body_mismatch or repeated precondition_required |
| Errors | 401 leads to a new session, 403 step_up_required is left to the component, 429 honours Retry-After |
your error handling, in the showcase or a recording |
| Webhooks | a public https receiver that verifies the signature, answers 2xx within five seconds, processes by event id, and survived a rotation drill | GET /webhooks/deliveries shows delivered, no dead |
| Journeys | at least one company provisioned, set up to readiness, one employee self-onboarded, one pay run approved and lodged, payslip opened | the audit rows and the usage record |
| Synthetic data | nothing real went to sandbox | your word |
| Support contacts | supportEmails on your record reach people who can act |
Payroo writes there about incidents and rotations |
Ask for production
When the list above is done, an admin of your team opens Go live in the partner portal, enters the production origins and a go-live contact, confirms each item and sends the request. The page shows the status: in review, approved, or changes needed with Payroo's note; after changes you can ask again.
Payroo also runs a credential rotation drill with you (issue a second credential with an overlap, you switch, the old one expires) so both sides know the procedure before it matters.
What Payroo does
- Creates your production partner record with your origins, components, scopes, brand and support e-mails, and issues the production credential, shown once, through a channel you agree. Rate limits above the defaults (600 per credential and 120 per session per minute) are set on the record on request.
- Announces the production API base and the host names to allow (see Environments and sandbox); the frame and asset origins differ from sandbox.
- Delegates any business that already uses Payroo to your record on its written authority, and maps its administrator to your user id.
- Keeps the audit trail and the seven-year records; lodges with the ATO through its own registered software id; pays super through its clearing house; sends the self-onboarding e-mails under your brand.
Your production configuration
| Setting | Sandbox | Production |
|---|---|---|
| API base | https://sandbox.payroo.com.au/api/v1/embedded |
announced by Payroo |
| Credential | sandbox credential | production credential, a different value |
Adapter mode |
staging |
production |
| Webhook destination and secret | your test receiver | your production receiver; set with the production credential |
| Companies | synthetic | real; provisioned through the same call |
Nothing minted on sandbox works on production and nothing on production works on sandbox, by design.
Operating
- Rotation. Payroo issues a second credential with an overlap; both work until the old one's
expiresAt(401 credential_expiredafter). Switch inside the window and tell Payroo. Rotate the webhook secret yourself with a secondPUT /webhooks/config. - Compromise. Tell Payroo at once; the credential is revoked and answers
401 invalid_credentialfrom that moment. Sessions already minted keep running to their own expiry; usePOST /sessions/revokefor a user or a company if needed. - Incidents. Quote
X-Correlation-Idvalues. If Payroo support needs to look at a company, a time-boxed support delegation is created and every read under it is audited. - Maintenance.
GET /metaanswers404briefly during a Payroo deploy; the runtime shows a blocked state and recovers. Lodgements already handed to the channel are unaffected.
What you should see
Your production record's first session answers 201 with principal.employerId of a real company and frame.frameOrigin on Payroo's production host; the first employer.provisioned webhook arrives at your production receiver; and GET /usage for the month shows your first active company.