Stripe Connect: Fix negative balance liability and separate charge and transfer incompatibility for accounts that pay Stripe fees and use the Stripe Dashboard

[nstk-prog]

Bug Description

Hello,
Got this email warning from Stripe this morning (see attached).

Here is the complete description of the issue described in the Stripe Workbench:

Years ago, when I first use Stripe Connect, I asked for Direct Charges being deployed in your gateway plugin, but you did stick with Separate Charges and Transfer. Now, Stripe recommend using Direct Charges, which is obviously a better solution, for accounting issues with Stripe fees, VAT rates, negative balance, refund of vendor with no money, ..

This is part of the Stripe documentation for the changes to be made according to this:
https://docs.stripe.com/connect/configuration-migration-guide?none=Separate%20charges%20and%20transfers#change-charge-type

Can you please give us information on how you could change the payment process for Stripe Connect gateway in a near future? Thanks in advance.

Step To Reproduce

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected Behaviour

Dokan Stripe Connect payment gateway should use Direct Charges.

Actual Behaviour

Dokan Stripe Connect payment gateway currently use " separate charges and transfers "

Additional Information

No response

Environment (please complete the following information)

1. Dokan Version: [e.g. v3.1.2]
2. Dokan Pro Version: [e.g. v3.1.2]
3. WooCommerce Version: [e.g. v4.9.2]
4. Browser [e.g. chrome, safari]
5. Current Theme: [e.g. Store Front]