#Dani Murcia

1 messages · Page 1 of 1 (latest)

warm perchBOT
fringe oyster
#

What kind of connect accounts do you have?

granite granite
#

Standard

fringe oyster
#

Wait are you both together?

granite granite
#

Yes

mossy tangle
#

Yes

granite granite
#

We are building a project together

fringe oyster
#

Ok. Assuming you're doing direct charges?

granite granite
#

we are doing payment intent

fringe oyster
#

Right

granite granite
#

and then a transfer to our account for our application fee

fringe oyster
granite granite
# 
            'amount' => $prices['total'] * 100,
            'currency' => 'eur',
            'customer' => $customer->id,
            'application_fee_amount' => $prices['fee'] * 100,
            //'confirm' => true,
            'transfer_data' => [
                'destination' => $stripeClubAccount,
            ],
            'payment_method' => $customer->default_source,
            'payment_method_types' => ['card'],
            'transfer_group' => $transferGroup,
            'description' => __('Reservation created'),
        ]); ```
fringe oyster
#

Oh you shouldn't do that with standard accounts

#

You should do direct charges

granite granite
#

Ok, but that wouldn't make it possible for us to charge only our fee and that our client will be able to see on his connect dashboard the money right??

#

basically we have a platform where our clients can sell a product and our users can buy that product directly to our client

#

we just want to charge a feee

fringe oyster
#

If you need to use destination charges, then you should use express or custom accounts

mossy tangle
#

And if we had a custom account, we could disable refunds for connect accounts?

fringe oyster
#

So there's no need to disable refunds because connect account doesn't control that at all

granite granite
#

Yes I read that but actually on the connected account our clients can see the refund button even if that money goes to our Stripe account

#

We don´t want that

#

We want our clients to just be able to do refunds from our platform

#

like this we have more control

#

otherwise how can we listen to your refund event when the client clicks the refund button

fringe oyster
#

Use custom accounts then

#

There's no dashboard with custom accounts

granite granite
#

aaahhhh ok

fringe oyster
#

It really locks down what the account holder can do that way

granite granite
#

so they only will see what we want with custom account??

fringe oyster
#

yes

#

Really you should read the connect docs before using connect

#

It's a very feature rich product

warm perchBOT
fringe oyster
granite granite
#

Yes we read that before, the thing is that our base idea was for our client to have the dashboard on Stripe so we wouldn't have to build it ourselfs in our platform and we saw that with Connect Standard works like this plus Fraud and dispute liability is the User that is responsible with custom we loose all that

opal elbow
#

👋 hopping in here since codename_duchess had to head out soon

#

If you use Express then your users will still have a limited Dashboard on Stripe and wouldn't be able to do the refund through it

#

And the fraud/dispute liability stuff wouldn't fall to the standard account in this case still- with destination charges since the funds first go to you the platform is the one who has initial liabilty for chargebacks

granite granite
#

Yes after some tests we've seen that the money is actually going to our account

#

so as you say we would always be due to refund that money to the final user

#

is there a way to listen to this event just out of curiosity?? Like, when the client with a standard account refunds the money and actually goes to ours we could automatically create an event in our code to refund the money to the final user

mossy tangle
#

We really are intermediary between the end user and our customer, the commission that we charge is the one that we do not want to return in any case. We do not want the user(connect) to return our comission to us