1. Production credentials
1
Request production API credentials
Ask your Jupico account team for production API credentials.
2
Store credentials securely
Save the API user and secret in your secret manager. Never commit credentials to source control.
3
Confirm access
Call
GET /status against production and confirm a 200 response.2. IP allowlisting
Production requires that your server IP addresses be allowlisted. Sandbox accepts any source IP.1
Collect your server IPs
List every public egress IP used by services that call the Jupico API.
2
Share with Jupico
Send the list to your Jupico account team for allowlisting on production.
3
Test connectivity
From each source IP, call the production API and confirm a successful response.
3. Production base URL
Update your integration to point at the production base URL.4. Hosted tokenization web component
If you use the hosted tokenization web component, load the production build:5. Apple Pay domain verification
If your integration accepts Apple Pay, verify the domains that will invoke Apple Pay.1
Download the domain association file
Obtain the
apple-developer-merchantid-domain-association.txt file from Jupico.2
Serve the file
Host it at
https://<your-domain>/.well-known/apple-developer-merchantid-domain-association.txt on every domain that shows Apple Pay.3
Verify Apple can retrieve it
Fetch the URL over HTTPS to confirm it returns the file contents with a
200 response.4
Register the domain
Confirm domain registration with your Jupico account team.
6. Google Pay merchant registration
If your integration accepts Google Pay, register your merchant account with Google.1
Register with Google
Complete Google Pay Business Console registration for your merchant.
2
Capture proof
Take screenshots of the completed registration and any assigned merchant identifiers.
3
Provide screenshots to Jupico
Send the screenshots to your Jupico account team so production Google Pay can be enabled.
7. Webhooks
1
Register your production webhook endpoint
Provide the production HTTPS URL to Jupico. Use a different endpoint than sandbox.
2
Confirm subscribed events
Confirm the list of subscribed event types with your account team.
3
Test end-to-end
Trigger a real production event (for example, activating a submerchant) and confirm your endpoint receives it.
4
Verify authentication
Confirm the authentication mechanism agreed with Jupico is enforced on your endpoint.
8. Error, timeout, and reconciliation logic
1
Timeouts
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.
9. Operational readiness
1
Runbook
Document how the on-call team investigates payment failures, decline spikes, and webhook outages.
2
Support contact
Confirm the Jupico support escalation path is documented.
3
Alerting
Add alerts for repeated
500, 503, authentication, and webhook delivery failures.4
Rollback plan
Document how to quickly disable production traffic or revert to fallback processing if needed.
Ready to launch?
Authentication
Confirm production credential setup.
Environments
Verify base URLs and testing data.
Webhooks
Confirm your production endpoint and events.
Timeout Handling
Verify rollback flows against production.
Need help with any item? Reach out to your Jupico account team.