Going live

When your sandbox integration passes every test case, apply for production access from the product’s Production tab.

9.1 What you need

A registered EcoCash merchant line (merchant MSISDN). There’s an I Don’t Have a Merchant Line option if you don’t have one yet.
A completed, signed-off test script covering all four PIN scenarios, plus lookup and refund (7.6).
Confirmation of the merchant ownership disclaimer.

9.2 Steps on the Production tab

Merchant MSISDN validation: enter your merchant line and click Validate Merchant.
Capture test evidence: run your sandbox test cases. The portal records the requests as evidence (Captured Test Evidence).

Download Completed Test Script: the Excel workbook is generated from your captured evidence. Complete it:

Column	Filled by
Test Case ID, API Tested, Test PIN Used, Merchant Reference, Expected Result	Pre-filled / you
Actual Result, Status (Pass/Fail), Comments	You

Submit Production Request with the script attached, then track it under My Production Requests.

EcoCash reviews the script together with your merchant MSISDN. The target is 2 business days. Production credentials arrive in your portal Inbox.

9.3 Go-live checklist

Credentials and merchant PIN are loaded from a secret store, not from code
Every charge gets a new unique clientCorrelator, saved before sending
A timeout never triggers a second charge; the code looks the charge up first
Only SUCCESS fulfils an order; unknown results go to review, not to “failed”
Callbacks are verified with a lookup (and signature-checked), and handled idempotently
Refunds use a new correlator, the original reference, and an amount ≤ the original
4xx errors aren’t retried; 500/503 retry with backoff
Request bodies are redacted in logs (they contain merchantPin)
The production base URL and credentials come from config

This page is generated from section 9 of the README in README.md. Spotted something wrong? Open an issue.