Please help to solve our problem with Visa Card Eligibility Service
Request :
POST https://sandbox.api.visa.com/visacardeligibilityservices/v1/cardeligibility/validate HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: application/json
Authorization: Basic TkcwSzhURjQwUVdHWlhFNFI2WDEyMXprX2pySmdicl9JcEdPc2RmSFFMMExFY29nQTpJTDVlTlk3SUc4aGxvcW5vMjRCNDhwdjl6S3pjcFp4NA==
Content-Length: 181
Host: sandbox.api.visa.com
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)
{
"validateRequest":{
"vendorUniqueId":"3108_TstVDPPgm2",
"correlationId":"1234567890456",
"requestTimeStamp":"5/29/2018 7:22:56 AM",
"permanentAccountNumber":"4000000000000008"
}
}
Response :
HTTP/1.1 400 Bad Request
Server: Apache
X-SERVED-BY: l73c032
X-CORRELATION-ID: 1527587482_242_97_l73c032_VDP_ARM
X-Backside-Transport: FAIL FAIL,FAIL FAIL
Cache-Control: no-cache, no-store ,no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: -1
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
Content-Security-Policy: default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';
X-Global-Transaction-ID: 1696630015
X-APP-STATUS: 400
Strict-Transport-Security: max-age=2592000;includeSubdomains
Content-Type: application/json;charset=utf-8
Content-Language: en-US
Content-Length: 180
X-Cnection: close
X-Cnection: close
Date: Tue, 29 May 2018 09:51:22 GMT
Connection: close
{"statusCode":"105","statusDescription":"Invalid request object. Please check.","CorrelationId":null,"responseTimeStamp":"5/29/2018 9:51:22 AM","eligibilityLevel":"0","cardId":"0"}
Thanks.
Solved! Go to Solution
Hi @Sergey,
Thank you for your inquiry. Can you please make sure you are using the right credentials, such as username and password?
In addition to that, the issue could also be caused by the Certificates not being sent with the request. Check File->Settings->SSL Settings and make sure the KeyStore and KeyStore Password are populated in Soap UI.
The Certificate Signing Request is a prerequisite to get your application certificate (cert.pem), which is required to establish a two-way SSL connection. Additionally, you will need a root certificate (VICA-SBX.pem) and your private key.
You have two options to generate a Certificate Signing Request (CSR):
Have Visa generate a CSR for you
Select "generate a CSR from me" when you create a new Visa Developer application. When you select this option, Visa will generate a CSR for you, and you will be prompted to save your private key file when it is downloaded through your browser. Once you save your private key, go to your Visa app page and download your client certificate (cert.pem), as well as your root certificate (VICA-SBX.pem). You will then have everything you need to create a key store.
Generate your own CSR
You can choose to create your own CSR. The Visa Developer Getting Started Guide provides detailed steps on how to generate CSRs: https://developer.visa.com/vdpguide#twowayssl. Please note that you have to fill out all required fields in your Certificate Request. Also, note that the organization name and unit fields do not accept punctuation characters – your CSR will be deemed invalid if you use these characters. Once you have a CSR file, go ahead and create a Visa app, choose "Submit my own CSR", and upload your CSR file. During the CSR creation process, take note of the file containing your private key. Once you upload your CSR, go to your Visa app page, and download your client certificate (cert.pem), as well as your root certificate (VICA-SBX.pem). You will then have everything you need to create a key store.
Continuing to the Key Store
Once you have a private key and two certificate files in your local directory, you will need to combine them into a key store. You can decide whether to use Java Key Store (JKS) or PKCS (P12) key store, depending on what your development environment requires. There are sections in “getting started” ->“Using two-way SSL” (https://developer.visa.com/vdpguide#twowayssl), that describe how to create each type of key store, please follow those steps. Note, that the root certificate is not needed for a P12 file, you can create a P12 file out of two files: private key and cert.pem
If you are still getting an error please provide more information on the error you have received. Please send the response request of the error received, screenshot and the Correlation ID.
Below are the steps to get the Correlation ID using a Google Chrome browser.
1>Open Chrome menu.
2>Click on More tools then Developer tools.
3>Check the box to Preserve Log for the Network Tab.
4>Then try to click on the add API link.
5>You can find the Correlation ID in the network log for add API call.
Please perform these steps and let me know your findings.
Can you please make sure you are using the right credentials, such as username and password?
In addition to that, the issue could also be caused by the Certificates not being sent with the request. Check File->Settings->SSL Settings and make sure the KeyStore and KeyStore Password are populated in Soap UI.
Yes, HellowWorld completed successfully through SoupUI :
But Card Eligibility return an error :
Hi @Sergey,
Therefore, please start off by seeing if this could be a username and password validation issue. Please ensure that a correct username/password is entered in the SOAPUI basic auth screen and the raw request contains “Authorization: Basic XXXXXXXXXX” header.
Therefore, please start off by seeing if this could be a username and password validation issue. Please ensure that a correct username/password is entered in the SOAPUI basic auth screen and the raw request contains “Authorization: Basic XXXXXXXXXX” header.