Skip to content

Build

How to Build a Payment Gateway for a Bank

A bank that wants to offer online payments to its business customers already has most of what a PSP lacks: the license, the acquiring relationship, the merchants' accounts and their trust. What it often lacks is modern software for the online part, with a branded checkout, fast merchant onboarding and a dashboard merchants actually use.

This page is for banks planning a payment gateway for a bank's own merchants. It compares the three routes to payment processing software for banks, sets out how such a project usually runs inside a bank, and covers two topics that come up early: data rules and pay by bank.

Three routes to a payment gateway for a bank

Banks get there in one of three ways. The choice depends on the bank's engineering capacity, its existing vendors and how quickly it wants to launch.

Route What it means When it fits
Build in-house The bank's IT team designs, builds and certifies the gateway The bank has a large payments engineering team and wants full ownership
Extend the core or card vendor The bank adds a gateway module from its existing core banking or card processing vendor The vendor's module meets the bank's needs and timeline
License white label gateway software The bank runs a ready gateway under its own brand, on its own infrastructure or as SaaS The bank wants a modern merchant experience quickly

Some banks combine the last two. The card processor keeps doing scheme processing, and a white label gateway sits in front of it for online merchants.

If you were a bank starting an online payment gateway

Inside a bank, the technical work is only one track. Governance, procurement and risk review run alongside it and often set the pace. A typical sequence looks like this.

  1. Define the product: which merchants, which payment methods, which countries and which channels.
  2. Decide the route above, and run vendor due diligence if you license.
  3. Take the plan to the risk committee, with data location, outsourcing and security in writing.
  4. Choose the deployment: in the bank's data center, in a cloud account the bank controls, or as SaaS where rules allow it.
  5. Connect the gateway to the bank's card processor and core systems.
  6. Brand the payment page, merchant dashboard and reports, and set up merchant pricing.
  7. Run testing, certification and the PCI DSS assessment for the bank's environment.
  8. Migrate existing online merchants in waves, starting with a small group.

Steps 3 and 4 are where bank projects slow down most. Bringing data residency and outsourcing answers to the first committee meeting saves weeks.

Data rules and where the gateway runs

Banks often operate under rules on where payment data may be stored and processed. Saudi Arabia's SAMA and Qatar's QCB, for example, set expectations on where that data sits, and EU banks also work under outsourcing and operational resilience rules for their technology vendors.

That's why self-hosting matters more for banks than for most PSPs. Our gateway runs on servers the bank owns, inside a private cloud or in a local region of one of the big cloud providers, with deployment in about 30 days in a cloud account and about 60 on dedicated infrastructure. An on-premises setup also leaves the timing of maintenance windows to the bank.

How to integrate pay by bank into a PSP platform

Pay by bank lets a shopper pay straight from their bank account through an online banking approval, instead of with a card. For a bank, it's a natural addition, since the money moves between accounts it may already hold.

In the EU and UK, pay by bank usually runs through payment initiation under open banking rules. Open Banking Limited reported in July 2026 that more than one billion open banking payments had been initiated through the UK's major banks since open banking launched. In other markets, national instant payment schemes play the same role.

To add it to a gateway, the method needs a connector like any other: either to an open banking provider or directly to the scheme. Once connected, the hosted payment page shows it next to cards by the shopper's location, and routing, reporting and reconciliation treat it like any other payment method.

What the merchant side needs from day one

A bank's merchants compare its gateway with fintech PSPs, so the merchant experience can't feel like an afterthought. Online onboarding, a branded checkout on the bank's domain, a dashboard with transactions, statements and settlement status, and clear pricing are the minimum.

Existing merchant accounts should move across without re-onboarding. On our platform, they can be imported into the merchant management system, so the bank keeps its portfolio intact during the switch.

Questions

What payment processing software do banks use for online merchants?

Banks use gateway software from their core or card processing vendors, white label gateway software they license and brand, or in-house builds. Some combine a card processor for scheme processing with a separate gateway for online merchants.

Can a bank run a white label payment gateway on its own infrastructure?

Yes. Self-hosted deployment runs the same software in the bank's data center or cloud account, which helps with data residency rules. The bank's environment then needs its own PCI DSS validation.

How long does it take a bank to launch an online payment gateway?

Technical deployment of licensed software takes about 30 to 60 days on the bank's own infrastructure with ours. Governance, procurement and risk review often take longer than the technology.

How does a bank add pay by bank to its gateway?

Through a connector to an open banking provider or a national instant payment scheme. The method then appears on the payment page and flows through the same routing and reconciliation as cards.

Plan your bank's gateway with us

Bring your data rules, card processor and merchant numbers, and we'll map out a deployment for your bank.