#testing_83560
1 messages · Page 1 of 1 (latest)
Yes, P24 is a single-use PM so can't be saved
You need to omit the setup_future_usage param
Omit that too
ok, it worked.
Is there any way to know which enabled payment methods need these?
See: https://stripe.com/docs/payments/payment-methods/integration-options#additional-api-supportability
How to know this while passing params,the user may select any payment method?
Paypal need these :
mandate_data
setup_future_usage
save_payment_method
But some dont so is there any way to know while creating payment intent if these params are needed or should i just hard code these conditions
There's no API to know that no
is there any param which automatically filters these off if addittional params are passed
No, because the issue is you're passing an existing PM via payment_method
i didn't understand ,can you elaborate on that?
You're passing a previously collected P24 Payment Method when creating the Payment Intent, so you need to only pass parameters that that PM supports (i.e. not s_f_u)
If you were creating the PI without the payment_method parameter, then the dynamic PM filter wouldn't render P24 on the Payment Element for example