Re: Unable to obtain a real response from the Payment Eligibility API

Solved! Go to solution
VinceC
Regular Visitor

Unable to obtain a real response from the Payment Eligibility API

Hi,

 

I have set up my SSL with my VDP and can confirm that the connection is working. However, by using the sample data provided on the Payments API page for Payments Eligibility, I can't get a proper response back from the validateEligibility API. I get this response from the API:

 

{"errorMessages": [" Header Bank Id's Bic and Debtor Bank Bic do not match."]}

 

I'm using SoapUI to test, below is the exact JSON payload I am sending. I'm not sure what this 'Header Bank Id's Bic' is referring to.

{
"debtorBankBic": "VISAUSVDXXX",
"creditorBankBic": "VISAUS11",
"debtorIBAN": "GB60GBRP12345612345678",
"creditorIBAN": "GB94VISA12345623456789",
"settlementCurrency": "USD",
"settlementAmount": 1
}

 

Thanks,

Vince

5 REPLIES 5
API_Products
Visa Developer Support Specialist

Re: Unable to obtain a real response from the Payment Eligibility API

Hey @VinceC,

 

I'm happy to help you resolve the issue that you're experiencing. Please provide the following information, and I'd be happy to help investigate:

1. End Point
2. Request Header
3. Request Body
4. Response Header (include the x-correlation-id)
5. Response Body

Using SoapUI, you can find the x-correlation-id in the Raw Tab of the response header.

 




Thanks,

Tee



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

VinceC
Regular Visitor

Re: Unable to obtain a real response from the Payment Eligibility API

Hi Diana,

Here are the details:

 

1. End Point:

https://sandbox.api.visa.com/visab2bconnect/v1/payments/validateEligibility

2. Request Header: 

POST https://sandbox.api.visa.com/visab2bconnect/v1/payments/validateEligibility HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: application/json
Authorization: Basic TzlKUVcwRThWOVVGRDI2NEExSEUyMUFzTktuWHhMTGJCV1hhTm1tN0d3X2l1ZWFaZzpOOVFXTmI4TFMwUFFCRDZubUt5dm9t
Content-Length: 199
Host: sandbox.api.visa.com
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.1.1 (java 1.5) 

3. Request Body: 

{
"debtorBankBic": "VISAUSVDXXX",
"creditorBankBic": "VISAUS11",
"debtorIBAN": "GB60GBRP12345612345678",
"creditorIBAN": "GB94VISA12345623456789",
"settlementCurrency": "USD",
"settlementAmount": 1
}

4. Response Header (include the x-correlation-id): 

HTTP/1.1 401 Unauthorized
Server: nginx
Content-Type: application/json;charset=UTF-8
Content-Length: 77
X-SERVED-BY: l73c018
X-CORRELATION-ID: 1572572812_148_554730069_l73c018_VDP_WS
X-Backside-Transport: FAIL FAIL,FAIL FAIL
X-OPNET-Transaction-Trace: a2_d74241a2-4da6-4d9c-a07d-82dea43f5950,a2_d74241a2-4da6-4d9c-a07d-82dea43f5950
X-APP-STATUS: 401
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=2592000;includeSubdomains
Cache-Control: no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Thu, 01 Jan 1970 00:00:00 GMT ,-1
Content-Security-Policy-Report-Only: default-src 'self' https://*.v.me https://*.visa.com;script-src 'self' 'unsafe-inline' 'unsafe-eval'  https://*.visa.com https://*.v.me;img-src 'self' https://*.v.me https://*.visa.com https://*.unica.com https://ad.doubleclick.net;style-src 'self' 'unsafe-inline' https://*.visa.com;object-src  https://*.v.me https://*.visa.com data:;report-uri /logging/logCSPReport;
X-Content-Security-Policy-Report-Only: default-src 'self' https://*.v.me https://*.visa.com;script-src 'self' 'unsafe-inline' 'unsafe-eval'  https://*.visa.com https://*.v.me;img-src 'self' https://*.v.me https://*.visa.com https://*.unica.com https://ad.doubleclick.net;style-src 'self' 'unsafe-inline' https://*.visa.com;object-src  https://*.v.me https://*.visa.com data:;report-uri /logging/logCSPReport;
X-WebKit-CSP-Report-Only: default-src 'self' https://*.v.me https://*.visa.com;script-src 'self' 'unsafe-inline' 'unsafe-eval'  https://*.visa.com https://*.v.me;img-src 'self' https://*.v.me https://*.visa.com https://*.unica.com https://ad.doubleclick.net;style-src 'self' 'unsafe-inline' https://*.visa.com;object-src  https://*.v.me https://*.visa.com data:;report-uri /logging/logCSPReport;
X-Global-Transaction-ID: 69536f0d5dbb8e8c06a85455
Date: Fri, 01 Nov 2019 01:46:52 GMT
Connection: close

