Hi @abdulwahid1,
Thanks for contacting SkyVerge about our GoDaddy Payments plugin. I’m sorry that you’re seeing Bad Request errors when checking out.
I would like to get some additional information so I can best assist. Can you please let me know if the error only says “Bad Request”, or if it gives additional context you could send over to me?
Cheers,
Kayla
On the checkout page its only bad request and when i see inside the order notes from dashboard its says: GoDaddy Payments Payment Failed (Bad Request) Order status changed from Pending payment to Failed.
Here are the more error when i see on the networks tab below are the error I get:
{
“code”: “woocommerce_rest_checkout_process_payment_error”,
“message”: “Bad Request”,
“data”: {
“status”: 400
}
}
and Also can you please provide me the link where i can Copy your Application ID and Private Key in the Poynt Collect API Settings section beacause https://poynt.godaddy.com/ This Link is not working
Hi @abdulwahid1,
Thank you for getting back to me! The Bad Request message alongside a 400 error can be an indicator of the GoDaddy Payments account having an invalid status for processing.
I’d like to ask that you reach out to the GoDaddy Payments team directly so that they can ensure your profile is all set for processing and can fix any settings that may need to be adjusted. You can reach out to them here: https://www.godaddy.com/help/contact-us
Those settings would be found on this page under Poynt Collect API Settings. Can you please check if the direct link to that page works for you?
Cheers,
Kayla
Thank you for your time, Kayla. I did contact GoDaddy support and had them talk on the call, but they said everything is fine from their end. I also have another question: Does GoDaddy Payments only work with GoDaddy Managed WordPress Hosting, or can it run on any server, inside or outside the US? By the way, that Poynt link works for me.
Good Day,
Abdul Wahid
Hi @abdulwahid1,
Thank you for getting back to me! I appreciate your patience over the weekend and apologize for the delay in my reply.
I’m happy to hear that the GoDaddy Payments team was able to confirm your account is properly set up and that the Poynt link I sent over worked for you! GoDaddy Payments is meant for use in the United States or Canada, so use for transactions outside of that could cause flagged transactions and declines. Can you please confirm that the cards you are testing with align with your GoDaddy Payments account (whether it’s a US or Canada account)?
Cheers,
Kayla
Hi @kaylaskyverge,
Yes, The card we are using for testing is from the US. I appreciate you for replying me again, but you didn’t me answer my question, My question was:
Does GoDaddy Payments Plugin only work with GoDaddy Managed WordPress Hosting, or can it run on any server, inside or outside the US?
Good Day,
Abdul Wahid
Hi @abdulwahid1,
Thank you for getting back to me! I apologize for that oversight; GoDaddy Payments is pre-installed on the Managed Hosting for WordPress plans, however, you can use this plugin so you can use GoDaddy Payments as a processor on another server either with GoDaddy or another hosting provider. It would be recommended to use a server within the region you are approved to use GoDaddy Payments in.
Can you please let me know if that helps clear things up?
Cheers,
Kayla
Hello @kaylaskyverge ,
Thank you for being here.
My client’s website is currently hosted on litespeed servers located in the Netherlands. On this server, the Godaddy Payments plugin was not pre-installed, so I installed it from the WordPress Plugin library.
Could the issue with the payments processing be related to the servers being located outside the US? The card I am currenly using for testing is a US card.
Best Regards,
Abdul Wahid
Hey @abdulwahid1,
Thanks for getting back to me! The server being in the Netherlands alone shouldn’t create the issue as long as the business is US-based.
Since the account itself is set up correctly per the GoDaddy Payments team, let’s dig into the technical side to find out what’s causing this “Bad Request” error. The 400 error could be related to how the plugin is communicating with the payment gateway.
Could you try these troubleshooting steps?
- Enable Debug Mode to capture more detailed error information:
- Go to WooCommerce > Settings > Payments > GoDaddy Payments
- Enable the Debug Mode setting
- Save changes
- Attempt another test transaction so the error gets logged
- Check the debug logs under WooCommerce > Status > Logs and look for the GoDaddy Payments log file
- Share the relevant log entries – Since this is a public forum, please copy the error messages but remove any sensitive information like names, addresses, or card details before posting
The logs should give us a more specific error message that can point us in the right direction. Sometimes the generic “Bad Request” message hides a more specific issue that only shows up in the debug logs.
Let me know what you find, and we’ll go from there!
Cheers,
Kayla
Hi @abdulwahid1,
I wanted to follow up on the previous message regarding our GoDaddy Payments plugin. Were you able to enable debug mode and review the logs from a test purchase? I’m happy to help with any questions!
Hope you have a great day!
All the best,
Kayla
Greeting @kaylaskyverge ,
I’m really sorry for the late response from my end. Thank you so much for still opening this conversation.
Below are the error I Found inside poynt_credit_card logs:
CONTEXT: {"_legacy":true}
2026-04-10 Notice Response
code: 400
message: Bad Request
headers: Array
(
[date] => Fri, 10 Apr 2026
[content-type] => application/json;charset=UTF-8
[content-length] => 218
[poynt-request-id] => ******
[x-request-id] => ******
[poynt-build-info] => 1.4.535
[instance-id] => poynt-fargate/******
[poynt-error-code] => CARD_VERIFICATION_FAILED
)
body: {"code":"CARD_VERIFICATION_FAILED","httpStatus":400,"message":"The card data provided is invalid or is not verifiable.","developerMessage":"Card Verification failed.","requestId":"*****"}
CONTEXT: {"_legacy":true}
2026-04-10 Notice Response
code: 401
message: Unauthorized
headers: Array
(
[date] => Fri, 10 Apr 2026
[content-type] => application/json;charset=UTF-8
[content-length] => 229
[poynt-request-id] => ******
[x-request-id] => *********
[poynt-build-info] => 1.4.535
[instance-id] => poynt-fargate/******
[poynt-error-code] => INVALID_ACCESS_TOKEN )
body: {"code":"INVALID_ACCESS_TOKEN","httpStatus":401,"message":"Access token is missing or invalid.","developerMessage":"Access token is not a valid token. Token might have expired.","requestId":"*****"}
Hope these error are helpful to you.
Best of Luck,
Abdul Wahid
Hey @abdulwahid1,
No worries at all about the delay – thank you for sharing those logs! They’re really helpful and give us a much clearer picture of what’s going on.
There are two separate errors showing up in your logs. I’d recommend addressing them in this order:
1. 401 INVALID_ACCESS_TOKEN – This one should be fixed first
This error means the plugin is having trouble authenticating with GoDaddy Payments. The access token it’s using is either expired or invalid. Here are a few things to check:
- Head to WooCommerce > Settings > Payments > GoDaddy Payments and confirm your Application ID and Private Key are entered correctly under the Poynt Collect API Settings
- If those credentials look correct, try deactivating and reactivating the GoDaddy Payments plugin – this can sometimes force the token to refresh
- Double-check that your credentials were copied directly from https://poynt.godaddy.com without any extra spaces before or after them
2. 400 CARD_VERIFICATION_FAILED – Card data could not be verified
This error means the card used during the test transaction couldn’t be validated by the processor. A couple of things worth checking:
- Could you confirm what card details you’re using for testing? Make sure the billing address entered at checkout matches exactly what’s on file with the card’s bank
- If you’re using a test card number, could you let us know which one? Some older test card numbers (like
4111 1111 1111 1111) are no longer supported and may trigger this error
The 401 token error is likely the root cause here, so getting that sorted first should help us narrow things down. Could you give those steps a try and let us know what you find?
Cheers,
Kayla
Hello @kaylaskyverge ,
I double checked Poynt Collect API Settings those are perfect, also I deactivating and reactivating the GoDaddy Payments plugin but gets same error again.
I use my client’s card for test payment of 1 dollar with the same billing address file in his bank and I’m not use test card yet at all.
Best Regards,
Abdul Wahid
Hey @abdulwahid1,
Thanks for jumping back in, and no worries at all about the delay! My name is Amber, and I’m happy to step in for Kayla.
Those logs are super helpful – great work tracking them down! Looking at the two errors, I want to build on what Kayla shared and give you a couple of additional things to try.
1. 401 INVALID_ACCESS_TOKEN – Start here
Since you’ve already confirmed the Poynt Collect API Settings look correct and you’ve tried deactivating/reactivating the plugin, the next thing worth checking is whether the credentials themselves may have been regenerated or rotated on the GoDaddy Payments side. Even if they look correct visually, they may no longer be the active set.
Could you try these steps?
- Head to https://poynt.godaddy.com and log in
- Navigate to your App settings and locate your Application ID and Private Key
- Regenerate or copy a fresh set of credentials if that option is available
- Go to WooCommerce > Settings > Payments > GoDaddy Payments and paste the new credentials in the Poynt Collect API Settings section – making sure there are no extra spaces before or after them
- Save, then attempt a test transaction again
2. 400 CARD_VERIFICATION_FAILED – A note on test cards
I also want to flag something important here: you mentioned you are not using a test card and are using your client’s real US card instead. Just so you’re aware, the Visa test card 4111 1111 1111 1111 is no longer supported for GoDaddy Payments and will trigger as fraudulent. If you do want to use a test card, the currently supported one is the MasterCard 5555-5555-5555-4444 with any future expiration date and a 3-digit CVV.
That said, since you’re using a real card, the CARD_VERIFICATION_FAILED error could be related to the 401 token issue above. Fixing the access token first may resolve both errors together.
Could you give those steps a try and let us know what you find?
Cheers!
Amber
Hello @amberskyverge ,
Hope you are doing well, thank you for having patience and sorry for the delay in response.
I’ve regenerate Poynt Collect API Settings and also deactivating and reactivate plugin, but the error is same: Bad Request. Inside poynt_credit_card logs first error is 400 CARD_VERIFICATION_FAILED and there is one new error which is given below but this time there was no error of 401 INVALID_ACCESS_TOKEN was there:
Error:
CONTEXT: {"_legacy":true}
2026-04****
code: 401
message: Unauthorized
headers: Array
(
[date] => Apr 2026
[content-type] => application/json;charset=UTF-8
[content-length] => 264
[vary] => Array
(
[0] => Origin
[1] => Access-Control-Request-Method
[2] => Access-Control-Request-Headers
)
[poynt-request-id] => ****
[x-request-id] => ****
[poynt-build-info] => 1.4.535
[instance-id] => ****
[poynt-error-code] => UNAUTHORIZED_ACCESS
)
body: {"code":"UNAUTHORIZED_ACCESS","httpStatus":401,"message":"Access not authorized for the requested resource.","developerMessage":"Unauthorized access attempt. This principal does not have access to this resource.","requestId":"****"}
I hope this will helpful to you.
Best Regards,
Abdul Wahid
-
This reply was modified 1 month, 3 weeks ago by
abdulwahid1.
