markopec

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,