#Sadness ;'(
1 messages Β· Page 1 of 1 (latest)
Hi π can you elaborate on what you mean by "right before payment is executed"?
Our webhook events all have actions that trigger them, and as such it's not possible for us to trigger events for actions that haven't happened yet.
I mean the event that will be broadcasted before the stripe is trying to collect money from the user
No event is generated and sent due to a payment about to be processed. What is it that you're trying to accomplish, maybe I can suggest a different event or approach?
I have an ordering system that orders things. It's a certain amount of these "things". When user orders this "thing" another user can try to order it too. So i need somehow prevent users to order the same thing twice. I assume that user that earlier ordered "thing" gets it. The order starts to be fulfilled when user pays for it. I came up with a solution to block another person to pay for the order when another tries. It worked well when i used server-confirmed payment intents. When i switched to client-confirmed i relay only on webhooks so i can not "block" other users to pay for the order when another person tries. That's the problem.
And i need to switch to client-confirmed to support for example apple pay and other wallets easliy.
π stepping in as toby needs to step away
Good to know!
So one easy way to handle what you are talking about is to use manual capture: https://stripe.com/docs/payments/place-a-hold-on-a-payment-method
Are you familiar with auth & capture (manual capture)?
Payment methods that donβt support this include: ACH and iDEAL. Read more about payment method integration options.
Not quite
It seems like a good idea
Gotcha yeah this is mostly for card payments
It allows you to hold an authorization for up to 7 days
Got it. In that case you likely want to go 1 of 2 routes
You either want to block Customers from entering your checkout flow unless you are sure you have sufficient inventory, or you want to refund a Customer immediately if they complete a checkout and you no longer have sufficient inventory
I would recommend the former
I tried the first one
But it's a bad idea, because a suspicious user can order one thing non-stop, and block other users.
And the second one too, because users will be confused
Well I assume you would have measures in place to handle "suspicious users".
Yeah, it is possible to do. But i feel like i write unessecary code.
Is there any way to handle ACH or iDEAL in auth & capture model?
Auth & capture seems like a good option overall
No it isn't possible with ACH or iDEAL as they don't support just authorizing a Charge.
I laid out the potential options already. If you want ACH/iDEAL and other LPMs then you can't use manual capture so you are going to have to stop customers from attempting to pay until you know you have inventory (either you get more inventory or another customer's session ends without them buying the held inventory).
What do you mean by LPMs? This situation is frustrating.
Thanks for clarifing but it kind of dissapoints me because of the fact that:
Only some payment methods support separate authorization and capture. Payment methods that support this include: cards, Afterpay, and Klarna
Afterpay, Klarna and also Apple Pay (https://support.stripe.com/questions/using-authorization-and-capture-with-apple-pay) support this (they are LPMs!, non card payments) but iDEAL and ACH does not?
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
Hi there π taking over for @trim sundial as they must step away
Is there an outstanding question here?
Good to know! Right above your message π
I believe that was answered here: #1065006989668790323 message
If you want ACH/iDEAL and other LPMs then you can't use manual capture so you are going to have to stop customers from attempting to pay until you know you have inventory (either you get more inventory or another customer's session ends without them buying the held inventory).
Kind of, this idea of blocking users is not good because of several reasons (complicates code, decreases conversion, and frustrates users). But my real question was: Apple Pay supports manual capture (as I understand it is LPM) then why ACH and iDEAL does not?
I'm just curious which payment methods actually support auth & capture.
I can't answer the "why" questions, because the answer is either (a) "the financial infrastructure is not available to do this, or there is an inherent incompatibility with how the payment method type operates", or (b) "the product team decided to do it that way"
OK, thanks. Then, is there a list of payment methods that support auth & capture?