k3davis

[vernal totem]

The Setup Intent, once confirmed successfully, will generate a Payment Method object (pm_xxx) that can be used to create off-session payments.

This part of the guide indicates how you'd re-use a pm_xxx generated from a Setup Intent to charge a customer: https://stripe.com/docs/payments/save-and-reuse?platform=web#charge-saved-payment-method

[grim ocean]

Yes, I'm able to do that successfully. So it sounds like my understanding is correct, I don't need to keep track of the SetupIntent ID, I only need to keep track of its resulting payment method in order to capture an off-session payment. The SetupIntent is effectively not needed anymore.

Correct?

I guess another way of asking, what's the difference between a payment method I created using the API and a payment method created using a setupintent, if either one can be used for future off session charges.

[vernal totem]

I don't need to keep track of the SetupIntent ID
Correct, once succeeded it is redundant and can be discarded.

I guess another way of asking, what's the difference between a payment method I created using the API and a payment method created using a setupintent, if either one can be used for future off session charges.
Creating them directly via API (/v1/payment_methods) won't correctly setup the card for off-session usage (i.e. carry out any 3DS/auth for SCA, that we can later use to request exemptions for).

If you use that endpoint directly, chances are your off-session payment would be declined. Always use a Setup Intent and confirmation flow with Stripe.js: https://stripe.com/docs/payments/setup-intents

[grim ocean]

That makes perfect sense, thanks for helping me sort it out 🙂