Go-Live Process
Go-Live Process
This section outlines the complete process that the partner needs to follow in order to successfully integrate and go live with the Prepaid Recharge APIs.
1. Access to Sandbox Environment
• Partner receives sandbox API credentials from Nuclei.
• Partner integrates the APIs in the sandbox.
• Partners should simulate complete recharge flows using test data.
• Partner to host a callback URL (optional) to test webhook responses from Nuclei.
2. UI/UX Readiness
• Finalize front-end designs for:
• Mobile number entry
• Operator & circle selection (automatic & manual fallback)
• Plan browsing and selection
• Ensure graceful handling of edge cases (validation failures, API downtime, etc.)
• Error messages for validation failures
• Payment confirmation screens
• Recharge status/result page
3. UAT Testing
• Complete end-to-end test cases executed in the sandbox:
• The operator fetched automatically
• Operator not found – manual selection
• Plan browsing
• Validation success
• Validation failure
• Payment flow simulation
• Fulfillment success and failure cases
• Confirm the callback URL is correctly receiving final status updates.
4. Request for Production Access
• Partner shares:
• Final callback URL (if applicable)
• IP whitelisting (if required)
• SSL certificate or domain configuration (if HTTPS endpoints are used)
• Confirmation of test cases executed
• Nuclei provides production credentials and endpoint URLs.
5. Production Integration & Dry Run
• Partner integrates production APIs with real user flows.
• Perform limited dry-run transactions with internal testers using real mobile numbers .
(within the allowed limit).
• Monitor API performance and final status callbacks during dry run.
6. Go-Live Approval
• Partner shares the go-live checklist report with:
• UAT sign-off
• Dry-run results
• Callback testing logs
• Screenshots of UI flows (optional)
• Nuclei provides the final go-ahead for launch.
7. Go-Live & Monitoring
• Recharge feature launched for end users.
• Nuclei and partner teams monitor traffic and performance.
• Both teams align on error-handling processes:
• Alerts for high failure rates
• Fallback mechanisms
• Support and escalation matrix