* Cardinal Posport Indigo Release Notes V 20231026 *** The release notes contained in this document are available in iVeri’ s repository in production and can be installed on any Cardinal and or indigo installation on a case-by-case bases as agreed with Customers and or Integrators. */ Whats new  /* * PosPort * "Single Tap" feature has been updated to cater for scenarios where the issuer does not support “Single Tap and Pin”. In such scenarios, the cardholder will be requested to dip the card, eliminating the need for PIN collection.   An improvement on the reversal of an authorization has been introduced. Previously, authorizations reversed on a different day presented a challenge, but now the process has been updated so that these authorizations can be efficiently processed as "Authoriza

Merchant Hash Token Generation * ** /* *secretKey - Lite Shared Secret *resource - /Lite/Authorise.aspx *applicationId - {435407B0-8A28-4152-9649-A932423F72EB} *amount - Lite_Order_Amount *emailAddress - Ecom_BillTo_Email */ public static string GenerateTransactionToken(string secretKey, string resource, string applicationId, string amount, string emailAddress) { string time = Convert.ToString(UnixTimeStampUTC()); string token = secretKey + time + resource + applicationId + amount + emailAddress; return String.Concat(time, ":" + GetHashSha256(token)); } public static Int32 UnixTimeStampUTC() { Int32 unixTimeStamp; DateTime currentTime = DateTime.Now; DateTime zuluTime = currentTime.ToUniversalTime(); DateTime unixEpoch = new DateTime(1970, 1, 1); unixTimeStamp = (Int32)(zuluTime.Subtract(u

Then merchant token generation is a security measure introduced to hash merchant and transaction specific data elements, using SHA256 hashing algorithm. An effort which reduces the risk of data being exposed or intercepted by 3rd parties during the submission of transaction requests to the gateway.

1.Make a selection on what you want to purchase. 2. Select Add to Bag 3. Select Go to checkout Here you can either select Checkout or select the Bag icon it is still the same. 4.Insert your email address and the select Checkout This cardholder email is used to send the correspondent updates regarding the transaction and order status updates 5.Complete the Shipping & Delivery details for the delivery of the goods. Select Continue 6.Complete the delivery date details Select Continue */Please Note!/* The Store owner needs to set the charges and shipping method under “Shipping and Pick Up” on their Back End IYS Profile. 7.Choose how you choose to pay for this order. Which in this case it is iVeri Scroll down 8. Select Go to Payment */Please Note!/* Payment Instruction is set up by the merchant

* Payment Method Configuration – Back End Interface * 1.User to use the left adjusted Menu Items, navigate to Payments – To set up your payment provider. Select iVeri as a Payment Processor. This is done so that iVeri becomes the payment provider. The radio button will be on the disabled state until the merchant sign’s in. Scroll up and enable iVeri as the payment process here as well. Select the Enable radio button to allow iVeri as the payment provider 1. Turn the Radio button on. Select Actions then Edit 2. The system will update the page. 3.Insert your iVeri Provided store credentials. These are the merchants BackOffice account details that you would have already received. 4.This screen indicates a successful log in and link of the merchants’ store Profile with their iVeri merchant Pro

Introduction * ** Automatic Billing Updater (ABU) is a web service that provides access to updated account credentials (cards). This can be leveraged by Merchant/Acquirers/Payment Service Providers to ensure that they always have their customers’ most up to date card credentials for recurring and card-on-file payments. Simply put, ABU allows card details to be updated automatically in the event they are no longer valid. Types of updates include: Expiration dates Replacement card numbers Account closures Issuer brand changes to Visa and MasterCard

MasterPass is a safe and easy way in which merchants can present the QR code which customers can scan using a MasterPass application to affect a payment. */Requirements/* Merchant must be onboarded for MasterPass on the iVeri Gateway and on the MasterPass platform.

* Query Transaction Status * ** /*Note*/: This is just an extra step that can be used by the Merchant to make sure about the Transaction results. We would recommend that a Merchant should use this as a call to make sure the results he received back from the Authorization (Debit) of a transaction are consistent with the results returned here. The URL to post to is defined under the None [1] Gateway Addresses * Name * *General Description* * Length * *Notes* Lite_Merchant_ApplicationId iVeri ApplicationID 36 Allocated to the merchant during registration Lite_Merchant_Trace Merchant Trace 64 Unique merchant identification for the request. This value is to be used by the merchant to confirm the status of the transaction. The response to the Authorisation Information request is the following: L

Introduction ** The documentation, titled Merchant Onboarding Guide, is intended to provide a comprehensive and methodical explanation of the merchant onboarding process within the Standard Bank Administration Website. The Merchant Onboarding Guide provides the onboarding process for Card Not Present iVeri solutions. Objectives ** The purpose of this user guide is to assist users in navigating the merchant take-on process by providing step-by-step visual representations on the screen. Accompanied by detailed explanations, these screen representations aim to enhance the user's understanding of the iVeri administration website interface. The guide contains all the essential information for users to successfully onboard a merchant. It also covers typical scenarios that may arise based on the

Live phase * ** Before the merchant can start doing Live transactions, the acquirer or iVeri must validate that their implementation is correctly completed. For that purpose, the merchant shall send a request via email to the acquirer contact (available here) once they have completed their implementation, and after they have tested in the Test environment, while providing the following: Merchant's Website URL User Group Number / Merchant number  Test login credentials (Username / Password) for logging in to the merchant website as an end-user (if applicable) NB: It is time consuming for our test team to register as users on each website that we have to test hence this is required by them. If no log-in required, please state so within your email. Instruction on how to buy products from your