#dan-classfit_cards-auth-errors

1 messages ยท Page 1 of 1 (latest)

fathom tartanBOT
#

๐Ÿ‘‹ 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/1308085247228907551

๐Ÿ“ 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.

thorny geyser
#

Hi. I've had a couple of threads around this. Last one finished saying we could disable zipcode match at a country level. When we've tried we've been told we can't do this without upgrading to the paid radar plan. Can you support please.

#

We only need this to overcome a known Stripe bug while our customers in Ireland can't take payments. Seems silly that we would either have to upgrade and pay to overcome a stripe bug, or disable zipcode match globally and increase risk substantially.

white brookBOT
rapid skiff
#

Hi there ๐Ÿ‘‹ I recall discussing this with you previously. You do need to be a Radar for Fraud Teams subscriber in order to write your own custom Radar rules.

Can you elaborate on what the known bug is here?

thorny geyser
#

customers in ireland aren't able to take payment

#

estimates of 50%+ payment attempts failing, with an Eircode not matching error

#

It's been over a week now.

rapid skiff
#

What is an Eircode?

thorny geyser
#

What they call zip code in Ireland

rapid skiff
#

Do you have an example payment that failed, the ID of the Payment Intent?

thorny geyser
#

They don't register as far as we can see - part of the bug

#

I can give you express account IDs for the two customers who have raised this

rapid skiff
#

A Payment Intent must exist if an AVS check is failing.

#

Otherwise what is doing the check?

thorny geyser
#

If they exist, I've not been able to locate them

#

acct_1PyERWPMrjVzxHLp
acct_1PuGsFPL8kfqWlLt

#

These are the 2 Express accounts

#

And don't have the end user details to search otherwise

rapid skiff
#

Removing that sceenshot as it appeared to have real customer data and was posted in this public server.

thorny geyser
#

but both businesses are effectively offline until either Stripe fix the bug, or we figure out a workaround. I was happy to disable zipcode match requirement if I could do it via country, but we can't be expected to upgrade to radar for teams and considerable expense just to work around a Stripe bug. Any other options?

rapid skiff
#

Is this a Separate Charges and Transfers flow that you're using for your Connect integration?

thorny geyser
#

I don't know what that means...

rapid skiff
#

The Stripe Connect integration that you built and maintain, did you build it using the Separate Charges and Transfers charge type that we discuss here?
https://docs.stripe.com/connect/charges

I'm asking because if so, the failed payments are expected to be on the Connected Accounts, they'll be on your Platform account.

Create a charge and split payments between your platform and your sellers or service providers.

#

I suspect this because I didn't see any logs on the first Connected Account that you shared that give me the impresison you're using Direct or Destionation Charge flows.

#

I see we sent the same postal code value to the issuer as we were provided, and that the issuer told us that value was incorrect.

If the value is correct, then the bug seems to be on the issuer's side when they verify that value rather than on Stripe's.

My understanding is these concerns typically get fixed fastest when your customers reach out to their bank to make sure the bank (issuer) is aware of the problem, as Stripe has little influence on the customer's banks.

thorny geyser
#

Sorry for the delay

#

it could be an example

#

But with this being a known Stripe error, and us having confirmed that to our clients - I'm not sure how feasible it is for me to ask our clients to ask all of their clients to contact their banks

rapid skiff
#

Not a Stripe error.

thorny geyser
#

And, you know how it is - they'll speak to some noddy person on customer support who won't raise the issue from a technical side either

thorny geyser
rapid skiff
#

We don't do the postal code checks, we use the outcome values that the issuing banks provide us.

thorny geyser
#

So as of last week, all Irish banks at the same time developed the same issue?

rapid skiff
#

I don't know, it's really hard to say since you haven't been able to share any examples with me. Did you look into the failed payments to see if they were scattered across banks, or if they're all concentrated at one bank?

thorny geyser
#

Are you able to guide me on how I can find these - I'm happy to do the work

#

Initial thought is 2 clients, both saying that 50% of customers' payments failing is unlikely to result in it being just the one bank, unless there is a monopoly on banks in Ireland

rapid skiff
#

I'm not exactly sure a good way to filter these from a dashboard view, that isn't something we are too familiar with in this forum. I'll poke around between threads and see if I can spot a good path for that.

thorny geyser
#

In the meantime - any clever workaround you can think of without needing to pay for radar for teams?

#

Seems chaotic that businesses are just meant to wait indefinitely for a fix here....?

rapid skiff
#

No, not without somewhat significant changes to your integration.

thorny geyser
#

I've got 2

#

pi_3QKKFeAsUHpP4Znk192KDace

#

pi_3QKK9VAsUHpP4Znk0nrxfVFq

#

Same customer

#

Another customer screenshot

#

When I check her account on Stripe I can't see any payment intents that failed despite having this screenshot as proof

