DeputyCheese-pi-action

[quick oar]

Hey! Hmm, there's direct correlation between the Sources API and Payment Intents. You can theoretically use Sources with PIs if you wanted

This doc outlines the various statuses of PIs: https://stripe.com/docs/payments/intents

The general flow is:

• Creation.
• Confirmation (and attaching associated payment instrument).

[lunar solar]

Thanks for your answer. My question was related to the specific webhooks.

That means I created the PI already and - especially for deferred payment methods like SOFORT - I already confirmed it and/or have confirmation_mode set to auto

When using sources I had to wait for the payment status to become "chargeable", this parameter doesnt exist now anymore

https://stripe.com/docs/api/events/types#event_types-source.chargeable

As far as I understand the webhook will be getting called when the payment was already charged by stripe itself (or if it's failed)

But I don't have to wait/check for a chargeable parameter anymore and do the charge by myself

[quick oar]

Yeah there's no concept of 'chargeable' with Payment Methods. Will you find though is that those bank redirect methods (like SOFORT) is that they are async/delayed: https://stripe.com/docs/payments/payment-methods#payment-notification

So they will be in a limbo state (processing) for X number of days until the payment is actually complete

[lunar solar]

Yes that's exactly what I mean

So, when the stripe hook is getting called, it's just a notification for me that a payment was charged successfully or if it failed

No need for me to finalize anything in this hook, right?

[quick oar]

Exactly, yep

[lunar solar]

Ok great, thanks!

[quick oar]

So if you got payment_intent.payment_failed you'd want to bring your user back on-session to capture a new payment method: https://stripe.com/docs/payments/payment-intents/verifying-status#handling-webhook-events

[lunar solar]

Thanks

[quick oar]

Sure, np