Broad, top-of-funnel guides to Stripe products and concepts.
Both use the same PaymentSheet under the hood. The differences that matter are in setup, not in the payment flow.
The official plugin covers most stores. Here's how to tell when it doesn't, before you've built the wrong thing.
Manual tax tables work fine until they don't. Here's the point where automation pays for itself.
Refunds are the most commonly under-designed part of a marketplace payment architecture.
Proration is where most custom billing bugs live. Here's the mental model that actually holds up.
The single biggest risk in a billing migration is re-collecting cards. Here's how to avoid it.
These three products solve real problems that most teams don't know Stripe already handles: until they've half-built a worse version themselves.
Buy-now-pay-later isn't a UI toggle. It changes your refund logic, your risk exposure, and what "payment confirmed" means.
Card fees make sense for small transactions and stop making sense fast as transaction size grows: here's when to switch rails.
Wallets convert better than manual card entry, and Stripe surfaces them automatically. If the integration is set up correctly.
Both let you accept payments, but they solve different problems. Here's how to choose.
Book a free consultation and get a clear scope within 24 hours.