API auth 9611

[white]

Hello,

While testing the 'Visa Payments Processing' sandbox I am getting 403 - Auth failed, with code 9611. Upon searching previously asked question for this error code, the answer was that account is not activated. Additionally, I've successfully tested the 'helloworld' two way SSL example - getting 200. G the 403 response comes upon requesting "https://sandbox.api.visa.com/pav/v1/cardvalidation". Thank you very much in advance!

[API_Products · Accepted solution]

Hey @white,

Can you please confirm if you're testing Visa Payments Processing or Payment Account Validation? You mentioned both APIs in your post. I just ran a Payment Account Validation test and I got a successful 200 OK result. Please see my successful request and response payloads below and refer to screenshot. 

For error codes and resolution, please visit this link - https://developer.visa.com/pages/visa-developer-error-codes

HTTP STATUS: FORBIDDEN

HTTP CODE: 403

CAUSE/RESOLUTION: 

The 403 (Forbidden) HTTP Status code indicates that this project does not have permission to access the requested resource. This can happen if you are trying to invoke API request for a resource that is not part of your project e.g. if you have created a project with Visa Direct Product but are trying to use the same credentials to access Visa Consumer Transaction Controls.

Check for the following:

• You are using a project and the credential for the project which includes the API being accessed.
• Create a project and receive sandbox credentials for the API’s being called.
• Add the API being called (if not already included) to the project with credentials that are being used.

Payment Account Validation VDC Playground Sandbox Test Results

Request

{
"systemsTraceAuditNumber": "743720",
"cardCvv2Value": "672",
"cardAcceptor": {
"address": {
"country": "PAKISTAN",
"zipCode": "94404",
"city": "fostr city",
"county": "CA",
"state": "CA"
},
"idCode": "111111",
"name": "rohan",
"terminalId": "123"
},
"primaryAccountNumber": "4957030000313108",
"retrievalReferenceNumber": "015221743720",
"addressVerificationResults": {
"street": "2881 Main Street Sw",
"postalCode": "T4B 3G5"
},
"cardExpiryDate": "2020-06"
}

Response

{
"cvv2ResultCode": "P",
"transactionIdentifier": 119445572196667,
"actionCode": "25",
"addressVerificationResults": "I",
"responseCode": "5"
}

Response Header

Status Code: 200 OK
Server : nginx
Content-Type : application/json;charset=UTF-8
Content-Length : 705
X-SERVED-BY : l55c018
X-CORRELATION-ID : 1583948709_215_1276114114_l55c018_VDP_WS
X-APP-STATUS : 200
X-APP-STATUS : 200
X-Backside-Transport : OK OK,OK OK
X-Global-Transaction-ID : 1adcbd165e6923a572c51157
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
encrypted : true
Content-Language : en-US
Date : Wed, 11 Mar 2020 17:45:09 GMT
Connection : keep-alive

[white]

Hello Diana,

Indeed I ment Payment Account Validation. Although I see you used it in the example, just want to verify one thing: MLE (message level encryption) is required for Payment Account Validation even on sandbox? 
Thank you very much for the help!

[swaritsharma]

Hi white,
MLE isn’t necessary for testing unless you are going to deploy the application. And as per your error 403 Auth Failed please verify that you’re using credentials of that specific APIs.

Good luck!

[API_Products]

Hey @white,

You don't have to use MLE in sandbox. Please refer to screenshot below to see that MLE is not enabled and I still get a successful result.