#dan-classfit_error

1 messages · Page 1 of 1 (latest)

ripe jewelBOT
#

đź‘‹ 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/1306262631270580325

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

wintry crater
#

hi! do you have an example of a 'rejected' payment on this account?

whole kayak
#

They're not showing up on our dashboard

#

It seems like the bank approves it - then the process is aborted/abandoned before completion

wintry crater
#

sounds like just a problem between the customer and their bank and how 3D Secure is implemented and confusion/issues on their phone, which can happen(this is why conversion is impacted by 3DS unfortunately) .
it's hard to say more without a specific example to look at logs for

whole kayak
#

I have setup intents if helpful?

#

seti_1QErvrAsUHpP4ZnklzeB6lC4

#

In example above they tried phone and laptop and another card. Seems to be multiple issues with one express account and multiple of their customers. All as of this week when fine before. Not sure this can be one specific bank issue?

wintry crater
#

well in this example the validation charge we run on the card is blocked because the AVS (postal code) check is failing.
We have been monitoring an uptick in that for Irish issuers, there's some ongoing investigation into it. I suggest reaching out to your Stripe contacts/support so they can help you with this.

whole kayak
#

We did. They helpfully passed the buck back to us with the client.

#

Is there anything specific about this I can use in my response to Stripe other than what you've just said above?

wintry crater
#

I mean kind of but I can't talk about this in public channels. Make sure you get escalated to T2-level support and tell them I told you it's related to an ongoing incident

whole kayak
#

OK perfect will do thanks

wintry crater
#

sorry for the complexity

ripe jewelBOT
wintry crater
#

I connected with the team involved with this so we publish this better internally. In any case I can share the workaround they have with you, which is basically around disabling the default Radar rules for blocking by ZIP

Radar standard users: you could disable the “Block if postal code verification fails” rule in the Stripe dashboard [0].

Radar for Fraud Teams users: you may consider disabling the “Block if postal code verification fails” rule and instead using a custom Radar rule which also considers the transaction’s risk level. Example of a custom rule:

Block if :address_zip_check: = 'fail' AND :risk_level: in ('elevated', 'highest')

whole kayak
#

That would increase the risk our side too though right?

north harness
#

Hi there đź‘‹ I'm taking over as my teammate needed to step away.

We aren't too familiar with assessing risk in this forum, but that rule would allow payments, where the postal code provided doesn't match what the issuer has on record, to succeed if Stripe doesn't assess a high risk level on the transaction.

whole kayak
#

Hey, thanks for this - much appreciated.