#yandos666-payment-methods
spark zealot
Sort of. You can still set them on the Customer object to be used at a later time, but the customer would have to present to authenticate the payment method in cases where setup_future_usage isn't allowed.
barren bramble
so for example, using ACH Direct Debit outside of a subscription, we'd be able to store them against the customer object but when looking to take a payment they would have to re-confirm somehow e.g via their banking app?
spark zealot
Ah, so you can use ACH for future payments with setup intents, so that's not a good example: https://stripe.com/docs/payments/ach-debit/set-up-payment
barren bramble
ah no i think this is a good example 🙂 looks like what we're looking for
ACH would be preferred option, i think its just the page i linked to originally is pretty vague
final question, does ACH support retries?
spark zealot
I believe so: https://stripe.com/docs/invoicing/automatic-collection
Based on a combination of these factors, Stripe intelligently assesses when to retry payments. We continuously learn from new purchaser behaviors and transactions, which provide for a more optimized approach over traditional rules-based payment retry logic. Any invoice with the auto_advance attribute set to true goes through the Smart Retries flow (if enabled), regardless of the selected payment method.
barren bramble
https://stripe.com/docs/billing/revenue-recovery seems to say that bank debit methods are not supported but that seems odd as retries is pretty fundamental to direct debits such as BACs