Title: markopec's Replies | WordPress.org --- # markopec [ ](https://wordpress.org/support/users/markopec/) * [Profile](https://wordpress.org/support/users/markopec/) * [Topics Started](https://wordpress.org/support/users/markopec/topics/) * [Replies Created](https://wordpress.org/support/users/markopec/replies/) * [Reviews Written](https://wordpress.org/support/users/markopec/reviews/) * [Topics Replied To](https://wordpress.org/support/users/markopec/replied-to/) * [Engagements](https://wordpress.org/support/users/markopec/engagements/) * [Favorites](https://wordpress.org/support/users/markopec/favorites/) Search replies: ## Forum Replies Created Viewing 3 replies - 1 through 3 (of 3 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[GoDaddy Payments for WooCommerce] Fatal error at checkout when tokenization nonce is missing](https://wordpress.org/support/topic/fatal-error-at-checkout-when-tokenization-nonce-is-missing/) * Plugin Support [markopec](https://wordpress.org/support/users/markopec/) * (@markopec) * [2 days, 15 hours ago](https://wordpress.org/support/topic/fatal-error-at-checkout-when-tokenization-nonce-is-missing/#post-19009859) * Hey Daniel [@riseofweb](https://wordpress.org/support/users/riseofweb/) , * Thanks so much for your prompt reply here, and for your kind words about our team’s efforts to assist you. * I’m really glad to hear that debug logging is enabled on your end, and that if the error pops up again you’ll share the logs with us. That’s very reassuring. * I’m going to mark this request as solved now, since we’ve already created a bug report with our plugin engineers. In the meantime, please keep an eye out for the next plugin updates—they should include the fix for this error. * Have a great day ahead! Best regards, * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[GoDaddy Payments for WooCommerce] Fatal error at checkout when tokenization nonce is missing](https://wordpress.org/support/topic/fatal-error-at-checkout-when-tokenization-nonce-is-missing/) * Plugin Support [markopec](https://wordpress.org/support/users/markopec/) * (@markopec) * [2 days, 18 hours ago](https://wordpress.org/support/topic/fatal-error-at-checkout-when-tokenization-nonce-is-missing/#post-19009667) * Hey there, * Marko here, thanks for contacting SkyVerge about our GoDaddy Payments plugin! We’re happy to help out. 🙂 * Thank you for such a thorough report — genuinely, this is one of the clearest write-ups we’ve seen, and the stack trace, patch suggestion, and order-volume context all make it much easier for us to act on quickly. We’re sorry this cost you a $799 sale and a frustrating few minutes for your customer at checkout. That’s exactly the kind of failure we don’t want merchants to hit. * To confirm we’re on the same page: this is happening during `process_payment()` at live checkout (not the saved-card flow from the earlier threads you linked), when the Poynt Collect SDK doesn’t populate the payment nonce client-side. Right now that missing nonce isn’t caught before it hits `TokenizeRequest`, so instead of a normal declined-payment message, the customer hits a white screen and the order is left with no note and nothing in the gateway log. You’ve diagnosed that correctly. * On the browser-side root cause — why the SDK doesn’t set the nonce for that particular session — we don’t have a reproduction case either, and neither did the two earlier reports. We’re not going to pretend we can chase that down right now without something to reproduce it against. But we agree with you that this shouldn’t matter: a missing nonce should be treated as a failed tokenization, not a fatal error. That’s the part we can and will fix, and your suggested guard (checking the nonce is a non-empty string before it reaches the constructor, throwing ` SV_WC_Payment_Gateway_Exception` instead) is exactly the right shape of fix, since the framework’s `process_payment()` already catches that exception and routes it into the normal failed-order flow with a note and customer-facing message. We’ve opened this internally and will track it against the two prior reports. * One small correction on your framework version note: it’s not quite “highest version wins.” When multiple plugins bundle the framework, whichever loads first wins if the versions are identical — so in that scenario the version number itself isn’t deciding anything. We looked into it and don’t think the framework instance running on your site (`v5_15_12` via the CSV Export plugin) is a contributing factor to this bug, so no action needed there on your end. * If it happens again with debug logging on, we’d love to see the Poynt-side request/ response you mentioned — that could end up being the thread that finally cracks the browser-side mystery, even though it’s not what we’re fixing right now. * We’ve added this to our issue tracker for the developers to get this patched up. While we don’t have an estimated time for resolution right now, please know that our team is now aware of the issue and will work to incorporate a fix into the plugin as soon as they can. * Thanks again for taking the time to dig into this as deeply as you did — reports like this make the plugin better for everyone. * All the best, * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[GoDaddy Payments for WooCommerce] GoDaddy Payments – Selling in Person is not configured](https://wordpress.org/support/topic/godaddy-payments-selling-in-person-is-not-configured/) * Plugin Support [markopec](https://wordpress.org/support/users/markopec/) * (@markopec) * [1 month, 3 weeks ago](https://wordpress.org/support/topic/godaddy-payments-selling-in-person-is-not-configured/#post-18963757) * Hey @mvpboothgurus , * Thank you for reaching out for help with GoDaddy Payments for WooCommerce plugin, I’m happy to help out here. * Reading your initial feedback here, it looks like you’ve already done the needed steps to connect the plugin to your GoDaddy Payments account and that the block you face is that the Selling in Person feature doesn’t seem to work for you. * With that in mind, this doesn’t seem to be an issue with the plugin itself. It could be that particular connection points between your website and your GoDaddy Payments account are not met and therefore feature can’t be enabled or doesn’t work as expected. * That all said, the best way to move forward in getting a resolution on the block you face is to kindly follow the steps below: - From the left side menu in your WP-Admin Dashboard navigate to **WooCommerce > Settings > Payments > GoDaddy Payments** and click the **Get Help** link. - Once the new window pop-up contact form opens, please choose “Account setup” or “Other” as the Why are you contacting support. - Fill in the rest of the fields with as much detail as possible regarding the exact blocks you face when you try to enable the GoDaddy Payments – Selling in Person feature. * Would you please review the above guidance and let me know if that helps you move forward in regards to the block you face? * Cheers, Viewing 3 replies - 1 through 3 (of 3 total)