#zonos-paymentintent-expiration

1 messages · Page 1 of 1 (latest)

deft ledgeBOT
tired hill
#

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

brazen wadi
#

Do you mean a new Authorization?

tired hill
#

Yes, apologies, mixed up the words

brazen wadi
#

Can I use the same Payment Intent? Or would that require a new PaymentIntent?

tired hill
#

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

brazen wadi
#

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?

tired hill
#

Correct, that is a possibility that they may have to complete 3DS again

brazen wadi
#

What payment methods are available for authorization without capture? Is it only CC?

tired hill
brazen wadi
#

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?

tired hill
#

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.

deft ledgeBOT
spark talon
#

If the expiration fails, the PaymentIntent gets canceled and you get payment_intent.canceled