5. Response Body: 

{"errorMessages":[" Header Bank Id's Bic and Debtor Bank Bic do not match."]}

 

Thanks,

Vince

API_Products
Visa Developer Support Specialist

Re: Unable to obtain a real response from the Payment Eligibility API

Hey @VinceC,

 

I'm happy to help! So I did some sandbox testing today for B2B Connect and I was able to get successful results for B2B Connect Validate Payment Eligibility. Please see my successful Request, Response, Response Header and its related screenshots below.

 

Also, when you create a test App in our sandbox you'll receive test data in your App. The test data for your Visa Developer application is available in the Dashboard under test data in the left side menu, this will ensure that you're using valid data that has been provisioned for specific scenarios. You'll basically have a table per API that is split into the Request and Response sections and the values on the Request section are meant to be populated in the payload with the intention of obtaining results specified in the Response section.
 
Sandbox data is limited to what is provided in the Test Data tables and is not integrated to the Visa Network and you cannot test real data in sandbox. Per the screenshot below, as you can see I used my own Test Data that I found in my project app.

 

Please try to test again and share your results with us.

20190521 Test Data.jpg

 

20191104 B2B Connect validateEligibility Test Data.png

 

 

Request

 

{
"debtorBankBic": "CITIGB2L",
"creditorIBAN": "GB94VISA12345623456789",
"settlementCurrency": "JPY",
"debtorIBAN": "GB60GBRP12345612345678",
"settlementAmount": 100,
"creditorBankBic": "CITIGB3L"
}

 

 

Response

 

{
"debtorEnterpriseId": "V-CAN-CAD-00000876-100007640-001",
"responseList": [{
"reasonCode": "SU10",
"reasonDesc": " Payment eligibility validation success."
}],
"creditorEnterpriseId": "V-CAN-CAD-00000876-100007640-001"
}

 

 

Response Header

 

Status Code: 200 OK
Server : nginx
Content-Type : application/json;charset=UTF-8
Content-Length : 210
X-SERVED-BY : l55c016
X-CORRELATION-ID : 1572905721_101_1380324530_l55c016_VDP_WS
X-Backside-Transport : OK OK,OK OK
X-OPNET-Transaction-Trace : a2_ce628ced-46da-4240-a082-4ccd26f95efa,a2_ce628ced-46da-4240-a082-4ccd26f95efa
X-APP-STATUS : 200
X-Frame-Options : SAMEORIGIN
X-XSS-Protection : 1; mode=block
X-Content-Type-Options : nosniff
Strict-Transport-Security : max-age=2592000;includeSubdomains
Cache-Control : no-cache, no-store, must-revalidate
Pragma : no-cache
Expires : Thu, 01 Jan 1970 00:00:00 GMT ,-1
Content-Security-Policy-Report-Only : default-src 'self' https://*.v.me https://*.visa.com;script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.visa.com https://*.v.me;img-src 'self' https://*.v.me https://*.visa.com https://*.unica.com https://ad.doubleclick.net;style-src 'self' 'unsafe-inline' https://*.visa.com;object-src https://*.v.me https://*.visa.com data:;report-uri /logging/logCSPReport;
X-Content-Security-Policy-Report-Only : default-src 'self' https://*.v.me https://*.visa.com;script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.visa.com https://*.v.me;img-src 'self' https://*.v.me https://*.visa.com https://*.unica.com https://ad.doubleclick.net;style-src 'self' 'unsafe-inline' https://*.visa.com;object-src https://*.v.me https://*.visa.com data:;report-uri /logging/logCSPReport;
X-WebKit-CSP-Report-Only : default-src 'self' https://*.v.me https://*.visa.com;script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.visa.com https://*.v.me;img-src 'self' https://*.v.me https://*.visa.com https://*.unica.com https://ad.doubleclick.net;style-src 'self' 'unsafe-inline' https://*.visa.com;object-src https://*.v.me https://*.visa.com data:;report-uri /logging/logCSPReport;
X-Global-Transaction-ID : 1adcbd165dc0a2f911f498cf
Date : Mon, 04 Nov 2019 22:15:21 GMT
Connection : keep-alive

 

20191104 B2B Connect validateEligibility 200OK.png

 

 




Thanks,

Tee



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

VinceC
Regular Visitor

Re: Unable to obtain a real response from the Payment Eligibility API

Thanks Diana, this resolves my queries here. I'm able to simulate the same with the given test data.

 

Vince

API_Products
Visa Developer Support Specialist

Re: Unable to obtain a real response from the Payment Eligibility API

Hey @VinceC,

 

Great to hear your issues are resolved! Have a wonderful weekend!

 




Thanks,

Tee



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