Moustache | Stripe Developers | Page 1

cold fableBOT Mar 21, 2023, 2:05 PM

#

sage terrace Mar 21, 2023, 2:06 PM

#

Here is the POST data

#

...and the response

signal surge Mar 21, 2023, 2:07 PM

#

Hmm, ~~maybe there was a pending invoice item~~? (that doesn't make sense) Let me take a look

#

I'm stumped too, I've asked a colleague to take a look and see if they know what's happening here.

sage terrace Mar 21, 2023, 2:20 PM

#

ok, thank you. The POST request seems to have the exact same ~~name~~ description as the archived product but it seems crazy that would attach it to the invoice

signal surge Mar 21, 2023, 2:27 PM

#

Okay so it seems like the price was generated previously due to another Invoice Item creation that used the exact same params
https://dashboard.stripe.com/logs/req_PBBt3O1SDLwGUl

A colleague tested this and are seeing the same results as well. It seems like this is expected for "ad-hoc" prices that are created from invoice items we reuse previous price object ID if the params are exactly the same.

It is confusing and counterintuitive as this is an archived price ID, I'll file feedback for this internally to see if we can clarify anything.

#

One question though, how is this affecting your usecase if the invoice items are getting created with inline data anyway?

sage terrace Mar 21, 2023, 2:33 PM

#

Hmm so the stripe product was added because it had the same name as the description? That seems oddly implicit. My client brought this error to my attention, and was generally confused about what was going on.

signal surge Mar 21, 2023, 2:36 PM

#

Gotcha. Yeah I think this is due to these invoice item parameters being exactly the same.

sage terrace Mar 21, 2023, 2:38 PM

#

We handle our own products internally and though the connect clients are able to create non-recurring products, we never want to interact with them. Should I try to make the request unique each time? Maybe adding something like metadata:{uuid:asdfasdfa} or something?

#Moustache