#Hi we re wanting to migrate off of

1 messages · Page 1 of 1 (latest)

rustic horizon
#

tbash-paymentelement-serverside

#

Would the following items from the comparison list not be supported using the Payment Element if the PaymentIntent is created server side?
correct, right now, PaymentElement does not support those flows, this might be something it supports down the line but AFAIK no timeline on that

versed void
#

Ok, so if PaymentMethod was created using the Payment Element from a SetupIntent, a PaymentIntent cannot be created using that PaymentMethod with a variable amount? Do all PaymentMethods behave the same, regardless of them being created by the Card Element or the Payment Element, when interacting with the PaymentIntent API?

rustic horizon
#

ah so

#

so if PaymentMethod was created using the Payment Element from a SetupIntent, a PaymentIntent cannot be created using that PaymentMethod with a variable amount?
this DOES work yes

#

but it isn't the recommended flow really, doing a SetupIntent, followed by a PaymentIntent

my earlier answer was around how you could do the

  • Charge a different application fee amount based on the card brand, country, or payment method
    without using a SetupIntent on CardElement -> that doesn't work with PaymentElement + PaymentIntent alone
versed void
#

If we want users to add a PaymentMethod to be charged a later date (note: we don't intend to create a PaymentIntent immediately after creating a PaymentMethod w/SetupIntent), what would be the recommended flow? So even though it's not recommended, the following flow works? Customer -> SetupIntent -> PaymentElement -> PaymentMethod -> PaymentIntent (w/ variable amount based on payment_method.type)

rustic horizon
#

what would be the recommended flow?
in that case yes, i.e. collect PaymentMethod now, charge later

#

Customer -> SetupIntent -> PaymentElement -> PaymentMethod -> PaymentIntent (w/ variable amount based on payment_method.type)
and yes, just confirming the above, this is fine to do in your scenario

versed void
#

Awesome, thank you! One last question, is it possible to update a customer's invoice_settings.default_payment_method from the PaymentElement or is updating this server side only?

rustic horizon
#

server-side only!