#newtreyes_unexpected

1 messages ¡ Page 1 of 1 (latest)

fast heraldBOT
#

👋 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/1267491546543030293

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

fierce flower
fossil pebble
#

@fierce flower Hi

#

The thing is that both PMs represent the same CC with the same information

#

nevertheless, one fails and the other one doesn't

fierce flower
#

Yeah looks like there was an AVS check failure from the issuer on the one Radar blocked (as per the rule)

#

Not sure why the AVS check failed for one but not the other, that's a question for the card issuer

fossil pebble
#

Is there a way I can find the info for the request that created this pm? pm_1PhtJqDfcmTYbu9YOgCp41sy

#

I know it wasn't created using a setup intent

#

but I would like to know if it was created as part of a payment intent capturing process

#

Seems like the payment method address came from its related customer

#

while for this other pm (pm_1PhshODfcmTYbu9Y8IlUxayR) it looks as if it came from the setup intent

fierce flower
fossil pebble
#

Thank you, @fierce flower

#

There is something odd here

#

Look

#

Nevertheless, it was not created with that information

#

here

fierce flower
fossil pebble
#

Ahhhhh

#

that makes sense