#billinghamj
1 messages ยท Page 1 of 1 (latest)
Yes ๐
Cool
Or alternatively, if there's a way to know what caused a charge via the APIs, that'd be v helpful
Go ahead and outline your question here and I'll help if I can
๐
Basically we have ~550 charges, payments for subscription invoices
Some have been triggered by Stripe's internal system, as part of the regular Billing cycling/smart dunning
Some have happened due to the user manually paying via the hosted invoice URL (sent to them via email)
We need to determine which charges were automatic/internal, and which were user-initiated
When looking in the dashboard, I noticed the user-initiated ones have associated logs, but I don't know of any way to query logs - only events
I couldn't see any differences in the data of the charge/payment intent/invoice on the API level
Yep unfortunately this isn't possible via the API as like you said you can't query logs.
There won't be any indicator on the objects themselves
So it's right to say this has to be a support request? Is support able to pull data on our behalf in these sorts of situations?
Also if we ran https://dashboard.stripe.com/ajax/logs with Dashboard cookies a few hundred times (with a related object filter), is that something that would be very much frowned upon, or probably not a big issue?
No Support can't pull data. I can't really recommend scraping the logs though I don't think it is necessarily frowned upon.
Mostly there isn't a good way to determine this right now but I will log a feature request internally that we should have a differentiator here
So what is the "right" way to get something like this if there's a compliance need for it?
Getting someone to manually check each one I guess?
If it was some number that can't practically be done by a person manually, do you know how it'd be handled?
There is no way to really do this right now
That's what I'm saying
Other than a manual check
Sure. Like I said I'll lodge a feature request here as I understand why you want this info
Unfortunately we just don't support this yet
ty