#nikunj_32420
1 messages · Page 1 of 1 (latest)
@polar narwhal hello! I'm not sure I understand what you're asking I'm sorry. Why would you use a SetupIntent if you have already done a "transaction" before? Can you provide a bit more details?
Sorry, basically we noticed the authorizations on Stripe were 2x the settled transactions. On taking a closer look it seems to be coming from failed authorizations and saving of cards (Setup_intent). We had enabled the zip code requirement on the processing side and it seems the failed transactions have increased due to it. Also can we enable something like saving of card post authorization of the transaction so that we are charged only once for authorization?
This is our understanding not sure if that is how it actually works or not
I'm really sorry, I still barely understand anything you are describing as it's lacking the context of the real APIs you are using and our Stripe vocabulary.
If you are using SetupIntents and ask Stripe to block bad postal code/ZIP verification then yes a real "authorization" with the bank happens and we might block it. But I have no idea what you're asking compared to a previous transaction
@polar narwhal did you have a more detailed explanation?
Ok can you confirm that there are 2 type of authorizations that happen
- One for each transactions
- One when card is saved
We want to understand since transaction authorization preceded card save authorization is there a way to club these 2 authorizations?
we don't have a vocabulary of a "transaction" so not really. I'm really sorry you did seem quite lost with your Stripe integration. Are you the developer writing the code and in charge of the whole integration?
No I work on the finance side
We can say authorization instead of transaction
Say a new user uses our app and pay for our service and chooses to save the card in the profile. The same card is authorized twice once for payment and then for saving it (setup-intent).
We want to understand if these 2 authorizations can be clubbed
All good, just this Discord server is aimed at developers asking questions about their integration and their code. That's why it took us 40 minutes to get to some kind of alignment on the vocabulary and I'm still guessing a bit here unfortunately.
What you are supposed to do is configure your integration to save card details while you are charging their card. It's documented here: https://stripe.com/docs/payments/save-during-payment. This would ensure there's only one "authorization/transaction" (which are not words we use in this flow in our API/product).
Thank You let us review. I appreciate the help and patience 🙂