Matt Spieg

[vale patio]

This is expected. Stripe fees come out of the platform's balance when using destination charges

[inner oasis]

I'm trying to do direct not destination here but i think its coming through as destination

We are a marketplace platform and want the payments and fees to go directly to our sellers

[vale patio]

I see. Do you know how your payments are setup?

Do you have a Payment Intent ID I can look at to confirm you're using destination charges?

[inner oasis]

sure: pi_3Lhu6GHTbd3kAH1o1ecPWP0s
We are trying to do direct not destination though.

[inner oasis]

Would you mind clarifying what you mean here 🙂

[vale patio]

So yeah, these are destination charges. Let me dig a bit more and circle back

[inner oasis]

Okay thanks!

Also please @ me for a faster response!

[vale patio]

Okay @inner oasis, so somewhere in your Checkout Session creation API call you are specifying payment_intent_data.transfer_data to create a destination charge. All you have to do is omit that and I believe that will automatically default to direct charges.

[inner oasis]

Okay will try that now!

the only payment_intent_data in my payload is payment_intent_data[application_fee_amount]=199980 see here: #dev-help message

[inner oasis]

are you seeing this in the api call on your side?

[vale patio]

Interesting. I wonder if specifying an application fee causes it to default to destination charges. The docs you posted are for destination charges, after all

Let me try to repro

I ran the cURL command from the docs you posted and it did not result in a destination charge.

Do you have a request ID for the request you used to create the Checkout Session? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request

[inner oasis]

here's a request id: req_DYM77kgtnd1vqM

[vale patio]

So the below is coming through as parameters to the creation request:

payment_intent_data: {
application_fee_amount: "199980",
transfer_data: {
destination: "acct_1Lhan0Qat9Qo8K9i"
}
},
Can you post the exact code you're using to make the API call? If you don't specify destination in your code, , then it might be because you're on an old API version