Debit Card Inquiry in sandbox using test data always errors with "No Card Found"

[KJG]

Started working with Visa API this morning. I have my ssl configured and helloworld  request is successful. 

I am now working through the debitcardinquiry request /dcas/cardinquiry/v1/accounts/debitcardinquiry

using the test data designated for this request. For all combinations of directDebitAccountNumber and routingNumber test data I am getting a 404 and "No Cards Found".

Am I correct in assuming that the provided test data should result in a successful response with valid data?  

thanks

[API_Products]

Hi KJG,

To further investigate, please provide the following information:

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.

[KJG]

Thanks Diana,

I am getting similar responses for the other API calls too, 

/dcas/cardinquiry/v1/accounts/debitcardinquiry results in  "No cards found" 

/dcas/cardservices/v1/cards/{cardId}/cardstatus results in  "No card found"

I pulled the endpoints from api links that are part of my account dashboard, so they should be correct.

Here is the requested information with the authorization masked

1. End Point 

https://sandbox.api.visa.com/dcas/cardinquiry/v1/accounts/debitcardinquiry
2. Request Header

POST https://sandbox.api.visa.com/dcas/cardinquiry/v1/accounts/debitcardinquiry HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: application/json
Authorization: Basic ########################################################################################
Accept: application/json
Content-Length: 82
Host: sandbox.api.visa.com
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)
3. Request Body

{
"directDebitAccountNumber": "4XXXXXXXXXX26006",
"routingNumber": "598XXXXXX06"
}

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

HTTP/1.1 404 Not Found
Server: nginx
Content-Type: application/json
Content-Length: 130
X-SERVED-BY: l73c015
X-CORRELATION-ID: 1559042251_041_1358076184_l73c015_VDP_WS
X-Backside-Transport: FAIL FAIL,FAIL FAIL
Cache-Control: no-cache ,no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: -1
X-OPNET-Transaction-Trace: a2_c682bcf8-28c2-45af-96bd-ace25b82acb9-6648-1601
Correlation-ID: 8f0317ff-104e-4fff-a6e7-c7f028a96aa7
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: 1419771149
X-APP-STATUS: 404
Strict-Transport-Security: max-age=2592000;includeSubdomains
Date: Tue, 28 May 2019 11:17:31 GMT
Connection: close
5. Response Body

{
"resource": {"debitCards": null},
"processingTimeInMs": 16,
"receivedTimestamp": "2019-05-28 11:17:31.106",
"errors": ["No Cards Found"]
}

[KJG]

Thank You Diana,

I am getting a simimilar no card found for both the
/dcas/cardinquiry/v1/accounts/debitcardinquiry
/dcas/cardservices/v1/cards/{cardId}/cardstatus

The debitcard query has the following documentation for the 404 response code. I am assuming that the test data is fully populated and that I should received a successful
response with data

404 - Not Found: The account could not be found
404 - Routing number to Institution ID mapping Failure
404 - No Cards tied to Account
404 - No Active Cards found
404 - No Cards found

Here is the requested information with the Authorization masked

1. End Point 
https://sandbox.api.visa.com/dcas/cardinquiry/v1/accounts/debitcardinquiry

2. Request Header
POST https://sandbox.api.visa.com/dcas/cardinquiry/v1/accounts/debitcardinquiry HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: application/json
Authorization: Basic ################################################
Accept: application/json
Content-Length: 82
Host: sandbox.api.visa.com
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)
3. Request Body
{
"directDebitAccountNumber": "4XXXXXXXXXX26006",
"routingNumber": "598XXXXXX06"
}

4. Response Header (include the x-correlation-id)
HTTP/1.1 404 Not Found
Server: nginx
Content-Type: application/json
Content-Length: 130
X-SERVED-BY: l73c015
X-CORRELATION-ID: 1559042251_041_1358076184_l73c015_VDP_WS
X-Backside-Transport: FAIL FAIL,FAIL FAIL
Cache-Control: no-cache ,no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: -1
X-OPNET-Transaction-Trace: a2_c682bcf8-28c2-45af-96bd-ace25b82acb9-6648-1601
Correlation-ID: 8f0317ff-104e-4fff-a6e7-c7f028a96aa7
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: 1419771149
X-APP-STATUS: 404
Strict-Transport-Security: max-age=2592000;includeSubdomains
Date: Tue, 28 May 2019 11:17:31 GMT
Connection: close
5. Response Body
{"resource":{"debitCards":null},"processingTimeInMs":16,"receivedTimestamp":"2019-05-28 11:17:31.106","errors":["No Cards Found"]}

[API_Products]

Hi @KJG,

I will take a look and someone will reach out to you soon with an update.

[API_Products]

Hi @KJG,

Please check with the below payload and confirm back to us that it resolves the issue.

{
"routingNumber": "59777000016",
"directDebitAccountNumber": "45147844690346016",
"cardholderName": {
"lastName": "DADE",
"firstName": "JACK"
}
}

You can also try using the Test Data from VDP Dashboard --> Test Data tab. You can try using the test data from your dashboard (refer to screenshot).

[KJG]

Hello Diana,

I have been using the test data from the test tab you reference, hence my question regarding its validity.

I can confirm that the the test data that you provided is successful but it is not data from my test data tab as shown below.

Since I have similar issues with other API calls,  returning "no cards found" 

Where can I get useful test data if not from the test data tab? 

Thanks again for your assistance.

Debit Card Inquiry

---

Scenario Based Test Data (v1)

RequestResponseScenariodirectDebitAccountNumberroutingNumberHTTP Response CodedebitCards.primaryAccountNumber

Success	45603167	59800000001	200	PANs associated with the AccountNumber and InstitutionID
Success	47705678	59800000001	200	PANs associated with the AccountNumber and InstitutionID
Success	47703429	59800000001	200	PANs associated with the AccountNumber and InstitutionID
Success	47709099	59800000001	200	PANs associated with the AccountNumber and InstitutionID
Success	4XXXXXXXXXX26004	598XXXXXX04	200	PANs associated with the AccountNumber and InstitutionID
Success	4XXXXXXXXXX26005	598XXXXXX05	200	PANs associated with the AccountNumber and InstitutionID
Success	4XXXXXXXXXX26006	598XXXXXX06	200	PANs associated with the AccountNumber and InstitutionID
Success	4XXXXXXXXXX26007	598XXXXXX07	200	PANs associated with the AccountNumber and InstitutionID

[API_Products]

Hi @KJG,

Test data for DCAS API needs to be updated. I will log an incident ticket for the team to add valid test data in VDP for the DCAS API.

[KJG]

Thanks again for the assistance. I am standing up our Credit Union rest api for VISA functionality. I will be doing both debit card and VISA card api work such as inquiry, listing all cards for an account,  turn on/off cards and travel itinerary. I'll keep an eye out for the new data and start using as soon as it arrive. regards.

[API_Products]

Hi @KJG,

I'll provide you with an update when the issue is resolved.