#nickdnk-reporting
gaunt current
Hi! A topup is when you add funds to your Stripe balance, a payout is when you send money to your bank account.
And it's possible to have a negative payout, as explained here: https://stripe.com/docs/payouts#negative-payouts
gilded saddle
Yes, I know
But I have people adding to their balance without any topups showing up
in two cases: automatic withdrawals and manual payouts to Stripe's bank
I am assuming topups are for some kind of automatic debiting system that we don't use or support?
(in our country, Denmark)
I understand the withdrawals are negative payouts, and I got that under control
velvet chasm
Hey there 👋 topups are also unique to US platforms, so it might be expected that you're not seeing them. Do you have an example of one of these objects that I can take a closer look at on my side?
gilded saddle
Okay, which object exactly do you mean?
And fine if we don't have topups
One less thing I have to worry about
velvet chasm
The balance_transfer_inbound object that you mentioned.
velvet chasm
Ah gotcha, sorry
gilded saddle
Because they look very similar to what I'm seeing as the way you add funds to your account balance via bank transfer
on the dash
I mean it's almost the same process
So I was confused what they were as I was not seeing them
velvet chasm
Apologies for the confusion on my end as well, it's the first time I've seen the term balance_transfer_inbound and had to do some digging to find anything on it. Although it's not much to go on, below is a description of those objects that I found.
Funds moving into a balance (e.g. Issuing balance) from another balance where the presentment currency is different from the settled currency (e.g. Stripe balance).
full mantle
Hey there @gilded saddle -- re-opening this
gilded saddle
Alright
Let me get the object I'm talking about so you can inspect
hold on
po_1KFPjIIXmFfWZ4Evp3KZUlof
This comes out in another automatic payment as a balance_transfer_inbound and changes a future automatic payout's amount ,as expected
But all the transfers are DKK and so is the Stripe account
So going back to: Funds moving into a balance (e.g. Issuing balance) from another balance where the presentment currency is different from the settled currency (e.g. Stripe balance).
That seems to not be the case here
po_1KOXiXIXmFfWZ4EvMuvkLGxE is the automatic payout affected by that payout, just in case
full mantle
I'm having trouble understanding exactly what you need help with, to be honest
There are multiple ways to move funds into and out of your stripe balance: payouts, top-ups, bank account debits to cover negative balances, transfers etc
But for help with these kinds of balance movements and payout investigations, this is really something better addressed by support, so I suggest you reach out here with a detailed explanation and clear question about what you need help with: https://support.stripe.com/contact
gilded saddle
I'm asking how "Funds moving into a balance (e.g. Issuing balance) from another balance where the presentment currency is different from the settled currency (e.g. Stripe balance)." can be true when all transactions I'm looking at are in the same currency.
But alright
full mantle
Yea, ok, I have little to no understanding of how that works. I think we do some auto-FX when that kind of balance conversion happens, but this is definitely a question support is better suited to answer
gilded saddle
Alright, fair enough
With that being said, I think I found a bug in the report run export
Hold on let me summarize it
If you take a look at req_N8xvXrJcQeqDXv you will see I requested the source_id column, which is supposed to indicate the source of the transaction. However, the export for the payout (po_1KOXiXIXmFfWZ4EvMuvkLGxE) I get contains the manual bank transfer with ID po_1KFPjIIXmFfWZ4Evp3KZUlof - but the row for that column in the file for source_id is emty. It looks like this:
,"Transferring funds from future refunds or disputes to cover a negative Stripe balance.","other_adjustment","60205.66","0.00","60205.66","2022-01-10 05:21:12",,"dkk",,"txn_1KGGJhIXmFfWZ4EvqFn3pGUK",
Where I would expect it to look like this:
,"Transferring funds from future refunds or disputes to cover a negative Stripe balance.","other_adjustment","60205.66","0.00","60205.66","2022-01-10 05:21:12",,"dkk","po_1KFPjIIXmFfWZ4Evp3KZUlof","txn_1KGGJhIXmFfWZ4EvqFn3pGUK",
Specifically, the source ID is missing in the third column from the right (note that the most-right column is empty; trailing comma)
If this is outside the scope of development I can report it to support if you want. Just wanted your take on it first.
And yes, this field is normally populated with po_xx for source ID. It works for the export of po_1EMQuPIFDslEWhBAi6l9uxvf
Which contains failed payouts that were refunded
full mantle
Looking at this, but as I said this is unfamiliar territory. Trying to get another set of eyes to help understand whether we'd expect that to be populated or not. I suspect this is going to be best handled via a detailed explanation to support@stripe.com as I mentioned. But looking a bit longer.
gilded saddle
Yes I know I'm right on the edge of the support capabilities here on Discord
full mantle
Yea, since it doesn't deal with API/client integration details it's outside what most of us are deeply familiar with.
Yes, please write in describing this. Please make sure to include the request to produce (as above) & actual result CSV with the missing expected info (you can highlight excerpts in the email, eg). This will be allow the folks to are more expert in reporting help either explain to you or investigate if they consider it a bug too.
full mantle
Thank you!