#

Setup intent is the closest I can get seti_1QErvrAsUHpP4ZnklzeB6lC4

rapid skiff
#

The two payment intents you shared are for the same issuer as the one I shared.

#

Please stop posting screenshots with customer details. This is a public forum.

thorny geyser
#

Sorry

rapid skiff
#

Stick with object IDs

fathom tartanBOT
thorny geyser
#

OK here are some more

#

pi_3QMUvRAsUHpP4Znk0frbmH5y

#

pi_3QMUAhAsUHpP4Znk0p8W7f3x

rapid skiff
#

You can see that in your Stripe dashboard

#

In the Payment Method section, in the Issuer field

rapid skiff
thorny geyser
#

So is that confirmation this isn't an issue specific to bank of ireland?

rapid skiff
#

I never mentioned a specific bank, there are two distinct banks in the examples you shared, but it's very possible for two banks to be handling postal code checks incorrectly simultaneously.

#

(I won't mention bank names, as these are real payments and I'm not willing to disclose information about them in a public forum)

thorny geyser
#

I've found an export of all zipcode errors. Filtered to just these 2 businesses in Ireland.

#

I can provide if you're happy for me to - but I assume there is some personal data in there

#

otherwise here is a list of all payment intent IDs

#

pi_3QMUGuAsUHpP4Znk0zO49zke
pi_3QMUH8AsUHpP4Znk0Yp7dPZq
pi_3QMUCMAsUHpP4Znk0c82aBMH
pi_3QMUAhAsUHpP4Znk0p8W7f3x
pi_3QMRV8AsUHpP4Znk1a7y3oNR
pi_3QMRTeAsUHpP4Znk0bkN8bYI
pi_3QMRRXAsUHpP4Znk0AjKYKnE
pi_3QMRQiAsUHpP4Znk1XP1WUdp
pi_3QMRNeAsUHpP4Znk0wRKf43y
pi_3QMGAxAsUHpP4Znk1U0jNo0w
pi_3QMG5AAsUHpP4Znk1hloh1Ci
pi_3QMF76AsUHpP4Znk0NtP7L29
pi_3QMF46AsUHpP4Znk0UI5UkF2
pi_3QMF1zAsUHpP4Znk0LO5RcvA
pi_3QMF0FAsUHpP4Znk0mmEao8T
pi_3QMEzIAsUHpP4Znk17nMeOLq
pi_3QMEylAsUHpP4Znk0bbOl8tE
pi_3QMEefAsUHpP4Znk0xLfpaaj
pi_3QMEakAsUHpP4Znk0ayxEpkN
pi_3QMEaPAsUHpP4Znk1YgSnldI
pi_3QME3uAsUHpP4Znk1ZerREdk
pi_3QMDizAsUHpP4Znk1RYMacha
pi_3QMDezAsUHpP4Znk0sB5APqp
pi_3QMDcvAsUHpP4Znk0Sgzs42c
pi_3QMDa2AsUHpP4Znk0HqXi5Ka
pi_3QMDDRAsUHpP4Znk05gfJAn0
pi_3QMDAiAsUHpP4Znk0Lgjwu3c
pi_3QMD5nAsUHpP4Znk0w2Mwwn8
pi_3QMD3tAsUHpP4Znk1aQWsnQS
pi_3QMD2KAsUHpP4Znk1PQswK3K
pi_3QMS4CAsUHpP4Znk0E0GCEl3
pi_3QL3GYAsUHpP4Znk1R31XwOj
pi_3QL13eAsUHpP4Znk0muygL5n
pi_3QKlx6AsUHpP4Znk08my27xx
pi_3QKltBAsUHpP4Znk0XHChHl2
pi_3QKlqtAsUHpP4Znk1pIFam4m
pi_3QKKFeAsUHpP4Znk192KDace
pi_3QKK9VAsUHpP4Znk0nrxfVFq
pi_3QJhATAsUHpP4Znk0KfAG2XW
pi_3QJf9vAsUHpP4Znk1nD1o4pI
pi_3QGShEAsUHpP4Znk07GCfHVC
pi_3QGSXKAsUHpP4Znk0mvP4xEq
pi_3QCcRvAsUHpP4Znk0QlgAfq4
pi_3QCcObAsUHpP4Znk1PaKsQMq
pi_3QCcMBAsUHpP4Znk1HfhGTdp
pi_3QCGbvAsUHpP4Znk0OnWZgeo
pi_3QCGasAsUHpP4Znk1VM1CJxk
pi_3QCGaOAsUHpP4Znk0kLSsogi
pi_3QCGaeAsUHpP4Znk0bRz4eES
pi_3PXuC9AsUHpP4Znk0DGPtfs0
pi_3OfAEIAsUHpP4Znk1960gD61

rapid skiff
#

