*Registering as a merchant * ** Merchant account can be attained by registering with an acquiring bank, a list of which can be found on this page [1] [1] /knowsystem/distributors-contact-information-33

This section describes the various gateway parameters available. This is followed by a table of what input and output parameters are relevant for each action. Parameters are shown grouped according to their usage. Data Types  * ** The following key table is used for data types: Data Type * Description * A Alpha only (A-Za-z) AN Alphanumeric (a-zA-Z0-9) Base64 Base64 encryption of binary data Boolean True or False Guid Globally Unique Identifier:  {[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}\} (eg {8E51611F-E19A-4FF0-B229-6A69F42AAA62}) Hex Hex (0-9A-Fa-f) N Numeric (Positive integer) N. Digits and dots (.) (e.g's 4242........4242, 1.0) N: Digits and colons String ANPS Free format string containing: Alpha, numeric, special and padding (printable ASCII) Z P

Test File * ** Purpose *– A test batch file can be created to validate that the file format uploaded is in accordance with the iVeri Batch Specification. The test results will provide details should there be any errors within the Test file. Action: * From the main menu the user will navigate to: Batch - Test File.* Action: * The user will click on "Browse" to locate the created batch. When located on your PC (file directory), select the file, and click on Open.  Alternatively the user can drag and drop the file in the space provided. Lastly the user will click on "Submit" to upload the test file. The result of the format test of the selected batch will be displayed.

* Application Parameters * ** */ Purpose /* – This function is used to allocate application ID(s) that a User is only allowed to have access to. This application refers to specific product and what a merchant uses to process transactions through iVeri. Example below indicates that when you select a particular Application ID an Administrator can configure what functions can this user perform in a particular Application ID. If no function is associated to an Application ID, no access is granted to that user. Administrator can configure what Transaction Types a user can perform on a specific Application ID. If no Transaction Types are configured for a user, the user will be unable to process transactions for any of the Application IDs. */ Action /*: Select the product and Live Application IDs

*** Requirements *** With the API, merchants are able to generate payment requests to their clients by implementing the “DebitRequest” command and include the specific data parameters that are expected in the message request to the Gateway. The data elements required in the “DebitRequest” command are covered in the Enterprise Documentation In order to implement the DebitRuquest method, the following should be downloaded or in place. Reference the Divert Specification Guide  Reference the using the “RequestDebit” method in the Enterprise Documentation  Merchant Agreement with an acquirer with Divert as the solution which will result in a merchant profile on the Gateway

DiVert Functionality * ** The Divert API has a parameter “CreateTransactionUrl” that can be set to either “True or “False”. The value set determines how the Gateway handles and processes the message request. Scenario 1 * If CreateTransactionUrl” is set to“True” - the Gateway generates a transaction URL and makes a callback to the merchant with the URL. The merchant can then construct and format their own message, including the URL (returned by the Gateway) and distribute the message to their cardholder using either SMS|Email When the cardholder receives the messages, it will have all the particulars of the merchant, the cardholder can then click on the URL, and be redirected to a payment page wherein they can make a payment to the merchant Scenario 2* If CreateTransactionUrl is set to “Fal

3D Secure * ** 3D secure is an XML-based security protocol for online credit and debit card transactions. 3D Secure adds an authentication step for online payments, making it possible for cardholders to authenticate their online transactions with their card issuers, using a password or OTP. Benefits of using 3D secure * Reduces fraudulent debit & credit card transactions processed through online platforms Gives the merchants and acquiring bank liability protection 3D secure providers * CyberSource Bankserve 3D secure with iVeri * High: 3D secure – If a merchant is deemed high risk, the acquiring bank can set merchants on this level. Merchants that want lowest possible risk can also opt for this level. Medium: 3D secure/attempted- This option gives merchants a broader reach in the cards the

V4.139 7/2/2024 ** Release Notes Overview The release notes provided in V1 of this document serve as an initial preview of the changes expected in the upcoming production release scheduled for November 12th, 2023, on the Hosted Gateway. The definitive release notes for deployment in production will be included in V2 of this document. Summary The Gateway release notes will contain information related to the new iVeri software release. The release notes will include the impact of software release to the intended target audience. The release notes will adopt the format outlined below, as applicable: Compliance - Refers to the adherence of the software to specific industry standards, regulations, or internal policies. This includes ensuring that the software meets legal and regulatory requirem

V4.144 10/05/2024 ** The release notes provided in V1 of this document serve as an initial preview of the changes expected in the production release scheduled on May 19th, 2024, on the Hosted Gateway. Summary* The Gateway release notes will contain information related to the new iVeri software release. The release notes will include the impact of software release to the intended target audience. The release notes will adopt the format outlined below, as applicable: Compliance* - Refers to the adherence of the software to specific industry standards, regulations, or internal policies. This includes ensuring that the software meets legal and regulatory requirements, follows best practices, and aligns with established security and quality Optimisation* - The process of refining or improving