Visa Developer Community

Regular Contributor

Bad Request 400 Error

I got rid of 400 (Unauthorised errors)


For over 12hrs i keep getting 400 Bad Requests while doing sandbox tests

My Headers are Perfect ,Aunthentication is Very okay

But i just cant Explain why this Error Keeps Coming


I Badly Need Help


"cardAcceptor":{"address":{"country":"USA","county":"San Mateo","state":"CA","zipCode":"94404"},"idCode":"CA-IDCode-77765","amount":null,
"name":"Visa Inc. USA-Foster City","terminalId":"TID-9999"}
"addressVerificationData":{"street":"Kampala Road","postalCode":"256"},"pointOfServiceData":null}

Visa Dev Moderator

Re: Bad Request 400 Error

Hi @ezamarichard,


Oh, I see you're working with Visa Direct APIs but before taking a deep dive into your inquiry, can you please provide confirmation that you've read the Visa Direct documentation via this link -  


There's an important note in the first few paragraphs of the Visa Direct documentation, that discuss the requirements to use Visa Direct and it's shaded in yellow.


After you've read the documentation and if you meet the requirements shaded in yellow, then please fill out the Visa Direct Program Implementation Questionnaire, and submit to the email address listed on that form.


Was your question answered? Don't forget to click on "Accept as Solution" to help other devs find the answer to the same question.


Regular Visitor

Re: Bad Request 400 Error

How to Fix the 400 Bad Request Error
Check for errors in the URL. The most common reason for a 400 Bad Request error is because the URL was typed wrong or the link that was clicked on points to a malformed URL with a specific kind of mistake in it, like a syntax problem.
Important: This is most likely the problem if you get a 400 Bad Request error. Specifically, check for extra, typically non-allowed, characters in the URL like a percentage character. While there are perfectly valid uses for something like a % character, you won't often find one in a standard URL.
Clear your browser's cookies, especially if you're getting a Bad Request error with a Google service. Many sites report a 400 error when a cookie it's reading is corrupt or too old.
Clear your DNS cache, which should fix the 400 Bad Request error if it's being caused by outdated DNS records that your computer is storing. Do this in Windows by executing ipconfig /flushdns from a Command Prompt window.
Important: This is not the same as clearing your browser's cache.
Clear your browser's cache. A cached but corrupt copy of the web page you're trying to access could be the root of the problem that's displaying the 400 error. Clearing your cache is unlikely the fix for the majority of 400 bad request issues, but it's quick and easy and worth trying.

While this is not a common fix, try troubleshooting the problem as a 504 Gateway Timeout issue instead, even though the problem is being reported as a 400 Bad Request.
In some relatively rare situations, two servers may take too long to communicate (a gateway timeout issue) but will incorrectly, or at least unhelpfully, report the problem to you as a 400 Bad Request.
If you're uploading a file to the website when you see the error, chances are the 400 Bad Request error is due to the file being too large, and so the server rejects it.
If the 400 error is happening on nearly every website you visit, the problem most likely lies with your computer or internet connection. Run an internet speed test and check it with your ISP to make sure everything is configured correctly.
Contact the website directly that hosts the page. It's possible that the 400 Bad Request error actually isn't anything wrong on your end but is instead something they need to fix, in which case letting them know about it would be very helpful.
See our Website Contact Information list for ways to contact a number of popular sites. Most sites have social network contacts and sometimes even telephone numbers and email addresses.
Tip: If an entire site is down with a 400 Bad Request error, searching Twitter for #websitedown is often helpful, like #facebookdown or #gmaildown. It certainly won't contribute anything to fixing the issue, but at least you'll know you're not alone!
If nothing above has worked, and you're sure the problem isn't with your computer, you're left with just checking back later.
Since the problem isn't yours to fix, revisit the page or site regularly until it's back up.