Dokan Stripe Connect modification
- or -
Post a project like this1167
£50(approx. $63)
- Posted:
- Proposals: 9
- Remote
- #3140315
- Awarded
Top rated PHP Web Development | WordPress | Magento | Drupal | OpenCart | PrestaShop | Joomla
Leicester
PAKISTAN'S No.1 - All Time Top Rated Freelancer | Wordpress|Magento|PHP| Responsive UI Design | PSD to responsive html | Shopify | Ecommerce | SEO
Islamabad
Professional Software Developer (Windows, Web and Mobile Apps)
Mohali
Microsoft Azure Office 365 Sharepoint Google Workspace Online Marketing Consultant,
Brighton
✨ 11+ years of Exp. in iOS App, Android App, PHP, Symfony, eCommerce, WordPress, WooCommerce, Angular, Node, React, Full Stack ✨
Ahmedabad
105075419094882099264235156527683122803772314221651349725401463
Description
Experience Level: Entry
I need a modification of the Dokan Stripe Connect payment method.
As of now Dokan Stripe Connect plugin manage in a different way the fee splitting looking at the 3Ds (3 Data Secure) configuration. In particular:
- when the 3Ds is enabled: the plugin first land the money in the Admin account and then split the payment in the vendor account (subtracting the admin's fee)
- when the 3Ds is disabled: the plugin first land the money in the Vendor account and then split the fee in the Admin account
Although this model, from the fee point of view, produce the same result, from the legal point of view is different.
In the first case (3Ds is enabled) the Admin is part of the sale (in fact the money lands in its account before), while, in the latter case (3Ds is disable), the admin is just a technology provider and they are not part of the sale (in fact the money lands in Vendor account before).
The change that I need is to have the same behaviour regardless the 3Ds functionality.
In particular I need that my platform will be a technology provider and the plugin should always land the money in Vendor account and then subtract the fee for the Admin (that is the current behaviour when the 3Ds is disabled).
I've already spoken with the Stripe Support Team and they confirmed that the 3Ds should not affect the fee splitting and that by using their API it is possible to obtain this behaviour.
Can you mange this development?
As of now Dokan Stripe Connect plugin manage in a different way the fee splitting looking at the 3Ds (3 Data Secure) configuration. In particular:
- when the 3Ds is enabled: the plugin first land the money in the Admin account and then split the payment in the vendor account (subtracting the admin's fee)
- when the 3Ds is disabled: the plugin first land the money in the Vendor account and then split the fee in the Admin account
Although this model, from the fee point of view, produce the same result, from the legal point of view is different.
In the first case (3Ds is enabled) the Admin is part of the sale (in fact the money lands in its account before), while, in the latter case (3Ds is disable), the admin is just a technology provider and they are not part of the sale (in fact the money lands in Vendor account before).
The change that I need is to have the same behaviour regardless the 3Ds functionality.
In particular I need that my platform will be a technology provider and the plugin should always land the money in Vendor account and then subtract the fee for the Admin (that is the current behaviour when the 3Ds is disabled).
I've already spoken with the Stripe Support Team and they confirmed that the 3Ds should not affect the fee splitting and that by using their API it is possible to obtain this behaviour.
Can you mange this development?
Jenny G.
100% (2)Projects Completed
3
Freelancers worked with
3
Projects awarded
50%
Last project
3 Aug 2023
Italy
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies