#sam_best-practices
hazy sealBOT
đ 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/1359966076393488595
đ 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.
- sam_saved-pm-setup-intent, 1 hour ago, 7 messages
- sam_setup-intents-auth-charges, 1 day ago, 17 messages
dim vigil
Hello, by default it is possible for a $0 to happen when attaching a PaymentMethod directly to a customer or when updating the address on a payment method. For both of those methods you can pass validate=false if you don't want that to ever happen, but it should mean that the card details are more likely to be accepted later on. I am not sure if you can check the authorization charge retroactively via the API but will look into this
Taking a step back, can you tell me more about the context of what your integration is doing here and what you are trying to do where this info is helpful?
elfin plank
we are a refund platform.
We create a setup intent, and a payment method to gather folks payment information.
We've not changed anything here, but folks are trying to understand what auth stripe is peforming on our behalf.
Yesterday the support tech indicated that the auth occurs, but it wasn't clear in their documentation:
We don't explicitly say it very clearly (I'll recommend we add a callout to it in our
. But we do have a couple Support Articles that mention this:
https://support.stripe.com/questions/payment-intents-api-vs-setup-intents-api
https://support.stripe.com/questions/confirm-success-of-a-setupintent
My management is asking me to clarify:
- what auth is occuring ?
- is the auth for $0 ?
- how can we confirm from our side that the auth took place
We have customers who we've onboarded, and assumed authd using stripe, but when we attempt payments they sometimes fail - leading us to believe the auth never occured on the card network in the first place.
So trying to understand what verifications are taking place, so we know we can charge a card
dim vigil
what auth is occuring ?
Can you tell me more about what info you are looking for in this question?
is the auth for $0 ?
It is almost always $0 when it happens, in rare cases it can be a $1 auth. There are times when validation charges won't happened, we are required to do that at least some of the time to prevent card testing, though we do try to make sure to do what is most advantageous for your auth rate overall.
https://support.stripe.com/questions/check-if-a-card-is-valid-without-a-charge
how can we confirm from our side that the auth took place
This is not visible in the API as far as I can tell, I am checking to see if there is a way to get this in the Dashboard. If not, the best thing would be to reach out to our support team.
elfin plank
From https://support.stripe.com/questions/check-if-a-card-is-valid-without-a-charge
The card information is verified when the card is saved, but it only verifies that the information is valid: it cannot check credit limits or account balances to guarantee that a card will have sufficient funds when you do decide to charge it.
Seems to indicate it just verifies information, but doesn't mention a auth check being performed?
dim vigil
Oh it looks like you can get this via the API, my apologies for getting that wrong earlier https://docs.stripe.com/api/charges/object#charge_object-payment_method_details-card-authorization_code
Sorry "auth" may be the wrong term. We reach out to the bank to validate card details through a $0 (or rarely $1) charge. This happens often when confirming a setup intent but not always. I don't know the overall rate, that would be something to
elfin plank
Ah yeah, so we can see the auth on the charge attempt.
But we were curious how the card was verified before any charges are made against the card
dim vigil
I don't think we have docs on how this process works, are you lookin for info at this level? https://en.wikipedia.org/wiki/Authorization_hold
elfin plank
Unfortunately not, I think we were under the impression that an auth was occuring when we added the payment method to a setup intent / customer
But it sounds like this might not be happening, or it isn't documented?