Understanding Third Party/Issuer Backend System Response Codes

Document ID : KB000112440
Last Modified Date : 30/08/2018
Show Technical Document Details
Introduction:
In some specific implementations, CA ACS needs to connect to 3rd party or issuer backend system to verify/send data. This call could be responded with error codes based on different scenarios. 
This document intends to explain some of the common responses/error codes in such calls.
Question:
In some specific implementations, CA ACS needs to connect to 3rd party or issuer backend system to verify/send data. This call could be responded with error codes based on different scenarios. 
This document intends to explain some of the common responses/error codes in such calls.
Environment:
Transaction Manager 7.8 and above
Answer:
Below are the few Backend response codes which will give more details about Backend issues. Admin will able to see these Response codes in Callout status field which will helps them to Understand more about the issue.


1. BACKEND[F - IOException occurred]
This could due to a cinnectivity failure between CA and bank’s backend system. 
When the cardholder attempted to register, our servers tried connecting to the Bank backend. While our systems were attempting to connect to the Bank backend, we observed connectivity errors from Bank backend systems. 

2.WebServices Failure_RemoteException while connecting Bank
These exception (Webservices Exception)occurs  while trying to connect with Bank's Bankend

3.Please find below the below details for the OTP codes mentioned in Callout status field : 
Response Code: 
00 - Success 
98 - Hand Phone number invalid 
97 - Invalid Card Number 
99 - System Error 

OTPSENT[S] --> OTP has been sent.
OTPMATCH[F] --> OTP match failed.
OTP[Y] --> OTP Matched 
OTP[N] --> OTP not matched 
OTP[EXP] --> OTP sent has been expired.
Resend[TMO] --> Resend tries maxed out 


PasswordMatch[N] --> Password do not match