3 ms·
This is a great improvement! Last time I did a stripe integration it was definitely kind of a painful, disjointed experience.
by chadlavi 7y ago
This is a great improvement! Last time I did a stripe integration it was definitely kind of a painful, disjointed experience.
- MuffinFlavored 7y agoReally? It's like... 3 API calls. Create a customer, store a card, create a charge.
- ceejayoz 7y agoThere's quite a bit more complexity in some use cases. Some payments are now asynchronous due to https://en.wikipedia.org/wiki/Strong_customer_authentication https://en.wikipedia.org/wiki/Strong_customer_authentication ; handling failed payments for things like subscriptions takes some effort (and managing webhooks). My experience with Stripe has been great, but payments can still get into the weeds through no fault of Stripe's.
- MuffinFlavored 7y agoI might sound a bit dumb here, but would a cron job that runs daily, finds customers who haven't been billed in 30 days, then tries to bill them and disables their account on failure easier than dealing with webhooks/etc.?
- ceejayoz 7y agoPotentially, but Stripe has a lot of features you might have to duplicate in that case. They automatically re-attempt (including machine learning that tries to do it when the card's least likely to be maxed out). They send email receipts, handle SCA notifications if additional authentication is required...
- twunde 7y agoSome other examples of complex use cases: connected accounts, reconciliation reports, dunning reports, non-traditional ecommerce workflows. From a security perspective, I'd love the ability to enforce 2FA instead of having to audit the users table every month. To be fair I think the number of clients with 50+ connected accounts is fairly low
- sbensu 7y agoHi! I'm Sebastian and I work at Stripe. We would love to understand what went wrong so that we can keep improving the integration experience. If you are interested in talking to us, please email me at sebas@stripe.com