#kanishkaNangia-error

1 messages · Page 1 of 1 (latest)

modern mulch
#

hello! can you share the PaymentIntent id? it'd look like pi_xxx

#

hello! can you share the PaymentIntent id? it'd look like pi_xxx

high dawn
#

in_1LPVqYI5vSu94Gk8dRhfzpfq

#

seti_1LPVqSI5vSu94Gk8YNXoEbbn

#

So we did set up intent and then send Payment method ID

#

to the API

#

then we get error ininvoice pay

modern mulch
high dawn
#

ok so what all rules we should enable..

modern mulch
high dawn
#

but when we try this in test account it fail sin set up intent

#

is radar automatically enabled in the test mode. Then it should not catch wrong CVC in the set up intent..

modern mulch
#

you can toggle the test mode on that page to check if it's on in test mode

#

also which test card did you try it with in test mode?

high dawn
#

in Tets mode also RADAR is off

#

test*

modern mulch
#

did you use 4000000000000101 ?

high dawn
#

4000 0000 0000 0127

#

this one

#

So the CVC error for this 4000000000000101, I am getting error..on set up intent only

#

which I feel should not be the case if set up intent does not check the CVC

#

{
"error": {
"code": "incorrect_cvc",
"doc_url": "https://stripe.com/docs/error-codes/incorrect-cvc",
"message": "Your card's security code is incorrect.",
"param": "cvc",
"payment_method": {
"id": "pm_1LPfRAK5Jxl3vjti44Uhu8UG",
"object": "payment_method",
"billing_details": {

high dawn
#

So Although i agree may be Radar can add rule.. but then in using this card I should nto get erro in set up intent

#

rather it should go through and fail in intent..

#

So Although i agree may be Radar can add rule.. but then in using this card I should not get error in set up intent
rather it should go through and fail in intent..

modern mulch
#

If you've enabled the Radar rule to Block if CVC verification fails and you've enabled Radar for SetupIntents as well - The SetupIntent using 4000000000000101 will fail - this is expected behaviour right?

high dawn
#

we have no enabled for test mode

#

not*

#

in test mode I feel it just check ir-respective even when the radar is not set up

#

THis scenario may have to be tested once at Stripe's end.. This may cause an issue in our system for not covering that scenario

modern mulch
#

hmm, gimme a while to test this

high dawn
#

ok sure

#

just an update even after adding RADAR< although the rule kicked in but again at Payment intent level and not at setup intent level

modern mulch
#

hrm okay, i see what you mean. I don't know off the top of my head if it's expected behaviour that we reject on the client side for incorrect CVC for 4000000000000101.

What I'd recommend though is to ensure that your integration is able to handle scenarios whereby the SetupIntent passes, but the PaymentIntent subsequently fails.

The reason is that to prevent card testing, Stripe is sometimes required to not check cvc and zip checks on card validations. So it's possible that it may only fail and be blocked during payment instead. https://support.stripe.com/questions/check-if-a-card-is-valid-without-a-charge

high dawn
#

all is great

#

but these testing are all taking my commission 😦

#

wish I could get refund for the ones I am testing in live env

novel holly
#

Hi @high dawn I'm taking over this thread, give me a sec to catch up

#

Please note that Stripe’s fees on the original payment will not be returned in case of a refund. https://support.stripe.com/questions/understanding-fees-for-refunded-payments

high dawn
#

i know

#

it just we are testing this feature..

#

because in test CVC fails at the SET up intent

#

however in prod env it goes through to Payment intent..

#

How do I turn off the Radar on my account

novel holly
high dawn
#

Thanks for you time.. However one thing which is bothering me is all these checks happen at payment intent time.. which is ok..But it shoudl also do these checks for Set up intent..

novel holly