Hello,

It’s at least remotely possible that cloudflare is causing this. Or your server-side cache is preventing the API call, although I find this unlikely: Even if a single such URL is cached, that can’t affect any other transactions, since the TXID is part of the request URL and it’s different every time.

The plugin’s JSON API2 and API3 should be equivalent as far as the notify mechanism is concerned so it makes no difference. To use API2 with the latest version of the plugin, you’d first need to enable “Legacy JSON APIs” from the frontend settings. I wouldn’t do this if I were you. Since you already know that you can trigger the notify mechanism from your browser, the issue is not with the plugin.

You can try any transaction ID to see if you get a response. The call simply tells the plugin to go query that transaction, if it is a fake or non-existend transaction then nothing happens. But in any case you should see a JSON response with result: success, meaning that your request was submitted successfully, not that the transaction was found necessarily.

Since you know that the plugin works when you trigger the URL manually, this is something that has more to do with the wallet than with the WordPress plugin. You should focus on why the actual wallet does not do the same call. Perhaps you can redirect the output of the curl call to some log file, for example:

walletnotify=curl -k --verbose https://www.urcryptodepot.com/wallets/api3/notify/FCK/wallet/%s >>~/walletnotify.log

Then your ~/walletnotify.log file should contain some output.

Or check your webserver’s access log and see if the wallet is making the calls you expect to see.

Hope this helps.

with regards

P.S. I am happy to answer any specific questions, such as yours. It’s my choice to work alone so it’s cool. I can usually handle the context switching, and when I can’t, I just answer everything on the next morning 🙂