Skip to content

Build

On-Premises Payment Gateway: When PSPs Need One

An on-premises payment gateway is gateway software that runs on infrastructure you control, your own servers or your own cloud account, instead of the vendor's shared SaaS environment. It's also called a self hosted payment gateway. The software is the same; what changes is where it lives, who operates the servers and whose PCI DSS scope the hosting falls into.

Most PSPs don't need one. Some can't operate without one. This page explains how to tell which group you're in, what the deployment options are and how the work splits between you and the vendor.

Who needs an on-premises payment gateway

The reasons are almost always regulatory or contractual, rarely technical. If none of the cases below applies to you, hosted SaaS gets you live faster with less to run.

Situation Why it points to on-premises
A regulator sets where payment data is stored and processed Supervisors such as SAMA in Saudi Arabia, QCB in Qatar and Egypt's FRA set rules on where payment data sits
A license condition requires in-country processing The license itself rules out a foreign data center
A bank's own policy keeps cardholder data inside its infrastructure Internal risk rules can be stricter than the regulator's
Volumes across several group entities are consolidated One platform on owned infrastructure can serve every entity

Data rules are the trigger in the first row. Our own on-premises clients are licensed banks and PSPs in Saudi Arabia, Qatar, Egypt and four other countries in the region.

Three ways to deploy an on-premises payment solution

On-premises doesn't have to mean racks in your own basement. There are three variants, and they differ mostly in how much hardware you manage.

  1. Dedicated infrastructure, meaning servers you own or rent in a data center you choose.
  2. A private cloud hosted in your own environment.
  3. Your own account with a public cloud provider such as Oracle Cloud, AWS, Azure or Google Cloud, in a region inside your country.

A cloud account is often the quickest variant when a local cloud region exists, because it keeps data in the country without buying hardware. The first suits institutions whose policy rules out public clouds altogether.

Who does what

A self hosted payment gateway still comes with the vendor's work. The split looks like this on our deployments.

Task You We
Hosting environment (servers or cloud account) Provide and own it Agree the setup with you
Deployment and configuration Give access Deploy, configure and connect
Connectors to acquirers and methods Hold the contracts Enable 700+ ready connectors, build missing ones
PCI DSS Certify your hosting environment Platform is PCI DSS v4.0.1 Level 1 certified; we support the audit
Updates and support Schedule maintenance windows Deliver updates and support through a dedicated account manager

The PCI DSS row is the one to plan for. On SaaS our certification covers the platform; on your own infrastructure the hosting environment is in your scope, so you need your own assessment.

How long deployment takes

Deployment time depends on the model and on how ready your infrastructure is. Ours typically takes 30 to 60 days.

In a cloud account you control, plan on about 30 days. On dedicated infrastructure or another provider, plan on about 60. Much of the difference comes from preparing hardware, networking and security reviews on your side, which is why it pays to prepare the environment before the contract is signed.

On-premises payment gateway for PSPs versus SaaS

Hosted SaaS and on-premises run the same software, so the comparison is about operations, not features. These are the differences that decide it.

SaaS On-premises
Where data lives The vendor's hosting regions Your servers or cloud account, in your country
Time to start About 5 business days with ready connectors About 30 to 60 days
PCI DSS Vendor's certification covers the platform You certify the hosting environment
Infrastructure work None Yours, or your cloud provider's
Control over maintenance timing Vendor's schedule Yours
Uptime commitment 99.95% uptime SLA on ours Depends on your environment

An on-premises payment gateway for PSPs makes sense when the first row is a legal requirement. If it's only a preference, compare the extra hosting and audit work against what you gain.

Features don't change with deployment

The self-hosted gateway is the same product you'd get on SaaS. You get the 700+ connectors, routing and cascading, 150 built-in configurable fraud filters, 3-D Secure and the merchant management system, with branding across every screen.

Two things become possible only on your own infrastructure. You decide when maintenance happens, and dashboard localization is available, while the payment page runs in 25+ languages on any setup. You can also add capacity or new providers as you grow without rebuilding the setup.

Questions

What is an on-premises payment gateway?

It's payment gateway software installed and run on your own infrastructure, your servers or your own cloud account, so you control operations, security and where data is stored. It's also called a self hosted payment gateway.

Can I deploy it on any cloud provider?

On ours, yes: Oracle Cloud, AWS, Azure, Google Cloud or another provider you prefer, as well as dedicated servers or a private cloud.

Does on-premises deployment make us compliant?

It keeps transaction and cardholder data in your country, which helps with data residency rules. Licensing and other regulatory obligations stay with your company and its regulator, and your hosting environment needs its own PCI DSS validation.

Can I use my existing acquirers?

Yes. The gateway connects to your current acquirers, gateways and payment methods, and one integration gives you access to 700+ pre-integrated providers.

Plan a deployment on your infrastructure

Tell us where your data has to stay and what infrastructure you have, and we'll map out the deployment.