#piercy
fierce solarBOT
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.
plucky venture
Hi there!
You want to test payouts on your own account or on a connected account?
echo flare
Connected account
plucky venture
Can't you set the payout schedule to daily then? https://stripe.com/docs/connect/manage-payout-schedule
echo flare
I have but its still showing the 4th as the next payout date, potentially because its the first payout
acct_1OH7MmPF3AqWxX7b is the account in question
plucky venture
Oh right. Then I recommend asking Stripe support if they can unblock you: https://support.stripe.com/contact
With the API, except changing the payout schedule or making a manual payout, there's nothing you can do.
echo flare
Ok ill drop them an email, thanks
fierce solarBOT
inland coral
What specifically do you need to test? Webhook events that trigger logic?
echo flare
@inland coral Morning, we produce reporting to our customers to assist them in identifying where the payments came from, ie, which product they belonged too or some other information - essentially the information on the transaction but enriched with information from our system that makes sense to them.
as were switching from direct to destination payments, we want to identify how these payouts and the reported transactions per payout will change
We do this by calling the API to get information about the payout
If support refuses to help, because they want me to login to a test connected account, when I am already logged into the platform account, and the test account was just created with random information to get setup and testing, what would be my next step to be able to test this?
As you can appreciate I can't really wait till Monday to do my job..
inland coral
Hmm, trying to think if there's an alternative. What specifc information are you retrieving from the Payout?
echo flare
Its getting the payout, then getting the list of balance transactions to then enrich and return to the customer. We're getting a fair amount of information from the balance transaction expanding customer, transfer, source_transaction and payment_intent
inland coral
What is stopping you from looking at the Balance Transaction objects for destination charges on the account without the Payout?
Like the fields will be exactly the same
You don't need a Payout to understand the potential differences
echo flare
Fair point, it would work for development purposes, but is there really no way to bypass this? It seems absurd that I need to wait a week when using your test bank account. its not like I can pay myself out from test mode, with test cards, and your test bank account
Ill do this to develop the system, but it surprises me theres no alternate option.
inland coral
Yeah I agree it's a bit of a hole right now. Is this a new connected account? That might explain the delay in the payout
echo flare
It is new but thats sort of the point, switching from direct to destination payments is quite a big change. Were having to rework how we handle checkouts, payment intents, all of the stripe fees and a bunch of other scenarios across our application. So, being able to quickly setup and test connected account for various scenarios (and having clean accounts to test specific scenarios) is quite useful.
Support has just suggested to use the test ibans that should yield immediate payouts, currently were using the default test bank account (the one offered when you create the account), so I am going to try this and hopefully it can be quicker. Even if it was tomorrow, at least i can reason with that but pushing back development for a week (especially with christmas holidays approaching), isn't something we can really afford to do.