What it takes to launch a payment gateway
Starting a payment gateway company means building the infrastructure that lets merchants accept card payments, digital wallets, and other payment methods. You are not just writing software—you are handling other people's money, which means you need banking relationships, regulatory approval, fraud prevention systems, and the technical ability to move funds securely between customers, merchants, and banks.
The path depends on whether you want to build from scratch or resell existing infrastructure. Building your own requires significant capital, technical depth, and regulatory navigation. Reselling (becoming a payment facilitator or ISO) is faster but limits your control and margins. Most new entrants start as facilitators and move toward independence only after they have merchant relationships and revenue to justify the cost.
Key Takeaways
- You need a sponsor bank relationship before you can process any payments—this is non-negotiable and typically requires $250,000 to $1 million in capital or revenue.
- Regulatory requirements vary by state and country, but you will need money transmitter licenses in most U.S. states and compliance with PCI DSS, KYC, and AML rules.
- The three main models are payment facilitators (fastest to launch, limited control), independent sales organizations (moderate complexity, moderate margins), and full processors (highest cost, highest control).
- Your first customers will come from your own network or from referral partners, not from cold outreach—payment processing is a trust business.
- Fraud prevention, chargeback management, and settlement reconciliation are operational problems that cost money to solve and never stop being problems.
The three business models and what each requires
Payment Facilitator (PayFac) is the fastest entry point. You sign up under a sponsor bank's license, and that bank handles the regulatory heavy lifting. You onboard merchants, collect their fees, and the sponsor bank processes the actual transactions. Your costs are lower upfront—typically $50,000 to $200,000 to build the onboarding platform and integrate with the sponsor's API. Your margins are thinner because the sponsor takes a cut, but you can launch in 6 to 12 months.
Independent Sales Organization (ISO) sits in the middle. You recruit and support merchants, but you do not hold the merchant accounts yourself. Instead, you refer them to a processor or acquiring bank, and you earn a commission on their volume. This model requires less capital than a PayFac but more sales infrastructure. You are essentially a sales channel, not a platform. Margins depend on your negotiating power with the processor.
Full Processor means you own the merchant relationships, hold the money in escrow, and settle directly with banks. This is the most expensive path—$1 million to $5 million in capital, 18 to 36 months to launch, and ongoing compliance costs. You need a sponsor bank relationship, but you control the customer experience and keep the highest margins. Only pursue this if you have significant merchant volume or a specific vertical where you can differentiate.
Banking relationships and the sponsor bank requirement
No payment gateway exists without a sponsor bank. This is the bank that actually holds the merchant accounts, manages the reserve funds, and takes the regulatory risk. You cannot build a gateway and then find a bank—you must identify a sponsor bank before you build anything.
Sponsor banks are selective. They want to see a business plan, proof of capital, a management team with payment industry experience, and a clear customer acquisition strategy. They also want to understand your fraud controls and chargeback management before they agree to sponsor you. Expect the conversation to take 3 to 6 months, and expect them to say no if you cannot demonstrate that you will be profitable and compliant.
The relationship costs money. Sponsor banks typically charge setup fees ($25,000 to $100,000), monthly platform fees ($2,000 to $10,000), and per-transaction fees or percentage cuts. They also require you to maintain a reserve account—usually 1 to 2 percent of your monthly transaction volume, held in an escrow account at the bank. This capital is tied up and not available for operations.
Licenses, compliance, and regulatory costs
Money transmitter licenses are required in most U.S. states if you handle merchant funds. The number of states that require a license varies depending on your business model—PayFacs typically need fewer licenses because the sponsor bank holds the accounts, but you should assume you need licenses in 10 to 20 states. Each license costs $500 to $5,000 to obtain and $500 to $2,000 per year to maintain. Some states require a surety bond, which adds another $1,000 to $10,000 per state.
PCI DSS compliance is mandatory if you touch payment card data. This means your systems must meet security standards set by the card networks. Compliance costs range from $10,000 to $100,000 per year depending on the scope of your systems and whether you use a third-party assessor. You also need cyber liability insurance, which typically costs $5,000 to $25,000 per year.
Know Your Customer (KYC) and Anti-Money Laundering (AML) rules require you to verify merchant identities and monitor for suspicious activity. You will need to build or buy a KYC platform, integrate it into your onboarding flow, and staff someone to review flagged accounts. This is not a one-time cost—it is an ongoing operational expense.
Technology, fraud prevention, and operational costs
The software itself is not the expensive part. Building a merchant dashboard, API, and settlement system is straightforward if you have experienced engineers. The expensive part is everything around the software: fraud detection, chargeback management, customer support, and reconciliation.
Fraud prevention requires real-time decision-making. You need to detect stolen cards, account takeovers, and money laundering attempts before they cost you money. Most new gateways buy fraud detection from a third party (Kount, Sift, Stripe Radar) rather than build it themselves. This costs $500 to $5,000 per month depending on volume. You also need to staff someone to investigate chargebacks and disputes—this is manual, time-consuming work that never stops.
Settlement and reconciliation are operational nightmares. You are moving money between customers, merchants, and banks, and every transaction must be accounted for. A single reconciliation error can cascade into weeks of investigation. Most gateways hire a finance operations person or outsource this to a third party. Budget $50,000 to $150,000 per year for this function.
Customer support is expensive because payment issues are urgent and merchants will call you at 2 a.m. when their transactions are failing. You need 24/7 coverage or a clear escalation path to your sponsor bank. Budget $100,000 to $300,000 per year for a small support team.
How to find your first merchants and build trust
Payment processing is a trust business. Merchants will not switch to an unknown gateway because your rates are 0.1 percent cheaper. They switch because someone they trust referred you, or because you solve a specific problem they have.
Your first customers will come from your own network—people you know, businesses you have worked with, or verticals where you have credibility. If you have experience in e-commerce, you might launch a gateway for e-commerce merchants. If you have relationships in the restaurant industry, you might build for restaurants. Vertical focus makes it easier to understand customer needs and to build trust.
Referral partnerships are your second channel. Partner with accounting software, e-commerce platforms, or POS systems that already serve your target merchants. These platforms can integrate your gateway and refer merchants to you. You will pay a commission or revenue share, but you get access to their customer base.
Direct sales is expensive and slow. Cold outreach to merchants rarely works. If you do hire a sales team, focus them on warm leads—referrals, inbound inquiries, and existing customer expansion.
Capital requirements and realistic timelines
The total cost to launch depends on your model. A PayFac typically costs $300,000 to $500,000 to launch and break even in 18 to 24 months. An ISO costs $100,000 to $250,000 and can break even faster if you have strong sales relationships. A full processor costs $1 million to $3 million and takes 24 to 36 months to profitability.
These numbers assume you are not paying yourself a salary during the launch phase. If you need to pay yourself and a small team, add $200,000 to $400,000 per year. They also assume you already have the technical informed in-house. If you need to hire engineers or buy technology, add another $100,000 to $300,000.
Timelines are measured in years, not months. From the day you start conversations with a sponsor bank to the day you process your first transaction is typically 12 to 18 months. From first transaction to profitability is another 12 to 24 months. Plan for 24 to 36 months before you see positive cash flow.
Common obstacles and why most startups fail
The sponsor bank says no. This is the most common failure point. If you cannot find a sponsor bank relationship, you cannot launch. Banks are risk-averse and will reject you if you lack payment industry experience, do not have enough capital, or cannot demonstrate merchant demand. Solution: hire someone with payment industry experience before you approach banks, or partner with someone who has existing bank relationships.
Chargebacks and fraud exceed your reserves. If your merchants are high-risk (high-ticket items, digital goods, international sales), chargebacks and fraud can wipe out your margins. You need to price for this risk and build fraud controls before you launch. Many new gateways underestimate chargeback rates and run out of money.
Merchant acquisition costs exceed lifetime value. If you spend $500 to acquire a merchant who generates $200 in lifetime revenue, you lose money. This happens when you try to compete on price alone or when you target merchants who are already well-served by larger gateways. Solution: focus on a vertical where you have an advantage, or build features that solve a specific problem.
Regulatory surprises. A state you did not expect requires a license, or a regulator interprets the rules differently than you did. Budget for legal review and assume you will need to hire a compliance consultant. This is not optional.
Frequently Asked Questions
Do I need to be a bank to start a payment gateway?
No. You need a relationship with a bank (a sponsor bank), but you do not need to be a bank yourself. The sponsor bank holds the regulatory license and the merchant accounts. You build the platform and manage the customer relationships. This is how most payment gateways operate.
How much money do I need to start?
Minimum is $250,000 to $300,000 for a PayFac model, assuming you have technical informed in-house and do not need to pay yourself a salary. This covers sponsor bank setup fees, compliance costs, basic technology, and initial operating expenses. If you need to hire a team or buy technology, add $200,000 to $500,000. Full processors need $1 million or more.
Can I start as an ISO and move to a PayFac later?
Yes. Many successful gateways started as ISOs, built merchant relationships, and then moved to a PayFac model once they had enough volume to justify the cost. This is a lower-risk path because you can test the market and build revenue before making the larger investment.
What if I want to focus on a specific industry like restaurants or e-commerce?
Vertical focus is smart. It makes it easier to understand customer needs, build features they actually want, and establish credibility. You will still need a sponsor bank and comply with all regulations, but you can differentiate on industry knowledge and customer support rather than competing on price.
How long until I process my first transaction?
Expect 12 to 18 months from the day you start conversations with a sponsor bank to the day you process your first transaction. This includes sponsor bank approval (3 to 6 months), technology build (3 to 6 months), and regulatory approval (2 to 4 months). Timelines vary based on your model and the complexity of your platform.