#caitlin-short_docs
autumn apexBOT
đź‘‹ 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/1352411081670398062
đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- caitlin-short_docs, 1 day ago, 7 messages
cold coral
Hi! In the context of your question, it should fire when there are changes to "... the new updated Stripe balance and Issuing balance after the balance transfer".
tacit valve
Hi! Thanks, but balance transfer - does this only relate to top ups and withdrawals - or is there technically a balance transfer after every card transaction or authorization
cold coral
It would not reflect 'withdrawals' in your model, no.
So you're trying to build an accumulator that should represent the balance for a card, based on ins and outs?
tacit valve
I currently display the current issuing balance, which I retrieve from Stripe each time. However, I want to track the starting and ending balances within a given time frame to ensure that all credits and debits reconcile.
Additionally, I'm working on generating statements, which requires determining the starting and ending balances for a specified period.
cold coral
Ahhh ok, gotcha.
So you could in theory use https://docs.stripe.com/api/issuing/transactions/list and ... something to list the top-ups? and then combine that?
Or you could just listen to the whole spread of Issuing Events on your Connect Webhook and process them as they come in.
tacit valve
Yes we do process all transaction events, top ups and withdrawals
I am just trying to avoid having to get the entire history of top ups and withdrawals and then all the transactions to do the math every time I need to generate a statement to get the starting balance and end balance.
Just trying to figure out the best approach to track it on my end.
So I was thinking I need to list ot the balance.available event just not sure thats the right event or not
cold coral
You can only get events back 30 days so I don't think that's going to work.
Are you looking to make a (or multiple) API request(s) to gather up the data, or would you prefer that it already exists in your systems?
tacit valve
I do store it in my syste (all transactions, top ups, withdrawals)
However I would prefer to get the data from stripe regarding the balance on a given date
but it seems that is not possible ?
cold coral
You can retrieve the balance, but you cannot (as far as I know) ask for the balance on a particular date (except the date on which you ask for it).
tacit valve
Ok thanks
Maybe I just need to run a job that at the start of each day retrieves the issuing balance and store this history
cold coral
How are you planning to encapsulate the 'period'? Is everyone's statement period the same, or is each person's different?
*statement period
I suspect you'll want to have a Connect Webhook set up to listen to all of these:
issuing_dispute.closed
-> Occurs whenever a dispute is won, lost or expired.
issuing_dispute.created
-> Occurs whenever a dispute is created.
issuing_dispute.funds_reinstated
-> Occurs whenever funds are transferred to your Issuing balance (usually associated with won dispute status).
issuing_dispute.submitted
-> Occurs whenever a dispute is submitted.
issuing_dispute.updated
-> Occurs whenever a dispute is updated.
issuing_transaction.created
-> Occurs whenever an issuing transaction is created.
issuing_transaction.updated
-> Occurs whenever an issuing transaction is updated.
topup.created
-> Occurs whenever a top-up is created. Only relevant for Issuing-only integrations.
topup.canceled
-> Occurs whenever a top-up is canceled.
topup.failed
-> Occurs whenever a top-up fails.
topup.reversed
-> Occurs whenever a top-up is reversed.
topup.succeeded
-> Occurs whenever a top-up succeeds.
balance_transfer.created
-> New balance transfer API—transfer funds from acquiring to issuing
balance.available
-> Reflects the new updated Stripe balance and Issuing balance after the balance transfer
...and from there, adjust your local 'transactions' based on those events. You could then retrieve the actual available balance on the statement end date (which serves as your open/close balance) and go from there - does that make sense?
tacit valve
Can you tell me what defines a balance transfer? Wouldn’t that only be if we were transferring funds from our platform balance to the connected account balance
Yes we do listen to those events today!
With the exception of balance transfers
cold coral
I actually don't know what that word means in context here, but I assume it would fire any time the available balance changes in either the Stripe or Issuing balance.
tacit valve
Oh ok because balance transfers API is if we were moving money from the platform to the connected account from my understanding which we do not do
Our connected accounts can top up their issuing balance directly from an account they link or through external funding option which is where they can send a wire directly to the issuing balance account
cold coral
Cool. I would recommend listening to that event then, as it should tell you about the issuing balance too.