#cco3-checkout-savedpm
hot tendon
Hello
We will only pre-fill a payment method in a Checkout Session if you pass a Customer ID and all of the things we document here are true: https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-customer
This is mostly intended to pre-fill if a Customer uses Stripe Checkout and you save that card and then returns to Stripe Checkout again later on.
rugged isle
Is there a reason it only works for cards? I'm trying to do this with ACH payments.
hot tendon
We just don't support this for payment methods other than cards
I can put in a feature request with that feedback
But not supported today
rugged isle
If they use the same bank they have set up elsewhere, will they have to go through the verification process again?
hot tendon
If they go through a Checkout Session again then yes
rugged isle
Also, will I be able to set a saved ACH payment method by switching to the payment intents API?
hot tendon
Generally you wouldn't send them back through Checkout if you are charging a saved PaymentMethod
rugged isle
hm, why is that? I think I'm missing something about the paradigm.
hot tendon
Checkout is for collecting new payment details. If you have a saved payment method you don't want the customer to have to enter new details so you just show them a UI of their saved payment methods and if they select one of those to pay with then you create/confirm a PaymentIntent from your backend using that PaymentMethod ID without sending the customer to Stripe Checkout
rugged isle
OK...I thought the point of checkout was primarily to easy the UI burden
hot tendon
I mean it certainly is.
But it doesn't handle saved payment methods well yet.
So you can either send them back through Checkout and have a bit more customer friction
rugged isle
got it
hot tendon
Or invest in building a "saved payment methods" UI
rugged isle
OK, well going to have to rewrite all this now =P, thanks
supple estuaryBOT