Verify credentials, webhooks, error handling, security, and monitoring before switching your Jupico API integration from sandbox to production.
Use this checklist before switching your integration from sandbox to production. Every item should pass in sandbox first and then be re-verified in production before routing real customers.
Do not enable production traffic until every applicable item below has been completed and re-tested in production.
You create production API credentials yourself in Backoffice. Your Jupico account team provisions your production Backoffice user during onboarding — if you can’t sign in to production Backoffice yet, contact them first.
1
Sign in to production Backoffice
Use your production Backoffice user account.
2
Create an API key
Select Developer at the bottom of the left navigation, choose API Keys, then select New API Key and complete the required fields to generate the key. See Manage API keys in Backoffice for details.
3
Store credentials securely
Save the API user and secret in your secret manager. Jupico does not display the secret again. Never commit credentials to source control.
4
Confirm access
Call GET /status against production and confirm a 200 response.
Confirm every HTTP client uses a timeout of at least 35 seconds. See Timeout Handling.
2
Rollback flows
Verify transaction rollback logic runs on timeout and 500 responses.
3
Error handling
Confirm your integration surfaces safe messaging for HTTP 200/success: false outcomes and handles 400, 401, 403, 404, 500, and 503 server-side. See Error Handling.
4
Logging
Confirm every request logs the X-Request-ID, operation type, and outcome.
5
Reconciliation
Confirm settled transactions and payouts reconcile against your ledger using the Query API or Backoffice reports.