I didn't see any personal data in the snippet of the shared file initially, but it was removed before I could look closer.

thorny geyser
#

I'll re-add

rapid skiff
#

Did you go through those? I really don't need much more context here. The banks are telling us the provided postal code is wrong. If the value is actually correct, the bug is on the issuing banks side and our checks are behaving as expected.

thorny geyser
#

We've had people try 3 cards, their's, their moms and their husbands. Is it really likely that they got the zipcode wrong on all of them?

#

And the rate of failure across just the Irish businesses, just in the last week

#

Half of Ireland all of sudden forgot their zipcode

#

Realistically I think we can see there is a problem here

#

And that's either, 1 bank, or a group of banks reliant on the same software has a bug. Or Stripe has a bug.

dapper kelp
#

HI ๐Ÿ‘‹

I'm stepping in as my colleague needs to go

thorny geyser
#

Hi Snufkin

#

Hopefully you can see the issue here and help?

dapper kelp
#

It looks like this is a known incident with specific Irish banks/card issuers. You should have received multiple communications about this. I'm still reviewing the recommended actions for more details

thorny geyser
#

Neither ClassFit or our customers seem to have received any comms around this - other than when we've reached out here directly. Generic support didn't seem to know about it either.

#

But more improtantly, our clients' businesses are effectively shut down until we solve this, or find a workaround

#

Which I'm hoping you can help with...

dapper kelp
#

I see the general guidances is to turn off block_if_wrong_zip Radar rule

thorny geyser
#

We don't have radar for teams

#

So our options are

  • upgrade and pay a premium to solve a bug which isn't ours
  • Turn off worldwide and assume all risk for this ourselves
  • Don't turn off at all.
#

I did ask for a country or user option but we need radar for teams for that...

dapper kelp
#

Unfortunately that is the case. From what I can gather, the IE banks unexpectedly began performing AVS checks which led to lower card auth rates

thorny geyser
#

Is the suggestion here that this is performing bug free, and that our Irish customers are just getting their own postcodes wrong over and over again?

dapper kelp
#

No

#

At least, not that I can gather

thorny geyser
#

So if the error doesn't sit with 50+ customers, which I agree is unlikely, it must sit with either multiple banks, or Stripe right?

#

Unless I'm missing a third option?

dapper kelp
#

It appears that at least 3 large Irish banks are performing AVS checks incorrectly and responding to our auth checks with failures.

thorny geyser
#

I don't want this to sound loaded....

#

But why do Stripe think the problem lies with 3 separate banks, rather than Stripe?

#

(and it may do - I just always look to a single point of failure before assuming multiple separate points of failure)

dapper kelp
#

I'm still catching up on all the documentation (this has been ongoing for a while) but I know that we can see internally what your customers enter and follow those same values all the way through to network conversation we have with issuing banks without any change in the values.

And we've been investigating this since last Tuesday

thorny geyser
#

So as things stand, Stripe's stance is there's nothing to fix internally, multiple Irish Banks have initiated AVS checks at the same time ( I assume to meet some legislation deadline) and they've done it erroneously so until they fix it nobody paying online with those banks will be able to make any payments?

dapper kelp
#

Customers will be able to make payments if merchants disable the block_if_wrong_zip radar rule

thorny geyser
#

Which Stripe only allow to do at a country level if we upgrade to Radar for teams. So we need to:

  • Pay more
  • Increase risk
  • Lose our Irish clients?
#

Seems to be a tough spot we're being put in here...

dapper kelp
#

Yes, I'm reviewing the back-and-forth about this situation

thorny geyser
#

Thanks - any workaround that doesn't involve the above 3 painful options will be appreciated

dapper kelp
#

My colleague has reached out for clarification but unfortunately I don't see any clear next steps other than the Radar rule recommendation.

The issuing banks appear to consider the fact that they are authorizing the payments sufficient, even if they do return an incorrect AVS check value.

thorny geyser
#

Are stripe in communication with the banks about these issues, or just waiting for them to figure it out on their own?

dapper kelp
#

We are in active communication with the banks and communicated with them by last Wednesday (or ealier, still back-scrolling).

#

At this point the best approach you can take would be to write in to Support https://support.stripe.com/contact. This will ensure you receive communications about remediation efforts and any additional support we can offer your account

thorny geyser
#

We already have a ticket open

#

Their response was essentially sucks to be you - please wait, no timeline.

#

which our Irish customers loved...

#

They also seemingly had no clue about the issue.

#

I had to inform them based on my prior support here

dapper kelp
#

That is understandable. Unfortunately there isn't much more I can offer since this is no longer and coding or API integration question

thorny geyser
#

OK - well thanks for your support.

dapper kelp
#

I know it is frustrating but I would push back on that open ticket and request additional investigation.

fathom tartanBOT
#

dan-classfit_ie-avs-errors