Re: Response code 200 instead of 402 in PAR Inquire API sandbox

Vital
New Contributor

Response code 200 instead of 402 in PAR Inquire API sandbox

Hi,

I'm checking error case from the Test data and it should return code 402 but I'm getting 200.

Is it just sandbox issue and in prod I'll get the documented code?

 

Best Regards,

Vital

playground_200.png 

6 REPLIES 6
SLi
Visa Developer Support Specialist
Visa Developer Support Specialist

Re: Response code 200 instead of 402 in PAR Inquire API sandbox

Hi @Vital,

I am checking with our internal team and will get back to you with an update as soon as I have one. Thanks.


Best,
Stacey

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

Re: Response code 200 instead of 402 in PAR Inquire API sandbox

Hi @Vital,

Thanks for your patience. A member from our CEMEA team will reach out to provide a workaround. Please let us know if you have any further questions. Thanks.


Best,
Stacey

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

Re: Response code 200 instead of 402 in PAR Inquire API sandbox

I am also getting this issue, as asked in the original post is this an API change or a bug in the test sandbox?

SLi
Visa Developer Support Specialist
Visa Developer Support Specialist

Re: Response code 200 instead of 402 in PAR Inquire API sandbox

Hi @dhn_vix,

 

I checked and the PAR Inquiry API is working fine in Sandbox. Please see below for sample request and response. 

 

End Point https://sandbox.api.visa.com/par/v1/inquiry
Method POST
Request
{
"clientId": "0123456789012345678901234567999",
"correlatnId": "0123456789012345678901234567000",
"primaryAccount": "1234567898XXXXXX"
}


Response
{
"paymentAccountReference": "11111111111111111111111111111111",
"paymentAccountReferenceCreationDate": "18033",
"primaryAccount": "1234567898XXXXXX"
}


Response Header
Status Code: 200 OK
Server : nginx
Date : Tue, 05 Oct 2021 03:21:22 GMT
Content-Type : application/json;charset=UTF-8
Content-Length : 721
Connection : keep-alive
X-SERVED-BY : l55c017
X-CORRELATION-ID : 1633404082_571_1229117697_l55c017_VDP_WS
X-APP-STATUS : 200
Cache-Control : no-cache, no-store, must-revalidate
Pragma : no-cache
Expires : 0 ,-1
encrypted : true
Content-Language : en-US
X-Frame-Options : SAMEORIGIN
X-XSS-Protection : 1; mode=block
X-Content-Type-Options : nosniff
X-XSS-Protection : 1; mode=block
X-Content-Type-Options : nosniff
Strict-Transport-Security : max-age=31536000;includeSubdomains;always

 

If you are getting an error, please share below details so we can investigate the issue.

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

 


Best,
Stacey

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

Re: Response code 200 instead of 402 in PAR Inquire API sandbox

Hi Stacey

 

Thanks for your prompt response. The issue is not with responses that have a PAR, I have these working fine.

The issue is with responses where the PAR does not exist. When I send the test case with card value 0234567898XXXXXX. For this I do get the error json, but rather than getting a status of 402 as per the docs, I get a status code of 200.

 

I just wanted to confirm that if the PAN has no PAR will we receive a status of 402 as per the docs, or 200 as I am currently receiving from the sandbox?

 

Cheers

Dean

SLi
Visa Developer Support Specialist
Visa Developer Support Specialist

Re: Response code 200 instead of 402 in PAR Inquire API sandbox

Hi @dhn_vix,

 

Thank you for clarifying. This is a known issue. The sandbox has not been provisioned with data for the error scenario. So it always return 200 OK response. When you are ready to promote your project to the higher environment, you will receive the correct response code.

 

Can you please send an email to developer@visa.com and let us know your project name and the country you are launching your app? I will check with our region support team to see if there's a workaround. 

 

 

 


Best,
Stacey

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