Base URLs
The API is provided in two environments.
| Environment | Base URL | Notes |
|---|---|---|
| Sandbox | https://staging.remittance.gofreshpay.com | Default after self-registration. Transaction amount capped at 1 USD. |
| Production | https://remittance.gofreshpay.com | Activated after a successful Go Live request. |
All API routes share the prefix /api/v1/remittance/… or /api/v1/merchant/….
Other subdomains
You will see these hosts referenced in the docs; here is what each one is for.
| Host | What it is |
|---|---|
dashboard.remittance.gofreshpay.com | Merchant dashboard SPA. Log in to manage your account, view transactions, top up wallets, get API keys, submit Go Live. |
partner.remittance.gofreshpay.com | Partner portal (operator-scoped) for telecom partners (Vodacom, Airtel, Orange). |
admin.remittance.gofreshpay.com | Moko internal admin console. Not for merchants. |
remittance.gofreshpay.com | Public landing (marketing) — same origin as the API. |
docs.remittance.gofreshpay.com | This documentation site. |
Connection & versioning
- HTTPS only (TLS 1.2+). Plain HTTP is rejected.
- Every request should include
Content-Type: application/jsonforPOST/PUT. - API version is
v1and is present in every path. There is no minor version negotiation via header — read the Changelog for content changes and use it to align your client.
Rate limiting
There is no strict per-second rate limit today. Callers who abuse the API get their INTERNAL_CRON_TOKEN, IP or merchant_code throttled per-incident, not by header. If you need documented rate limits (e.g. for a shared control panel), let us know and we'll add explicit limits per merchant tier.