[alexg]

This is by design. Returning the crypto amount would not make sense. Imagine a crypto that suddently spikes 50%, all your users with pending orders would suddenly be incentivised to request refunds on that day.

If you are running a legitimate business, in terms of accounting, you immediately convert any crypto you receive to whatever currency you are paying your taxes with. You want to be hedged against crypto volatility. A business is not a place to speculate with price movements or expose yourself to price risk. If you want to do that, go to an exchange and start trading, but that shouldn’t have anything to do with your s-shop or other businesses. Crypto is used as a medium of exchange here. Shop prices should be set in fiat currencies.

Again, in a normal situation you would have more funds in your admin account so that you can pay out more crypto if the crypto value goes up, and less if it goes down. This will average out over time.

Hope this makes sense.

If you really need to refund the original amount, you can always mark the order as cancelled, and go to the transactions list and cancel the internal transfer. But there is no legitimate situation where you would want to do this.

Therefore, this calculation is not the problem. The problem is that in some situations the method is not being triggered (e.g. with auto commissions, or other edge cases) If there was a clear API on how to hook to the plugin to create a payout payment gateway, these problems would not exist. But the plugin is too closely tied with paypal and there is no sufficient decoupling of payout methods to the multivendor plugin, hence the need for the DB hacks you see in the code.

with regards

[alexg]

WCMp was requested by several people at the time and it seemed popular.

In retrospect maybe I should have chosen Dokan as it is more popular and possibly better.

In any case, the problem is elsewhere: None of these plugins seem to come with instructions on how to develop additional payment gateways for commissions, so any solution is going to be a hack.

with regards

[alexg]

@alecmtetwa I will not discontinue it, but at the same time I am not in a position to do the improvements that I’d like to do.

If you currently rely on it, that means it’s working.

The main issue here is that it works in some cases and not in others. I will have to write up in which cases it works.

@d3vnu77 Your flowchart looks good. The difficulty will be in implementing it.

[alexg]

Thank you for providing detailed information about the issue.

Unfortunately the gateway is somewhat hard to use. There was no API with which to extend WC Marketplace with payment gateways, so I had to improvise as I went along. If it turns out that the gateway does not work, then I will take the decision to decommission it.

However, I have tested refunds multiple times, and I know that they work, at least when certain conditions are met.

In your case, it looks like you attempted to perform a refund, but it did not go through, because the price of Litecoin has changed in the mean time. The amount refunded is calculated in the store currency, but is returned in the currency the user initially paid.

Therefore, if the admin account had more Litecoin, the refund would have been executed.

As a sidenote, I do not know if the Marketplace plugin or the crypto gateway are compatible with the RMA plugin you mentioned.

Yes, please do check the information given in the other thread related to refunds. I will add this information to the homepage soon.

with regards

[alexg]

Hello,

1. This is a very good idea. If you disable auto-payments in WCMp, then you can decide when commissions are being disbursed. You can do this after making sure that the client is satisfied. In fact this is highly recommended, because this payment gateway does not work correctly with auto-disbursals. If you have the setting on, you will get a warning in the admin screens about it.

2. Unfortunately I do not know much about how to do this. I simply developed a payment gateway. A gateway’s only role is to execute payments. All business logic should be in your multivendor plugin. So I highly recommend that you contact the developers of multivendor plugins for questions regarding how and when commissions are issued. A payment gateway does not know about disputes, grace periods, trust models, etc. This is all the job of the e-shop logic.

Sorry for not being of more help about 2.

with regards

[alexg]

Hello,

Yes, I am aware that refunds are hard to use, but unfortunately not much can be done about this. As mentioned in the extension’s FAQ, refunds are paid from the admin account to the buyer, not from the vendor’s balance.

You, as an admin, can perform a partial or complete refund of an order, as long as commissions have not been paid yet. This returns the correct funds from the admin account back to the user. Always choose the button (“Refund via Bitcoin and Altcoin Wallets”, not “Refund manually”).

If the commission has already been paid then it’s still possible to return the funds from the vendor to the admin. go to the transactions list, locate the transaction corresponding to the order id, then cancel the internal transfer. Note that the admin may have withdrawn the funds from the platform at this time. This can result in a negative balance for the vendor. Therefore it’s best to do any refunds before paying out any commissions.

