#SCIF
frigid condor
brazen plank
if i understand this correctly, your application fee is dependent on the amount after the coupon is applied?
grizzled cobalt
My app fee is a percent off the purchase price, because I leave up to the merchant pricing strategy. Actually, it's the same as Stripe does
brazen plank
you may have to switch to using separate charges and transfers and transfer the amount less the application fee that you want to take to the connected account instead then
grizzled cobalt
So essentially to administer revenue share on my own rather than relying on Stripe?
brazen plank
yep
are your connected accounts all in the same region as you (the platform account)?
grizzled cobalt
WDYM region? Uses the same currency?
brazen plank
if your Stripe account is based in the US, are your connected accounts also all in the US? or are they in different regions e.g. EU?
grizzled cobalt
We are NZ based, but handles NZD/AUD/EUR/USD/GBP.
brazen plank
country, not currency
so your connected accounts might be in a different country i.e. not NZ based?
brazen plank
that's a problem then, you can't do a separate transfer to the connected accounts if they're based in a different country
grizzled cobalt
Got it
That's a little bit weird 🙂 Recurring supports % application fee, while one-off's aren't
brazen plank
hmmm, gimme a second to try something
there's two workarounds here that I can think of :
- use capture_method=manual -> subsequently, you can update the application_fee_amount when capturing the payment : https://stripe.com/docs/api/payment_intents/capture#capture_payment_intent-application_fee_amount
- set the application_fee_amount to the undiscounted amount first, later refund the application fee (after payment is received and doing your calculations) : https://stripe.com/docs/api/fee_refunds/create
the problem with capture_method=manual is that not every payment method supports it - it's mainly for cards, so that'll affect the available payments shown to the customer
grizzled cobalt
What does imply the #1 approach?
Does it mean my app has to handle 3ds/sca/etc on my own?
brazen plank
capture_method=manual is authorize and capture i.e. https://stripe.com/docs/payments/place-a-hold-on-a-payment-method
no, you don't need to handle 3DS on your own
grizzled cobalt
That sounds really interesting. Let's imitate selling of $100 plan. App fee is 20%.
Does it mean, the flow will look like:
- app creates the session having app_fee using full price as a base ($20)
- customer input CC details, inputs coupon 40%
- Stripe handles 3ds/sca/indian mandate/etc if required
- Once all checks are done, Stripe reserves $60
- App receives the callback
payment_intent.capturedand updates app_fee according to $60 purchase amount, so essentially decreases from $20 to $12. Once done, app finalizes the PI?
brazen plank
looks correct to me - you can test it out to see if it works too