#stripe_connect_platform-payment-methods

1 messages · Page 1 of 1 (latest)

marble vigil
raw ingot
#

If you just show 'card' you can save the payment method.

#

But if you show 'card' + something else, the payment method is also not saved if they choose card (even though cards allow setup_future_usage if alone). Is there a workaround?

#

OK, totally separate issue:
Also, once a "Guest" is created, is there any way possible to move the payment method and the invoices from the "Guest" to a new Customer we create? We tried to update the PaymentIntent with the new Customer ID but that failed. And we get an error when we try to attach the pm_ to the new Customer as well.

marble vigil
#

I don't believe there's a way to conditionally set setup_future_usage depending on the payment method types being used, but let me check on that

raw ingot
#

I don't think so either.

#

but it is a bummer since by adding an alternative payment option you kill the default functionality on the credit card option.

marble vigil
#

For your guest customer question - once the payment method and invoice are created there isn't a way to migrate those over to a new Customer you create

raw ingot
#

OK, I didn't think so. Just double checking.

#

OK, sounds like we are a no on conditional setup_future_usage and a no on migrating a Guest to a Customer. OK. Thank you.

marble vigil
#

Yeah it's a no on the conditional setup_future_usage for Checkout - I believe we did just add this for plain old Payment Intents (to be used with elements), but no support for it on Checkout yet