#zonos-paymentintent-expiration
1 messages · Page 1 of 1 (latest)
There isn't a special doc for it, the options would typically be to either make a new capture (but you can do it automatically if you saved the payment method), to automatically capture as you suggested, or to release it and not capture again
Do you mean a new Authorization?
Yes, apologies, mixed up the words
Can I use the same Payment Intent? Or would that require a new PaymentIntent?
New payment intent
And one potential sharp edge there is that some banks don't release funds immediately, so it is possible to get a decline for insufficient funds if the customer doesn't have enough in their account for the new auth
If a new PaymentIntent is required, I imagine that the customer may need to complete extra steps if the payment intent comes back with a status of "requires-action"... is the right?
Correct, that is a possibility that they may have to complete 3DS again
What payment methods are available for authorization without capture? Is it only CC?
Our doc says cards, Afterpay, Cash App Pay, and Klarna
Only some payment methods support separate authorization and capture. Payment methods that support this include cards, Afterpay, Cash App Pay, and Klarna. Payment methods that don’t support this include ACH and iDEAL. Read more about payment method integration options.
https://stripe.com/docs/payments/place-a-hold-on-a-payment-method#auth-capture-limitations
Sorry, got pulled away.
One last question. Is there an event that gets fired for a webhook when a card authorization is expiring? Or should we just hard code a capture to take place after a duration of 168 hours?
I don't think there is an event for upcoming expirations. Once the hold expires I think we sent a payment_intent.payment_failed or payment_intent.amount_capturable_updated event but I am not finding a solid doc on this.
If the expiration fails, the PaymentIntent gets canceled and you get payment_intent.canceled