How much does it cost to build an app like PayPal?

There is no one figure, because "an app like PayPal" covers three very different builds: a first version with only the essential features, a complete and credible competitor, and a rebuild of everything the mature product does at the traffic it carries. Those are several-fold apart. What this page gives you is the shape of each — the sides, the feature tiers, the stack and the compliance — and the calculator turns whichever one you actually mean into a cost range, hours and a timeline.

Because it is not one app. It is 4 separate applications — consumer wallet, merchant dashboard, developer platform, risk & compliance console — sharing one backend, each with its own design, release cycle and test matrix. Most quotes that come in low have counted one of them. The ledger is not a database table: Holding customer balances means double-entry accounting that reconciles to the cent against external settlement, survives partial failures, and can be audited years later. Teams that treat balances as a mutable integer discover the problem during their first reconciliation break.

Yes, and you should. A first version ships the essential feature tier rather than all three, on fewer surfaces, at a launch-sized audience — materially less than the full product, and the calculator will show you by how much. What it does not cut is compliance: finance & fintech obligations apply from the first user, so those stay in whatever else is deferred.

It depends on the same three things the cost does — which tier of the product you mean, how many surfaces you ship, and how settled the scope is. The calculator returns a timeline alongside the cost, derived the same way: hours divided across a realistic team shape, never a target date worked backwards from.

Cloud infrastructure, third-party services and annual maintenance, and the calculator reports all three separately from the build. They are kept out of the build figure deliberately: they are operating expenditure rather than capital, and adding the two together produces a number that means nothing. Maintenance in particular is not optional — an app that receives none stops working within about a year as OS releases and SDK deprecations accumulate.

This page carries no figures at all, and nobody outside the company has real ones. What it describes is the product SHAPE, observed from what any user can see — the sides, the feature tiers, the stack, the compliance. Nothing here describes what PayPal actually spent, earns, employs or runs on. The calculator prices building something of that shape today, for the United States market, at our own blended delivery rate.

Three reasons, in order of cost. First, correctness: a ledger that must reconcile to the cent needs idempotency, settlement handling and daily reconciliation that a normal CRUD app does not. Second, identity: KYC, sanctions screening and fraud scoring are a subsystem, not a feature. Third, evidence: audit logging, access reviews, retention control and SOC 2 artefacts are continuous engineering. None of it is user-visible, and all of it is mandatory.

Usually, and it will save more than any engineering decision you could make. Using a sponsor bank, a licensed banking-as-a-service provider or Stripe Treasury keeps the regulated activity on their licence rather than yours. This changes your product architecture substantially, so decide it before you build. Talk to fintech counsel early — it is the cheapest hour on the project.