Did some more digging on this, and it looks like actually @stripe in general just doesn't work with third party cookies blocked (Firefox -> Privacy -> Cookes -> Block all third party). This _really_ needs to be fixed. Why are cookies even necessary for this process?https://twitter.com/cmuratori/status/1229187173036855296 …
-
Show this thread
-
Performing a credit card charge should not involve cookies at all. It can be done with a secure HTTPS exchange, there is no way cookies should ever be _required_. Plus, the error message should never have been "declined" (which also appears to be a Stripe failure?)
1 reply 0 retweets 6 likesShow this thread -
Because trying it with SendOwl, I get the exact same results when trying to charge through
@stripe ("card declined"), even though Stripe never actually tried to charge the card at all due to the blocked cookies.1 reply 0 retweets 3 likesShow this thread -
Finally, why am _I_ the person who had to find this? Shouldn't there be a team of people at
@stripe who try all browsers and all configurations looking for errors like this?3 replies 0 retweets 25 likesShow this thread -
This Tweet is unavailable.
-
It's insane to envision a scenario where not using cookies would be a major investment, but I guess that's the state of web programming today?
2 replies 0 retweets 6 likes -
Replying to @cmuratori @stripe
It's a lot of work (manual testing) to support 1-2% of the web?
1 reply 0 retweets 0 likes -
Replying to @FatalSweater @stripe
2% of your sales would be the entire revenue taken by Mastercard/VISA. Just as a simple example. It is not small or irrelevant, even a little bit.
1 reply 0 retweets 1 like -
Replying to @cmuratori @stripe
<2% of all web browsers on the internet, not 2% of all stripe sales.
1 reply 0 retweets 0 likes
Well it's 0% of all Stripe sales, because it doesn't support it. The point is 2% of web browsers is 2% of sales. There isn't some weird concentration of users where the 2% who have cookies turned off make drastically less internet purchases.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.