←back to thread

693 points hienyimba | 1 comments | | HN request time: 0.442s | source
Show context
0des ◴[] No.28523494[source]
As someone with a pre-launch SaaS who just signed up for Stripe, reading this has me shook up a little bit. I'm Stripe-integrated for payments, and poised to go through Stripe Atlas soon, or at least I was.. Now I have no idea what to do. I know that OP's story isn't spotless, but what if it's my thing that gets in this situation too?

I wish I could say I'm joking but I don't need this right now, I'm ~90 days out from launch, I should be tweaking final touches, not building just-in-case backup integrations with other processors.

replies(6): >>28523538 #>>28523607 #>>28523809 #>>28524057 #>>28524718 #>>28527471 #
soco ◴[] No.28523607[source]
Like another commenter said, think about your payment processor like another thing which needs redundancy. Have another one prepared - braintree or whatever.
replies(1): >>28523656 #
0des ◴[] No.28523656[source]
That's my initial assumption. I'm curious if this is common behavior to have two integrations, or if it is prohibited by the TOS.
replies(4): >>28523779 #>>28523859 #>>28529295 #>>28529586 #
1. ◴[] No.28529295[source]