#RobertGoddard - transfer data
fervent ocean
It seems like direct charges would be better for your usecase then
What's the reasoning exactly?
tight bane
In our system we want to collect a payment as if the checkout process has succeeded, this creates a manual paymentintent that eventually needs to be captured before it is cancelled. We can only transfer money once someone has onboarded with a connected account. At that time, we want to capture the payment intent and transfer the money to the connected account.
We would like to avoid any temporary "escrowing" of the money into our platform account; even if for the milliseconds it takes to create a transfer.
fervent ocean
That's not possible unless you use direct charges
tight bane
I can't do direct charges because I won't have a destination account to send the money to until the person receiving the money onboards.
by onboarding (creating a connectedStripeId and setting up a bank account)
fervent ocean
We would like to avoid any temporary "escrowing" of the money into our platform ...
Why specifically do you want to avoid this
tight bane
Customer requirements. They do not want, in any form, to escrow money intended to be sent to connected stripe accounts.
This seems like a bit of an oversight of the API, honestly... When an uncaptured payment intent is created, there is an authorization on the purchaser's card. When we capture it, we should be able to specify which connected account to immediately transfer the collected payment to...
The payment is already authorized; so why are we prevented from specifying a destination account when capturing the payment intent?
brisk coyote
👋 stepping in as codename_duchess needed to step away.
As mentioned, this just isn't a flow we support
You can't set a destination upon capture. The only time we support setting a destination is upon PaymentIntent creation
tight bane
Fair enough, but I'll still be able to create a transfer to transfer the funds to the newly connected account; correct? When it asks for a source_transaction, (when creating a transfer), can I specify either a payment intent id OR a charge id? I think it'd be easier to reference the original payment intent ID.
brisk coyote
You can still create a transfer afterward as long as your Connected Accounts are in the same region as your platform
tight bane
So 1. Capture uncaptured payment intent (Money goes to platform account), 2. create transfer to transfer money to connected stripe account using source_transaction (id of uncaptured/captured payment intent)
brisk coyote
Yep you use source_transaction to be able to transfer the funds from your platform to the Connected Account before they are actually "available"
tight bane
And that can be either the payment intent ID, or the charge id correct?
tight bane
Alright, thanks so much for the clarification and help 🙂