zuckerbez

[hoary marsh]

You'd use webhooks, specifically payment_intent.processing and payment_intent.succeeded to be notified of async payment status changes: https://stripe.com/docs/payments/payment-methods#payment-notification

[distant sequoia]

Does that all cover the use case of a bank transfer which is "on it's way" but hasn't yet arrived?

The use case in questions, is when user is paying for monthly subscriptions using bank transfer and that we'd like to reduce the idle time between bank transfer and subscription activation.

i.e., an ACH credit process

[hoary marsh]

Yes, any async payment methods

[hoary marsh]

ACH CT? That's different

[distant sequoia]

Is there anyway to mitigate this scenario with ACH CT?

Activate the subscription, since the payment has been initiated by payer and is on it's way (but hasn't yet arrived)

[hoary marsh]

Do you have an example I can look at?

Unfamiliar with ACH CT as its a PM built on older APIs

[distant sequoia]

1- A user wants to renew their monthly subscription using ACH CT
2- Until the payment arrives we can turn their status to inactive, however if there's a way where we can know they initiated a transfer we can avoid that.

Hence, avoiding the downtime while we're standing by for payment to arrive

[hoary marsh]

Ok, let me check

Based on this: https://stripe.com/docs/sources/ach-credit-transfer#charge-request

source.transaction.created event should fire when the customer initiates a transfer

[distant sequoia]

Does that mean the source.chargeable fires afterwards?

[hoary marsh]

Seems like that fires once the funds arrives and you can charge the Source yep

[distant sequoia]

ok, thank you