I realize that this information is not obvious, so I will be adding it to the plugin’s homepage.

with regards

[alexg]

Hello,

I have looked at this some more, consulted the relevant docs, and it turns out that you can use the plugin wallets on IPv6 hosts.

If you use an IPv6 address in the “Daemon RPC API IP field”, enclose it in square brackets.

For example to connect to localhost using IPv6, you would type [0:0:0:0:0:0:0:1].

Therefore I believe you will be able to connect to an IPv6 host with no issues.

with regards

[alexg]

Hello,

Good news!

I have now tested the Crypto Gateway extension with WooCommerce Subscriptions and it works fine.

with regards

[alexg]

Thank you for reporting this.

Unfortunately it could be a problem at this time.

I tested connecting to a local wallet with IP 0:0:0:0:0:0:0:1 and the result I got back is “Port number ended with ‘:'”. This is probably coming from the PHP curl module or from the EasyBitcoin library.

Obviously I will have to investigate and fix this. I am adding it to my list, as the plugin should be made to work with IPv6.

I will contact you again here once I have a fix.

with regards

[alexg]

Hello,

I am not aware of this issue. Normally, the wallet notifies the plugin about transaction updates via the notification mechanism.

Please consult this article: https://www.dashed-slug.net/howto-debug-an-incoming-deposit-full-node-wallet/

and in particular focus on step number 5.

Try constructing a URL of the form https://www.example.com/wallets/api3/notify/DEM/wallet/TXID where you replace example.com with your domain name, and TXID with an actual transaction id. Visit the URL in your browser. This should force the plugin to query the wallet about that transaction, and update the confirmations count.

If this doesn’t work, try the same with the URL https://www.example.com/?__wallets_apiversion=3&__wallets_action=notify&__wallets_symbol=DEM&__wallets_notify_type=wallet&__wallets_notify_message=TXID

Does this make the confirmation count update? Do you get back a JSON message?

If the above works, check your walletnotify line in your wallet’s config file. You should have placed a curl command in there. Does the curl command work from the host where your wallet runs? Could it be some networking issue?

Please try the above and let me know if you were not able to resolve the problem or if you have any questions.

with regards

[alexg]

Hello,

I’m glad you figured it out!

Thank you very much for providing this detailed follow-up.

with regards

[alexg]

Yes, you would get this error message if the JSON API did not return a JSON response but an HTML. If you follow the URL you gave me you’ll see that it responds with your web page, not JSON.

I cannot know why this happens on first inspection, but here’s some guesses:

1. Check your server cache or caches. First, disable your caching mechanism altogether to see if it makes a difference. Then enable it again. Look at any caching mechanisms you use on your server and try to add to your exclusion list or whitelist URLs that include the GET parameter __wallets_action. For some popular caching mechanism the plugin will warn you about this.

2. Check your server configuration. It is possible that your apache mod_rewrite rules or your nginx config does not allow for URLs of this type. If unsure, revert to the recommended configs for WordPress and try again. Currently the JSON API endpoint you gave me shows your webpage, while it should be responding with JSON, even if you are not logged in. The plugin will not work until this is fixed.

3. The DB deadlock you report indicates that maybe your MySQL server needs to be restarted. I have seen this type of deadlock before but only occurs while starting my machine, and it’s not something serious. It simply means that the new exchange rates for coins were not saved in this particular instance, but will be saved again in a few minutes.

Hope this helps. Please check the above and let me know if you need further help or if you weren’t able to resolve the issue.

with regards

[alexg]

Yes, one issue is that an order can have sub-orders to many vendors. And also, another issue is that commissions have to be paid in crypto for all payments, not just those done in crypto. Unfortunately all marketplace plugins are a mess, because WooCommerce was never built for this. You can get a multivendor plugin to work and you can get it to work with crypto, but you will always have to disallow certain features or options. It’s complicated 🙂

[alexg]

Hello,

I expect that there shouldn’t be any problems, but I haven’t tested this combination. I know that this add-on does not work with all payment gateways.

Fortunately I have a copy of the subscriptions add-on. I can test to see if it works. I will get back to you on this thread soon.

with regards

[alexg]

MyCryptoGive.com

Work in progress with currently over 1600 registered users.

[Author]

Posts