fesaponet
Forum Replies Created
-
Hello
The laws grant the customer a minimum period of 14 days to refund the order. The disadvantage of using stripe split payment is that if the customer requests a refund after 7 days, the admin cannot refund because the money has already been deposited in the seller’s account.In Europe it is only possible to use a payment method that allows refunds whithin 14 days and that the admin does not control the flow of payments. At the moment the only method similar is the periodic withdrawal system every 7 days 8plus 7 days of stripe) or more and with automatic admin approval. Although I don’t know if this method is valid at all.
Any more solution about it? For Europe it is necessary that you help us with it.
Thank you very much
Hello,
I Will take a look at it.
Currently in Europe the laws do not allow the Marketplace’s admin to take control of the flow of payments to suppliers. It must be an automatic process.
Thanks
Hello,
It happens the same thing to me. With WC-Marketplace vendors cannot access or see their orders. Why?
Thanks
Hello,
I hope that Stripe will soon allows direct charges with several accounts and you can implement it. It would be easier for marketplaces to comply with European Union payment laws, when we use standard Stripe accounts.
With separate charges and transfers, the administrator is responsible for making refunds to customers. In many countries, customers have a minimum of 14 days to request a refund of money for free from the date of delivery.
Once the split payment is made to vendor, stripe transfers the money to the vendor’s bank account in 7 days. So, how can the administrator make the refund to the customer if the money is no longer in Stripe? It is a complicated situation.
One solution to this is direct charges and that the seller is responsible for refunds (impossible at the moment). The other solution would be automatic approved auto withdrawals scheduled from time to time (every 7 days for example) using Stripe split payments. In that way the splited amount of the vendor remains in stripe for the time necessary for the administrator to make a refund without problems. It is a way to comply with the laws. WC-Marketplace allows you to do this but I can’t find a way to do it with WCFM. Is it possible now?Thanks
Hello again,
Take a look at WC-Marketplace Demo page. Stripe Payments settings. It does. Then It’s possible or not? Where is the trick?
I’m making several markets. I was using Dokan-pro. Dokan stripe connect plugin doesn’t allow direct charges if SCA-3d secured is activated. This situation forces me to change. Then I have discovered wcfm marketplace and I’m loved with it. However I need comply with e-commerce european laws and I need set direct charges.
I am sure that many marketplaces owners now or in the near future will be in this situation and will want to find the solution here, with wcfm marketplace
Thanks again.
Hello,
I read stripe documentation and it says:
“As of September 2019, a regulation called Strong Customer Authentication (SCA) requires businesses in Europe to request additional authentication for online payments. Businesses in Europe must start building their Stripe integrations with the Payment Intents API instead of the Charges API to be ready for these rule changes”
https://stripe.com/docs/connect/direct-charges
Then Direct charges are possible with Payment Intents API. Is that right?
Thanks!
Hello,
Dokan lite 2.9.15 and ALL RIGHT
THANKS!!
Hello,
It’s true. When a vendor adds hidden products, pagination doesn’t work correctly
Hello,
With Dokan-lite 2.9.14 the same thing happens. When I opened this ticket I was running 2.9.14 release. The issue started with 2.9.13 release.
Thanks
Hi,
I totally agree with Ndiebere about the wholesale feature and the woo-wallet add-on that I suggested the same in another post before. I hope that all our suggestions are developed. I use dokan pro because I think it is the best. But our suggestions are small details that can make Dokan a more fantastic marketplace plugin even. Because we are the ones who use it every day and we know what we need and what can be improved.
Thanks
It would be a great feature for Dokan to have a cashback system in which the cashback earned in purchases from a seller can not be used in purchases from a different seller, which would be a detriment to this second seller. I have sent a post to woo-wallet author about this. I trust that this feature will work correctly soon. It would be great to promote the sales of our vendors and it would be great for Dokan.
Thanks!
Woo-wallet presents a problem. The cashback earned with a supplier can be used to make purchases from a different supplier, so this second supplier would be harmed in the sale of its products. A discount obtained with another provider would apply, which would not be to your liking.
It would be convenient that the cashback obtained with a supplier can only be used in purchases from that seller. Otherwise it is not convenient to use in a marketplace.Hello,
I’m in a hurry to solve the problem and I could not wait for Dokan stripe connect technical support. I’ve been investing a little and I found which is the cause of the problem and how to solve it.
In Dokan-lite 2.9.3, removing vendor id from order post table does not allow Stripe Connect extract seller_id and iterate through orders..I fix issue extracting seller id from order metadata in Dokan Stripe Connect.
Again, I insist that all updates should be tested and released once it is verified that they do not cause additional failures. To all users this causes us inconvenience and wasted time. Quality is to minimize failures. Quality is looking for zero failures. Quality means trust.
Thank you very much.
Hello Nazmul,
I agree with you. But the problem has been generated by dokan-lite and I think that dokan-lite should solve it.
I think that before release an update, you should check the total compatibility with the most relevant products, starting with all the other dokan plugins.
An update must serve to provide improvements and solve problems and not to generate new ones
This causes disruption in the normal functioning of your clients’ businesses and discomfort in the users.
An update that does not generate new problems means quality in your products and ultimately satisfaction and confidence in customers.
Keep this in mind because it prevents users from choosing competitive products.
I will consult with the support of stripe connect, but I still think that the problem is dokan-lite and dokan-lite should solve it
Thank you
Forum: Plugins
In reply to: [Contact Form 7 SendInBlue Opt-in Checkbox] Recording also Name and Last NameHola,
Para lograr que el nombre y los apellidos, u otro atributo que desees a?adir queden grabados hay que hacer coincidir el nombre de los elementos del array en ‘attributes’ con el nombre de los atributos que figuran en los ajustes de tu cuenta sendinblue. Es lo que hice yo y me ha funcionado. Echale un vistazo a la siguiente función dentro de sendinblue.php
public function cf7_filter($posted_data){
if($posted_data[‘sendinblue-opt-in’][0] && $posted_data[‘sendinblue-list-id’]){
$mailin = new Mailin(‘https://api.sendinblue.com/v2.0’,SEND_IN_BLUE_KEY);
$data = array(“email” => $posted_data[‘your-email’],
“attributes” => array(“NOMBRE”=>$posted_data[‘your-nicename’]),
“listid” => array($posted_data[‘sendinblue-list-id’])
);
if($posted_data[‘apellidos’]){
$data[‘attributes’] = array(‘SURNAME’ => $posted_data[‘apellidos’]);
}
$mailin->create_update_user($data);
}
return $posted_data;
}Se ha cambiado NAME por NOMBRE porque es así como figura en la configuración de atributos de la cuenta de sendinblue
Lógicamente debes asegurarte también que los nombres de los campos de CF7 son los mismos que los que están en el código de la función
Hazlo y te irá bien.
Un saludo