#daagcentral
wild dew
sharp parrot
This comes down to the difference between direct charges: https://stripe.com/docs/connect/direct-charges and destination charges: https://stripe.com/docs/connect/destination-charges. With direct charges, the connect seller pays the fees. With destination charges, you pay the fees
Direct charges are only recommended if you're using Standard accounts. Destination charges are only recommended if you're using Custom and Express accounts
noble sedge
so our intent used to look like this:
stripe.paymentIntents.create({
amount: 5500,
currency: 'usd',
application_fee_amount: 246,
automatic_payment_methods: { enabled: true },
metadata: { custom_id: '92b57243-0d61-4214-8374-079541be0515' },
transfer_data: { destination: 'acct_SOMESELLERACCOUNT' }
})
what we should do is this:
stripe.paymentIntents.create({
amount: 5500,
currency: 'usd',
application_fee_amount: 246,
automatic_payment_methods: { enabled: true },
metadata: { custom_id: '92b57243-0d61-4214-8374-079541be0515' },
}, {
stripeAccount: 'acct_SOMESELLERID',
})
sharp parrot
No problem
You should also fully read that doc to understand all the differences with direct charges
noble sedge
will do
Just to confirm, we will get our application_fee, seller gets total - stripe fees right
sharp parrot
Correct
noble sedge
we keep getting this
message
:
"No such payment_intent: 'pi_3NgYc4GRs6B1g8ST1tNCuFrb'"
sharp parrot
When trying to do what?
noble sedge
when completing the payment
sharp parrot
Again, recommend reading the direct charges doc. It sounds like you're not initializing Stripe clientside with the connect account header
ie the second code snippet here :https://stripe.com/docs/connect/direct-charges#create-a-charge
noble sedge
I'm an idiot haha. fixing!
sharp parrot
No worries!