Skip to content

Build

How to Create an Online Payment System

"Online payment system" means different things to different founders. For one it's a service that lets shops accept cards. For another it's a wallet where people keep a balance and send money, and for a third it's the payments layer inside a marketplace. All three are online payment systems, and they need different licenses, partners and software.

This guide starts by sorting out which one you're building, because that decides everything after it. Then it covers how to create an online payment system of each kind, what they share, and when licensing the core software beats writing it.

Three kinds of online payment system

The difference between them is who holds the money and for how long. That single question decides your license and most of your architecture.

Kind What users do Who holds funds Usually needs
Merchant payment system (PSP) Businesses accept cards and local methods from shoppers You, briefly, between acquirer and merchant payout A payment license, acquirer contracts, PCI DSS
Wallet or stored-value system People keep a balance, pay and send money You, for as long as the balance stays An e-money license, safeguarding, a banking partner
Platform payment system A marketplace or SaaS takes payments and pays sellers You or a licensed partner, until seller payout A license or a PayFac or partner model, split payouts

If you're not sure which row you're in, look at your money flow on paper. Draw where a shopper's money goes and how long it stays with you before it reaches the merchant or seller.

How to create an online payment system for merchants

A merchant payment system is a payment service provider. It signs businesses, gives them a checkout, routes their payments to acquirers and pays them out after fees.

The software has two halves. The gateway carries payments from checkouts to acquirers, with a tokenization vault, routing, 3-D Secure and fraud screening. The back office onboards merchants, prices them, settles their money and reconciles it against what the acquirers paid. Teams that build a gateway themselves tend to plan the first half carefully and underestimate the second.

How to make a payment system with wallets

A wallet system adds accounts that hold value over time. That changes the regulation more than the code: in most countries, holding customer balances is e-money issuance or a similar activity, and it needs its own license with capital and safeguarding rules. The e-money license requirements differ by country.

On the software side, a wallet needs a ledger that records every balance change exactly once, user identity checks, limits and a way to load and withdraw money. Loading and withdrawing are card payments and bank transfers, so a wallet system still needs a payment gateway underneath.

How to build a payment system inside a platform

Marketplaces and SaaS platforms want payments inside their own product. Their customers pay, the platform keeps a fee and the sellers get the rest.

The key features are sub-merchant onboarding through an API, split payments and payouts across sellers, and reserves for sellers without a track record. The platform either becomes a payment facilitator under a sponsoring acquirer or works through a licensed partner, and a PayFac platform of its own suits the first route.

Steps every online payment system shares

Whichever kind you build, the order of work is similar. These steps apply to all three.

  1. Map the money flow and confirm which license it needs in each country.
  2. Choose acquirers, banks or payment partners, and start their onboarding early.
  3. Keep card data inside as few systems as possible, and give PCI DSS an owner before any code is written.
  4. Build or license the gateway, then the ledger or back office your kind needs.
  5. Connect the local payment methods your users actually prefer.
  6. Test every flow with partners, pass their certification and your PCI DSS assessment.
  7. Launch with a small group of users and watch the first settlements closely.

Steps 1 and 2 decide your launch date. Partners and regulators work on their own schedules, so starting them late delays everything else.

Build for one country, then grow

Online payment systems usually start in one market. The local methods there matter as much as cards: bank transfers in some countries, wallets in others, cash-based vouchers in a few.

Plan the second market before you finish the first, because each country brings a new license question and new connectors. Our on-premises clients include payment companies in Lebanon, Jordan, Egypt and the Gulf.

The faster route for the payment part

Choosing to build an online payment system from scratch commits you to a project measured in many months. For many founders, the gateway and merchant back office aren't the product that makes them different, so licensing them frees the team for the parts that are.

Our white label gateway covers the merchant payment system end to end: 700+ ready connectors, routing and cascading, 3-D Secure, fraud screening and a merchant management system with settlements and reconciliation.

It runs as SaaS, where processing starts in about 5 business days on average with ready connectors, or in your own cloud account or on your own servers. We provide the software and stay out of the flow of funds, so the license and the money stay with you.

Questions

How do I create an online payment system for my country?

Start with the money flow and the license your country requires for it, then pick acquirers or banks and the local payment methods people use. Build or license the gateway and back office, pass PCI DSS and partner certification, and launch with a small group first.

Do I need a license to make a payment system?

Usually, if you hold or move other people's money. Merchant payment systems tend to need a payment institution license, and wallets an e-money license, though the rules differ by country.

Can I build a payment system like PayPal?

PayPal combines a wallet, merchant payments and its own licenses in many countries, so building a system like PayPal means building all three businesses, not one.

What's the difference between a payment gateway and a payment system?

A gateway carries payments between checkouts and acquirers. A payment system is the whole business around it, including merchant onboarding, settlements, balances where there are any, and the licenses behind them.

Start with the payment core

Tell us which kind of payment system you're building and where, and we'll show which parts our gateway covers.