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?)
-
-
Show 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.Show 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?Show this thread
End of conversation
New conversation -
-
-
I'm guessing it's a part of their fraud prevention systems.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Isn‘t modern web technology awesome..
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.