#davidlfox_api
karmic rapidsBOT
👋 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/1484555341227364455
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
river star
Hello, unfortunately there isn't a programmatic way to get around that restriction. If you can get logged in in some way, you can try reaching out to our support team: https://support.stripe.com/?contact=true
zinc heron
stripe support is unresponsive for well over 24 hours. ive asked several times to escalate this issue because ive been blocked for days
theyve provided zero possible solutions, not even an explanation for the delay
i wouldnt be on discord if i werent desperate. im close to scouring my LinkedIn connections to see who im connected to at stripe to figure out a way to get a response, escalation, or solution
river star
This server can't help with account setup and can't push on support tickets, so I understand that pushing on support hasn't been productive but I do think it is the best path that is available at the moment.
river star
We are API support at Stripe, we help users write their API code when building their Stripe integrations.
zinc heron
got it--as ive been working in sandbox, i have yet another support ticket open with garbage, non-technical responses and zero hint at escalating. should i open another ticket here for that? that is definitely an API/CLI-related issue
river star
Happy to try to help with that issue. Can you tell me more about what you are running in to there?
zinc heron
my scenario is:
- all my users can be Stripe-Connect onboarded and connect something like a checking account
- user A wants to invoice user B for money
- user A creates an invoice in my platform
- user B clicks a "pay" button in my platform
- I want to charge user B
- Then transfer to user A
my problem is money is always sitting in connect_reserved instead of my platform's available funds to transfer so i cant fulfill step 5
before i test a bunch of UI in my platform dev environment, i have asked stripe for cli commands to simulate the exact steps (or an alternative) so i can prove this works.
their latest response was something like:
"oh that will happen when your account is new, but it wont happen in production"
which i find to be ridiculous claiming that sandbox versus production has different feature parity
i need to see it work in sandbox before i release this to my customers, so i dont look like a fool
my whole reason for going down the production path (my original request in this thread) is so i can test in production with my own bank accounts, because stripe refuses to give me any kind of technical response
river star
Are you using this private preview functionality to set those reserves? I hate to have to pass on this too but we're only familiar with Stripe's public APIs, so support is the team for private preview questions.
If this isn't preview functionality, can you try sending me the ID of a request (req_123) from a time step 5 failed?
zinc heron
i dont know what private preview functionality is so im going to say no. let me see if i can dig up a request id
river star
Sorry to put it in better terms: are you using the functionality from that doc? The doc has a private preview tag, we have this doc explaining the term but it is similar to a beta.
river star
Have you considered using the transfer_availability parameter when creating your transfer? Basically, you can specify that the transfer is being funded by a specific payment, so Stripe waits until the funds for that specific payment land before transferring them.
https://docs.stripe.com/connect/separate-charges-and-transfers?platform=web&ui=stripe-hosted#transfer-availability
zinc heron
oh my god did that actually work?
i didnt log a request id in my test, but
charge: ch_3TD4sNBLpvoMKCk80djNRrbS
transfer: tr_3TD4sNBLpvoMKCk80vpKgFFh
it shows up as a positive transfer in both accounts
sender: https://dashboard.stripe.com/acct_1RXlkVBLpvoMKCk8/test/connect/accounts/acct_1T7QTFBWPR821iiR/activity
recipient:
https://dashboard.stripe.com/acct_1RXlkVBLpvoMKCk8/test/connect/accounts/acct_1T7QTHBH27edtTFv/activity
is that by design?
river star
I am actually surprised the sender account has some kind of payment record, it looks like that charge was from a payment intent directly on your platform account. I can't see dashboards by default but can request access to take a look
karmic rapidsBOT
Hello @zinc heron, we have sent you a direct message, please check it at https://discord.com/channels/@me/1484575824542826576
- 🔗 The message has instructions on how to grant read and write access to your Stripe Dashboard for our Developer Support team, in order to help you more effectively.
river star
Thank you, that is strange, it looks like the transfers tab for both of those shows the exact same transfers. When I click the "view all transfers" it goes to a transfers page that does properly filter transfers for each connected account.
https://dashboard.stripe.com/acct_1RXlkVBLpvoMKCk8/test/connect/transfers?destination=acct_1T7QTFBWPR821iiR
https://dashboard.stripe.com/acct_1RXlkVBLpvoMKCk8/test/connect/transfers?destination=acct_1T7QTHBH27edtTFv
So I think this is a UI bug on that page. Seeing if I see this on my own account.
zinc heron
yeah its the identical ...FFh transfer id on both accounts. i dont necessarily hate it, but ill defer to you if it lines up on the backend and stripe's data is all in order
im happier just because its the first successful test in over a week of throwing #$%! at the wall to see what sticks, so i think this proves my scenario so far.
but now the $64,000 question--when do the imaginary funds show as cleared in the recipient account in sandbox? is there some artificial delay built in?
river star
Yep, everything looks to be fine in terms of the transfers actually having data for the connected account they were sent to. I will file a bug report to fix that UI.
And yep there is an artificial delay built into test mode by default. If you retrieve the charge and expand latest_charge.balance_transaction there is an available_on field in the expanded object that indicates when the funds will be available. In test mode I think the default is 2 days.
Though we do have these test cards that skip that wait time and make the funds available immediately.
zinc heron
these are effectively ACH transfers though, which more matches my scenario. the scenario is:
- user B (an actor) receives a paper check and owes 10% to their agent (user A)
- user B deposits their check in their business/personal checking (onboarded to Stripe Connect)
- agent (user A) creates an invoice for the 10% because theyre aware of the acting job being done
- actor (user B) clicks pay button and TalentFlow (my platform) facilitates the transfer, grossing up the fees so we pay nothing, and just pass Stripe fees to the sender
i ran
stripe charges retrieve ch_3TD4sNBLpvoMKCk80djNRrbS
and i dont see latest_charge or "available_on
river star
latest_charge is something on the payment intent. If you are looking at the charge you just need to expand its balance_transaction. With the CLI that is the -e flag https://docs.stripe.com/cli/get#get-expand
zinc heron
the payment_intent just shows latest_charge as the same charge id i used.
i did grab the balance_transaction (txn_3TD4sNBLpvoMKCk804a0NyCg) from the charge
but its available_on timestamp (1774569600) is a couple days ago....huh?
im an idiot...timestamp is in the future 1774569600 == Friday, March 27, 2026 at 12:00:00 AM
7 days...is there any way to tighten that up (id love it to be 0 minutes for the sake of testing) with the ACH scenario versus using a card
serene briar
👋 Hi David, changing of the guard. I'll be taking over watch of the server, just getting caught up on your thread.
zinc heron
no sweat. this has already been more productive in an hour than a week with stripe email/phone/chat support
serene briar
Do you have any familiarity with our Test Clocks? https://docs.stripe.com/api/test_clocks
Really handy for quickly testing scenarios that would normally play out over an extended period.
zinc heron
loosely--how would i "attach" a clock in this use case?
serene briar
https://docs.stripe.com/api/customers/object#customer_object-test_clock
Essentially you create the test-clock and then pass in the test_clock id at customer creation time.
Then transactions associated with the customer follow the test-clock. Our general API documentation focus' primarily on using them to test Subscription scenarios but they can be used outside that context. https://docs.stripe.com/billing/testing/test-clocks/api-advanced-usage?dashboard-or-api=api
zinc heron
ok so i have to create the entire customer with a test clock to emulate this. is there a way to attach it to an existing customer?
serene briar
Unfortunately not, the test clock id has to be provided at customer creation, so you'd have to walk through the test flow again.
We have some feedback logged requesting that functionality that I can add your vote to (i'd personally love to see this as well)
river star
@zinc heron quick correction, test clocks won't speed up simulated settlement time. As best we can tell there isn't currently a way to speed this up, so I don't think there is a good way to test this specific use-case specifically. You can test ACH payments, and separately test with the bypass pending balance cards to test what happens when they settle, but there isn't a good way to test both together. I will file a feature request for this but can't promise if/when it will get added.