#poobear_api

1 messages ยท Page 1 of 1 (latest)

wheat zephyrBOT
#

๐Ÿ‘‹ 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/1288959785643016252

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

high heartBOT
limpid thistle
#

Hi ๐Ÿ‘‹ not that I'm aware of offhand. I believe the field you're referring to is a dashboard-only concept and I'm not familiar with how it's calculated .If you don't see a field (or combination of fields) that add up to the amount shown in the dashboard when you retrieve the balance from the API, then I don't think it's possible to get that detail from the API.

junior coral
#

Hey! Ah, good to know. any workarounds you could think of off the top of your head that would solve for that? Could we use a connect account for refunds instead?

#

i know we can retrieve connected account balances

#

thank you for the quick answer also, appreciated

limpid thistle
#

I'm not sure what you mean by "use a connect account for refunds instead". Can you elaborate on that?

junior coral
#

Sorry - as of now, we would top up that extra refunds amount since refunds would come out of that first, before our payout accounts (we do this because our payout account doesnt support PAD). is there any other intermediary accounts we could route refunds out of (eg. a connect account) so that we would be able to see that balance in api?

seems like a lot of running around - i know

#

eg. refunds coming out of that connect reserved

{
"object": "balance",
"available": [
{
"amount": -XXXX,
"currency": "cad",
"source_types": {
"card": -XXXX
}
},
{
"amount": -XXXXX,
"currency": "usd",
"source_types": {
"card": -XXXXXX
}
}
],
"connect_reserved": [
{
"amount": 0,
"currency": "cad"
},
{
"amount": 0,
"currency": "usd"
}
],
"instant_available": [
{
"amount": XXXXXX,
"currency": "cad",
"source_types": {
"card": XXXXXX
}
}
],
"livemode": true,
"pending": [
{
"amount": XXXXXX,
"currency": "cad",
"source_types": {
"card": XXXXXX
}
},
{
"amount": XXXXXXX,
"currency": "usd",
"source_types": {
"card": XXXXXXX
}
}
]
}

limpid thistle
#

Sorry, I'm having hard time wrapping my head around what you're describing. I think the problem with trying to route refunds out of another account, is that it won't have any context on the payments and payment methods from other accounts.

wheat zephyrBOT
junior coral
#

That's what I'm also unsure of, since we don't really have a choice of where the refund comes out of, other than know that if that Future refunds or disputes or negative balance has a balance, it will hit that first.

low summit
#

Hello! I'm taking over and catching up...

junior coral
#

Thank you for trying, @limpid thistle! ๐Ÿ™

low summit
#

I'm not 100% clear on what your goal is. Can you tell me a bit more about what you're trying to do and what's blocking you?

junior coral
#

Sure! Let me break it down better.

  1. Right now, we fund that Future refunds or disputes or negative balance so that when we perform refunds, the dollar amount comes out of that balance.

1a. We do not want refunds coming out of our payouts, since sometimes that amount isn't equal to the payout and will result in a withdrawal/debit from our destination payout account.

1b. We can't have it draw from the destination payout account because that account doesn't support pre-authorized debits, but banking there is key for our business right now.

  1. I'm building a function that would essentially check to see if there is an available balance in the above mentioned future refunds/disputes account, and then perform the refund if logic allows.

In this logic (the missing piece) though - I have no way of calling an API or check to see what the balance in the Future refunds or disputes or negative balance is. The current /v1/balance API doesn't return that amount.

What I'm looking to solve for is the above missing piece.

low summit
#

Right now, we fund that Future refunds or disputes or negative balance so that when we perform refunds, the dollar amount comes out of that balance.

How do you do this? What specific steps do you take?

junior coral
low summit
#

Oh, okay, that makes more sense. One moment...

#

Are you using Connect?

junior coral
#

Nope

#

open to it

low summit
#

Nah, I just wanted to make sure I understood the situation.

junior coral
#

cool cool - yeah sorry, i know its a weird one

low summit
#

So the good news is that this balance is available in the API. The bad news is that it has to be turned on for your account, and it doesn't seem like it is turned on for you right now. Back to some more good news: all you should need to do is write in to Stripe support and ask them to enable the refund and dispute prefunding balance in the API for your account. After they do that, you should be all set!

junior coral
#

AHHH

#

thats awesome, thankfully already submitted a ticket. gotta love a good feature flag!

thanks a ton @low summit!