Technology & APIs
Documented REST APIs, a working sandbox, webhook callbacks and a partner console — so your team can integrate bill payments without guesswork.
Two ways to go live
Some partners want to own the customer experience end to end. Others just want a working counter tomorrow morning. We support both, on the same underlying platform.
API integration
JSON over HTTPS, signed requests, idempotency keys and webhook callbacks. Plug bill payments into your existing app, core banking system, ERP or POS software.
Partner web console
A ready browser-based counter for institutions that do not want to build anything: agent management, bill fetch, payment capture, receipts and reports.
Core API surface
-
GET
/v1/categoriesList live biller categories -
GET
/v1/billersSearch billers by category, state or name -
GET
/v1/billers/{id}Fetch input parameters and validation rules -
POST
/v1/bill/fetchFetch a live bill for a consumer number -
POST
/v1/bill/paySubmit a payment against a fetched bill -
GET
/v1/transactions/{id}Check transaction status and reference number -
POST
/v1/complaintsRaise a transaction or service complaint -
GET
/v1/settlementsDownload settlement and reconciliation files
Endpoint paths are indicative. The current specification, request signing details and Postman collection are shared with partners at the sandbox stage.
Things we take seriously
Payments code is judged on its worst day, not its best one.
Signed requests
Every call is authenticated and signed. Credentials are scoped per environment and rotatable without downtime.
Idempotency
Payment submissions carry an idempotency key so a retry after a timeout never becomes a double debit.
Webhook callbacks
Asynchronous status updates delivered with retries and exponential backoff until acknowledged.
Environment parity
Sandbox mirrors production behaviour including failure and dispute scenarios, not just happy paths.
Observability
Transaction-level logs, latency dashboards and alerting on error-rate thresholds.
Human support
A named integration engineer during certification and a technical escalation path after go-live.
What your developers can expect
Most teams reach sandbox certification in one to two sprints. The paperwork usually takes longer than the code.
Request Sandbox AccessSandbox credentials
You receive base URLs, API keys, signing keys and a Postman collection with worked examples.
Build against test billers
Test billers cover success, pending, failure, refund and dispute paths so you can handle each one properly.
Certification review
We review your request signing, error handling, idempotency and receipt formatting against network rules.
Production keys
Live credentials issued after certification sign-off, with rate limits set to your expected volume.
Monitored go-live
First transactions watched jointly, with a direct escalation channel open during the ramp-up window.
Send us your integration questions
Tell us what you are building and which platform you are building it on. We will send the API documentation and set up a technical call.