PAYMENT GATEWAY
White-label payment gateway for merchants
Your platform’s rails are an asset, the gateway turns them into a product. Merchants and partner platforms initiate and receive payments through your API, settle into accounts you hold for them, and reconcile against your books. A second business line, running on infrastructure you already operate.
Your rails, their business, one set of books
The gateway is the platform’s outbound face. A merchant, an online business, a marketplace, a partner platform embedding payments, connects through the API and moves money over the rails you run. Their funds settle into accounts held on your platform, which means their activity lives in your double-entry ledger like everything else: booked, balanced, reconcilable. You are not reselling someone’s gateway; you are operating your own, on your accounting.
API-first: merchants integrate like providers do
Merchant integration uses the same discipline as the rest of the integration layer: API access with per-partner credentials, token and key management, IP restriction, and inbound and outbound webhooks for event delivery. A merchant connects, authenticates as themselves, initiates and receives payments, and hears about every event the moment it happens, controlled, credentialed, observable, exactly the standard your own provider integrations are held to.
Checkout, settlement cycles and disputes, configured per programme
Merchants differ, so programmes do: checkout and collection flows, settlement cycles and dispute handling are configured per merchant programme, mapped to how each business actually collects and settles. And because merchants are clients of your platform, the tariff engine prices them like clients: gateway fees per merchant, down to an individual account, changed without a release, booked to their own income positions, merchant revenue that reports itself by line.
Gateway traffic under the same controls
Gateway volume is money movement, and it gets the platform’s full treatment: compliance screening before funds leave, per-client limits, policy-based routing to back-office review, and the attributable audit trail underneath. Merchant onboarding runs through the same tiered KYC/KYB as everything else. Your gateway business inherits your institution’s discipline, because it runs inside it, not beside it.
A second business line on infrastructure you already have
Institutions monetising their rails
Platforms serving marketplaces and software companies
Brands with merchant ecosystems
White-label payment gateway FAQ
Who can connect as a merchant?
How does a merchant technically integrate?
Where does merchant money sit?
How do settlement cycles and disputes work?
How do we price gateway services?
Is gateway traffic monitored like other payments?
Turn your rails into revenue
Bring one merchant use case, a marketplace, a platform, a web shop, and we will walk it through the gateway live: connection, payment, settlement, the entries behind it.