How to Build an App Like PayPal: What fintech founders need to know before writing a line of code

Most founders building a "PayPal-like" product are not trying to compete with PayPal. They are building embedded finance for a specific market — a marketplace needing custom split payouts, a gig platform needing instant worker wallets, or a vertical SaaS product that wants payments baked in. The engineering question is almost secondary. The first question is: are you building ON payment infrastructure, or are you building payment infrastructure?

That distinction sets your entire cost structure.

What does it cost to build a PayPal-like payment app?

A BaaS-based MVP — wallet accounts, P2P transfers, linked bank accounts, and basic KYC — costs $120K–$200K and takes 20–28 weeks. A full product with merchant tools, invoicing, and international transfers runs $350K–$600K over 36–52 weeks. Building your own regulated infrastructure with a money transmitter license costs $1M+ and takes 18–24 months before a single transaction clears.

The MVP range assumes you are layering your product on a Banking-as-a-Service (BaaS) provider — Unit, Treasury Prime, or Stripe — rather than obtaining your own money transmitter license. That single architectural decision is what makes a $150K build possible instead of a $1M+ regulated infrastructure project.

How does PayPal actually make money?

PayPal's net take rate across its full payment volume sits at roughly 1.9%. According to PayPal's 2023 Annual Report, the company processed $1.53 trillion in total payment volume against net revenue of $29.8 billion. The standard card rate is 2.9% + $0.30. ACH transfers earn 1.5–3%. International transfers generate additional margin through foreign exchange spreads.

That take rate tells you what the ceiling looks like in a commoditized payments market. When you are building a niche product — a vertical wallet, a corridor remittance product — your take rate can be higher because you are solving a specific problem, not competing on brand recognition.

Your revenue options, assuming a BaaS-based build:

• Transaction fee — 2–3% is the industry standard. Stripe's 2.9% + $0.30 sets the reference point in buyers' minds.

• Subscription for business accounts — monthly fee for invoicing, payout dashboards, and reporting tools.

• FX margin on international transfers — if you are targeting a specific remittance corridor, the spread between your BaaS provider's FX rate and your user-facing rate is real revenue.

• Float income on wallet balances is only available when you hold a money transmitter license and can legally earn interest on customer deposits.

Who actually builds a PayPal alternative?

Two-sided marketplaces with complex payout logic

Stripe Connect handles standard marketplace splits. It breaks when you need sub-merchant wallets, multi-stage escrow holds, tiered payout schedules based on seller performance, or payouts in multiple currencies with different settlement windows. A home services marketplace paying contractors differently than vendors, holding escrow until job completion, and managing disputed transactions requires custom payout orchestration above the BaaS layer. That is the gap.

Gig economy platforms that need instant worker payouts

ACH transfers take 3–5 business days. That is too long for a delivery driver who finishes a shift at 11 PM. According to Aite-Novarica Group's 2022 Earned Wage Access report, payout speed ranks as a top-three factor in contractor platform selection. Platforms that offer instant payout via debit card or real-time payment rails retain workers at meaningfully higher rates. The engineering work is a dedicated wallet per contractor, connected to a real-time payment rail (RTP or push-to-debit), funded by the platform's own BaaS account.

International remittance startups targeting specific corridors

PayPal's FX rates run 3–5% above mid-market on many corridors. Wise's 2023 Transparency Report shows legacy providers charging 4–8x more than mid-market on popular remittance routes. A startup targeting the US-to-Philippines or UK-to-India corridor — built on modern FX APIs — can offer materially better rates and still earn meaningful margin. The addressable volume on a single well-chosen corridor can reach hundreds of millions per year within three to five years.

Vertical SaaS platforms adding embedded payments

A property management platform whose users leave the app to send rent or pay contractors loses engagement at every handoff. A legal practice management platform that processes client retainers through a separate payment processor creates reconciliation work for every user. Embedding payments — wallet, invoicing, payout — keeps users inside the product and generates revenue the platform did not have before. This is the fastest-growing category of payment builds we see.

Build vs. PayPal: when does custom actually win?

Keep using PayPal (or Stripe) when:

Payments are a checkout button, not a product feature. You need users to pay for something — that is all. At monthly transaction volume under $500K, the transaction fee economics do not justify custom engineering. You do not need custom wallet functionality, split payouts, or per-user wallet accounts. You are pre-product-market fit and speed matters more than differentiation.

Build your own when:

