#TLShadow-dynamic-app-fee
1 messages ยท Page 1 of 1 (latest)
Hi ๐ this is a really interesting scenario. It's likely that you won't be able change the application fee after the end-customer selects a payment method, but can you tell me a little more about your integration so we can be sure?
Since you're working with Express accounts, are you using destination charges? You mentioned that the payment method is selected on a Stripe site, does that mean you're leveraging Checkout Sessions?
If you're already using destination charges, then you could look into converting to separate charges and transfers 0. It's a very similar flow, but you define the transfer amount after the transaction which allows you to adjust how much your platform keeps at that time.
sorry i was distracted for a moment
and yes we are using desitnation charges, as far as i have gathered we have to for express accounts ๐
so just that i get it right, i would place the charge .. and once the webhook goes through i can use transfers to split the sum .. and if i enter the plattform id as connected account id it will go to the plattform and the other transfer will be left at the destiation ? or di have to number up all transfers ?
Typically we'd suggest setting your application fees high enough to cover any potential stripe fees and accept that your margin may vary a little bit
If you want to manage this more precisely, you would need to identify/collect the payment method being used first then set your application fees
Not all payment method types support separate capture, but for ones that do you can adjust your application fee during capture:
https://stripe.com/docs/api/payment_intents/capture#capture_payment_intent-application_fee_amount
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
ok so i kinda would have to say i don't want to auto capture the checkout session, and then have to manually capture the payment and set the fees for processing, is this about right ?
That's right, but again you need to be aware that this is not available for all payment methods, so you should test your flows in test mode
okay, yeah understood that ๐ woudl have to test which payment methods have that available ๐
Support for "manual capture" is documented here: https://stripe.com/docs/payments/payment-methods/integration-options#additional-api-supportability
It's currently only supported by Cards, Afterpay/Clearpay and klarna
ok thank you, i will check back with the customer and team, though i guess we'll have to implment fees infront of selection to be sure (since i recall apple and goolge play beeing on the list aswell)
those are just cards under the hood, so they do also support manual capture yes
ok good to know so well test it ๐ thanks for all the help
NP!