#daniel.3dturnier
split birch
woeful osprey
I suppose by 'hosted' you mean Checkout? https://docs.stripe.com/payments/checkout
woeful osprey
OK, then you likely need to pass the payment_method_types parameter when you create the session and only pass the PM the customer preselected
Like, payment_method_types: ['eps'] then that will be the only method on the page
tender hedge
I have tested this part - than I can't use "payment_method_configuration"
I would prefere not to remove the possibilty to change the method on the stripe page
woeful osprey
Yep, because that parameter is mututally exclusive to dynamic PMs which you opt out of when using payment_method_types
tender hedge
but just "preselect" one
woeful osprey
I would prefere not to remove the possibilty to change the method on the stripe ...
Then what you want to do isn't possible
The pre-selected PM is determined automatically using an algorithm to optimise conversion
tender hedge
Ok - I think than I will life some weeks with that "double selection"
I have also a second question - where to stripe support couldn't help me
woeful osprey
Sure
tender hedge
I want to hand over the "name" of the customer (like the customer_email) - as I have it already in my system
the support send me this:
woeful osprey
Also not possible I'm afraid
tender hedge
customer_data.name - but testing it failed
woeful osprey
Yep, that's not a parameter. Just a field on the object
tender hedge
how can I avoid to force the customer to enter his name again?
woeful osprey
The only way to do that is by creating a Customer object upfront and passing it to the session: https://docs.stripe.com/payments/accept-a-payment?platform=web&ui=checkout#handling-existing-customers