Embedded finance is your core product differentiation — the reason users choose you over a generic alternative. Your use case requires multi-party payout logic that Stripe Connect cannot configure without significant workarounds. Your target market is underserved by existing rails: a specific international corridor, a regulated industry with unusual KYC requirements, or a vertical where existing processors have excluded-category rules. At $5M per month in volume, a 0.5% cost reduction on transaction fees is $25K per month — the unit economics start justifying a custom build.

Feature phasing: V1, V2, V3

V1 — Launch (20–28 weeks, $120K–$200K)

This scope assumes you are NOT attempting to hold a money transmitter license. The BaaS provider handles regulatory compliance for core money movement.

V2 — Growth (36–52 weeks total, $350K–$600K cumulative)

V3 — Scale ($1M+, 18–24 months if pursuing own MTL)

V3 is not a product decision. It is a company strategy decision. Most venture-backed fintech companies at Series B or later consider this path. At seed or Series A, it is usually the wrong use of capital.

What engineering problems eat your budget?

Licensing: the decision you must make on day one

Teams that discover money transmitter licensing requirements after spending $200K building the product face a hard stop — pause 18 months or rewrite the architecture. Money transmitter licensing in the United States requires separate applications in most states. The process takes 12–18 months. Legal fees and capital reserve requirements run $150K–$400K.

"The most expensive mistake in fintech is treating licensing as an afterthought," says Ashit Vora, co-founder of RaftLabs. "In every payment infrastructure project we scope, the first question is: are you building on payments or building payments? At seed stage, founders who try to own the license add 18 months and $500K to a build that could have shipped in 24 weeks on a BaaS layer."

The fix is structural, not technical. Before any engineering begins, define your licensing strategy. If you need to move money in your own name at scale, budget for the MTL from day one and build your product layer to eventually migrate off BaaS dependency. If you are building a product experience on top of licensed infrastructure, choose your BaaS provider and design against their API constraints from the start.

KYC edge cases: the compliance iceberg under your MVP

Basic KYC — government ID verification plus a selfie liveness check — is well-solved. Services like Persona, Onfido, and Jumio integrate in days. The iceberg is everything else.

KYC for business accounts requires collecting and verifying beneficial ownership information for every owner above a 25% threshold. High-risk payment categories (adult content, firearms, cannabis, lending) require additional legal analysis before a BaaS provider will approve you. Joint accounts, custodial accounts, and non-US users each carry their own compliance requirements.

Teams that start coding before defining their full KYC scope consistently spend 40–60% more on compliance engineering. The pattern is always the same: the basic flow ships, edge cases arrive from legal review, and engineering retrofits checks that should have been in the data model from the start. A single week of legal scoping at the start eliminates six weeks of rework at the end. That delta — roughly $30K–$50K in engineering time — is the most predictable cost overrun in fintech MVP builds.

What does a real build look like?

One of the clearest patterns we see is in home services and property management platforms. These are two-sided markets with contractors on one side and property managers on the other. Stripe Connect technically handles split payments. When the payout rules include: hold 10% of payment in escrow until 72 hours after job completion, pay out the contractor minus a platform fee on a weekly cadence, and apply a different fee tier for contractors who have completed over 50 jobs — that logic cannot be configured in Stripe Connect's standard rules engine. It requires a custom payout orchestration layer above the BaaS provider.

The international remittance pattern is different in structure but similar in logic. A startup serving Filipino nurses in the US wants to let them send money home with rates that beat Western Union and PayPal. The product is simple: a wallet, a corridor, and a competitive rate. The engineering is a wrapper around a wholesale FX provider (Currencycloud, Wise Platform, or a direct banking relationship). The compliance work — US MSB registration, FinCEN reporting, OFAC screening — is what takes time. The product can be live in 24 weeks. The compliance infrastructure to support real volume takes another 6–12 months to mature.

How RaftLabs approaches this

We start every payment infrastructure project by establishing the legal architecture before the technical one. Which BaaS provider fits the use case (Unit for neobanks, Treasury Prime for community bank partnerships, Stripe for product-first builds)? What KYC categories will your users fall into, and which require legal pre-clearance? What is the payout logic, written out as a decision tree, before anyone writes an API call?

Once the legal and product architecture is settled, the engineering scope becomes predictable. We have built payout orchestration layers for marketplace platforms, wallet products for gig economy operators, and international transfer flows for corridor remittance startups. The builds that go cleanly are the ones where the compliance team and the product team have finished their work before the engineering team starts.

The first conversation should take 30 minutes, not 3 months. We can tell you within that call whether your use case requires BaaS or a licensed infrastructure, what the realistic budget range is, and where the compliance landmines sit. Book a 30-minute scoping call and we will give you a straight answer.