Payment Gateway Engine
A complete payment gateway engine — connect to an existing gateway, or become one.
A complete payment gateway engine for gateways and aggregators. Connect it to an existing acquirer or use it to stand up a new gateway, then sell online collection to your merchants under your own brand. We support the PCI DSS and ISO 27001 certification process; certification and audit fees are yours.
Updated August 2026
Becoming a gateway is mostly engineering you should not have to write twice.
Whether you are an aggregator adding your own processing or a company standing up a gateway from scratch, the same components are required: merchant onboarding, a checkout that converts, transaction handling, refunds, reconciliation, settlement and reporting merchants will trust.
None of that is where you compete. You compete on pricing, on acquirer relationships, on which merchants you can win and how well you serve them. The engine underneath is table stakes, and building it takes a year that most companies do not have.
So the engine exists and you brand it. Connect it to an acquirer you already work with, or use it as the base for a new gateway. Your merchants see your product; we keep the engine current.
It runs in production as part of the Kuickpay ecosystem, which is where our founder spent six years as CTO. That is where the understanding of what actually clears in these markets comes from rather than from documentation.
What it looks like.
Representative screens, not screenshots — the live product carries your branding, not ours.
What the engine covers.
Merchant onboarding
Registration, verification, configuration and going live. The workflow that decides how fast you can grow.
Checkout that converts
Card and wallet, mobile-first, with the failure paths handled properly — where most payments are actually lost.
Transaction processing
Authorisation, capture, void, refund and partial refund, with a state a merchant can understand.
Acquirer connections
Connect to the acquirers you already work with, or to new ones as you add them.
Reconciliation
Transactions matched to settlement batches. The part merchants ask support about most.
Settlement and payouts
What each merchant is owed, when it moves, and a record they can check against their bank.
Risk and limits
Velocity rules, per-merchant limits and flags, so a problem merchant is visible before it is expensive.
Merchant reporting
Numbers that reconcile with the money. A dashboard that disagrees with settlement destroys trust quickly.
What the engine gives you, and what stays yours.
Being clear about the boundary matters — particularly on certification, where the cost sits with you.
| We provide | You provide | |
|---|---|---|
| The engine | Onboarding, checkout, processing, settlement | Your brand and pricing |
| Acquirer relationships | The integration | The commercial relationship |
| PCI DSS | The process, controls and evidence | Certification and audit fees |
| ISO 27001 | The process and documentation | Certification and consultancy fees |
| Merchant relationships | The tooling | Sales, support and pricing |
| Maintenance | Engine, scheme changes, new methods | Your operations |
Who this is for.
Aggregators moving to their own processing
You have merchants and want the economics of running the gateway rather than reselling one.
Companies standing up a new gateway
You have the acquirer relationship and the market, and need the engine that sits between them.
Existing gateways on legacy software
A platform that works and cannot keep up — with merchants asking for things it cannot do.
Not for a single merchant
If you are one business taking payments, use a gateway. This is infrastructure for someone selling payment collection onward.
How it goes.
We map what you have
Acquirer relationships, existing merchants, and whether you are extending a gateway or standing one up.
We agree the boundary
What is branded yours, what merchants configure, and who does what on certification. In writing, early.
We connect to your acquirer
Or acquirers. Your commercial relationships stay exactly as they are.
We work through certification
PCI DSS and ISO 27001 — controls, evidence and documentation. You engage the auditor and carry those fees.
We test the failure paths
Declines, timeouts, double submissions, 3-D Secure returns. The happy path is the easy part.
You onboard merchants gradually
A first group, watching completion and settlement before opening it wider.
We maintain the engine
Scheme changes, new payment methods, and the ongoing work of keeping completion rates up.
What people ask.
The whole engine. Merchant onboarding, checkout, transaction processing, refunds, reconciliation, settlement, risk rules and merchant reporting. The checkout is the part shoppers see and the smallest part of what a gateway actually needs to run.
We provide the process — the controls, the evidence collection and the documentation an auditor will ask for. What we do not do is certify you, because no supplier can both prepare and audit credibly. The certification fees and any external consultancy are yours, and we would rather that boundary be explicit from the first conversation than discovered during budgeting.
Yes, and that is the usual case. Your acquirer relationships, your commercial terms and your settlement arrangements stay exactly as they are — the engine sits between your merchants and the processing you already have. If you are adding acquirers later, that is an integration rather than a rebuild.
Yes, provided you have or can obtain the acquirer relationship and the regulatory position your market requires. We supply the engine and support the certification process; we cannot supply the licence or the banking relationship, and any supplier suggesting otherwise should be questioned.
Yes, as part of the Kuickpay ecosystem, reached through the banking apps most Pakistanis already use. Our founder was CTO there for six years. That is also where the understanding of local payment behaviour comes from — which methods clear, which fail quietly, and what merchants actually complain about.
Longer than the invoicing product, and it depends heavily on certification and acquirer integration rather than on our engineering. We will give you a realistic sequence at the first conversation, including which parts are gated by your auditor and your acquirer rather than by us.
Let's build what's next.
Tell us what you’re building. We’ll tell you how we’d help.