#yunior-payment-intent

1 messages · Page 1 of 1 (latest)

wary patrol
#

You would need to update the PaymentMethod, not just payment_method_types

undone sage
#

thanks for help, but how can i do that? Should I use payment_method_data field while updating payment intent?

#

or update payment method separately using POST /v1/payment_methods/:id

wary patrol
#

Have you collected the new sofort PaymentMethod to an object with id pm_xxx?

undone sage
#

ok so if I understand correctly, I should create new payment method via POST /v1/payment_methods and then provide collected payment method id to payment_method attribute in POST /v1/payment_intents/:id

wary patrol
#

Mostly. But generally you can't collect new paymentmethod by a backend call such as POST /v1/payment_methods. You would need to use client-side to collect

undone sage
#

ok, thanks a lot for ur help

wary patrol
#

good luck!

full wyvern
#

@undone sage What's the question?

undone sage
#

is there any way one can unset/reset payment method on payment intent?

full wyvern
#

It would depend on the status of the Payment Intent

undone sage
#

status is requires_action

full wyvern
#

Sure, you'd just re-confirm the PI with a new Payment Method

#

Or I guess reading your original Q, you'd pass the payment_method parameter in your update call

#

It's probably a lot easier just to create a new PI tbh

undone sage
#

ok i understand, but regarding creating new PI, I read that stripe encourage to have only one intent per order/transaction

full wyvern
#

There's no harm in multiple Payment Intents really

undone sage
#

ok, i think i get it now, thank u for ur help