#sam_api
rocky galleonBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1331672932417667165
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- sam_api, 4 days ago, 7 messages
cinder hound
Samples:
BAD CVC
- ch_3QVcvfD0zA5dJXSs03Y60Ak6
- ch_3QVGS7D0zA5dJXSs0JtCPIfv
- ch_3QaXuPD0zA5dJXSs0fDaZsSx
Trxn Not allowed
- ch_3QaXtaD0zA5dJXSs1XQ2KVDE
- ch_3QaMDxD0zA5dJXSs1c6ppetb
- ch_3QaI55D0zA5dJXSs05Fv5V04
topaz skiff
Hello! A Setup Intent performs validation of the payment info provided, but does not always verify the CVC. The behavior you're describing is normal and expected.
cinder hound
I think we want to figure out how we can
- force a preauth
1a) validate the preauth occured (shoudl this be the status of the setup intent?) - how to force a preauth if it didn't occur
- understanding why txn not allowed occur, or how CVC checks would fail
topaz skiff
There's no way to "force a preauth". The closest thing we have would be placing a hold on funds: https://docs.stripe.com/payments/place-a-hold-on-a-payment-method
cinder hound
Gotcha, is there a way to force the CVC check? Maybe using something other than a setupintent after that's been created for further validation?
Sounds like that is one issue
Separately is understanding why we would have these failed transactions
topaz skiff
For #1a, you can check the cvc_check value on the Payment Method to see the status of that: https://docs.stripe.com/api/payment_methods/object#payment_method_object-card-checks-cvc_check
The bottom line is that a Setup Intent is designed to save payment information for future use. It's not designed to tell you if the payment info can be successfully used later. Nothing can tell you that. For example, a perfectly valid card can be set up today, but might not work tomorrow (it could be reported stolen, the available balance could decrease, etc.). The only way to know for sure if a given transaction will go through or not is to attempt that transaction and see what happens.
cinder hound
So the best path towards checking the funds would be to put a hold on the payments first, like yo mentioend above?
Also what determines if the cvc_check gets run, is this Stripe, or the card network?
topaz skiff
Yes. Note that there are time limits with that approach, but if you want to guarantee the funds are present and reserve those funds that's the way to do it.
The CVC check happens or doesn't happen based on a combination of factors. There's no simple explanation.
cinder hound
One last question I had, we have additional failures for incorrect_number
The bank returned the decline code incorrect_number.
We set these up in a similar way. But what we are saying is that setup_intent won't validate the account. Is there a way to know whether a credit card provided is actually valid, in advance of charging the card?
Is there a field I can look to on the PaymentMethod to determine if the card number was validated? Similar to checking how the cvc was validated?
topaz skiff
No, there isn't.
cinder hound
Okay thanks Rubeus