toast

[opal chasm]

Hello! I wish I could help, but this chat is focused on developers and technical questions. Our support team will be able to assist you better with fraud and pricing questions than I can: https://support.stripe.com/contact

[stable belfry]

My technical question is: How can i implement a stripe flow which prevents payments with incorrect CVC and/or zip code but does not use Radar?

per my previous message: "Is Radar required to prevent payments which have incorrect CVC and/or zip code? "

[opal chasm]

No, you would need to enable the Radar rules for that in your Dashboard here: https://dashboard.stripe.com/test/settings/radar/rules

I am not sure how those specific rules are priced though.

[idle nacelle]

How can i implement a stripe flow which prevents payments with incorrect CVC and/or zip code but does not use Radar?
Good question. Our payment intents do have a cvc_check property which talks about CVC check passes or failures but I am unsure if you can get them before fully completing a payment. Will think on this and get back to you https://stripe.com/docs/api/payment_intents/object#payment_intent_object-last_payment_error-payment_method-card-checks-cvc_check

[stable belfry]

thank you!

[stable belfry]

In my case we use capture_method: 'manual. Perhaps we can leverage the cvc_check and address_postal_code_check attributes to confirm before we capture our payments serverside.

[idle nacelle]

Yes that would be the way to do this. I was just testing with our flows and not having success but that was for automatic capture. For manual capture you will have that point when Stripe has already talked to the bank so those fields should be filled out. Would you be able to test this quickly in test mode to see if those fields are filled out after the initial capture?

[stable belfry]

i will test it asap and get back to you