#torossian

1 messages · Page 1 of 1 (latest)

slow houndBOT
crystal cradle
#

Hi there! do you have a PaymentIntent ID that failed with a verification error?

sharp snow
#

Yes I do! Should I dm it to you or is here fine?

#

Not sure how sensitive those IDs are

crystal cradle
#

You can share the ID here

sharp snow
#

"pi_3MtIj7GL9lTS5Gb80Vr714Wl"

slow houndBOT
crystal cradle
#

Thanks! Looks like in this case, we sent the postal code to the networks but the postal code did not match the one they had on file

sharp snow
#

Ok, is there a reason why the setup intent isn't erroring as well? Verification should be the same when confirming a setup, or am i incorrect? I've tested the setup intent and it fails with another postal code, but passes with this one.

viscid wolf
#

Hi @sharp snow I'm taking over

#

Please note that this is the error code that the card issuer decides to return to us, if your customer is certain that the zip code is correct, I'd suggest you to ask your customer to reach out to the issuer bank.

sharp snow
#

Thanks, is verification different between confirmSetup and confirmPayment? Just confused why the two are behaving differently

#

Do I need to explicitly add billing address to paymentIntent, or is the PM (which holds the postal code) enough?

viscid wolf
#

The payment info is processed in the issuer and we don't know how the bank verifies it.

sharp snow
#

Ok, but the expected behaviour of both paymentIntents and SetupIntents are the same right? Like they should both go through the verification rules defined?