Go-Live Checklist
1. Environment Setup
1. Environment Setup
Confirm your production environment is fully configured before flipping the switch.
- Production API credentials generated
- Sandbox credentials removed from production code and configuration
- Base URL updated from
https://sandbox-platform.jupico.com→https://platform.jupico.com - All API requests use HTTPS
- IP allowlisting configured (if required)
2. Payments Testing (Required)
2. Payments Testing (Required)
Test all critical transaction scenarios in sandbox before going live.Card Payments
- Successful sale transaction
- Declined / failed transaction
- Authorization + capture flow
- Refund flow
- Void flow
- Successful transaction
- Failed transaction (invalid account, insufficient funds)
- Refund / reversal flow
- All responses handled correctly
- Transaction statuses mapped correctly
- Idempotency / duplicate prevention considered
3. Webhooks & Event Handling
3. Webhooks & Event Handling
Verify your webhook infrastructure is production-ready before going live.
- Webhook endpoint is publicly accessible
- Webhooks configured in your production environment
- All required events handled:
- Payments
- Refunds
- Failures
- Duplicate webhook handling implemented
- Retry logic supported
- Webhook signatures validated (if applicable)
4. Onboarding & Merchant Flows
4. Onboarding & Merchant Flows
Validate end-to-end onboarding before accepting live merchant applications.
- End-to-end onboarding completed successfully
- Invite flow tested for:
- New applicant
- Existing applicant (additional submerchant location)
- All required fields captured correctly
- Business type logic validated (SSN / EIN / ITIN)
- Owner and contact flows validated
- Application status transitions verified
- Rapid (Jupico-branded) flow tested
- Flex (custom-branded) flow tested (if applicable)
5. Error Handling & Resilience
5. Error Handling & Resilience
Ensure your integration handles failure scenarios gracefully.
- 4xx errors handled gracefully (validation errors)
- 5xx errors handled with retry logic
- Timeouts handled correctly
- User-facing error messages implemented
6. Backoffice Validation
6. Backoffice Validation
Confirm that data flows correctly through to reporting and settlement.
- Transactions appear in Backoffice
- Refunds display correctly
- Merchant data is visible and accurate
- Reporting and exports validated
- Settlement data verified
7. Security & Compliance
7. Security & Compliance
Review your security posture before exposing your integration to live traffic.
- API credentials stored securely (no frontend exposure)
- Sensitive data is not logged
- Tokenization used where applicable
- PCI scope understood
8. Monitoring & Alerts
8. Monitoring & Alerts
Set up observability so you can detect and respond to issues quickly after launch.
- API request logging enabled
- Webhook delivery logging enabled
- Alerting configured for:
- Failed transactions
- API errors
- Webhook failures
- Support escalation path defined
9. Go-Live Execution
9. Go-Live Execution
Complete these steps when you are ready to flip to production.
- Production credentials deployed
- First live transaction completed successfully
- Transaction verified in Backoffice
- Stakeholder sign-off obtained
10. Post Go-Live (First 24–72 Hours)
10. Post Go-Live (First 24–72 Hours)
Monitor your integration closely in the first few days after launch.
- Monitor transaction success rate
- Validate settlement reports
- Confirm webhook delivery reliability
- Review logs for unexpected errors
- Validate onboarding submissions
Common Go-Live Issues
Avoid these mistakes that frequently trip up integrations at launch:Need Help?
If you encounter issues during your go-live:- Contact your Jupico implementation manager
- Reach out via Jupico Support
- Review your API logs and webhook events for debugging clues