Downloads *** Download for products

Enabling ABU on the Admin Portal * ** Below we will look at the step-by-step process of enabling a merchant for Automatic Billing Updater via Admin Portal. Navigation Path: To navigate to this screen, Select Applications > Update > Provider Specific. Click on the ‘Common Provider’ expansion tab. Navigate to the ‘Supplementary’ parameter and click on the expansion tab. Navigate to the ‘ABU enabled’ parameter. This parameter defaults to ‘No’. To enable ABU, untick the default value. From the dropdown, select ‘Yes’. The next parameter that needs to be populated is the ‘ABU Merchant ID’. This parameter needs to be populated with the Merchant ID. The Merchant ID is provided / supplied by the Acquirer. Untick the default value and enter the ABU Merchant ID Lastly, save the changes that you hav

Below we will look at the step-by-step process of enabling a merchant for MauCAS via the Administration Website. Navigation Path: To navigate to this screen, Select Applications > Update > Provider Specific. 1. Click on the ‘Common Provider’ expansion tab. 2. Navigate to the ‘Third Party’ parameter and click on the expansion tab. 3. Navigate to the ‘MauCAS enabled’ parameter. This parameter defaults to ‘No’. 4. To enable MauCAS, untick the default value. 5. From the dropdown, select ‘Yes’. 6. The next parameter that needs to be populated is the ‘MauCAS Merchant ID’. This parameter needs to be populated with the Merchant ID. The Merchant ID is provided / supplied by the Acquirer. 7. Untick the default value and enter the MauCAS Merchant ID. 8. Lastly, save the changes that you have captured

Enabling Merchants for Recurring transactions * ** Merchants that process recurring transactions need to be enabled as such via the Admin Portal. In the authorization message that is sent to the Acquirer, as part of the transaction process, there is specific data that indicates that a transaction is recurring, and the merchant has been enabled for recurring transactions. We will have a look at how to enable a merchant for recurring transactions via the Admin Portal. Navigation Path to this screen: Applications > Update > Provider Specific. Navigate and expand on the ‘Processing’ parameter. Scroll down to the ‘Cardholder Presence default’ parameter. The parameter is defaulted to ‘no’ Untick the default value. From the dropdown menu, select ‘Recurring transaction’ The next parameter that ne

Below is the process of how to enable MOTO transactions for a merchant on the Admin Website: Navigation Path: Applications > Update > Provider Specific. Click on the ‘Common Provider’ expansion tab as illustrated. 1. Navigate to the ‘Processing’ parameter and click on the expansion button. moto1 [1] 2. Navigate your way to the ‘Cardholder Presence Default’ Parameter. This parameter will be defaulted to ‘Not specified’. moto2 [2] 3. Untick the ‘Use Default’ tab. From the drop down, select ‘Mail/Telephone Order (single transaction)’. moto3 [3] 4. Lastly, to ensure the change has been saved, click on the ‘Update Parameters’ tab. moto4 [4] [1] /web/image/351226-55085015/moto1.png?access_token=a03576b8-fe21-4b94-b4c7-b2fe65ec31f6 [2] /web/image/351227-0b632be4/moto2.png?access_token=8d6f6399-44

Merchants that process recurring transactions need to be enabled as such via the Admin Portal. In the authorization message that is sent to the Acquirer, as part of the transaction process, there is specific data that indicates that a transaction is recurring, and the merchant has been enabled for recurring transactions. We will have a look at how to enable a merchant for recurring transactions via the Administration Website: Navigation Path: Applications > Update > Provider Specific. Click on the ‘Common Provider’ expansion tab as illustrated. 1. Navigate to the ‘Processing’ parameter and click on the expansion button. me1 [1] 2. Navigate your way to the ‘Cardholder Presence Default’ Parameter. This parameter will be defaulted to ‘Not specified’. me2 [2] 3. Untick the ‘Use Default’ tab. F

Transaction integrity can be seen as ensuring that all players within an individual iVeri transaction agree on its outcome. When a Card Holder gets his statement from his Issuer, it must correspond to his instruction to the merchant for a corresponding transaction. When transaction integrity is compromised either willfully (fraud) or unintentionally, it can result in a disputed transaction with legal impacts. Individual transactions *** Void* A Void of a previous transaction request is a command to ignore (i.e. cancel the effects of) a previous (recently submitted) transaction request. When a merchant receives a successful response for a transaction request, and thereafter “something goes wrong”, then the Merchant has the option to “void” the transaction. Examples of “something goes wrong”

Example Message Format * **

FNBBase24FNBSouthAfrica ** Log on at https://admin.aws.iveri.com/ [1] and check the provider status for FNBBase24FNBSouthAfrica. If any issues exist, contact Retail Assist. [1] https://admin.aws.iveri.com/