#lucynoodles - charge to payment intent

1 messages · Page 1 of 1 (latest)

unreal rivet
#

When a payment intent is captured you'll get payment_intent.succeeded -- if you're using manual capture then after the authorization you'd get payment_intent.amount_capturable_updated to tell you to capture

opal coral
#

Okay, so to make sure I understand correctly: A payment intent will be captured automatically upon creation unless capture_method: 'manual' is specified. If it's captured automatically you'll get a payment_intent.succeeded event soon after payment_intent.created. If it's manual, you get payment_intent.amount_capturable_updated soon after payment_intent.created, and then you get payment_intent.succeeded when it goes through.

#

Is this correct?

#

Is there a flow chart that lays all this out somewhere?

unreal rivet
#

captured automatically upon creation
Not quite, it would need to be confirmed first, which may require handling additional authentication actions (3ds)

But otherwise the sequence is correct

opal coral
#

Okay, and my team is using confirm: true, so there is nothing we need to do there

unreal rivet
#

Assuming no authentication is required, correct

#

Then that will be confirmed and go to requires_capture status, and you'd get the payment_intent.amount_capturable_updated

opal coral
#

Will you get the payment_intent.amount_capturable_updated regardless of whether it's automatic or manual? Or only if it's manual?

unreal rivet
#

Only with manual capture

#

Another question about Payment Intent. It looks like Charges are still being used for refunds, is that correct? Payment Intents create a charge which, if it succeeds, can later be refunded directly?

#

You can supply either the charge or the PI ID when creating a refund, but yes, this is centered around the charge, so refunds exist on the inner charge and events are charge.refunded etc

opal coral
#

Okay, cool, thanks! And sorry about the separate thread

unreal rivet
#

No problem! (on either one :D)

#

Multiple questions usually are related (like these were) so it's helpful for us to keep in one thread, especially as we trade off with other team members here.

opal coral
#

Makes sense