#sina
urban loom
azure cobalt
Without upfront payment you'd use a setup intent as described here:
https://stripe.com/docs/payments/save-and-reuse?platform=web
If there is an initial payment, you can use the payment intent with setup_future_usage as described here:
https://stripe.com/docs/payments/save-during-payment?platform=web
hollow moth
Thanks, how would we do it in the case where there is an upfront payment?
For instance the cardholder goes online, purchases a subscription and pays for the first month, while authenticating themselves. Then next month we want to bill them again for their subscription.
azure cobalt
The latter guide would be what you want in that case, but if you're using Stripe BIlling and Subscriptions, this is also how the recommended integration works:
https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements#collect-payment
Not that future payments might still require authentication, that is at the bank's discretion
hollow moth
OK thanks. I believe this is all how we have it set up already (your first two links).
When using test card 4000000000003220 from https://stripe.com/docs/payments/3d-secure
to test this scenario, it always fails when doing an auto-pay despite having successfully authenticated the initial transaction. Is that just because that's how this test card is meant to behave? And in the real world, it wouldn't fail if the initial transaction was authenticated successfully?
off_session is true for the subsequent auto-pay attempts
azure cobalt
Yes that's right, its an artifact of that card, which ust be authenticated for all payments
You should use instead this card: 4000002500003155
https://stripe.com/docs/testing#regulatory-cards
This card requires authentication for off-session payments unless you set it up for future payments. After you set it up, off-session payments no longer require authentication.
That one is set up to succeed without auth for future payments after initial auth
hollow moth
Awesome, thanks