#fakossaconate
tawdry spade
Hey
First of all you need to switch using Express or Customer Connect Account in order to use destiantion charges
hardy dust
ok, this is mandatory?
tawdry spade
This is strongly recommended otherwise you'll be facing multiple issues later on handling refunds and funds flow
hardy dust
ok thanks. The easier way seems to be express account right?
hardy dust
ok thank you, I'll do that then
tawdry spade
You can also create Destination Charges using Invoices:
https://docs.stripe.com/connect/invoices#destination
Here how you can create a Desintation Charge with Checkout:
https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-payment_intent_data-transfer_data
hardy dust
This is not also meant for my use case? https://docs.stripe.com/connect/platform-controls-for-standard-accounts
tawdry spade
I'm not sure I understand your follow up question sorry.
The type of the Connect Account and the charge type are strongly coupled.
If you want to use Destination Charge then you'll need to have Customer or Express Connect Account.
Standard Account are for Direct Charges only.
hardy dust
no I know that. I'm just thinking in terms of use case. I just want to hold the payment until an event has happened and pay the host (connected account) after the event.
but I'm lost between all the vocabulary "hold & release", "destination charges", ""payment control"...
tawdry spade
I just want to hold the payment until an event has happened and pay the host (connected account) after the event.
How long does this usually take ?
hardy dust
It can take more than 1 or 2 weeks
tawdry spade
Regardless of the charge tye you are using, you can use the palce hold feature:
https://stripe.com/docs/payments/place-a-hold-on-a-payment-method
Then choose the Charge type you need more:
https://docs.stripe.com/connect/charges
It depends on who (the platform or the connect) will be managing the funds (e.g. refunds)
hardy dust
ok but I still need to switch from a standard account to an express account
uncut streamBOT
thick token
generally if you need more control/customisation of the marketplace and funds flow then Express/Custom fits better yes
hardy dust
Ok, I can deal with that. But with the goals I was referencing above, what features suits the best in my case?
-Destination charges
-Hold and release
-tranfer account
-payment control
maybe the words stripe is using is confusing me (I'm not english) but the scenario (in my mind seems pretty simple)
Client book and event and pay for it.
I keep the money unitl the event is gone
Then I pay the host of the event.
The host pays stripe charges.
So I can choose express account, but then, as os4m37 was saying, I need to do a hold and release feature?
thick token
the hold-and-release (auth-and-capture) makes sense if you only process card payments and the maximum amount of time you can wait is 7 days
otherwise generally you do this by either
- manually transferring the funds from your platform when you're ready(note you need to make your platform use manual payouts so you accumulate a balance)
- use Destination charges to transfer funds immediately to the connected account, but don't allow them to pay those funds out until you decide https://docs.stripe.com/connect/manual-payouts
hardy dust
when you are saying "but don't allow them to pay those funds out until you decide ", do you mean I transfer them the money but they can't touch it until I decide it?
thick token
you transfer it to their Stripe account but it's not paid out to their bank account until you call the API to process a Payout
hardy dust
cristal clear. To summarize my following action then:
- I need to switch from standard to express account
- create a destination charge to allow client to book an event
- create a checkout
- after the event, I can create a manual payout.
Does this workflow make sense to you?
thick token
sort of but I don't know what things like "create a checkout" mean
hardy dust
I meant create a checkout session
thick token
yeah but then that is not a seprate step than "create a destination charge"
they're the same step, you create the CheckoutSession with params that indicate it should process as a Destination charge, basically
hardy dust
I thought create a session and destination charges were separate... https://docs.stripe.com/connect/destination-charges#créez-un-paiement
hardy dust
ok
last question
is it finally not the same for me to do a transfer call?
https://docs.stripe.com/connect/separate-charges-and-transfers#transfer-options
But easier
thick token
well it's not a Destination Charge then, it's Separate Charges and Transfers
hardy dust
yes but I can do it with my actual standard account, no?
because I don't want to specifically do a destination charges. I just wants to pay the host when I (my client) decide it
thick token
you can technically use any charge approach (Destination/Direct/SC&T) for any account type
thick token
because I don't want to specifically do a destination charges. I just wants to p...
I mean to accomplish " I just wants to pay the host when I (my client) decide it" that kind of has to be solved in the ways we'be been describing, by doing transfers(a Destination charge is just a way to do an "automatic transfer" where you say "process this payment and transfer some if it to X account" in an API call)