ACH, SEPA, and Bank Transfers: Choosing the Right Rail for High-Value Stripe Payments
Card fees make sense for small transactions and stop making sense fast as transaction size grows — here's when to switch rails.
Zeeshan
Founder · Published
Card fees make sense for small transactions and stop making sense fast as transaction size grows — here's when to switch rails.
Zeeshan
Founder · Published
A 2.9% + 30¢ card fee is negligible on a $40 SaaS subscription and genuinely expensive on a $4,000 invoice. Once transaction values climb — rent, B2B invoices, large one-time purchases — bank-based rails (ACH in the US, SEPA in the EU, generic bank transfers elsewhere) usually beat cards on cost, at the price of slower settlement and a different failure mode.
We typically recommend offering both: cards for speed and low-friction checkout below a certain transaction size, ACH/SEPA/bank transfer as the default above it — with the threshold set by your actual fee economics, not a guess. Getting the pending-vs-confirmed state handling right up front avoids the much harder problem of retrofitting it after a customer has already been told their large payment "succeeded" and then watched it bounce.
Stripe insights, monthly
One email a month, no spam, unsubscribe anytime.
No spam, unsubscribe anytime.
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.