Building a payment gateway from scratch means paying an engineering team for a year or more before the first merchant pays you. Most new PSPs don't need to.
The gateway is the part of the business that works the same way everywhere, so it can be licensed and branded, while the parts that make your PSP different, such as the merchants you sign and the way you price them, stay yours.
This page covers how to launch a PSP without building a gateway: what you skip, what you still own, the routes founders take and the order to do things in.
What you skip, and what stays with you
Licensed software removes the engineering work. It doesn't remove the regulated and commercial work, and plans go wrong when founders expect it to.
| Piece of the business | If you build | On licensed gateway software |
|---|---|---|
| Gateway core, routing, tokenization | Your engineers, for a year or more | Comes with the platform |
| Acquirer and payment method connectors | Built and certified one by one | Ready connectors, new ones added by the vendor |
| Merchant back office | Built next to the gateway | Onboarding, pricing, settlements and reports included |
| PCI DSS for the platform | Your own validation | The vendor's certification covers the hosted platform |
| License or licensed partner | Yours | Still yours |
| Acquirer contracts | Yours | Still yours |
| Compliance team, AML program, merchant risk | Yours | Still yours, with the tools in the platform |
The last three rows set your launch date. So the license and acquirer work starts on the first day, not after the software is picked.
Three ways to launch a payment business without building your own gateway
There's more than one way to skip the build. The routes differ in how much of the payments business you own, so pick by whether you want your own merchants and pricing under your own brand on the checkout, or a share of someone else's processing.
| Route | What you run | What it takes | Fits |
|---|---|---|---|
| White label gateway | Your own branded gateway and back office on licensed software | A license or licensed partner, acquirer contracts, an operations team | Founders who want to own merchants, pricing and margin |
| Payment facilitator under a sponsor | Sub-merchants signed through your platform, under a sponsoring acquirer | Registration with the sponsor, onboarding and risk processes | Software platforms that want to earn on their users' payments |
| Referral or reseller program | Introductions of merchants or PSPs to a vendor or processor | A sales channel and an agreement | Consultants, agencies and ISOs testing demand |
The first route gives the most control. The third gives the least. A payment facilitator carries the risk of every sub-merchant it signs, so the sponsor's onboarding rules shape the middle route from the start. Some founders begin with a referral agreement to test demand, then move to their own gateway once they have merchants to bring.
How to launch a PSP without building a gateway, step by step
The order matters more than the speed of any single step. These six steps put the slow outside work first.
- Choose the model and market, and check whether you need your own license or can work under a licensed partner.
- File the license application or sign the partner agreement, since this usually takes longest.
- Approach two or three acquirers at once and prepare for their due diligence.
- Shortlist gateway vendors and check their connectors against the acquirers and payment methods your merchants need.
- Set up the branded platform, your pricing rules and the onboarding flow, then test every payment and payout path.
- Go live with a small first group of merchants and widen once settlements and reports reconcile.
Step 4 is the one that's expensive to get wrong. A vendor without a connector to your main acquirer turns a configuration task into a development project, so ask for the connector list before the demo, not after the contract.
What the software covers from the first merchant
Our white label gateway is built for founders on this route. You get PSP software with a branded gateway, a merchant back office and 700+ ready connectors. Is your acquirer missing? A new connector takes about 14 days, and while it's being built the branding and pricing rules can be set up and tested on the connectors you already have.
The merchant side handles KYB and KYC onboarding with risk scoring, per-merchant tariffs, and settlements that deduct fees and hold rolling reserves before reconciliation. On SaaS, processing starts in 5 business days on average, and the hosted platform runs under our PCI DSS Level 1 certification.
Some regulators want the system inside your own infrastructure. A self-hosted setup in your own cloud account takes about 30 days, or about 60 on your own servers. Either way we supply the software and stay out of the funds flow, so the license and your merchants' money remain yours.
Adding crypto without building from scratch
A processor that wants to add crypto has two separate pieces to source. The chain side, meaning wallets and custody, comes from a crypto partner and brings its own licensing questions, such as authorization as a crypto-asset service provider under MiCA in the EU.
The fiat side is where a white label crypto gateway setup fits. Deposits arrive through local methods such as Pix and UPI and can be routed or cascaded between acquirers. Every attempt keeps a single ID through retries, so matching the fiat records against the chain side stays straightforward.
Questions
Can I become a PSP without development?
Yes, if you license gateway software instead of building it. You still need a license or a licensed partner, plus acquirer contracts and compliance staff. What you don't need is engineers to run the gateway.
What is a white label fintech solution for a PSP?
It's software one company builds and another runs under its own brand. For a PSP that means a gateway, a merchant back office and acquirer connectors, with your name and domain on every screen merchants see.
How long does it take to launch a PSP without building a gateway?
The software can be ready in days; on our SaaS, processing starts in 5 business days on average. License and acquirer reviews usually take months, so they set the real launch date.
Do I still need PCI DSS compliance on licensed software?
Yes. On SaaS the hosted platform is covered by the vendor's certification, and you still answer for your own environment, your staff and how your team handles card data.