'Nonce' errors – repeated and continual

Resolved touchnova
(@touchnova)

9 years, 11 months ago

Throughout the process of development, this plugin has provided the following error:

“PayPal Powered by Braintree did not supply a payment nonce. Please try again later or use another means of payment.”

I assumed this was a sandbox issue, but now after going ‘live’ my site has received 3 orders, 2 of which generated this error (and frustration) for my customers.

Though this is related to a previous support thread on ‘credit cards fields working intermittently’, I updated the plugin to the latest version that is supposed to resolve this issue, but without success. I have also adjusted the ‘setInterval’ length to 2000 milliseconds as was recommended by others, but this, too, has not resolved the issue.

My primary concern is to resolve this so that people can pay via credit card, but a question to developers would be how this could even be made available to the public with such blatant, process-breaking errors in place.

Any/all help would be greatly appreciated.

https://ww.wp.xz.cn/plugins/woocommerce-gateway-paypal-powered-by-braintree/

Viewing 9 replies - 1 through 9 (of 9 total)

Thread Starter touchnova
(@touchnova)

9 years, 11 months ago

Created support ticket on Woo’s site…

cubantractor
(@cubantractor)

9 years, 10 months ago

Was there a resolution? Can you add the link to the new ticket? Thanks.

Thread Starter touchnova
(@touchnova)

9 years, 10 months ago

Only the temp resolution so far…adjusting the ‘setinterval’ to 2000ms. As far as my ticket, Woo and I set up a test site on their servers where we were able to duplicate the problem repeatedly, which they now fully acknowledge (though it was briefly touched upon in a previous plugin update, but that ‘fix’ did absolutely nothing). They have a support ticket themselves in with Braintree to address it there if possible. Braintree only allows access to a minimized SDK, so Woo is a bit in the dark until they can get access to the code or Braintree resolves it internally. As it stands, my ticket with Woo has been open for 2 months and my last communication from them was 16 days ago…it’s fully in Braintree’s hands, or so Woo claims.

Thread Starter touchnova
(@touchnova)

9 years, 10 months ago

Cubantractor, just to clarify….my ticket with Woo is an internal support ticket on their website, not here on the public WP forums. I’ll keep you updated if I get any news, but considering the already-lengthy process, I’m not sure when that might be.

Kyle_Irving
(@kyle_irving)

9 years, 10 months ago

Hi

I’m getting the same error in Sandbox mode with either Credit Card or Paypal payments.

Any news on the update?

gatta2
(@gatta2)

9 years, 3 months ago

I’ve the same error too. Also in sandbox mode the credit card fields in the checkout page isn’t enabled. There’s no way to put in credit card numbers.
Thread Starter touchnova
(@touchnova)

9 years, 3 months ago
@gatta2 – Do yourself a serious favor…get rid of the plugin. It caused me issue after issue after issue…I went through several MONTHS of customer support with WooCommerce, they created a sanitary hosting environment (no other plugins, scripts, themes, etc. to cause conflicts) and were able to replicate the error over and over and over. When I became tired of the months-long process with no progress being made and no resolution on the horizon, I switched to a different payment gateway and have not had a single issue since. So, my honest recommendation to you is…get away from this plugin as fast as you possibly can.
- This reply was modified 9 years, 3 months ago by touchnova.
gatta2
(@gatta2)

9 years, 3 months ago

@touchnova may I ask which plugin you switch to?

Thread Starter touchnova
(@touchnova)

9 years, 3 months ago

@gatta2 – I ended up using WooCommerce’s Stripe gateway, which has worked flawlessly. Being said, my saying as much is by no means intended as a recommendation or promotion for Stripe, I’m simply stating the plugin that allowed me to process payments without continuous struggles with basic functionality.