#HarAsz
1 messages · Page 1 of 1 (latest)
With express accounts you should be using destination charges, so all payments and customers reside on your platform account
Cloning to connected accounts should not be necessary
That only really applies to standard accounts & direct charges
Okay, right now i am creating payment intent like that const paymentIntent = await this.stripe.paymentIntents.create( { amount: total.getValueAsInteger(), currency, application_fee_amount: applicationFee.getValueAsInteger(), metadata: { orderId, env: this.config.envName, orderType }, }, { stripeAccount: connectedAccountId }, );
So providing stripeAccount: connectedAccountId as a second param
And you suggest that i should use transfer_data: { destination: '{{CONNECTED_STRIPE_ACCOUNT_ID}}', },
But here is the question, this all money comes from buying alcohol, and my client doesn't have right to collect money from alcohol, our shops does
Yes, that's what I'm suggesting
I see, let me see what i can find about that
I believe you'll want to use on_behalf_of for this use case to identify the connected account as the merchant of record: https://stripe.com/docs/connect/destination-charges#settlement-merchant
This all payment intent can't be related with platform account, only shops
But i would suggest you write in to support with the alcohol sale use case for confirmation for your account to ensure this will be acceptable
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.