#rafaelbaptista - Express Refunds

1 messages · Page 1 of 1 (latest)

cunning bough
#

Hi 👋

#

The transfer is returned to the connect account's Stripe balance. That balance is what gets paid out on the scheduled payout.

late lion
#

what you mean returned to the connected account, that parameter says that is to recover the funds from the connected account

cunning bough
#

Sorry, platform

late lion
#

from what i understand,
when a refund is made the money is first removed from the platform

#

and that parameter from what i understand what basically does is do the chargeback to get that money back from the connected account

#

So what you meant is that the chargeback will only reflet on the next payout of the connected account?

cunning bough
#

If by "reflect" you mean show up on the list of transactions associated with a given payout, then yes. The funds will be withdrawn from their Stripe account balance as soon as you initiate the reverasal

late lion
#

ahh, so as soon as the refund is processed if that flag is set to true the platform receives that money right away?

#

but if for example the connected account dont have balance?

cunning bough
late lion
#

i dont know if i express myself right but i'm doing the reversal manually, i'm doing by setting the reverse_transfer to true

late lion
cunning bough
#

On a Refund request, correct?

late lion
#

yes

cunning bough
late lion
#

i already read that doc but dont have any information on how stripe procceds if the connected account dont have balance

#

will only the value of the chargeback be paid by the connected account on the next payout?

cunning bough
#

If the connect account has a 0 balance and you process a refund it will debit the connect account balance to make it negative. Then Stripe will attempt to debit the connect account's external bank account to bring the balance back to 0

late lion
#

ok, thanks for clarifying
regarding the parameter refund_application_fee, i also set that to true .. but when i made the partial refund seems that it had no effect on the final value

#

can you please confirm?

#

this is the charge id : ch_3KuaYcCRI4H2eNZZ060CnkvR

cunning bough
#

There is no application fee on this charge.

late lion
#

yap, thats why .. thanks for the help

#

have another question regarding the charges
when a charge is made using destination charges the charge is create on the platform and then is create a py_ charge for the connected account.

That py_ charge is not getting any data like checkoutid, description that i passed to the charge, any way of the py_ charge also gets all the info that i pass

cunning bough
#

Do you have examples of the Charge ch_ and the py_ objects I could review?

late lion
#

yap 1 sec and i give you the id

#

ch_3KuaYcCRI4H2eNZZ060CnkvR
py_1KuaYd2EN2fYHAOBpBSeA4C8

late lion
# cunning bough There is no application fee on this charge.

regarding this, i remembered i do have an application fee . That application fee is capped from the original value so the connected account only gets the value without the fees,
so on this case how the fees are address? because from what i'm seeing for every total refund the connected account will be charged the amountwithfee + the fee again

cunning bough
#

However your integration is calculating and collecting application fees, it is not using the application_fee parameter, which is the only one Stripe knows about

late lion
#

alright so nothing that we can do there, regarding the charges you are able to find how we can do it?

cunning bough
#

regarding the charges you are able to find how we can do it

#

What are you trying to do?

late lion
cunning bough
#

The py_ is a payment, not a charge. So it does not have fields description available

late lion
#

so its not possible to pass some of the attributes of the charge like the metada,.. to the py_?

cunning bough
#

I do not think this is possible, no.

late lion
#

ok, no problem .. regarding the onboard of connected express accounts that already have an account or may not have an account should i have diffent approachs when onboarding?

cunning bough
#

These users will either A) have an existing Stripe Account or B) not. Those are the only two options. I think it makes sense to take the same approach in both cases and create new accounts.

late lion
#

right now our system i think is using the oauth legacy, its that still correct to use?

hoary jewel
#

👋 Hopping in since snufkin has to head out

late lion
#

But stripe still offers support for oauth onboarding auth right?

#

I'll try to migrate th onboarding to accounts but still want to know if i'm unable to, if the oauth is supported

hoary jewel
#

You're still able to onboarding accounts with oauth, it's just not something we recommend for new users who are just starting out

late lion
#

alright, in the case that i want to keep the oauth for the current time, i only need need o add oauth/express in order to onboard the express accounts right?

hoary jewel
#

correct

late lion
#

or i have also to create the account before like is saying on step 2 of that link

hoary jewel
#

Yes, the new onboarding flow would require a lot of changes from the oauth flow - you'd need to create an account up front and generate an account link to redirect your user to

late lion
#

to do it i only need to
$stripe->accounts->create(['type' => 'express']);
and then generate the link, right?

but in the case of the person already have an stripe account this will associate the previous with this new one?

hoary jewel
#

Yes, the two accounts will be associated (in that the user can log in to Stripe and be able to see both accounts in their dropdown in the top left hand corner)

late lion
#

alright sounds good, thanks for clarifying