#clearlyhope-availability
1 messages ยท Page 1 of 1 (latest)
@narrow hamlet the only way i can think of is to list the balance transactions using the available_on and charges parameters https://stripe.com/docs/api/balance_transactions/list
that's if you want to list all the charges that would have become available on a particular date
if you only want to know when a particular charge will become available, that's pretty easy - expand the https://stripe.com/docs/api/charges/object#charge_object-balance_transaction and it'll be in there
Thanks Alex! The last solution is what I was looking for. How reliable is the available_on field? Like it is pretty much set in stone or is it more of an estimate?
you're only dealing with card payments right?
As opposed to ACH or anything else? Yes only cards.
yep, it's "set in stone" as you put it
Sweet, okay so that being said. If the balance transaction associated with a charge is updated, will that trigger a charge.updated webhook or no?
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
i've personally never heard of a balance transaction being updated - i don't think it can be
yep, pretty sure it can't
What about the status field? It doesnt move from pending to available? https://stripe.com/docs/api/balance_transactions/object#balance_transaction_object-status
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
I dont mean updated by us, but on stripe's side
Like would we receive a charge.updated webhook if the associated balance_transaction object is updated from stripe's side
oh whoops, sorry my bad, you're right, the status of a balance transaction could change.
no you wouldn't receive the charge.updated webhook
because in the charge webhook event, it would only contain the transaction id
if you want the balance transaction to be expanded in the charge object (to include all the other data), you can either expand that field in the response when creating the charge, or else when retrieving the charge
Ok good to know, This was super helpful. Thanks Alex. I had Another question which was kind of related but not sure if you would pefer we create a new thread or If I can ask it here?
we can continue on here ๐
lol thanks
1.) When we initiate a transfer to a connected account is there a "waiting period" in which it stays in the pending balance or does it go straight to the available balance without any wait?
2.) I realize this isnt the "best practice", but our application requires us to store the users balance on our end (since the user can have multiple balances and Stripe connect doesnt actually support that yet). This means that when the user clicks on "payout" in our application we will initiate a transfer to his/her/their stripe account and then initiate a payout right after. Since we dont really use stripe balances, if the payout fails we would want to transfer the funds back into our platform account. All this would be done in a matter of milliseconds since it would be programmatic. Is there an issue with this approach? Its a workaround we have to do since Stripe doesnt support multiple balances per account.
hrm, can you elaborate a bit more on the user can have multiple balances bit?
is this the campaign fundraiser thing?
i could have sworn i spoke to someone about this yesterday
Yes! This is the crowdfunding app. And yes you spoke with me haha. Since each user can have multiple fundraisers at any given point in time, it doesnt make sense to mix up those balances and payouts all into one stripe account. So the only workaround is to keep track of multiple balances in our database, and only transfer the funds once the user manually initiates a payout.
you're planning to do Separate Charges and Transfers (SCT) then?
correct
There isnt a limit currently on campaign length
both platform account and connected accounts are all based in the US?
Yes all U.S.
the reason why i'm asking this is that if the accounts are not based in the US, you can only hold funds up till 90 days, but it's great that you're all in the US
Custom connected accounts? or Express or Standard?
Im using custom accounts
i personally think that you should go with destination charges so that you don't need to trouble yourself with handling transfers separately. If you already have all the data stored on your server for the charges, there's no real difference if the funds are in the connected account balance, or in the platform. Then again, i don't feel very strongly about this
- It depends - if you include the source transaction, then the transfer funds will only be available when the originating source transaction is also available. If you don't include the source transaction then the funds for the transfer are taken out of the platform's available balance -> i strongly discourage this. You're pretty much floating funds which you may not yet have to the connected account. Also, mistakes happen, you may transfer more than what you intend to if you're not using source transaction