3 ms·
> maintaining swift response times on an issue that isn't even theirs? But the problem is theirs. Their site says it all: "No setup fees, no monthly fees, no
by bittermang 15y ago
> maintaining swift response times on an issue that isn't even theirs?
But the problem is theirs. Their site says it all:
"No setup fees, no monthly fees, no card storage fees, no hidden costs: you only get charged when you earn money."
Therefore, if you're having an issue with your checkout form and their API, it very much is their problem. You're not able to process payments, so you're not able to get paid. Because you're not getting paid, they're not getting paid.
- michaelschade 15y agoThat's a huge stretch. It would be like claiming that an engineer at Google should email me whenever my website goes down and help me fix it because, if my website is down, then it's one less website in their index, and they need sites in their index in order to sell advertising. To make sure that I'm clear: the problem was entirely unrelated to Stripe; it had to do with a different component of my site.
- gtaylor 15y agoI don't even think the "Why?" of good support matters, from our (the user's) concern, as long as the support is there and fast. Technically, PayPal depends on people sending payments through them to draw profit, as well, but that didn't get us good support. The big takeaway from the top of this thread is: Stripe's support was fast, even when it wasn't necessarily their service that was causing the issue. Why they came to the rescue fast doesn't really matter.