#dan-classfit_error
cedar chasmBOT
đ 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/1308060653159845918
đ 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.
- dan-classfit_error, 4 days ago, 21 messages
waxen dust
Do you have some specific payment examples?
idle adder
Hey Ynnoj - I asked abotut this last week. There was a thread open but closed now. Not sure how to share this with you or if you need it?
waxen dust
idle adder
Yes
So we had one client there who has had her business pretty much shut down due to this error
Stripe said they knew about it and were on it but I've had more tickets open today, so I'm guessing it's still ongoing.
General support suggested we could turn of postcodes on radar completely (with obvious significant risk on our side so we can't)
Is there a way to do this at a more local level, either just in Ireland, or per customer until the problem is resolved?
waxen dust
So we had one client there who has had her business pretty much shut down due to...
I meant some IDs of payments
But yes, overall this sounds like an ongoing issue with some IE banks/issuers AFAIK. You/your accounts should have been receiving comms about this
idle adder
The payments aren't being processed because of the issue
so there are no payment ids
I have 2 Irish customers I can provide their account details
Neither of them seem to have received any comms about this, other than one who has been speaking directly to Stripe support with us on CC
and the answer seems to be - sucks to be you. Sorry you can't take any payments. Bear with us.
And we've not heard anything from Stripe on this other than speaking to you directly
So, in the meantime, as there seems to be no timeline to fix - is there a workaround where we can disable postcode match requirements just in ireland or per account?
As turning this off globally is too risky
waxen dust
Quite honestly I'm still not 100% on what the issue is despite what I suspect becuase you've not shared any concrete details/IDs for me to look at
idle adder
I usually think that
but it's way too common, only in Ireland, and we know there is an issue there.
Example here.
waxen dust
Sorry, do you have some Stripe IDs for me to look at?
idle adder
They don't exist...
they payment isn't processesd because of this
or do you mean express account ID?
acct_1PyERWPMrjVzxHLp
acct_1PuGsFPL8kfqWlLt
These are the two customers who are unable to accept a significant amount of payments. Both Ireland based.
waxen dust
You say they're unable to accept payments, yet claim there's no IDs. So what exactly happens in your integration that prevents payments? Is there an error? What APIs do you call?
idle adder
They get to the checkout part of the process and then get the standard error from Stripe saying that the eircode they've provided doesn't match the one the bank has on file.
Usually, I point to this and say well check with the bank
but this is 40% of customers' experience with one of our clients, and the majority for the other
From my Stripe dashboard I can't see any way to see these payment intents / failures.
And what I'm hoping for is a way to disable this postcode match functionality at a country or express account level - is that possible?
waxen dust
They get to the checkout part of the process and then get the standard error fro...
OK, and what does this part of the checkout flow in your app look like in your code? Which API requests are you making?
All I'm trying to find right now is some evidence of an error. In any case I re-read through your thread from last week and found that it is related to what I referenced before
waxen dust
And what I'm hoping for is a way to disable this postcode match functionality at...
Shoud be possible to detect the card issuer country in Radar yes
You can incorporate that attribute into your rule that specifically disables the AVS checks
As my coleague discussed in the old thread last week, we can't really discuss the details of this ongoing issue here publicly but you can reach out to support for updates. In the meantime the loosening on the Radar rule(s) as advised is the short-term resolution