Go-Live Checklist
Go-live Checklist
Use this checklist to ensure your integration is production-ready before processing live transactions.
This checklist covers:
- Payments validation
- Onboarding flows
- Web-hooks & async handling
- Backoffice verification
- Operational readiness
Skipping steps in this checklist may result in failed transactions, missing data, or reconciliation issues.
Who should use this
- Developers completing an integration
- Product / Ops teams validating readiness
Before you begin
Make sure you have completed:
✅ Go-live Checklist
1. Environment Setup
-
Production API credentials generated
-
Sandbox credentials removed from production code
-
Base URL updated to production
https://sandbox-platform.jupico.com→https://platform.jupico.com -
All API requests use HTTPS
-
IP allowlisting configured (if 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
eCheck / ACH
- Successful transaction
- Failed transaction (invalid account, insufficient funds)
- Refund / reversal flow
Validation
- All responses handled correctly
- Transaction statuses mapped correctly
- Idempotency / duplicate prevention considered
3. Webhooks & Event Handling
-
Webhook endpoint publicly accessible
-
Webhooks configured in production
-
All required events handled:
- Payments
- Refunds
- Failures
-
Duplicate webhook handling implemented
-
Retry logic supported
-
Webhook signatures (if applicable) validated
👉 See: Webhooks
4. Onboarding & Merchant Flows
-
End-to-end onboarding completed successfully
-
Invite flow tested for:
- New applicant
- Existing applicant (additional sub-merchant location)
-
All required fields captured correctly
-
Business type logic validated (SSN / EIN / ITIN)
-
Owner / contact flows validated
-
Application status transitions verified
Hosted Onboarding
- Rapid (Jupico-branded) flow tested
- Flex (custom branded) flow tested (if applicable)
5. Error Handling & Resilience
- 4xx errors handled gracefully (validation errors)
- 5xx errors handled with retry logic
- Timeouts handled correctly
- User-facing error messages implemented
👉 See:
6. Backoffice Validation
- Transactions appear in Backoffice
- Refunds display correctly
- Merchant data visible and accurate
- Reporting / exports validated
- Settlement data verified
7. Security & Compliance
- API credentials stored securely (no frontend exposure)
- Sensitive data is not logged
- Tokenization used where applicable
- PCI scope understood
👉 See: Security Guide
8. Monitoring & Alerts
-
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
- Production credentials deployed
- First live transaction completed successfully
- Transaction verified in Backoffice
- Stakeholder sign-off obtained
10. Post Go-live (First 24–72 Hours)
- 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 common mistakes:
- Using sandbox credentials in production
- Only testing successful transactions (no failure scenarios)
- Not handling duplicate webhooks
- Not validating refunds or voids
- Missing error handling for edge cases
- Not verifying data in Backoffice
📌 Need Help?
If you encounter issues during go-live:
- Contact your Jupico implementation manager
- Reach out via Support
- Review API logs and webhook events for debugging
💡 Notes
- Not all checklist items may apply depending on your integration
- This checklist should be completed before processing live payments
- You can print or copy this checklist for internal tracking