#focux-refund-negativebalanceagain

1 messages · Page 1 of 1 (latest)

errant basinBOT
#

Hello! We'll be with you shortly. 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.

trail nymph
#

So now I have a connected account that clearly has funds but still getting this error:

#

This is a screenshot of his dashboard:

image.png
worthy gate
#

Can you share the request id where you got above error

trail nymph
#

Yep, hold on

#

This is it req_iIoGBbDT3WyQ6J

worthy gate
#

The amount you're trying to refund is 26.32

#

You can see the amount

trail nymph
#

Oh I see, he told me that he charged himself $25 twice, to be able to do some refunds

#

But looks like the other $25 haven't been credited yet

#

Do you know how long does it take to do it?

worthy gate
#

Also looks like the total was 26.32, but you transferred 25 to the connect account and kept 1.32 for the platform

#

So not sure why the above refund failed...

#

Let me ask a colleague

#

Actually before I do that can you do 1 thing for me?

trail nymph
#

Ok, I'm doing that

# 
  object: 'balance',
  available: [ { amount: 0, currency: 'usd', source_types: [Object] } ],
  instant_available: [ { amount: 7500, currency: 'usd', source_types: [Object] } ],
  livemode: true,
  pending: [ { amount: 7500, currency: 'usd', source_types: [Object] } ]
}```
worthy gate
#

Hm weird. Yeah honestly not sure. Let me ask a colleague

worthy gate
#

So the issue is you're doing destination charges with Standard accounts. Really you're only supposed to do that with Express and Custom accounts. Standard accounts are meant to go with direct charges. With standard accounts, Stripe owns the loss-liability, so since your connect account's available balance is 0 (shown in the above response object), Stripe would need to cover the refund, so the request just fails. If this were an Express or Custom account, then the request would have succeeded

#

So you'll need to wait until the balance becomes available in the connect acocunt

#

Then the request will succeed

trail nymph
#

Oh I see...

#

So for our use-case, would it be better to use express accounts? Also, how hard it is to migrate from standard to express?

worthy gate
# 
So for our use-case, would it be better to use express accounts?```
Only you can know this since it's your integration. Please use this doc to inform your decision: https://stripe.com/docs/connect/accounts
trail nymph
#

I see, and is it possible to migrate from standard to express account?

worthy gate
#

No you'd need to create a new account

errant basinBOT
grand pagoda
#

focux-refund-negativebalanceagain

trail nymph
#

For ALL the connected accounts that I have?

grand pagoda
#

yes

#

or move off of Destination Charges in the first place

trail nymph
#

If I move off of destination charges, is there another way to keep a fee of my connected accounts transactions? Like, that's the only reason I'm using destination charges for.

grand pagoda
trail nymph
#

Ohhh

#

Okay, so supposing that I use that instead of destination charges, how are refunds going to work in that case?

grand pagoda
#

it's all documented in details on that page

trail nymph
#

Let me check

#

It doesn't say anything about negative balance when refunding

grand pagoda
#

not sure what you mean sorry

trail nymph
#

so how using direct charges solve the initial problem?

grand pagoda
#

the connected account is on the hook for the negative balance, not you and we (Stripe) deal with them directly

trail nymph
#

Ok, so let me see I understood everything:

  1. My first problem was that refunding without balance was erroring instead of creating a negative balance, this still isn't going to work with direct charges.

  2. My second problem was that using destination charges to add balance to the connected account wasn't somehow working when refunding. If I use direct charges, I'm assuming this is going to work.