Build and Release
Test, activate, and operate a Vendor USSD endpoint.
Build and Release
Test before UAT
Test locally before involving the mobile network, then add production-grade tests for state, signing, and business effects.
| Test | Expected behaviour |
|---|---|
| New session | HTTP 200, Continue, and the first menu. |
| Valid and invalid selections | Expected terminal response, or Continue with a helpful re-prompt. |
| Continuation reaches another instance | Journey continues from shared state. |
| Missing or expired state | Safe restart message; no unvalidated operation. |
| Irreversible operation is repeated | One business effect and consistent repeated handling. |
| Dependency is slow or unavailable | Controlled result within the gateway deadline; no false success. |
| Invalid signature, changed body, or stale timestamp | Rejected before business logic. |
| Repeated delivery ID | Handled according to the replay contract without duplicate effects. |
After Just-tap confirms routing and test setup, dial the assigned code on every launch network. Exercise each option, exit, invalid input, expiry, and controlled failures. Check actual phone display, including line breaks and message length, not only an HTTP client.
Production checklist
- The registered HTTPS URL is reachable and does not redirect.
- Request verification follows the agreed production configuration.
- Responses meet the JSON contract and 10-second deadline.
- State is shared and expires appropriately.
- Business operations are protected against duplicates.
- Invalid input, missing state, downstream failure, and uncertain outcomes have deliberate messages.
- Secrets and diagnostics are protected.
- The agreed UAT scenarios have passed on launch networks.
Submit the production endpoint and UAT outcome through the confirmed Just-tap activation process. After activation, dial the assigned code once more and verify the journey and monitoring.
To confirm before publication: Add the UAT environment, test networks or numbers, acceptance criteria, approval process, activation contact, endpoint-change and rollback procedure, and whether test and production use separate codes or secrets.
Monitor and troubleshoot
Track latency, non-200 responses, signature failures, dependency errors, missing-state events, and duplicate-operation attempts. Alert before latency approaches the 10-second deadline. Journey-completion and invalid-input rates can identify menu improvements.
| Symptom | Checks |
|---|---|
| No request reaches the application | Dialled code, routing activation, registered URL, and reachability. |
| Generic unavailable message | Latency, HTTP status, JSON shape, TLS, and redirects. |
| First menu works; later steps fail | sessionId, shared state, expiry, and current-step validation. |
| Signing verification fails | Secret decoding, exact raw body, headers, timestamp, and clock. |
| Text is cut off or formatted poorly | \n line breaks, concise text, and live-network display. |
| An operation happens twice | Atomic idempotency and durable operation records. |
When escalating, provide the environment, time and timezone, routing code, network, expected and actual behaviour, status, latency, and a safely shared correlation reference. Use the approved secure channel for sensitive data.