#jefskoa_api
lapis peakBOT
đ 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/1402277326305235004
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
fossil geode
No, there is no API that can replace that report result directly. Depending on what you need, you might be able to recreate it from the balance transactions as you mention, but it would be a complex calculation with a lots of API requests and I wouldn't suggest doing that. Better to leverage the report.
dusty depot
Got it. The next struggle / challenge I've come across then is getting payout information from our sandbox account. We have automated payouts that I can query in the Stripe CLI. However, when I request needed report in our sandbox, it always relays status pending, it does not complete. I read where that may be a limitation in the sandbox environments but was hoping I read that wrong.
fossil geode
I read where that may be a limitation in the sandbox environments but was hoping I read that wrong.
Can you share where you found this?
dusty depot
From this URL: https://docs.stripe.com/api/reporting/report_run/list, there's a section titled Report Types. I began to research this after requesting the report in the Stripe CLI and upon querying the report status to get the completed URL, it returned "Pending" until I gave up after an hour.
I should have clarified, the report request for the payout was in a Sandbox environment.
fossil geode
and will error when queried without a live key
I'd expect anything that returned a run ID to be something that can work, based on this
if it were not support in test/sandbox, i would expect the creation request to fail/error indicating that issue
dusty depot
Yes, I had the run ID after the API request for the report. But it never returned a success when querying for report status. It did not fail though, it just continued to return a pending status. This would seem to make it difficult to fully test in a sandbox: a payout, webhook receipt of a payout complete, then get the payout summary info needed via the report run.
lapis peakBOT
fossil geode
Do you have an example report run ID?
dusty depot
Yep, let me get that info for you. I closed the session so I'll fire one up again and get it for you along w/ any other info you need. Sure appreciate the assist/support.
I stand corrected. This morning the status for the report run ID I was checking yesterday now shows success. I will query the URL to get report content. Is there a way to request an API to just provide the payout summary directly without having to run a report/check status/retrieve URL content?
astral dock
Unfortunatley not, that concept is a report only one. You can use the API to get the transactions related to a payout and calculate those things yourself but there isn't a summary object in the API itself
dusty depot
I realize we are using a Sandbox for app development, so response times aren't expected to be production results. But for testing the functionality we need, our app would have queried for a report completion for over six hours. Any suggestions on a way to (1) get our needed data differently or (2) get better response time so we can have efficient testing of our integration app?
astral dock
Can you tell me more about the test you are running here? Are you running some test transactions, making a payout, and then are trying to confirm that the transactions are in the report properly?
dusty depot
We are working on a integration app with QuickBooks for our users. For some reason yet known to me, the Stripe supplied integration won't work. I'm in charge of building an integration from a Stripe payout complete, using a web hook to get the needed summary information into our proprietary PMS (Property Management System) and then allow users to upload/export to QuickBooks (deep sigh here). So, yes, creating transactions in our sandbox and then awaiting auto payouts as the Stripe CLI won't get our payout for a manual payout. Our webhook to the Payout can then use the payoutid. From what I'm learning, the only way then to get the info we need is to request the payout.summary.1 report, wait for it to be completed, then consume the report output. We aren't confirming the transactions as much as we need the summary of charges/refunds/fees for an individual payout.
astral dock
the Stripe supplied integration won't work
Can you tell me more about what the Stripe supplied thing is here and how it isn't working? Do we have any docs on this component?
And the info you need to supply is the full info from the summary report I assume?
dusty depot
Give me a few moments, I'm on a call w/ our Finance team now trying to understand why the supplied integration won't work. Thanks for being patient.
Let me speak to the IIF download first. I'm being told that the Stripe->QuickBooks IIF creation prepares everything, including revenue, expenses, etc. That would duplicate the Export we do from our PMS. If the IIF creation was only for the Payout, we'd be good for the QuickBooks Desktop piece.
Working on why the Stripe->QuickBooks Online integration won't work.
lapis peakBOT
dusty depot
On the QBO integration our Finance team did try to the integrator supplier. The issue was that for a Payout it sent QBO every transactions so reconciliation was a problem. We could have thousands of Stripe charges/refunds in a Payout at the detail level that would then hit QBO individually. That's why we have to build our own ingratiation with the payout.summary.1 info. Can anybody verify if we have our assumptions/findings correct for the IIF and QBO integrations? I would LOVE to NOT have to do our custom integration/coding.
quick fiber