#javier_unexpected

1 messages · Page 1 of 1 (latest)

ashen stirrupBOT
#

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

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

sacred dome
#

Hello, still looking in to what triggered the $0 auth charge here and will get back with what I can find

foggy topaz
#

I can wait 🙂

sacred dome
#

I think the authorization charge happened because of this call to attach the payment method to the customer on your platform account. By default time a PM is attached to a customer, even without an intent, it can trigger an authorization charge when validating the card. What you can do here is pass validate: false in your create customer API request to prevent this validation from happening.
https://dashboard.stripe.com/logs/req_44uRP0dhUh8mqu

ashen stirrupBOT
foggy topaz
#

Interesting, ok.

I'll give it a shot.
It's weird though, I've only seen these behavior with 3Ds challenges in European cards.

#

And, it's the first time a bank flags it as "risky" 🤔

sacred dome
#

Yeah $0 auth charges are common so I'm surprised it was considered risky but I don't know a ton about what this looks like from the bank's perspective. This should prevent the $0 auth charges from happening in general here though!

foggy topaz
#

But, this validate: false.

We're doing it preventively, for whoever needs validation.

#

Is this not going to cause some issues for CCs that do require validation?

rough karma
#

Hi 👋 my colleague had to step away.

#

It may cause future payments with the same PM to fail. For most use cases it's probably better to validate, we just have this option to set validate false for users who have niche use cases.