The release notes provided in V1 of this document serve as an initial preview of the changes expected in the upcoming production release of the PocketPos application *** Summary *** The PocketPos release notes will contain information related to the new PocketPos application 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 a software solution

* * The following section covers the details of POS Device integration (particularly PIN based transactions). PIN transactions are encrypted either using Triple DES DUKPT or Triple DES Master/Session encryption architecture. The combination of Acquirer and type of device used determine the encryption architecture chosen. iVeri provides facilities where PIN transactions can be process in either mode Live or Test.For security reasons, a key cannot be used in both modes Live and Test. Therefore, a device is either loaded for mode Test or mode Live. A Device that is to be used for mode Live must be injected with a key within an iVeri Trusted Centre using the appropriate encryption architecture.A Device that is to be used for mode Test may be injected by a merchant, or within the Trusted https:

PosPort BackOffice User Guide ** PosPort is a card-present solution designed to facilitate secure and efficient card payments in face-to-face environments through a standalone terminal. This comprehensive solution not only empowers merchants to seamlessly accept both contact and contactless transactions but also expands the horizon of transaction possibilities, offering a diverse and extended range of transaction sets. PosPort is tailor-made for Small and Medium Enterprises (SMEs) operating in the retail spaces where merchants accept and process face-to-face transactions, using a teller or cashier-operated standalone device.

PosPort -Transactions – View – Transaction History ** / Purpose: /* Users can access the Transaction History feature, enabling them to select a date range and view transactions spanning up to 6 months in the past. To access the Transaction History from the dashboard or homepage, users will navigate to the menu, then select the PosPort dropdown. Next, they'll click on the Transactions dropdown, followed by clicking on the View dropdown, and finally select Transaction History. Select the application mode the user would like to View Transaction History for. The user will now be able to select the date for transaction history they would like to view. Transaction details for the last 6 months will be available for the user to view. The transaction history and details thereof will be displayed f

Pre-Requisites * ** Acquirer Collaboration for ABU Implementation: Establish an agreement with the Acquirer regarding the submission process for the Merchant Registration file. Follow the necessary steps to conclude the project with MasterCard, including customization, testing, and obtaining final approval. Acquirer Configuration on Admin Portal: Input the provided ICA value from the Acquirer under "System > Distributor > Parameters" on the Admin portal. Merchant Eligibility Requirements: Merchants must be actively processing Card Not Present (CNP) transactions using any of the following platforms: Lite, Enterprise, DiVert, Batch, or Link. Mastercard Transaction Processing: Merchants should be actively processing transactions with Mastercard.

Print Report * ** / Purpose /*- To View/Print/Save reconciliation file for a specific acquirer cycle/settlement period in either: PDF XLS format CSV format / Action: /* Select the menu function Reconciliation then click on Print Report. / Action: /* If you have only one Merchant Card Acceptor ID, simply click on Submit. If you however have more than one, then click on the drop down and select the Card Acceptor ID for which you want the report before you click on Submit. The following screens and points highlight the various parameters that need to be selected before viewing the report. Action: * Select the required Output format – either PDF or XLS. Find the acquirer cycle number you want to view and click on the actual cycle number. You can now choose to either Save the report or to open

Profile Parameters * ** Purpose - * To set the Security Parameters for all users in terms of their passwords, validity, suspension, and login notifications. These parameters can only be set by the Back Office Administrator. Action:  * In the menu bar, click on User Manager, scroll to, and click on Security Configuration. This will bring up the following form on which you can now change the system defaults to suit your own requirements. Please remember that changes made to the defaults will apply to ALL users that you have given BackOffice access to / Note: /* Strong Password: The default is No. This means that the password can be anything if it is not less than the default minimum length. If you change the default to Yes, then the user’s password must be a combination of alpha/numeric and

* Purpose - * To set the Security Parameters for all users in terms of their passwords, validity, suspension, and login notifications. These parameters can only be set by the Back Office Administrator. * Action:  * In the menu bar, click on User Manager, scroll to, and click on Security Configuration. This will bring up the following form on which you can now change the system defaults to suit your own requirements. Please remember that changes made to the defaults will apply to ALL users that you have given BackOffice access to */ Note: /* Strong Password: The default is No. This means that the password can be anything if it is not less than the default minimum length. If you change the default to Yes, then the user’s password must be a combination of alpha/numeric and special characters

** * Purpose - * To set the Security Parameters for all users in terms of their passwords, validity, suspension, and login notifications. These parameters can only be set by the Back Office Administrator. * Action:  * From the main menu, the user will navigate to: *Configure - Profile Parameters*. Action:  * This will display a form where you can modify the system defaults to meet your specific needs. Please note that any changes made to these defaults will apply to all users with access to iVeri BackOffice. */ Note: /* Strong Password: The default is No. This means that the password can be anything if it is not less than the default minimum length. If you change the default to Yes, then the user’s password must be a combination of alpha/numeric and special characters also not less than th

QR Code – MasterPass Parameters * * Context * Parameter * MasterPassQuickResponseCod *e * MasterPassPaymentNotification * Credit with TransactionIndex * Void * Core ApplicationID M * M * M * M * Core Category M * M * M * M * Core CertificateID M * M * M * M * Core Gateway O * O * O * O * Core Command M * M * M * M * Core Mode M * M * M * M * Common Amount * * * * Common ExipiryDate * * * * Common Currency * * * * Common MerchantReference * * * * MasterPass MasterPassAction M * * * * MasterPass MasterPassMerchantID M * * * * MasterPass MasterPassShortDescription * * * * MasterPass MasterPassCodeExpiryDate * * * * MasterPass MasterPassMerchantName * * * * MasterPass MasterPassCode * * * * MasterPasss MasterPassTransactionID * * * *