#connor_api

1 messages ¡ Page 1 of 1 (latest)

flint oakBOT
#

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

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

hoary nimbus
#

Hello
Are you specifically trying to test automatic payouts?

You could use manual payouts and trigger the appropriate webhook events by calling the API if that's easier.

#

I don't beleive there's a way to speed up the automatic payout timing unfortunately.

spiral totem
#

Ah, we will eventually want to use the automatic payouts, but can solve that another day

For manual, does hitting the API like that supersede the 7 day available_on?

hoary nimbus
#

ah wait you're asking about funds settling in your account? My bad, I think I read the question wrong

spiral totem
#

All good, lemme write up a quick overview of the flow to clear things up

#

So, we were on the Charges and Sources APIs and are moving to PaymentIntents. We collect payments on behalf of other connected accounts as a platform account.

Part of that upgrade results in all PaymentIntent charges going to the single Card ledger, as opposed to the two ledgers in the past (bank account and card). So, we need to test end-to-end behavior now, from receiving payment for both card and ACH, all the way through resolving Payouts

That test card definitely seems like a step in the right direction. Is there anything else we should be aware of from a QA and testing standpoint?

hoary nimbus
#

Not that I can think of immediately but we're happy to help in case you come across any confusing behavior when you're testing