For partners
A tenant of your own. The engine underneath.
Banks, acquirers, aggregators — plug your operations into the Pokopay engine and get a whitelabelled portal for your CSAs and admins. Tenant isolation on every table, on every endpoint, on every screen.
Multi-tenant from the schema up
Each partner is a fully isolated tenant. Admin and CSA operators can only see merchants, terminals and wallets in scope — enforced server-side, checked again in the UI, audited on every write.
CSA workflows built in
A dedicated CSA role with the right defaults — search across the tenant, resolve merchant queries, act on their behalf, without seeing anything cross-tenant.
Processors & routing
Configure your acquirer stack, health checks, retry policies. Route by BIN, scheme, amount or your own rule set — surfaces the outcome per transaction in the reports.
Fee configuration you can reason about
Per-terminal fees with percentage, capped, flat, min and tiered rules. Preview any fee live with the Fee Simulator — same maths as settlement, no surprises for merchants.
Compliance-adjacent by design
Audit logs on every admin action, session revocation, absolute session cap, cryptographic keys never in the browser, PII scrubbed from logs and toasts. Ready for your QSA.
Whitelabel-ready
Brand tokens for logo, colours, tagline and legal URLs at the tenant level. Ship your customers a portal that looks like yours, on infrastructure that's ours to run.
The rails between
Your book is the tower. Their business is the market. Pokopay is the wire between.
The engine
Built for Nigerian rails.
NIBSS-compatible PTSP handshake, NGN-native settlement, Africa/Lagos date semantics everywhere. Runs on AWS Africa-adjacent regions with an audit trail your ops team can actually read.
Let's design the tenant that fits your book.