#Michael Frost

1 messages · Page 1 of 1 (latest)

wind shoreBOT
austere latch
#

Hi there, how can I help?

sudden bridge
#

Hi Jack!

#

On the frontend of our app we wan't to show the current balance of our users and their connected account to them.

#

The reason for this is that the users (sellers) should be able to trigger a refund of a group of sales and see if they have enough founds in the connected account.

#

if a user sells 10 orders worth 10$ each that means he receives a payment of 100$ minus the application fee minus the stripe fees.

#

In case the user wants to refund the the 100$ of 10 orders his balance is not sufficient enough because the balance of the connected account is missing the application and stripe fee.

#

We are able to show the user his balance with stripe.balance.retrieve

#

This would be not sufficient and we would redirect to user to his connected stripe dashboard to balance/overview to Add to balance

#

here he tops up the missing amount of stripe and platform fees to not have a negative balance after the rund.

#

I can see the top up in Future refunds or disputes or negative balance but I don't get it int he stripe.balance.retrieve

#

Do I missunderstand something how the tup up works or the balance?

fluid trellis
#

what type of connected accounts are you using?

sudden bridge
#

type: 'standard',

fluid trellis
#

unfortunately we don't currently return the future refunds or disputes or negative balance via the Balance API

#

that's a Dashboard viewable only balance

sudden bridge
#

Ok.

#

Is there any other way that I can check if the account has enough balance to not go negative when refunding?

fluid trellis
#

you can only use stripe.balance.retrieve

#

the way i would do it is to show the user his current balance, also point him to check / look at the future refunds or disputes or negative balance in his Dashboard and warn him that he may not have sufficient funds for the refund

sudden bridge
#

I see.

fluid trellis
#

but i would still allow the user to make an attempt to refund

#

because there's no way for you to retrieve or know of the balance in the future refunds / disputes / negative balance in the user's account

sudden bridge
#

If the total balance is not sufficient, would the first refunds succeed and when there is not enough balance they would start failing?

fluid trellis
#

are you only accepting card payments?

sudden bridge
#

No, we accept cards, apple pay, google pay, klarna, sofort ...

fluid trellis
#

the way refunds are handled are different between cards and non-cards

#

for non-card refunds though, the attempt to create a refund will simply fail if there's insufficient balance

sudden bridge
#

So i have to keep track of the 10 orders if they were all refunded or not and then try to refund again on a schedule basis, the ones that failed?

fluid trellis
#

are you using Direct Charges?

sudden bridge
#

Where do I see this?

fluid trellis
#

do you have a PaymentIntent id that you can share for me to take a look?

sudden bridge
#

Sure, this is a test mode connected account pi: pi_3Mbnox2aLYr3wpnw1gY9GKwL

fluid trellis
#

so you are using Direct Charges, I'm a bit baffled as to why you need to keep track of all of that?

#

the user has access to the Stripe Dashboard, they can refund those orders via the Stripe Dashboard as well

sudden bridge
#

The items being sold are tickets to attend events IRL.

#

Our users can create multiple events with multiple ticket sales.

#

Our goal is for the user to be able to refund all tickets of an event.

fluid trellis
#

i get that, but why can't they do it via the Stripe Dashboard? it seems that allowing the user to manage it themselves would make things easier for you as well

sudden bridge
#

Well, our though is that if the users sells 1000 tickets for 4 different events he should be able to select one of the events on our app and then be able to refund only the tickets assigned to that event with one click.

#

In the dashboard he would need to filter the payments by some meta data concerning the event and then select all and then refund. right?

fluid trellis
#

yeah, that's how i would go about it via the Dashboard