Olav Småriset

Hi @2fishone,

I want to thank you for leaving a review about our plugin and we’re happy to hear that the plugin works well for you but I am sad that you’re not happy with our pricing for our premium add-ons.

Each add-on requires continuous ongoing development, testing, updates, and support. Because of this, they are priced individually so users only pay for the features and coins or tokens they need.

The Dash add-on is currently €19.99 per year and works independently. It does not require any other paid add-ons to function. Regarding the estimate of $400, purchasing all coin add-ons currently costs around half of that. Most stores also only enable a small number of cryptocurrencies rather than all of the ones we have to offer. If you want full automation, we understand that the HD Wallet add-on adds more cost, but it also requires the most ongoing work from us, which is reflected in the price.

We would also like to point out that, unlike many cryptocurrency payment gateways, we do not charge any fees per transaction, neither percentage-based nor flat fees, and there are no withdrawal fees. Payments are sent directly from the customer to your wallet, so there is no middleman, no custodial risk, and you remain in full control of your funds. For many stores, a yearly subscription can be cheaper than services that charge per transaction. If your transaction volume is low, it is also possible, like many of our users do, to use the plugin for free and add HD Wallet or other add-ons later as your site grows.

We do understand that having many separate add-ons can feel overwhelming. We have been discussing about offering bundled or all-in-one premium add-on in the future to make this a simpler and more cost-effective solution for users who want everything included.

If you would like to help shape this, we would love to hear your feedback on our support desk.

Thank you!

Thanks again for the detailed reply — this is a bit puzzling, since I’ve confirmed that the wp_enqueue_scripts action (where the script is registered) runs before woocommerce_receipt_cryptowoo (where the script is localized and enqueued). That means wp_register_script() should always run before wp_localize_script(), and the CryptoWoo object should be available.

Since this issue does not occur on my end and has not been reported by anyone else, it seems likely that something in your local setup is firing woocommerce_receipt_cryptowoo earlier than expected — possibly from a custom function, plugin, or some custom logic.

To dig deeper, you can add the following code to your functions.php file. It will log when each action is fired and include a full backtrace, so we can see exactly where and when these functions are being triggered:

add_action( 'woocommerce_receipt_cryptowoo', function() {
	error_log( "--- woocommerce_receipt_cryptowoo fired ---" );
	error_log( print_r( debug_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS), true ) );
} );

add_action( 'wp_enqueue_scripts', function() {
	error_log( "--- wp_enqueue_scripts fired ---" );
	error_log( print_r( debug_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS), true ) );
}, 10 );

Then reload the checkout/order-pay page and check your wp-content/debug.log file. You should see the order in which the actions are firing, and what triggered them.

Let me know what it shows and we’ll figure it out from there!

Hi, and thanks for reporting this issue.

We identified that the problem occurs specifically when using WooCommerce Checkout Blocks. We’ve released version 1.6.12 with a complete fix, as the previous patch in 1.6.11 only partially addressed the issue.

Please update to the latest version and let us know if you continue to experience any problems.

Hi. Are you using WooCommerce Checkout Blocks or Legacy Checkout? Which version of WordPress and WooCommerce do you have? Do you use the dropdown selection or buttons for selecting the cryptocurrency in the CryptoWoo settings?

• This reply was modified 1 year ago by Olav Småriset.

I have received no reply to my previous message and I cannot reproduce this issue, so I marked this ticket solved now. Please reply here or email us in our support portal if you are still having issues.