I am using the exact same request is there on API reference Page. https://developer.visa.com/capabilities/visa_direct/reference
POST URL: https://sandbox.api.visa.com/visadirect/fundstransfer/v1/pullfundstransactions
Header :
Accept: application/json,application/octet-stream
Authorization: {base64 encoded userid:password}
In place of 'base64 encoded userid:password' i am using 'Authorization' generated in raw request during connection to Two-Way SSL. Right now i have juts tested the hello world thing. It works just fine . so i dont think there is any problem in mu username or password or my certificates. I think i need help regarding the correct input format of Authorizaion in the request header.
BODY:
{
}
Response :
{"responseStatus": {
"status": 401,
"code": "9123",
"severity": "ERROR",
"message": "Expected input credentials were not present",
"info": ""
}}
Thank You.
Solved! Go to Solution
Hi @malviyaash18,
The error "Expected input credential was not present" usually occurs when the credentials used are invalid. Can you please confirm if you are using valid credentials?
Visa Direct uses Two Way SSL for authentication. Please test the connectivity and credentials by following the Two-Way SSL (Mutual Authentication) guide: https://developer.visa.com/vdpguide#twoway_ssl_mutual_authentication
If you continue to get this issue, please provide us screenshots of your SoapUI setup so we can further investigate the issue.
Please also refer to this community forum post link for additional troubleshooting steps that we have provided: https://community.developer.visa.com/t5/General/Always-getting-quot-Expected-input-credential-was-no...
Hi @malviyaash18,
Thanks for sharing the screenshots, it's very helpful. The SoapUI setup looks correct. The Funds Transfer API has an option to turn on MLE. Can you please confirm whether you have MLE turn on or off for this API? Also, when you first created your project, did you upload your own CSR or did you have it auto-generated. Thanks.
MLE is turned on. I have use the auto-generated CSR.
Hi @malviyaash18,
Ok, if MLE for the Funds Transfer API is turned on, then you'll need to encrypt the payload with your MLE credentials, otherwise you will get the token validation error.