#jefskoa_unexpected

1 messages ¡ Page 1 of 1 (latest)

dense cradleBOT
#

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

📝 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.

rough umbra
#

hello! i can see the previous thread, i'm getting caught up on it now.

#

ok, i can't re-open the old thread but i can keep helping you here. FYI we typically close threads out if they remain inactive for long, but you can always make a new one and it will automatically link the previous thread too.

#

it sounds like we're still at the stage of:

  • the report is working but taking a long time to generate
  • you're wondering if there's a different way to get the same results faster

does that sound right? i also need clarification on what you mean by this, so just repeating the same question asked by the last person helping you, can you explain what you mean by this?

Can anybody verify if we have our assumptions/findings correct for the IIF and QBO integrations?

long jasper
#

We'll just take them one at a time, as this thread / question has a lot to it for us and our current development project. First, is our assumption correct that the QuickBooks download for an IIF file will have all transactions, not just payout info lines similar to what the payouts.summary.1 report delivers.

#

I've got to step away for about 30 minutes but will respond to any questions you have right after that if you can keep the thread open.

rough umbra
#

ok, i see what you're talking about - this is regarding the quickbook report export. my team can generally help around behavior of reporting APIs and things along those lines, but we can't help with the contents of specific reports. for that you're better off reaching out to our support team here:
https://support.stripe.com/

long jasper
#

ok, I'm back, let me catch up w/ your last post a minute.

dense cradleBOT
long jasper
#

I'm good at this point leaving the Stripe->QuickBook integrations Stripe offers alone at this point. I brought that into the prior thread only to try and explain why we need to get Payout summary information from an API.

#

I'd like to continue to examine my options for getting an efficient result from a Stripe API of the payout summary info.

green rover
#

Gotcha. We won't know much about third-party integrations like Quickbooks as such unfortunately..

This is something you'd ought to talk to Quickbooks or the owner for the Quickbooks integrations.
I'm not aware of first party integration for this platform

#

let me double check

long jasper
#

OK, I'm leaving QuickBooks alone for now. I'd like to discuss (from the prior thread) the best way to get a payout summary. I "think" -- thus the question -- there's only one way, and in my testing it took six hours to get the report back.

#

Here's a report ID for a Payout from our SandBox: frr_1RsS9WI1VSC7qNYw2lf7Bj79

green rover
long jasper
#

On my, I did not know that. That could cause us real problems trying to get Payout summaries on a timely basis as no API gives us that same information.

green rover
#

Ah also to correct my above statement, data is refreshed semi-daily not the reports.

long jasper
#

Would we expect less than 6 hours then for reports via the reports API in production?