alexandrfarkas-auth-capture | Stripe Developers | Page 1

glacial quiver Sep 9, 2021, 2:03 PM

#

It's a card-based payment so i would expect so. Are you having trouble with this? Can you provide an example?

sly shoal Sep 9, 2021, 2:06 PM

#

Nope, I have not implemented it yet. Business requires cards + Apple Pay + Google Pay. And separation of capture and auth allows me to dodge some edge cases with race-conditions. So I was wondering if Apple Pay + Google Pay are eligible for this "hold" technique

#

Thank you a lot for your response.

glacial quiver Sep 9, 2021, 2:08 PM

#

let me just do a quick test to verify for you, bear with me as there are many people here right now 😅

sly shoal Sep 9, 2021, 2:10 PM

#

Ok, thanks. It would be great. Waiting)

glacial quiver Sep 9, 2021, 3:19 PM

#

apologies for the delay getting back to you here, but i did confirm this works as expected 🙂

sly shoal Sep 9, 2021, 3:22 PM

#

Thank you a lot)

glacial quiver Sep 9, 2021, 3:22 PM

#

quite welcome 👍

sly shoal Sep 9, 2021, 3:25 PM

#

Also, could you help with other question - Does Stripe fire some webhook, if hold was removed (by bank) before capturing?

glacial quiver Sep 9, 2021, 3:45 PM

#

https://stripe.com/docs/payments/capture-later

Failure to capture the payment by this time cancels the authorization and releases the funds. When this happens, the PaymentIntent status transitions to canceled

Place a hold on a card

Separate authorization and capture to create a charge now, but capture funds later.

#

SO you'd expect to receive a payment intent canceled event: https://stripe.com/docs/api/events/types?lang=curl#event_types-payment_intent.canceled

Stripe API reference – Types of events – curl

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

#alexandrfarkas-auth-capture