`application_fee_amount` support, Stripe `acct_` backend option, per-course $ per-educator

[lsthompson]

Hi there,

Is there any chance that you'd consider (and could use our help) building in support for application fees? Which also means support for storing multiple Stripe acct_ identifiers, for each relevant transfer destination.

This is for the case of an online platform (Moodle) which charges a fee for service, which would be set at product-level. We should consider application_fee_amount, as this has the inner mechanics already worked out for this use-case.

// Set your secret key. Remember to switch to your live secret key in production.
// See your keys here: https://dashboard.stripe.com/apikeys
$stripe = new \Stripe\StripeClient('sk_test_NLSWiAT3rEo0Er1FeoqB0X1E');

$stripe->paymentIntents->create([
  'amount' => 300,
  'currency' => 'aud',
  'application_fee_amount' => 30,
  'transfer_data' => ['destination' => '{{CONNECTED_ACCOUNT_ID}}'],
]);

This would be configurable per-course and allows for the LMS operator to control the application/platform fee per-course, and from there the remaining funds (majority of them typically) goes to the designated Stripe account.

• https://stripe.com/docs/connect/direct-charges#collecting-fees
• https://stripe.com/docs/api/application_fees

Thanks, Luke

EDIT: We used the paid version of https://wordpress.org/plugins/bsd-woo-stripe-connect-split-pay/

[moumitahalder]

Hello @lsthompson,

Thank you for sharing your enhancement request. However, please note that this request is related to Stripe rather than MooWoodle. I've forwarded your request to our development team, and if it aligns with our development plan, we will consider adding this support to our Stripe Payment Pro plugin.

It's worth mentioning that we already have a similar concept implemented in our sister product, MultiVendorX : https://github.com/multivendorx/MultiVendorX

If you have any further questions or requests, please feel free to let us know. We're here to assist you.