Field and Reply Codes * ** Result Status Code * Result Status Code ResultDescription 0 N/A (Approved) -1 Timeout waiting for response. Try again -3 Hot card -4 Denied -5 Please call -6 Card Address Failure -7 Card Security Code Failure -8 Card Type not accepted -9 Unable to process the transaction -11 Invalid Amount -12 Invalid Budget Period -14 Invalid Card Number -15 Invalid Track2 -16 Invalid Expiry Date/Card Period -18 Invalid Authorisation code -255 * Unknown Error * Recon Status * * VALUE* * DESCRIPTION* "-1" Unreconciled - The reconciliation process for this transaction has not taken place yet. "0" Reconciliation has taken place and the result code accurately depicts the status of the transaction "1" Reconciliation has taken place and the transaction could not be found. "2" Reconcil

Recurring Transaction Processing * ** Recurring transactions are transactions that are processed by the same merchant to the same cardholder for the same services on an ongoing basis and are typically insurance, utility or telecommunications charges. With the advent of PCI the security and storage of sensitive card data (PAN, Expiry etc) requires that merchants take far more care of the data and perform annual audits of their IT infrastructure. The iVeri RecurringDebit transaction is designed to alleviate some effort that merchants have to put into place in order to conform to PCI DSS standards. Essentially what the solution entails is that instead of the merchant storing the PAN itself, the merchant must store a transaction identifier that refers to the PAN and it is this identifier that

Field Justification * ** All Fields are justified in the following manner:- Numeric Fields are pre-pended with 0's to the full width of the format Alphanumeric Fields are left justified and ' ' (spaces) appended to the full width of the format A* means an unspecified length field - we read to the end of the line.

Batch Processing Fixed Format Specification * **

Recurring Transaction Processing * ** Recurring transactions are transactions that are processed by the same merchant to the same cardholder for the same services on an ongoing basis and are typically insurance, utility or telecommunications charges. With the advent of PCIDSS, the security and storage of sensitive card data (PAN, Expiry etc) requires that merchants take far more care of the data and perform annual audits of their IT infrastructure. The iVeri Recurring Debit transaction is designed to alleviate some effort that merchants have to put into place in order to conform to PCI DSS standards. Essentially what the solution entails is that instead of the merchant storing the PAN itself, the merchant must store a transaction identifier that refers to the PAN and it is this identifier

What is New?* Support of PocketPos Transactions – functionality which allow merchants to use their compatible mobile phones as payment acceptance devices has been added.  Compatible with Android 7.0 and above*

What is New?* Support of Tap on Phone Transactions – functionality which allow merchants to use their compatible mobile phones as payment acceptance devices has been added.  Compatible with Android 7.0 and above* *

Introduction: *** Google Pay™* is a digital wallet service from Google that is expanding into e‑commerce to streamline online and in-app transactions. That allows customers to use payment cards saved to their Google Account to pay online without re-entering card details*. In essence, Google Pay functions as a secure intermediary: when a customer checks out with Google Pay, the system provides the merchant with a tokenised version of the customer’s card data instead of the actual card number. What is Google Pay in E‑Commerce? *** In the context of e-commerce, Google Pay* serves as a digital wallet checkout option* that lets customers pay on websites or mobile apps using payment cards saved to their Google account. When a customer uses Google Pay on an e-commerce site, Google Pay provides th