Error response 429

Hey there,

Thank you for reaching out about our plugin, GoDaddy Payments! I’m Kari, and I am happy to assist you with this. ??

A 429 error message can come from a wide range of triggers, including site timeout, too many redirects, and firewall blocking.

Here are a few things you can check right away, however we may need additional info about your site (what plugins and theme are active, are you on Cloudflare services, etc.) in order to locate what might be blocking the data from getting passed over to your GoDaddy Payments account through our gateway plugin.

1. Your business account must be USA or Canada based.
2. Your WooCommerce currency must be set to?United States (US) dollar ($)?if located in United States, or?Canadian dollar ($)?if located in Canada.
3. If you have any site security plugins with firewalls, such as Sucuri, Cloudflare, etc., you can try allowing that URL through the firewall (whitelist it) or temporarily deactivate the security plugin(s) to test if the order goes through without it active.
4. If the error is prompted by a timeout, be sure to check for any redirection or custom “order-received” WooCommerce page that might cause an infinite loop or cause the plugin to not be able to complete the checkout process.

Would you please review those four items above, and then let us know if none of those resolves the issue? If not, could you please include a System Status Report (with Theme, Active Plugins, and Page Template information specifically) so we can look for potential conflicts?

All the Best,
Kari | Merchant Success Team

Hey there,

It has been a long time since we heard from you, so I’m going to mark this topic as resolved.

If you’re still experiencing issues please take a look at our FAQs for more information and create a new thread if you have further questions.

Thanks,
Kari | SkyVerge Support Team ??

Heeey. I am getting this same error. Any solution ? I’ve checked all the things you asked us to check but I still see the same 429 + CORS error.

Hey there,

Thank you for reaching back out, but it’s unfortunate to hear that you are still having this issue.

This error?occurs when a server detects that a client has exceeded the rate limits or has made too many requests in a given period of time. GoDaddy’s API Gateway uses rate limiting?to protect its services from being flooded with too many requests.?Rate limiting tracks IP addresses and the time between requests, and temporarily blocks IP addresses that make too many requests.?GoDaddy’s API Gateway uses both service-level and client-level rate limiting.?Service owners can adjust the service-level rate limit through a UI.?

Are you only receiving this error, or are you having issues with fraudulent charge attempts as well?

All the best,
Amber

Hey Amber ! Thanks for answering !

I am trying to integrate GoDaddy payments and trying to buy test products, but I always get this error. I still don’t know why.

I am also not sure if there is a way to debug and check if my website is sending too many requests. I’ve checked the network tab on DevTools, but it looks ok, there’s no excessive API calls. Also there’s no timeout error. As soon as I click the checkout button the API call is made and less than 5 seconds later I get the 429 error.

Best,

Jones.

Hey Jonas,

Thank you for informing me of what you are trying to do.

Most payment gateway plugins offer a sandbox or testing mode, where you can test the payment gateway using testing credentials. The developers of GoDaddy Payments currently don’t have that type of feature at this time, but they are working to add that soon.

However, they do offer gateway logs, so let’s check this next.
1. Please go to WooCommerce > Settings > Payments > GoDaddy Payments (Manage) and enable Debug Mode, and click “Save”.
2. Then process a transaction, even if it’s for $1. We can refund it after.
3. Then go to WooCommerce > Status > Logs and look for the most recent logs for GoDaddy Payments.

When you review the logs, can you look for “response code” or “error” and let me know if you find anything?

All the best,

Hey Amber ! Thanks for the quick response !

I’ve asked GPT to look for payment failures on the log file and that’s what it said:

In the log provided, you can identify issues with GoDaddy Payments in the 401 Unauthorized error, indicating an invalid access token. Here’s a breakdown of what each segment suggests:

1. First Request (2024-10-28T02:12:57): The request was successful with a 200 OK response code, confirming the API was accessible with a valid token at this point.
2. Error Point (2024-10-28T14:13:21): This second request returned a 401 Unauthorized status, and the body message states:
   • INVALID_ACCESS_TOKEN
   • "Access token is missing or invalid." and "Token might have expired."
   This suggests that the token used in this request was either expired or invalid.
