The following is a breakdown of required Client APIs. The parameters defined in the Message Format section will be required for each function defined below. These parameters are utilized for validation to access the system. In addition, the MSGID will need to be a unique counter for each transaction. AuthENGIN API returns responses in two formats. The first format uses name value Pairs that are separated by an Ampersand (&).
E.g.: P1=000&P2=Assign Card-to-Card Holder successful.
AE CardAPI also uses XML to respond to certain requests. Some of the calls like transaction history can return multiple rows of data therefore they can be better displayed using XML. E.g.:
<TransferInfo>
<TransferAmount>200</TransferAmount>
<TransferBaseCurrency>840</TransferBaseCurrency>
<TransferFee>100</TransferFee>
<TransferToCardNumber>################</TransferToCardNumber>
An API response contains error code when the transaction is not successful. There is a list of error codes, which are returned part of an erroneous response at the end of the document.