#morey-bad-card
1 messages · Page 1 of 1 (latest)
I have a live card that I used for testing
the billing details are all wrong, exp_ dates all wrong
but I was able to successfully confirm and attach that card
confirm - req_Ow007Kn3mBpYSQ
attach - reqcIGTZ89rAH1whg
Okay so first: you should never be using real card in Live mode to test. You do you, but it's important that I say this, card networks do not like this
¯_(ツ)_/¯ sadly. You mostly test in Test mode which behaves like Live mode, you shou;dn't test with a real card, best way to get flagged
And the SetupIntent API will not always talk to the bank so here we didn't talk to them so there's no way to verify the expiration date until you charge
I see
So as long as my code works in development
I can assume the same for production?
the stripe portion anyways
in theory yes, though I know it's not easy to feel re-assured about that 😦
hahaha I guess ya I don't feel great
but I guess if that's the right way to do it
On adding a payment method without charging, I guess stripe only checks the card number
corect
we can talk to the bank too at the SetupIntent confirmation step
but it's not guaranteed
Is it possible for a card to succeed if some of the info is wrong?
say the billing details are off by abit
but the CVV/Postal/Exp are good
yes
most banks never check billing details beyond postal code (and many banks don't even check postal codes)
Gotcha. Thanks for this. learning alot about payment stuff last 7 days 😄
Then is it nessicary to collect that information you think?
if the target customer base is in USA
if not needed, just stick to the CC number/exp/cvv/postal is good enough?