higher_invoice-preview | Stripe Developers | Page 1

young quailBOT Sep 18, 2024, 5:23 PM

#

👋 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/1286014663179501653

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

#

terse olive Sep 18, 2024, 5:26 PM

#

From the data sent in the request we would have expected to see $400 as the upcoming invoice price, instead we saw $345 which doesn't make sense from our perspective

#

the endpoint was /v1/invoices/upcoming I believe

young quailBOT Sep 18, 2024, 5:28 PM

#

autumn lotus Sep 18, 2024, 5:28 PM

#

higher_invoice-preview

#

@terse olive can you share your exact code and what the exact issue is? If you just call the API and pass nothing then you'd get the real upcoming Invoice

terse olive Sep 18, 2024, 5:30 PM

#

            subscription_id=subscription.id,
            subscription_proration_behavior=self._stripe_service.DO_NOT_PRORATE,
            upcoming_items=upcoming_items,
        )```

#

upcoming items is defined here

            # Swap the stripe price ID for the new plan's vendor (stripe) ID on the email subscription item, keep all
            # other items the same
            price = (
                new_plan.vendor_id
                if item.vendor_plan_id == previous_plan.vendor_id
                else item.vendor_plan_id
            )
            upcoming_items.append(
                {
                    "id": item.id,
                    "price": price,
                }
            )

autumn lotus Sep 18, 2024, 5:31 PM

#

why are you passing any upcoming items though?

#

Like what is your goal, what are you previewing?

terse olive Sep 18, 2024, 5:32 PM

#

we are previewing what their price would be if they upgrade one of their subscription items

autumn lotus Sep 18, 2024, 5:33 PM

#

Gotcha. Then there would be no proration. If the amount isn't what you'd expect you likely have an already pending InvoiceItem, some coupon or something else.

terse olive Sep 18, 2024, 5:34 PM

#

is there any way for us to diagnose what caused the difference in this case?

#

I have a specific subscription id that I'm investigating

autumn lotus Sep 18, 2024, 5:35 PM

#

What I recommend is: dump the raw JSON you get back to a file and then carefully read each element in the lines.data array to pinpoint what doesn't match your expectations

#

terse olive Sep 18, 2024, 5:36 PM

#

it's not an issue that i can reproduce here. do you have access to GET logs that occurred during Aug 5th 2024?

autumn lotus Sep 18, 2024, 5:37 PM

#

ah no sorry that's not something I have access to

terse olive Sep 18, 2024, 5:38 PM

#

is there anyone you can bring in that does have access?

autumn lotus Sep 18, 2024, 5:38 PM

#

No, we don't log anything like this so there's no one to pull in

terse olive Sep 18, 2024, 5:39 PM

#

? but you do save GET logs here https://dashboard.stripe.com/workbench/logs?created[gte]=1722536064&created[lte]=1724004864&method[0]=get&object=&direction[0]=self&direction[1]=connect_in

#

or do you not save any GET logs beyond a time window

autumn lotus Sep 18, 2024, 5:40 PM

#

We delete GETs after 30 days. And we never log the response of GET requests even before 30 days.

terse olive Sep 18, 2024, 5:40 PM

#

ah

autumn lotus Sep 18, 2024, 5:41 PM

#

Sadly debugging the upcoming Invoice can be quite tricky. And what I recommend is to store the raw JSON to pinpoint the issue

#higher_invoice-preview