Start here
Mobile Contract
The mobile app must stay metadata-driven where the backend owns operational truth.
Country metadata
Use:
GET /mobile/countriesGET /mobile/countries/{iso2}GET /mobile/countries/{iso2}/service-catalog
The mobile app should not hard-code phone prefix length, national number length, operators, operator logos, currency, or service availability.
Onboarding
The registration path is:
- Country and phone input.
- OTP issue.
- OTP verification.
- PIN creation.
- Register with
otpToken. - Wallet provisioning status.
Email is optional. Phone number is the primary identity.
Runtime unavailable states
If a feature is disabled in /mobile/readiness or the service catalog, the UI should show an honest unavailable state and optionally call POST /mobile/feature-interest.
Release build rule
Profile and release mobile builds must pass:
Code
Release builds reject missing or non-HTTPS API URLs.
Last modified on