3. Token Refresh (Immediately after the error): A POST request to the token endpoint retrieves a new token successfully with a 200 OK response.
4. Resolution: The subsequent request (2024-10-28T14:13:22) reuses this new token and returns a 200 OK, indicating that the system properly handled the expired token by refreshing it.

Recommended Actions

• If these 401 errors occur frequently, implement a mechanism to check the token’s validity before each request.
• For a more proactive approach, schedule token refreshes before expiry based on the token’s lifespan (expiresIn value).

This flow shows the system self-recovering from an expired token, but if the 401 error persists at unusual frequencies, investigate the authorization handling further.

Hope to hear from you soon. Thanks !

Best,

Jones

I’ve asked GPT to extract the most important info from this log file and that’s what he said.

Here’s a summary of the key events from your log file to assist the GoDaddy Payments support team:

1. Successful Request – Initial Attempt

• Time: 2024-10-27 23:12:57 BRT
• Method: GET
• Endpoint: /businesses/0093aeb6-f74e-4ab6-8537-c6cdf1645773/stores
• Response: 200 OK
• Duration: 0.38773s
• Details: Received a successful response with status 200, confirming access to business data for the store at this timestamp. The store details (address, devices, attributes, etc.) were returned.

1. Unauthorized Request

• Time: 2024-10-28 11:13:21 BRT
• Method: GET
• Endpoint: /businesses/0093aeb6-f74e-4ab6-8537-c6cdf1645773/stores
• Response: 401 Unauthorized
• Error Code: INVALID_ACCESS_TOKEN
• Message: “Access token is missing or invalid. Token might have expired.”
• Details: The system could not authenticate due to an invalid or expired token, suggesting the need for a new access token.

1. Token Refresh Request

• Time: 2024-10-28 11:13:21 BRT
• Method: POST
• Endpoint: /token
• Request Body: grantType=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Ajwt-bearer&assertion=...
• Response: 200 OK
• New Access Token Issued: Successful token refresh, indicating the plugin automatically requested a new access token.

1. Successful Request – Retry After Token Refresh

• Time: 2024-10-28 11:13:22 BRT
• Method: GET
• Endpoint: /businesses/0093aeb6-f74e-4ab6-8537-c6cdf1645773/stores
• Response: 200 OK
• Duration: 0.34566s
• Details: The request was retried immediately after obtaining the new token and received a successful 200 OK response, retrieving the same store data.

Summary:

• The GoDaddy Payments plugin experienced an authorization issue due to an expired or invalid access token. However, it successfully performed a token refresh and retried the request immediately, receiving a successful response with the required data.
• The primary area for the support team to investigate might be ensuring tokens refresh before expiry to avoid unauthorized requests in between successful ones.
  
  Best,
  
  Jones

Hey Jones,
Thank you so much for pulling those records and also running them through GPT to obtain more information regarding the requests. I will absolutely pass on this information to my team, so I sincerely appreciate you sending that over.

Just to verify, the tokens are now working properly after the refresh, and you are able to process transactions?


All the best,

Amber

Hi Amber !

No, I am still seeing the same issues. I am not sure why there is no payment errors on the logs even though I have tried to pay multiple times with no success. The error on the console is always the same. 429 + CORS error.

I am using version Version 8.4.0 of GoDaddy Payments which I believe is the latest.

Best,

Jones.

Hey Jones,

Thank you for keeping me posted on what’s happening on your end. My sincere apologies that this is happening. I’d like to do some additional testing to better understand why this is happening so we can figure out how to fix it. I would like to have you create a support ticket next so we can assist you in more detail.

Would you mind going to WooCommerce > Settings > Payments > GoDaddy Payments and clicking the Get Help link?
Thanks ??

All the best,
Amber

Hey there,

It has been a long time since we heard from you, and I’m hoping you were able to reach out to us via a support ticket. I’m going to mark this topic as resolved.

If you’re still experiencing issues please take a look at our FAQs for more information and create a new thread if you have further questions.

Thanks,
Amber