Challenge
An agent network means companies that must not see each other sharing one system. Not balances, not customers, not payment history, not reference data.
Each of them also wants to connect programmatically rather than click through an office, which calls for a public API, documentation for it, and behaviour a partner can predict before any contract is signed.
Solution
The platform is split into four parts with separate jobs: a private API for the office, a public JSON-RPC interface for integrators, the agent office itself, and a documentation site.
Tenant isolation runs through every layer, and it is not a convention between developers but a requirement tested on its own, because one missing check means somebody else's data on screen.
Money is handled in two phases: a payment is reserved, sent to the provider, and only the provider's confirmation turns the reservation into an entry.
Architecture and implementation
The private API serves the office and the public JSON-RPC serves outside integrators. Agents get balances, payments, history and reports, plus a service catalogue whose fields depend on the provider. Payments carry explicit statuses and a way to resolve the ones that hang.
Stack: NestJS, PostgreSQL with functions and triggers, Redis for queues, React in the office.
Result
The platform is live and serving agents, and its public documentation does a job of its own. Outside payment companies read it to decide whether integrating with us is worth their time, and then arrive with offers to connect their own countries.
It is rare for the quality of an API to bring partners in directly.
