#hectopascal - balance transactions created

1 messages · Page 1 of 1 (latest)

eternal pelican
#

Good question. Checking in to it. To clarify, you are still looking for all transactions that are available after a certain point, but by using the created filter?

rancid zephyr
#

yes

eternal pelican
#

Gotcha. And to step back a bit more, what is the overarching goal? To see all balance transactions related to a certain payout or something?

rancid zephyr
#

I work at a company that provides financial analysis for our users, and some of them use stripe. we need to pull their balance transactions based on certain time ranges and we want to depend on the available_on timestamp

grim python
#

Hi @rancid zephyr 👋 taking over for Pompey. The time between created and available_on is going to vary depending on what the Balance Transaction type is, along with the payment methods used (if applicable). Unfortunately there's not really a good way to find the range of time in which these two things exist.

I would recommend pulling these two things separately, if possible

rancid zephyr
#

I was hoping for something like a maximum range, like I know that it takes at most 3 business days for funds for AU BECS debit to become available, for example. if I made my maximum range for my created API request to go two weeks beyond where I needed it, would that be enough

grim python
#

It varies too widely. length of time it takes funds to become available depend on the account's state. If the account is not verified, or if we are asking for KYC information, funds might not become available until the needed verification info is provided.

Setting it to 2 weeks seems like I could reasonably capture most created --> available_on transitions, but I wouldn't build anything that relies on that being true all the time