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.
Login ** Purpose * - To log in to the secure BackOffice Website, login credentials are emailed to the merchant during taken on process by the acquirer.
image%20%281%29 [1]
Action: *
User Group - enter your Billing Details ID User Name - type in Administrator Password - this is the Administrator password sent to you with the Billing Details ID by email. Copy and paste it from the email.
Reset Password **
To reset your password the user can select the forgot password tab
Login%20password%201 [2]
Enter the require details
Login%20password%202 [3]
The user will receive a notification to the saved email on your merchant profile
Login%20password%203 [4]
Click the link in the email to be direct to create a new password, select reset password once completed
Login%20password%204 [5]
This will di
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
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
Merchants are required to enter into a “agreement” with an authorized acquiring institution. Once there is a merchant agreement in place, a merchant profile can be created. With Enterprise calls to the Gateway, the presence of a certificate ID is required in the body of the request. While the inclusion of the AuthenticationToken and AuthenticationKey in the headers is optional. Test Mode should be used during integration, testing, and validation. Test application ID must be used with Mode Test Test cards should be used during integration testing and validation
Below is a step-by-step process on how to onboard a merchant on the iVeri Administration Website:
Capturing Merchant Information **
Login using the URL link for the iVeri Admin Portal and the login credentials that have been created.
From the homepage, navigate to: ‘ Merchant Profile*’ > select ‘ Create*’.
1. Under the ‘General Information’ tab, you would capture the details of the Merchant.
Note*: All the Yellow fields are mandatory and would need to be captured.
MTP1 [1]
2. Send Email Notifications:
If this tab is ticked the BackOffice credentials and other notifications will automatically be sent to the Contact persons’ e-mail address.
Leave this unticked should you not want the merchant to receive e-mail notifications.
3. Ensure that the Distributor is set. Depending on the region the
Below is a step-b-step process on how to onboard and configure a merchant on the iVeri Administration Website. **
User Group Capture **
Login: Using the URL link https://admin.host.iveri.com [1] for the iVeri Admin Website and login credentials that have been created & e-mailed to the user.
From your homepage, navigate to: ‘Merchant Profile’ > select ‘Create’.
1. Under the ‘General information’ tab, you would capture the details of the Merchant.
UGC1 [2]
Note: All the Yellow fields are mandatory and would need to be captured.
2. Send Email Notifications:
If this tab is ticked the BackOffice credentials and other notifications will automatically be sent to the Contact persons’ e-mail address.
Leave this unticked should you not want the merchant to receive e-mail notifications.
3. Distribut
Merchant Take on Process - IYS
**
User Group Capture *
Action: *Log on to: iVeri Admin website, navigate to Merchant Profile > select Create
1. Capture all the details on the form.
2. Ensure that the Distributor (Which is iVeri) is set.
3.“Aggregator” option is used should a merchant belong to a listed Payment Aggregator, and this is because the merchant agreement is between the acquirer and the Aggregator. If “yes” assign the appropriate Aggregator from the drop down.
Note: If the merchant does not belong to an Aggregator, the Aggregator field must be left to “None”
Once details are populated, Click on Create.
Important Note:
This Association of an Integrator or Aggregator of a merchant is standard across all products, and across all Take-On Processes This will generate the iVeri Merchant