cesperian

[tropic topaz]

The processing status should instantaneous for card Payment Methods, since our confirmation request is synchronous in that case

The processing status is more often seen when using asynchronous payment methods like ACH

[young otter]

Ok. Just to clarify; i'm currently handling both successful/requires_action responses. The asynchronicity of the processing status is what is making the handling 2x more complicated

[tropic topaz]

Do you have a concrete example I can review?

[young otter]

but you dont think accounting for 'processing' is necessary for a card-only payment?...

[tropic topaz]

Yes

But if you want to make sure you address that we would recommend listening for webhooks to get notified of updates to asynchronous payment methods: https://stripe.com/docs/webhooks

Then if your Intent winds up in a requires_action status you can bring the Customer back on-session to address it

[young otter]

ya, the requires_action is not an issue. But if you dont think accounting for 'processing' is necessary for a card-only payment than that would be good news on this end...

[tropic topaz]

Yes that shouldn't be an issue but I would still recommend at least investigating the webhooks approach. It can give you a good foundation if you decide you want to expand into non-card payment methods with asynchronous confirmation.

[young otter]

ya, ive got a good webhooks setup. But the ux of accounting for the indeterminate nature of asynchronous status' is becoming a real headache. Especially if its not necessary.

I think i can proceed, tho

thanks for the insight. Much appreciated