Payments for Django: what 13 makers' products chose
Among 13 makers' products built with Django that we know the payments of, Stripe leads: 12 of them (92%). Next come PayPal (6) and Paddle (1).
Payment processor or merchant of record (MoR). With a processor you are the seller and must register for and remit sales tax/VAT yourself. An MoR resells your product, so tax and compliance are theirs, for a higher fee.
What makers on Django chose
| Option | Django products | All makers | Free for | At 10,000 users |
|---|---|---|---|---|
| 12 (92%) | 77% | ~23 users | $410/moStandard | |
| 6 (46%) | 8% | ~18 users | $495/moStandard card payments | |
| 1 (8%) | 7% | ~13 users | $700/moPay-as-you-go |
Live makers' products with a source for both: that they're built with Django, and what they use for payments. A product using two options counts in both; not market share. "All makers" is the option's share among every maker's product that made this decision.
Costs are the cheapest plan that fits, from each vendor's pricing page, at the usage our stack planner assumes for a product with that many users. Free for: the users its cheapest plan a business can use stays free for; plans for personal use only, like a non-commercial hobby tier, don't count.
Which to pick, by situation
- You sell mainly in one country or can handle sales tax yourself, and want the lowest fees
Stripe 12 here - Your SaaS already has steady revenue and you want to hand off global tax to a long-established MoR
Paddle 1 here - Many of your buyers are consumers who expect a PayPal button at checkout
PayPal 6 here
Stripe
Payment processor12 Django products here (92%). Free up to about 23 users. About $410 a month at 10,000 users (Standard).
llms.txtMCPCLIIn Bolt, Lovable, Replit, v0Best forFull control over checkout and billing, lower fees than a merchant of record, and the widest integration ecosystem.
Trade-offYou are the merchant of record — tax registration and filings are on you.
“Listed in their tool stack on Starter Story (payments)”
- Subscriptions, trials, invoices, refunds and taxes are handled in one place, so founders skip building billing. 4 sources
- The APIs, webhooks and documentation are reliable and accurate enough to feel like a product themselves. 4 sources
- Sudden revenue jumps can trigger balance freezes with slow reviews and no stated reason. 4 sources
- Merchant fees become painful at scale, and merchant-of-record style services cost much more than plain processing. 3 sources
“Listed in their tool stack on Starter Story (payments)”
PaymentsMaker says so +1 · source ↗“Listed in their tool stack on Starter Story (payments)”
PaymentsMaker says so +1 · source ↗“Listed in their tool stack on Starter Story (payments)”
PaymentsMaker says so · source ↗“Listed in their tool stack on Starter Story (payments)”
PaymentsMaker says so +1 · source ↗“Listed in their tool stack on Starter Story (payments)”
PaymentsMaker says so · source ↗“Listed in their tool stack on Starter Story (payments)”
PaymentsMaker says so · source ↗“Listed in their tool stack on Starter Story (payments)”
PaymentsMaker says so · source ↗“Listed in their tool stack on Starter Story (payments)”
PaymentsMaker says so · source ↗“Listed in their tool stack on Starter Story (payments)”
PaymentsMaker says so · source ↗“Listed in their tool stack on Starter Story (payments)”
PaymentsMaker says so +1 · source ↗
PayPal
Payment processor6 Django products here (46%). Free up to about 18 users. About $495 a month at 10,000 users (Standard card payments).
llms.txtMCPBest forAdding PayPal and Venmo as a checkout option for buyers who won't type in a card.
Trade-offYou are still the merchant of record for tax; disputes and account holds are a common complaint, and its developer tools are clunkier than Stripe's.
“Listed in their tool stack on Starter Story (payments)”
- Simple to add as a payment option on a basic website, and a common backup checkout next to a card processor. 3 sources
- Accounts and funds get frozen or permanently locked with vague or no explanation. 4 sources
- Buyers are pushed to have a PayPal account, which adds checkout friction and raises cart abandonment. 1 source
“Listed in their tool stack on Starter Story (payments)”
PaymentsMaker says so · source ↗“Listed in their tool stack on Starter Story (payments)”
PaymentsMaker says so · source ↗“Listed in their tool stack on Starter Story (payments)”
PaymentsMaker says so · source ↗“Listed in their tool stack on Starter Story (payments)”
PaymentsMaker says so · source ↗“Listed in their tool stack on Starter Story (payments)”
PaymentsMaker says so · source ↗Also chosen, and not seen yet
Fewer Django products here: Paddle (1).
Real options for payments not seen among these Django products yet: Polar, Lemon Squeezy, Dodo Payments.
Who switches, and to what
Public GitHub pull requests whose title says "X to Y", by developers in general, not only on Django.
- Stripe → Paddle 18 pull requests
- Stripe → PayPal 9 pull requests
- PayPal → Stripe 6 pull requests
Getting payments right
Solo makers selling globally usually start with a merchant of record to avoid tax registration. Move to a processor when volume makes the fee difference matter and you can handle tax (e.g. with Stripe Tax).
- Choosing a processor to save a few percent, then finding out you crossed sales tax or VAT thresholds in places you never registered.
- Granting access from the checkout success redirect instead of the webhook, so a closed tab leaves a paying customer locked out.
- Handling only the first payment and ignoring failed renewals and cancellations, so users keep access after they stop paying.
The rest of the Django stack
What makers' Django products chose for their other decisions, the most common pick for each:
- Hosting: DigitalOcean 8 of 17
- Transactional Email: SendGrid 7 of 14
- Web Analytics: Google Analytics 10 of 12
Questions
What do most Django apps use for payments?
Among 13 makers' products built with Django that we know the payments of, Stripe leads: 12 of them (92%). Next come PayPal (6) and Paddle (1).
What does payments cost for a Django app with 10,000 users?
On our usage model at 10,000 users, Stripe comes to about $410 a month (Standard); PayPal comes to about $495 a month (Standard card payments); Paddle comes to about $700 a month (Pay-as-you-go). Prices are from each vendor's pricing page.
Which payments option stays free longest for a Django app?
Stripe: on our usage model its cheapest plan stays free up to about 23 users.
How this is counted: a product is on Django when a live-product source says so (the maker, its website, a customer story or a subprocessor list), and the same for its payments. How evidence is collected.