swapnil

[half bison]

Can you tell me more about your overall goal here? Is there a reason you are setting the address on the intent when creating it? I assume something like automatic taxes?

[shy cloud]

Well I wasn't the one who implemented this but now we are kind of stuck because that's how it's being done for months. As far as we know there isn't a specific reason
We have many intents that had addresses updated with secret key that haven't been confirmed yet
So that's why hesitant to change the logic on the backend

We could expire these intents after the update but if there is an alternative...

[half bison]

Can you send me the ID of a PaymentIntent that you got this error for? (pi_1234)

And do you know what coding change caused this error to start happening after months of this code working?

[shy cloud]

pi_3Ng79ICCUoxgsv0s0UUQ090l

Earlier we had the (shipping) address element and payment element on different pages i.e. we had a two step checkout
Now we are trying to move them to the same page

So it's picking up the address automatically

[half bison]

Thanks for the ID, checking in to it.

Can you send me your account ID as well? (acct_1234)

[shy cloud]

acct_1GWVl3CCUoxgsv0s

[half bison]

I'm not seeing a way to exclude the address element input when confirming the intent. It might be a good idea to not add that info specifically to the payment intent before confirming. You can do your calculations and update the amount if necessary but it does look like after the billing address has been set with the secret key it can't be set again with the publishable key even if the address is the one that is already on the intent

[shy cloud]

hmm, I see
Looks like we have to update our backend to not add address upfront then
Thanks for looking into this