Hello,
When trying to test the https://sandbox.api.visa.com/vctc/customerrules/v1/consumertransactioncontrols API to register in Visa Transaction Controls, I'm getting this response:
{"metainfo":{"Description":"Bad Request","Code":400},"error":"HV000028: Unexpected exception during isValid call."}
It was working. I have done some refactor to my code, so I was testing already developed functionalities, so, I think is not error on my code, but don't know.
Thanks,
Javier
Solved! Go to Solution
Hi @JavierSivack,
The API is working on my end. Please retry and let me know how it goes.
End Point https://sandbox.api.visa.com/vctc/customerrules/v1/consumertransactioncontrols
Method POST
Request
{"primaryAccountNumber": "451417000000XXXX"}
Response Header
Status Code: 200 OK
Server : nginx
Date : Tue, 14 Sep 2021 03:43:05 GMT
Content-Type : application/json;charset=UTF-8
Content-Length : 7676
Connection : keep-alive
X-SERVED-BY : l73c018
X-CORRELATION-ID : 1631590985_330_483784879_l73c018_VDP_WS
X-APP-STATUS : 200
X-Backside-Transport : OK OK,OK OK
Cache-Control : no-cache, no-store, must-revalidate
Pragma : no-cache
Expires : -1
Accept : application/json
X-Global-Transaction-ID : 69536f0d61401a49110dbfc7
Content-Language : en-US
X-Frame-Options : SAMEORIGIN
X-XSS-Protection : 1; mode=block
X-Content-Type-Options : nosniff
Strict-Transport-Security : max-age=2592000;includeSubdomains
X-XSS-Protection : 1; mode=block
X-Content-Type-Options : nosniff
Strict-Transport-Security : max-age=31536000;includeSubdomains;always
I fixed the problem in my side. I was sending incorrect data at callingCode on defaultAlertsPreferences.
If callingCode is not numeric characters, it throw that exception.
Thanks.
Javier
Thanks for sharing @JavierSivack