I can envision a scenario for telling one abusive customer asking for a refund “Look, we’re done here; take it up with your bank.” but if you’ve got it in your core payment flow that is a catastrophically bad decision.
-
-
Show this thread
-
I am not kidding, Internets. Do not do this. Do not do this. You will get fired as a customer by your payments processor. That is *not* the worst thing that can happen. Do not do this.
Show this thread
End of conversation
New conversation -
-
-
Screw idempotence keys, amirite?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The ALL RED. EVERYTHING IS MOST IMPORTANT was the biggest red flag (no pun intended). I knew a guy like that in Naval Crypto school: he highlighted the entire book.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Sagepay gateway has a delightful failure mode if they can't POST the auth confirmation back to your server, where they will leave an auth shadow on the card and nothing can clear it but for the passage of time (5 days)
-
but IIRC it gets worse if the card was a debit card not a credit card: debit cards don't do shadows, so instead the system performs an actual withdrawal
- 1 more reply
New conversation -
-
-
This is why I love Amex - 4 clicks and I get my money back from any bad merchant like that. And that bad merchant gets to pay a nice fat chargeback fee for being incompetent/awful.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Reminds me of the time Amazon customer support told me their system wouldn't let them cancel a charge, but to please dispute it with my bank because then it gets escalated to the fraud team and their system can cancel it.
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.