Skip to content

Platform modules

White Label Acquiring Software for Banks and PSPs

Some acquiring banks still sign online merchants with paper forms, send them to a gateway the bank doesn't control and settle them from a system built for card terminals. Merchants notice. They compare that experience with fintech PSPs that onboard online and give them a dashboard on day one.

White label acquiring software closes that gap without replacing the bank's acquiring license or its processor. This page explains which layers of a merchant acquiring platform our software covers, how it connects to what you already run and why banks often host it themselves.

The layers of a merchant acquiring platform

An acquiring business runs on several layers of software, and they rarely come from one vendor. It helps to name them before deciding what to replace.

Layer What it does Who provides it
Merchant onboarding and management Applications, KYB, underwriting, pricing, settlements, merchant dashboard Our software
E-commerce gateway and checkout Hosted payment page, SDKs, plugins, host-to-host Our software
Routing and fraud screening Rules across processors and methods, 150 configurable fraud filters, 3-D Secure Our software
Acquiring processing and scheme connectivity Authorization with the card schemes, clearing Your processor or processing partner
License and merchant contracts The acquiring license, the merchant agreement, the funds You

We aren't a processor or an acquirer. Our software sits in front of the processing layer and connects to it, so the bank keeps its license, its scheme memberships and its merchant contracts.

What a bank gets from merchant acquiring software

The point of modern merchant acquiring software is a better merchant experience on top of the bank's existing rails. In practice that means three changes.

Online onboarding instead of paper

Merchants apply through a structured form, and the system checks the business and its owners through the verification provider the bank chooses. Edge cases go to the bank's underwriters with all the context, and an approved merchant gets its merchant ID, pricing and access in one step.

A branded e-commerce gateway

The payment page runs on the bank's domain with its logo, in 25+ languages, and shows cards, wallets and local methods by the shopper's location. Merchants connect through a hosted page, CMS plugins, iOS and Android SDKs or host-to-host.

A dashboard merchants use

Each merchant gets a self-service view of its transactions, statements and settlement status under the bank's brand. Questions that used to reach a relationship manager by phone are answered there.

Connecting to your processor and other providers

Your existing processor is reached through a connector like any other provider, and if we don't have one for it yet, we build it in about 14 days from the processor's documentation.

The same gateway can reach 700+ other connectors to acquirers, PSPs and payment methods. A bank can add a local wallet or a bank transfer method next to its own card acquiring without a new integration project for each one.

A cross-border acquiring platform for PSPs

PSPs face a different problem from banks. Their merchants sell abroad, and cross-border card payments usually carry extra scheme and interchange costs. A cross-border acquiring platform lets the PSP hold acquiring relationships in several markets and route each payment to the right one.

Routing rules use region, card type and cost, and cascading retries a declined payment on another acquirer in the same attempt. The platform supports 200+ currencies, and the payment orchestration layer keeps the reporting from every acquirer in one place.

Hosting it inside the bank

Some banks can't send cardholder data to a vendor's cloud, either because a regulator requires in-country processing or because their own policy does. The gateway runs on dedicated servers, in a private cloud or in a local region of AWS, Azure, Google Cloud or Oracle Cloud, so data stays in the country.

Our on-premises clients run in Saudi Arabia, Qatar, the UAE, Egypt, Kuwait, Lebanon and Jordan, under supervisors including SAMA and QCB. The platform is PCI DSS v4.0.1 Level 1 certified. On the bank's own infrastructure the bank certifies its environment and we support the audit. A cloud deployment takes about 30 days and dedicated servers about 60.

Security in white label acquiring software

Risk committees ask about security first. Card data is tokenized and vaulted, with network tokens for stored cards, and 3-D Secure 2 runs on the gateway or through an external MPI the bank already uses.

Anti-fraud plans can differ per merchant, merchant group or MID, while roles and permissions control who in the bank can see and change what, with a full audit trail for internal review and regulators.

Questions

Does the software replace our acquiring processor?

No. It connects to your processor through a connector and adds onboarding, an e-commerce gateway, routing and a merchant dashboard in front of it. Scheme connectivity and the license stay with you and your processor.

Can fintechs use merchant acquiring software without a bank?

A fintech can run the software, but it still needs an acquiring partner and, in most countries, a license to serve merchants. We can refer an acquiring partner that fits its markets.

Can the dashboard be in our local language?

The payment page runs in 25+ languages on any setup. Dashboard localization is available on self-hosted deployments.

How do existing merchants move to the new platform?

The bank's current merchant accounts move across by import, so nobody re-onboards the whole portfolio.

See it on your own rails

Tell us which processor you use and where your data has to stay, and we'll show the setup that fits.