#NewtReyes
sonic wrenBOT
fair notch
So this actually turns out to be expected and I filed feedback with the team to update the docs. The reason this is expected is that there is no actual card authorization performed on card_present SetupIntents (like there is with card_not_present). So the only decline code we would return is a generic decline for SetupIntents of setup_attempt_authentication_failed if for some reason the SetupIntent did not succeed. But it won't have the typical decline codes present from an issuer decline.
Basically we have a way to verify the card via the Terminal that does not involve talking to the issuer.
So if that check fails it would just be a generic "nope this card isn't legit"
Which is the setup_attempt_authentication_failed decline
restive ether
Mmmm... that makes sense with CCs which are stolen or expired. But what about CCs which are good but don't have enough funds? Ex.
restive ether
I was expecting to be able to attach the card and then get the error when trying to process the payment.
fair notch
Oh you want to test attaching successfully via SetupIntent but decline on PaymentIntent
For Card Present
restive ether
As it is, the present behavior limits what can be tested with the test credit cards when one uses setup intents.
Oh you want to test attaching successfully via SetupIntent but decline on PaymentIntent
Yes
Does that make sense?
fair notch
Gotcha. Yeah unfortunately there isn't a Card Present test card like the 4000000000000341 online card which declines after attachment (https://stripe.com/docs/testing#declined-payments)
I can file a feature request for a test card number like that for Card Present
But yeah not going to be possible to do that flow right now of successful card present SetupIntent --> declined PaymentIntent
You should just mock the responses for that test instead
restive ether
LOL
Anyhow
I guess requesting test CCs that can be used with SetupIntents may be a good idea since these won't really work today: https://stripe.com/docs/terminal/references/testing#test-cards-for-specific-error-cases
:/
Is that something I could look forward to?
fair notch
I mean there is only that one scenario right? Attach successfully and then decline on payment?
restive ether
charge_declined_insufficient_funds
charge_declined_processing_error
refund_fail
fair notch
Since the only decline code you would see for other declines is setup_intent_authentication_failure I can't think what other flows you would need to test?
restive ether
I think those 3 scenarios would be worth testing
fair notch
I see. Honestly since we don't provide this for Card_Not_Present (attach and then decline with specific decline codes) I doubt we would prioritize it for Terminal.
But I can still put in a feature request
I would recommend though that you just mock these responses for your testing
I would not rely on us releasing test cards of this nature soon
restive ether
I would recommend though that you just mock these responses for your testing
Yeah
I think that's what I will do
restive ether
Let me ask you something else about this:
I am testing now using this: https://stripe.com/docs/terminal/references/testing#physical-test-cards
I just processed a payment for 100.01 without a problem using a physical reader and the test credit card provided.
Shouldn't that generate a declined payment?
fair notch
Can you give me the PaymentIntent ID?
restive ether
Nevermind
seems like the cent was not sent for some reason
Checking now on my side
fair notch
👍
fair notch
👀
restive ether
Thank you
restive ether
Mmmm... yeah... again, setupintent plus capture on the server side
fair notch
Right
So it won't follow those docs, which only trigger declines when confirmation comes via the Terminal SDK
fair notch
Sure thing
restive ether
I think testing when using setup intents is fairly limited right now.
fair notch
Unfortunately so
fair notch
Agreed