#linq2-separate-charges

1 messages · Page 1 of 1 (latest)

serene latch
#

@tender kayak hello!

tender kayak
#

hello

serene latch
#

The transfer is instant by default

tender kayak
#

currently we have it so the payment transfers from the main account instantly to the connected account, is this possible for multiple connect accounts?

serene latch
#

The thing is that you don't get the funds from the payment immediately. So you have to "float the money" as the platform

#

Is that what you are trying to do?

tender kayak
#

this comments part

#

Create a second Transfer to another connected account

serene latch
#

All Transfers are instant though, that's already how it works

tender kayak
#

right so it isn't going to store it and transfer it later as the comments suggest?

serene latch
#

what does that mean?

#

you say "as the comments suggest" but which comment? Sorry to ask again but can you be a lot more specific about the exact flow of funds you want to achieve?

tender kayak
#

https://stripe.com/docs/connect/charges-transfers in the php code, it says

// Create a Transfer to a connected account (later):
$transfer = \Stripe\Transfer::create([
  'amount' => 7000,
  'currency' => 'gbp',
  'destination' => '{{CONNECTED_STRIPE_ACCOUNT_ID}}',
  'transfer_group' => '{ORDER10}',
]);

// Create a second Transfer to another connected account (later):
$transfer = \Stripe\Transfer::create([
  'amount' => 2000,
  'currency' => 'gbp',
  'destination' => '{{OTHER_CONNECTED_STRIPE_ACCOUNT_ID}}',
  'transfer_group' => '{ORDER10}',
]);```

what does (later) : mean
serene latch
#

it's what I was explaining above

#

If you create a $10 charge right now, the funds are not available for 2 days in the US

#

So if you then transfer $4 to a connected account immediately, that money has to come from somewhere, which would be your own account's balance

#

you'd effectively be floating the money for all your connected accounts, while you wait for the money for the original payment to settle

#

So the code usually recommends creating the Transfer later/separately as most businesses who use this funds flow handle their own reconciliation and payout schedule

#

is that what you want to do? Or do you want it to behave exactly like a normal destination charge, where the Transfer is created immediately but the funds are "pending" too

tender kayak
#

right so If we have the payout set to lets say Mondays, the payment shows in the main account, the money that should go to the connected accounts is also showing in the connect accounts, but isn't available to payout until the following payout or the money has cleared

#

currently in our development, In test i can send a test payment, it goes to the main account, instant transfers the amount required to the connect account (or O can see it in the connect account physical or not) all I want to make sure is if a users buys from 2 partners, the money gets distributed correctly the same way except it is an extra connect account based on these documents.

serene latch
#

sorry I'm nitpicky but this is really unclear 😦

#

I need you to be a lot more specific and explicit

#

If you create a $10 charge on Monday, the funds are available on Wednesday. If you create the Transfer on Monday do you want the funds to be instantly available the same day on the connected account? Or do you want the funds to be pending until Wednesday

#

cc @tender kayak

tender kayak
#

pending

serene latch
#

perfect so you want to mirror Destination charges, just with multiple connected accounts in one payment

tender kayak
#

this is what it does currently

$payment_intent = \Stripe\PaymentIntent::create([
            'amount' => $request->amount * 100, // Needs to be Total amount Inc Fees
            'confirm' => true, // https://stripe.com/docs/payments/intents
            'currency' => 'gbp',
            'transfer_data' => [
                'amount' => $partner_amount * 100, 
                'destination' => $partner_account[0], // business_stripe_account_id 
            ],
```

all I require it to do is the same, but for multiple connect accounts at the same time.
serene latch
#

I understand, that's exactly what the doc I just gave you offers

tender kayak
#

ok thanks 🙂