*Configure Application*
**
* Purpose *- To receive e-mail confirmations after processing successful transactions and to set-up your transaction viewing preferences, you will now need to set up your choice of transaction configuration.
* Action: *
On the main menu go to Lite – Configure Application.
* Action: *
Click on the Application you want to configure, i.e., either the Test or the Live. Make the relevant changes and click on Submit
Below are some of the details a user would need to configure under Application settings:
E-mail confirmations can be sent to a cardholder. Confirm the E-mail address confirmations are sent to and from. Customise the message on the payment page. Customise the message on payment request e-mail. Copy or Link Merchants Terms and Conditions Show Associated Logo
CyberSource Fraud Management
**
CyberSource data is additional transaction data which iVeri Payment Technologies Ltd needs to process orders within CyberSource's fraud screening solution.
Device Fingerprinting *
To successfully implement Device Fingerprinting, a 1-pixel image file (which cannot be seen) and two scripts need to be placed in the <body> tag of the merchant’s checkout page*. This will ensure a 3-5 second window in which the code segments can complete the data collection necessary to create a fingerprint for the device making the order.
Below are the code segments for implementing Device Fingerprinting:
PNG Image
<p style="background:url(https://h.online-metrix.net/fp/clear.png?org_id= <org ID> &session_id= <merchant id><session ID> &m=1)"></p> <img src="https://h.onli
* 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
Download File – By Application *
**
Purpose: *
*– To download a processed file for a selected Application ID e.g., Live or Test or if you have more than one Live Application ID you can select the particular Application ID you wish to download. These could also be for the purposes of reusing the file for another entry.
Action: *
From the main menu the user will navigate to: Batch - Download File - By Application.*
Action: *
The user will select the applicable Application ID for which you want to download the file i.e., Either Live or Test.
Action: *
Choose the date that the file was created/uploaded in
the range above by manually changing the default dates above or clicking on the
calendar icon next to each date and select each date in the calendar that is
displayed. Then click on Search
*Transaction – Payment*
**
* Purpose *- This function allows you to pass a credit to any card without having a previous debit transaction. There is a limit to the amount that you can process a credit transaction for. Please speak to your Acquirer to obtain this limit.
* Action: *
On the main menu bar, Click on Lite – Transactions – Payments , select the relevant Application ID. A Capture Transaction screen will be displayed.
Once the an application ID is selected, the system will allow you to manually capture and do the transaction, however this would require all the card details to be inputted and the set limits to be adhered to.
Customize
*Card Details Capture Layout*
**
* Purpose: *
From the ‘Customise Card details capture Layout page, the Administrator can customise the look and feel of the payment page.
This is a preview of the defaulted payment page that cardholders will see.
* Action: *
From the main menu the user will navigate to: *Lite - Configure Application.*
Action: *
Select the applicable application ID.
*
*
* Action: *
The user will select the 'Customise Card Details Capture Layout' tab.
Action: *
The user can upload the company logo to align with their company’s Corporate Identity. JPEG and PNG are the accepted file extensions.This can be done by clicking on the "Upload Logo" expansion button. The user will be able to access the assets from their PC and upload the file extension.
*Under 'Style', the u
Cardinal Posport Indigo Release Notes V 20230323 ***
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 /*
Indigo Ingenico *
A change is implemented to make Ingenico devices reboot once a day to comply with PCI requirement. The default time is set to be at midnight.
PosPort *
Device Status is included as part of the data synchronized from Cardinal into MIS allowing for a better filtering in reports generated from MIS. Allowances that make it possible to enable "CashAdvance" in parallel with "Sale" transaction type have been made
SMYL Loyalty *
As part of the loyalty offering on the N700 device, enabli
Void
**
Void should be performed on an event where transactions are not responded to or not completed to the merchant’s application which could be due to a timeout scenario. When used the void message should be performed closer to the time it relates. For more on the use of Void messages, refer to the Ensuring end to end Transaction Integrity
REST
SOAP
Request
{
"Version" : "2.0" ,
"CertificateID" : "{5c4b9c74-0063-4240-9cff-f730675c5bd0}" ,
"ProductType" : "Enterprise" ,
"ProductVersion" : "WebAPI" ,
"Direction" : "Request" ,
"Transaction" : {
"ApplicationID" : "{d8d5a94-8fa0-428d-a539-3a5baf166f7f}" ,
"Command" : "Void" ,
"Mode" : "Test" ,
"OriginalMerchantTrace" : "DIAAAY22734" ,
"OriginalRequestID" : "{9667792F-635A-4121-AC85-E06856ADC3EF}"
}
}
< soap:Envelope xmlns:xsi = "