hector-vasquez_api

[shell ingot]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1366458785085919232

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[kind oxide]

Hello 👋

As you have already found out, you cannot change the payment method configuration of a Payment Intent created by an Invoice.

The Payment Intent's configuration must match the Invoice that created it

That's just how these APIs work

[obtuse sky]

Why it isn't possible to provide the payment_method_configuration param when creating an Invoice? https://docs.stripe.com/api/invoices/create

Based on all my tests, there is no way to make them "match".

[kind oxide]

What are you trying to make "match"?

Payment Method Configurations are a relatively new feature and, unfortunately, our Billing objects (Subscriptions & Invoices) don't currently support them

[obtuse sky]

I’m not trying to make the payment methods match — I’m looking for a workaround for an issue we’re encountering.

We are a connected platform, and we allow our connected accounts to choose which payment methods they want their customers to use through our system. To manage this, we are using payment method configurations.

In our custom checkout:
• If we don’t pass a payment method configuration ID or a list of payment methods/payment method types, the Payment Element only makes card payments available.
• If we do specify a list of payment methods (e.g., card, Klarna, Affirm), the Payment Element always renders those methods, even for customers whose connected accounts do not actually support those payment methods.
• If we instead pass a payment method configuration ID (which seems like the correct approach), the Payment Element correctly and conditionally renders only the available payment methods for that customer — exactly as we want.

However, the problem arises when trying to complete the checkout:
• The checkout fails because the Payment Element cannot confirm the Payment Intent when it was created by an invoice.
• This issue does not happen with subscriptions — the Payment Element correctly confirms payment intents created as a result of creating a subscription. See sample request here: https://dashboard.stripe.com/acct_1Iq9PYQOlQ0bobLE/test/logs/req_pUN3v4dENqOF1v

[tame cedar]

Hi there, I'm taking over from my colleague. Give me a moment to catch up on the thread.