#lachiu_best-practices
full flameBOT
👋 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/1465325695843700922
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- lachiu_webhooks, 4 days ago, 7 messages
lucid gazelle
but what's the charge has to do with the usage record?
I'm not sure I understand
would you mind elaborating?
frosty belfry
Usage records are stacked into the next invoice, right
lucid gazelle
correct
frosty belfry
We give our customers an invoice with this amount
We are now blindly matching the price of these usage records to what we think we should charge and what is actually charged.
As in, Stripe tells us there was a charge of 5 euros to their bank account but we have accumulated 6 euros of costs that we should have charged by using these usage records.
It obviously doesn't happen too often, but it happens and it's tedious to manually track each usage record to each cost we charge.
We can obviously track the id we get from creating the usage record and store it somewhere internally, but it would be easier if we could do that within Stripe. We feel like the metadata would solve this.
lucid gazelle
As in, Stripe tells us there was a charge of 5 euros to their bank account but we have accumulated 6 euros of costs that we should have charged by using these usage records.
maybe the timestamp of the usage record is outside of the current subscription's period
frosty belfry
That is indeed one of the issues we encountered.
Also system downtime, on our side.
lucid gazelle
so you should just add it to the next cycle
frosty belfry
Sure, but that doesn't solve our problem.
So to get back to my original problem, we can setup our own system but would prefer not to. Documentation shows no option for metadata on these meters or usage records. Is that missing or is that not possible?
lucid gazelle
unfortunately we don't have a way to store metadata on usage records
frosty belfry
Alright thanks