Re: DPS Card Services API return 503

sayanbardhan
Regular Visitor

DPS Card Services API return 503

Trying to retrieve the account balance for test cards provided under DPS card services. But "Retrieve account balance for account ID and card ID" keep returning http 503 response. Also tried generating the card ID using POST "Create card ID for a PAN" to no success. Certificates and authentication is configured properly since hello world is returning results.

https://sandbox.api.visa.com/vdp/helloworld

 

4 REPLIES 4
DianaTran-Yee
Visa Developer Support Specialist

Re: DPS Card Services API return 503

Hey @sayanbardhan,

 

I'm happy to help you resolve the issue. To continue, please provide the following information:

1. Endpoint
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,

Diana



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

sayanbardhan
Regular Visitor

Re: DPS Card Services API return 503

end point: https://sandbox.api.visa.com/dcas/cardservices/v1/cards

request body: {"cardIdModel": [{"pan": "4169334953890037","lookUpBalances": true}]}

request headers: 

Authorization Basic T1ZWNTNSV1g1Rk84U1JPNUZWRVMyMUZYMmhJUjVkb1ZYRkMwVnFfMk8xYVdmU3F5czpEMlIzQzhGV3ZlUTdxeA==
Cache-Control no-cache
Postman-Token <calculated when request is sent>
Content-Type application/json
Content-Length <calculated when request is sent>
Host <calculated when request is sent>
User-Agent PostmanRuntime/7.25.0
Accept */*
Accept-Encoding gzip, deflate, br
Connection keep-alive

 

 

response headers:

KEY VALUE
Server nginx
Date Tue, 26 May 2020 21:33:02 GMT
Content-Type text/html;charset=us-ascii
Content-Length 326
Connection keep-alive
X-SERVED-BY l55c016
X-CORRELATION-ID 1590528781_960_441667327_l55c016_VDP_WS
X-Backside-Transport FAIL FAIL,FAIL FAIL
X-Global-Transaction-ID 458484be5ecd8b0e0a4d74ef
X-APP-STATUS 503
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 -1

X-Cnection close

 

response body:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Service Unavailable</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Service Unavailable</h2>
<hr><p>HTTP Error 503. The service is unavailable.</p>
</BODY></HTML>

DianaTran-Yee
Visa Developer Support Specialist

Re: DPS Card Services API return 503

Hey @sayanbardhan

 

Are you using test data from your project app? The test data for your Visa Developer application is available in the Dashboard under test data in the left navigation, this will ensure that you are using valid data that has been provisioned for specific scenarios. You will 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.
20190905 Test Data.png 
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. 

 




Thanks,

Diana



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

DianaTran-Yee
Visa Developer Support Specialist

Re: DPS Card Services API return 503

Hey @sayanbardhan,

 

You can also refer to our Visa Developer Error Code page - https://developer.visa.com/pages/visa-developer-error-codes

 

HTTP STATUS: SERVICE UNAVAILABLE

HTTP CODE: 503

CAUSE/RESOLUTION: The Visa system is currently unable to handle the request due to a temporary overloading or maintenance of the server. Please contact Visa Support at developer@visa.com if the issue persists.

 




Thanks,

Diana



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