#nimheru_moto

1 messages ยท Page 1 of 1 (latest)

plush vigilBOT
#

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

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

gloomy maple
#

Info; it only seems to affect some Mastercard payments, but not all

#

Sorry you need to fill out a new request in #help , this thread is for the request I've posted

pallid gorge
#

@quartz cove could you please open a seperate thread please ?

#

๐Ÿ‘‹ @gloomy maple
Checking the request Id req_n1CWOawSJKJAPB I see that the bank issuer is blocking the payment

#

So the customer needs to reach out to their bank for more information on why the charge was declined.

gloomy maple
#

this is happening to a number of customers though not just an isolated incident, can I confirm that Stripe is correctly marking the payment as moto in its communication with the bank's network (and therefore exempt from SCA)?

#

I can provide more requests if thats any help

pallid gorge
gloomy maple
#

so it seems that some banks are now declining moto payments when they weren't before?

pallid gorge
#

I don't know honestly, as far as I can see is that the bank issuer has declined the payment.

gloomy maple
#

I can't help you with this, I don't work for Stripe, you'll need to visit the #help channel and click one of the relevant buttons to start your own request.

pallid gorge
#

The decline code from the bank issuer is 65

#

For Mastercard/Visa it means Exceeds withdrawal count limit and Stripe intercepts it as authentication_required code

#

@quartz cove Could you please open a separate thread for you using #help ?

gloomy maple
#

Is this a new change? Up until 7pm on Friday we weren't seeing a single authentication_required

#

might it have presented as a different decline code before or has 65 always been interpreted as authentication_required?

pallid gorge
gloomy maple
#

Ok thanks for your help, its just strange that I cant seem to find any network_decline_code: 65 from before Friday evening!

pallid gorge
#

Yeah, the customer needs to reach out to their bank issuer and check what is the issue. Sorry that's what I can tell as far as I can see...

gloomy maple
#

Ok thanks, I'll see what I can do there

plush vigilBOT
gloomy maple
#

one last thing sorry, I was hoping to use the API to attempt to filter these problem payments but I cant see a way to filter this decline_code or by network_decline_code, is this possible?

#

I notice you cant even filter the dashboard by Decline reason => authentication_required which is odd, the rest of the reasons seem to show but not that one

plush lagoon
#

hi! I'm taking over this thread.

gloomy maple
#

Ok thanks

#

To add to the dashboard issue; there is a "Withdrawal count limit exceeded" option which sounds like it would match what os4m37 was saying but this doesn't match anything

plush lagoon
gloomy maple
#

Ok thanks any idea on the API query? can we filter by decline_code or network_decline_code?

plush lagoon
#

so no. but you could list all PaymentIntent, and then do the filtering on your end.

gloomy maple
#

ok thanks i'll take a look at that

plush vigilBOT
#

nimheru_moto

azure moon
#

Hi there ๐Ÿ‘‹ jumping in as my teammate needs to step away soon. I do see that there was a concern over the weekend that led to moto transactions running into 3DS chellenges being required, but that it has since be mitigated. Please let me know if you're still seeing example of this occurring though.

gloomy maple
azure moon
#

I'm seeing that it was mitigated around 12:30 PM UTC today

gloomy maple
#

Ah ok the latest I'm seeing was req_ZMBa0CTwShBiW7 at 12:32:04 UTC so hopefully that will be the last of it, does Stripe have any background on what caused this? I'm assuming it was a change on MasterCard's side as it seemed to affect a number of institutions

azure moon
#

I suspect our Support team would have already tried to reach out regarding this, but if not and you need more details they'd be the best team to contact for those. You can open a ticket with them here:
https://support.stripe.com/?contact=true

gloomy maple
#

We haven't heard anything yet, I'll get in touch with them thanks