He is right, reading the docs you have no idea which events leads to what. Nowadays with llm's it's easy before that I still dont know which events mean what.
reply> Having done a major migration with Stripe, at a startup, I disagree
replyInitial integration is very simple and developer-friendly. The complexity comes later.
> If you just need to take dumb payments, just use Stripe Checkout.
replyCould not agree more. Offload as much complexity (receipts, invoices, tax, customer info, etc.) to Stripe as humanly possible in the beginning. Don't build for edge cases or UX polish. If people want your product, they will buy it.
and then without knowing it you are paying 1000's a month to stripe
replyThis is kind of the tradeoff you need to make when launching a product though. You cleave off some of the product's margin & send it to a third party so that you can get the thing launched. If it's unsuccessful, that's fine, you'll pay no money to the vendor. If it's successful..? Great! Now you can afford to pay someone to build a checkout that doesn't cost me thousands a month in fees.
replyStripe takes 1.5-2.5%, so if you're sending them 1,000s a month, your revenues from that checkout are approaching the $millions p/a. Certainly enough to hire an expert in the domain.
It costs much more then that, that's their feeds on top of CC, conversion etc. at 20K mrr you are easily paying 1k p/m in Stripe & Processing fees.
replyHow is that different than any other payment processor? Interchange isn't free anywhere
replybecause stripe on purpose hide fees, constantly asks you to try out new features and then secretly charges you more then market price when you say yes. See radar, managed payment, stripe billing management etc.
replyThis means you’ve done everything absolutely fucking right
replydeleted
replythats a bit my point, you get there at around 18-20K mrr already
replydeleted
replyFair point, just saw your other comment.
reply