#newtreyes
bleak coyote
meager sandal
Hi @topaz pilot
meager sandal
Yes
This is the code that confirms the setup intent
This is the code that sets the simulated CC number
And I am sure that we are setting the simulated CC because I can see the following in the logs:
topaz pilot
Real quick question - are you intentionally passing in a wrong number for the simulated card? From the log you're not passing in 4242424242424242, the one you're usingn is slightly different
meager sandal
Nice catch
I wasn't
Let me try with a good one
having said that, it should complain about the wrong number, right?
topaz pilot
It depends - I'm not super familiar with what we do internally with this flow, but it's very possible we just completely strip out any card number we don't think is valid/doesn't pass the luhn check (but this is just a guess)
meager sandal
I think that is what's happening
Once I fixed the CC number, it worked as expected
Should that be reported as a "bug"? I mean, as a developer I would like that if the wrong simulated credit card number is entered, then a proper "Wrong credit card number" error to be generated. The present one looks like the credit card number was never entered which can cause confusion (I was confused and at least one other stripe engineer thought it might be a bug on the Stripe Terminal SDK but we never got to debug the issue because it manifested as part of another issue which got solved)
Or maybe a some documentation on what will happen if the wrong simulated CC number is entered?
even that should be enough to point someone in the right direction.
topaz pilot
Yeah there's definitely room for improvement here - I can flag internally to see if we can get a more helpful error message here instead
topaz pilot
👍