#driesvints-checkout-invoice
1 messages ยท Page 1 of 1 (latest)
Hello! We'll be with you shortly. 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.
- driesvints, 1 hour ago, 18 messages
- driesvints, 4 hours ago, 43 messages
driesvints-checkout-invoice
@fast cipher do you have a concrete example Event id that is less than 24 hours old that I can look at? If not can you first reproduce this?
Okay I was testing in parallel I don't think the advice my colleague gave you works at all in this case. Are you using a Subscription in this flow @fast cipher ?
Hi @vocal jolt I got an example for you: evt_1O9skm4MjUVeuXeN8YhI9MRC
yes I am. It's a subscription checkout flow
Okay then set metadata on the Subscription so that you can read it off of subscription_details on the Invoice
you even seem to be doing that already!
hmm I seem to have a workbench issue now..
I can't scroll the "event data"
It just scrolls the main Stripe dashboard page. The content of event data stays fixed
likely a Workbench bug. This is a secret feature you're a part of so you should be careful discussing this publicly. I think you have some insider program where you can report those bugs to the team
but you're a developer so you can look up the Event in the API or on the Event page and such right?
I removed the screenshot. Good note ๐
ah the event section allows me to scroll thanks
yeah I think I'm in a github repo somewhere. I'll look it up later
yeah sorry I know it's a pain to have to split your feedback like that ๐ฆ
I'll see if I can repro on my own and push on the product team but I don't use Workbench yet
ah that might be a browser bug. I'm a Firefox user and I filed a few bugs for Stripe Shell recently too ๐
the worst lol
Okay then set metadata on the Subscription so that you can read it off of subscription_details on the Invoice
So there's nothing native in theinvoice.payment_action_requiredevent to know it's coming from a Stripe Checkout session?
Correct there is not. We have dozens of objects that chain to each other through others. If we made information available about every possible parent you'd have dozens of properties making the API unreadable
We've debated for a while to have some kind of "origin" hash that would have a list of parent object(s)
but for example what if you use PaymentLinks? Do you use that plink_123? The Checkout Session cs_test_123? Both? It is quite messy to design right ๐ฆ
We've done it on one API (on InvoiceItem) and it hasn't scaled well
I must say I haven't dug into paymentlinks a lot yet