#brk-afterpay
ocean geyser
hello @ebon spruce! we don't support setup_future_usage for afterpay_clearpay because it's a single use payment method.
To clarify, do you want to have afterpay_clearpay as a payment method option? If that's the case, you should use this parameter instead : https://stripe.com/docs/api/payment_intents/create#create_payment_intent-payment_method_types
ebon spruce
In my case, I'm using the react native payment sheet, and I let the use choose between card and afterpay.
So instead of creating new paymentIntent between changes I just update the one I first generated.
If I setup payment_method_types with ['afterpay_clearpay', 'card'] can I use setup_future_usage ?
Or do I need to re-create a new payment Intent
?
I was wondering if there's an option to remove the setup_future_usage
ocean geyser
you should be able to remove the setup_future_usage parameter - You're creating the payment intent in your server?
ebon spruce
Yes
ocean geyser
then are you passing in the setup_future_usage parameter when creating the PaymentIntent? If yes, you can always not pass it in
ebon spruce
Well first I create a PaymentIntent with setup_future_usage, then in my app I let let the user choose between using Cards or Afterpay, everytime they chose an option on the backend (php) I verify which option they selected.
in this case, the paymentIntent is created using card by default, so, when the user selects Afterpay y update the paymentIntent and change the payment method, but, I got that error. What I’ve been trying to do is find a way to unset the setup_future_usage, but unfortunately I can’t found a solution.
ocean geyser
i think you may need to change your flow - after the user has chosen the PaymentMethod, create a PaymentIntent. Don't update the existing PaymentIntent