#joel-k_api
velvet kelpBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1364688882968297604
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
primal kite
Hi 👋
clever comet
Hey there!
velvet kelpBOT
primal kite
That isn't supported. When processing Payment Intents on your Platform account (using one of the flows that we refer to as either a Destination Charge flow or a Separate Charges & Transfer flow) the Platform account pays the Stripe fees.
https://docs.stripe.com/connect/charges#stripe-fees
clever comet
Alright. Thanks. I suspected as much reading that documentation, but I figured I'd ask.
bright harbor
👋 stepping in as toby needs to step away
You can take an application fee equal to the fees, however you have to perform that calculation up front.
What integration flow are you using?
clever comet
We have our backend service call the payment_intents API upon receiving a request to charge a customer from our ERP system.
bright harbor
How are you collecting PaymentMethods?
clever comet
In this, case, I believe it's via the sources API.
bright harbor
Hmm okay well if you are confirming server-side then you know the type of payment method ahead of time and can calculate the fees accordingly to set the application fee to that amount if you so desire.
Oh actually are you transferring later on?
I inferred you were using destination charges
But seems like you might be doing Separate Charges & Transfers here
(In which case you would just transfer the amount - fees)
clever comet
It's all one API call. We hit the payment_intents endpoint with transfer_data.destination set to the connected account.
bright harbor
Yep okay then what I said above -- you would calculate the fees based on inspecting the payment method you are using and then set application_fee to that amount to hold back the amount of the fees.
clever comet
Ok.
I have another, somewhat related question. Is there a way to pass metadata to the payment created in the connected account by setting some parameters in the payment intents call? For example, in pi_3RH7kgEaVVvuwoDN1Sr8K4up, the description, statement descriptor, and metadata fields are all populated with data on which Sales order created this payment intent along with other data that's useful for debugging. But none of that propagates to py_1RH7kjJMDKccxs3Kr9GKFFpI. Is there a way within the payment intents call to specify that this data should be included in the payment to the connected account?
bright harbor
We are actually working on adding that to the API right now so it will be possible to do it in one request in the future. However, for now, you would have to make a separate request to update the Charge on the Connected Account using the Update Charge API (https://docs.stripe.com/api/charges/update) and passing the Stripe Account Header (see: https://stripe.com/docs/connect/authentication)