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.

Release Notes - NewPos Android 9200 * The release notes are available to CBZ NewPos Android 9200 device. What’s New * Zimra* Support of Zimra transactions on the 9200 introduced. Functionality added is a replication of what is currently supported in the NewPos 7210. Enhancements * Receipts* The receipt print timer has been increased to 2.5 Seconds. A “red cross” badge will be displayed before printing a failed transaction receipt. A “green tick” badge will be displayed before printing an approved transaction receipt.

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

*How to Configure Shipping & Pick Up* 1.Use the left adjusted Menu Items, navigate to Shipping & Pickup – To set up your Shipping methods. Choose your providers you will use to courier or ship the goods based on the aggreement you have with your partner.

Illustration of Visa Check-Out Process With iVeri Lite* **

Requirements * ** Merchants must generate the token on their web server and pass the generated token to the transaction request. The generated token must encompass the following data elements: Lite_Order_Amount: Total amount of the order Lite_Merchant_ApplicationId – The merchants app ID must be in uppercase and in curly brackets Ecom_BillTo_Email - The cardholder Email address TimeStamp – The timestamp when the token is generated Resource - Lite/Authorise.aspx SharedSecret - as configured in the merchants application in backoffice The parameters utilized in the hash token generation process must correspond exactly to those submitted via the form Post method to ensure token integrity and validation. **

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.

Release Notes * ** Release Notes for every iVeri product.

Token Verification Logic in the Hosted Payment Page * ** If Enable Token Verification has been set to YES and Lite Shared Secret has not been set an exception will be thrown when submitting a transaction request If Enable Token Verification has been set to YES and Lite_Transaction_Token has not been set an exception will be thrown when submitting a transaction request  If Enable Token Verification has been set to YES and the Lite_Transaction_Token does not match the calculated token an exception will be thrown