Stripe

What it is

Stripe is payment infrastructure. Not just a payment form. Stripe handles one-time charges, subscriptions, invoicing, refunds, disputes, tax calculation, revenue recognition, fraud detection, and financial reporting. It is the standard for internet payments, and it earned that position.

Who it's for

• Any app that takes money: SaaS subscriptions, one-time purchases, marketplaces
• Developers who want to implement payments correctly the first time
• Businesses that need billing, invoicing, and tax compliance without building it
• Anyone building in any country Stripe supports (46+ countries)
• NOT for: high-volume, low-ticket apps where the 30¢ fixed fee destroys margin on transactions under $5
• NOT for: businesses in countries Stripe doesn't support. Check the list before building

The good

The API is the reference implementation in payments. Stripe's API design is so good it's used as an example in API design courses. Idempotency keys, webhook events, versioning, error codes: all exactly right. You'll enjoy implementing this.

Docs are the best in fintech, maybe anywhere. Every endpoint is documented with curl, Python, Ruby, Node, and PHP examples. Interactive testing built in. Guides for every use case. The documentation alone is worth the transaction fee.

Stripe Checkout handles the hard stuff. PCI compliance, 3D Secure, GDPR, Apple Pay, Google Pay: drop in Checkout or Elements and these are solved. Building equivalent from scratch would take months and a lawyer.

Billing and subscriptions handle edge cases you haven't thought of. Trial periods, usage-based billing, seat pricing, annual discounts, proration: the subscription model covers edge cases you won't think of until you need them.

Stripe Radar catches real fraud. ML-based fraud detection included. You can write your own rules. For most apps it runs silently and catches fraud you'd have never seen coming.

The bad

2.9% + 30¢ is not cheap for low-ticket transactions. For high-ticket B2B SaaS ($500+/mo), this is fine. For high-volume low-ticket transactions (under $10), the fixed 30¢ eats margin fast. Braintree and Adyen negotiate lower rates at volume; Stripe does too, but you need $1M+ in annual volume to get there.

International support is uneven. Stripe supports 46+ countries but payout timing and feature availability vary by country. If your users are primarily outside the US, EU, or UK, check Stripe Atlas support for your region before committing.

Support is email-only for most tiers. Getting a human on the phone requires a paid plan. For most integrations you'll never need it (the docs are that good), but when something goes wrong with a live payment, waiting for email response is stressful.

Vendor lock-in is the hardest migration in payments. Migrating away from Stripe means migrating all your customer payment methods, subscriptions, and billing history. Nobody does this casually.

Onboarding experience

Test mode is available immediately, no approval, no KYC, no sales call. The sandbox is fully functional: you can make real test charges within 30 minutes of signing up. Getting-started guides are code-first with working examples in every major language. Going live requires identity verification and business details (1 to 3 business days for review). Stripe never gates evaluation behind a sales conversation.

Support reality

The documentation is so thorough that most developers never need to contact support. Email support is available on all plans; phone support requires a paid plan. Response on technical issues is typically 24 to 48 hours by email. The Stripe Discord and Stack Overflow communities are high-quality. Specific error codes and webhook edge cases have been answered hundreds of times. For a live payment emergency, the community is usually faster than official channels.

Migration and lock-in

The hardest migration in payments. Customer payment methods are tokenized in Stripe's vault, exportable, but most processors don't accept Stripe token imports, requiring customers to re-enter card details. Subscriptions, invoices, and billing history have no standard portable format. Realistically: new customers can move to a new processor cleanly, but migrating existing subscribers is a 3 to 6 month engineering project minimum. Nobody does this casually.

Pricing reality

2.9% + 30¢ per transaction is the standard rate. No monthly fees, no setup fees. At $1M ARR, you're paying roughly $29,000/year to Stripe, which is expensive but cheaper than building and maintaining payment infrastructure. Enterprise pricing kicks in around $1M+/year in volume and can drop to 2.2% + 25¢.

Vendor signals

• API versioning is the industry benchmark: deprecated versions get years of support with advance notice
• Changelog is detailed, date-stamped, and calls out breaking changes clearly
• Status page has years of real incident history, not sanitized
• Pricing has been stable for years; no surprise fee changes
• Well-capitalized, not acquisition-likely in a way that would change terms overnight

Verdict

Stripe is the correct default for payments. It's not the cheapest option at scale, but it's the best product, and payments is not the place to save money by using a worse tool.

Use Stripe until you have a specific reason not to. That reason usually only appears at significant transaction volume ($5M+/year) when the percentage fee becomes material enough to justify negotiating with Braintree or Adyen. For high-volume, low-ticket apps (under $10/transaction), model the 30¢ fee against your margin before committing.

Would I recommend a colleague start here? Without hesitation. Stripe is the answer to payments.