iy2011

[grave jasper]

Hi there

Yes you pass a PaymentMethod ID (pm_xxx) to the payment_method param of a PaymentIntent. Overall I'd recommend taking a look at https://stripe.com/docs/payments/ach-debit/migrations which talks about what is necessary to migrate ACH to PaymentIntents

[finite mango]

If we already have PaymentIntents generated against finalized invoices, what is the best way to update those to support the allowed payment_method_types?

[grave jasper]

Hmm that's a good question

Have you tried updating the payment_method_types on the PaymentIntent directly: https://stripe.com/docs/api/payment_intents/update#update_payment_intent-payment_method_types ?

Don't recall if we allow you to do that or not

Hmm yeah actually we don't allow that

It hits a validation error

[finite mango]

Apparently it's not allowed if it's already associated to an invoice

we really don't want to delete and recreate the invoice

[grave jasper]

Let me check with a colleague if this is possible without re-creation. Not sure it is unfortunately.

[grave jasper]

Okay actually looks like this is possible

So what you do is you set the us_bank_account PaymentMethod as the default for the Customer: https://stripe.com/docs/api/customers/update#update_customer-invoice_settings-default_payment_method

Then you use the /pay endpoint (https://stripe.com/docs/api/invoices/pay) to charge that default and it will override the payment_method_types set on the Invoice/PaymentIntent

[finite mango]

Got it, so there isn't something specific to the payment intent api that we could use? (e.g. update existing PaymentIntent)

[grave jasper]

No can't do that

[finite mango]

ok, thank you