#unexpectedtoken
1 messages · Page 1 of 1 (latest)
This is expected current behaviour, only the most recently used card payment method might be prefilled
We're currently working on expanding support for previously saved payment methods, but no specific timeline for that yet
It's going to get better though!
Thank you for the quick reply!
Do you know which feature(s) might be supported in the future? For example, are you thinking of adding support for specifying a previously saved payment method in the call to stripe.checkout.sessions.create?
I'm not sure exactly what options will be available like that, no. Likely you'll be able to manually set the default for the customer if they have multiple payment methods saved, though.
Ok, thanks again!
NP!