#sam_setup-intents-auth-charges

1 messages · Page 1 of 1 (latest)

lusty abyssBOT
#

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

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

zenith nexus
#

Hi 👋

Stripe does perform an auth with the issuing bank when you attach a payment method to a Customer.

However, I'm curious about the order of operations you are using. Setup Intents are designed to take care of both creating the payment method AND attaching it to the Customer in one API call. Is there a business reason you have those two steps separate?

void cobalt
#

Not sure, I came onto the project recently and its been around since 2022 so some things exist they way they have for reasons which aren't available to me at this time.

zenith nexus
#

Gotcha. It would reduce latency and the number of API calls if you simplified to just creating/confirming the Setup Intent

void cobalt
#

So there is an auth happening with our current setup of using setup intent and creating a payment method though?

Would there be a way to verify that the auth took place?

We recently started using the checks object that is returned with the payment method to verify how the cvc_check may or may not be happening, but we weren't clear what other validations we could glean

zenith nexus
#

The trouble with the checks property is that sometimes banks do not report the data back to us. It doesn't mean the check didn't happen but not all banks send the outcome back to us.

#

But I can confirm that, when you confirm the Setup Intent, we are performing an auth with the issuing bank

#

But if all you want to do is save a Payment Method to a Customer (with a $0 auth), you can follow this guide and reduce the number of API calls.

#

An added benefit is, if the auth fails, the customer is still on-session and can provide a new payment method

void cobalt
#

Is there any documentation you have around the auth($0) that occurs, when the setup intent is performed? I feel like i'm having a hard time getting a doc I can point my leadership too that says this is happening

zenith nexus
void cobalt
#

Okay and then tangentially related. - Last question 🙂

Would there be any benefit to us, performing a 1$ payment intent, and on success refunding this amount back to the customer imeddiately?

We wanted to verify the cards, because of some of the issuesd were are seeing with cards- but from your/stripe's perspective, it sounds like we shouldn't need to do this - correct?

Would this be a practice that would be frowned upon/ would it have negative impact potentially to us as a platform?

zenith nexus
#

This would negatively impact you as a platform and frequent auth and reversals can get your account flagged as fraudulent by card networks and Stripe.

void cobalt
#

Awesome thanks for that clarifiation

zenith nexus
#

Great 🎉 I'm happy to shed what 💡 I can 🙂