Payments
Payment Gateway
A merchant-ready payment gateway for invoices, hosted checkout, multi-rail collection, settlement, and disbursement — with a merchant portal operations can run.
For
Banks, PSPs under license, and institutions that collect fees or run merchant books.
You leave with
Merchant and admin portals, a stable collection API, and settlement finance can close without three tools.
Highlights
01
Merchant and admin portals
Merchants manage invoices and payment config. Operations manages merchants, pricing, and allowed processors.
02
Hosted checkout and APIs
A payment session merchants can open from web or API, with status and callbacks in one shape.
03
Settlement and disbursement
What the merchant is owed sits next to the collection path — not in a month-end spreadsheet.
Architecture
How the stack sits
Channels on top. Platform controls in the middle. Institution core and rails underneath — funds and regulated decisions stay with the licensed institution.
Layer 01
Merchant & admin portals
Checkout, invoices, and ops configuration under institution branding.
Layer 02
Gateway session layer
Payment sessions, status, and callbacks in one API shape.
Layer 03
Collection rails & settlement
Processors and settlement lines wired for finance close.
What UAT looks like
Invoice → checkout → settlement
UAT proves a live collection: invoice, hosted checkout, callback, and a settlement line ops can close.
Done means a real journey signed by your operators — not a deck alone.