#gmorris-paymentintent-charge

1 messages · Page 1 of 1 (latest)

lofty ferry
#

A PaymentIntent is like a state machine of all the payment attempts. A Charge is a "record" of one payment attempt

#

a PaymentIntent can have 0, 1 or N charges but only one successful (most recent)

#

when you deal with PaymentIntent, you don't have to look at the Charge, the status on the PaymentIntent is enough

fresh glen
#

If a charge fails, do i need to do anything to cause another charge to occur? Or will it automatically? Once the status of the payment attempt is failed (or whatever the exact status is) is this sufficient to assume the entire attempt failed?

lofty ferry
#

PaymentIntents don't change, you control them (unless you use Billing)

fresh glen
#

Sorry, to rephrase the question, when I receive a webhook, if it is payment_attempt_failed, can i assume that the entire intent failed?

#

Or could another charge occur later

lofty ferry
#

well the payment attempt failed. In most cases you would write code/UI flows to attempt again for that PaymentIntent

fresh glen
#

Yes that is what I assumed, I just meant in this case (since its ACH and could take some time), I can assume I have to retry it manually?

lofty ferry
#

yes

fresh glen
#

That is, stripe will not retry it automatically correct?

#

Awesome thank you!

lofty ferry
#

(again unless you use Billing)

fresh glen
#

Idk what billing is but I don't use it I don't believe]

lofty ferry
#

Billing is our product for recurring payments

fresh glen
#

Got it, we do not, but I appreciate all the help!!

#

This was extremely helpful and clear!