Delete Code *
**
Function: Delete a code that has been created
Delete Code Parameters *
Request
Parameter
Description
MasterPassAction
Mandatory, The action to perform.
MasterPassMerchantID
Mandatory, The merchant id as captured on MasterPass.
MasterPassCode
Mandatory, The result code that must be deleted
Response Parameter
Description
MasterPassAction
The action that was performed
Delete Code – REST Sample *
Request
Response
{
"Version" : "2.0" ,
"CertificateID" : "{xxxxxxxx-71dd-4044-802d-xxxxxxxxxxxx}" ,
"ProductType" : "Enterprise" ,
"Direction" : "Request" ,
"Enquiry" : {
"ApplicationID" : "{xxxxxxxx-68e0-42eb-aba9-xxxxxxxxxxxx}" ,
"Mode" : "Live" ,
"command" : "MasterPassQuickResponseCode" ,
"MasterPassMerchantID" : "xxxxx" ,
"MasterPassAction" : "DeleteCode" ,
"MerchantRefer
Gateway Release Notes V 4.130 *
**
/ Hosted Gateway: /*
Date: 21/05/2023
Start Time: 20:00 UCT +2
Duration: 2-4hrs
Expected Downtime: 5-10mins.
/ Nedbank Gateway: /*
Date: 11/06/2023
Start Time: 20:00 UCT +2
Duration: 2-4hrs
Expected Downtime: 5-10mins.
Enhancements *
Compliance – Mastercard Edits*
MCI: Edit 7 - TermPOS
The Terminal Operating Environment value in POSDATA element has been updated from value “5” to “0” for instances where POSEntryMode is set to “01
Amendments have been made on DE 123 for MasterPass Pin authenticated transactions.
Backoffice 2 *
The inclusion of the "View All" option for Batch users together with the ability to view transactions performed under specific users has been introduced. With this change it is now possible for users to view and do subsequent actions
DiVert Functionality *
**
The Divert API has a parameter “CreateTransactionUrl” that can be set to either “True or “False”. The value set determines how the Gateway handles and processes the message request.
Scenario 1 *
If CreateTransactionUrl” is set to“True” - the Gateway generates a transaction URL and makes a callback to the merchant with the URL.
The merchant can then construct and format their own message, including the URL (returned by the Gateway) and distribute the message to their cardholder using either SMS|Email
When the cardholder receives the messages, it will have all the particulars of the merchant, the cardholder can then click on the URL, and be redirected to a payment page wherein they can make a payment to the merchant
Scenario 2*
If CreateTransactionUrl is set to “Fal
3D Secure *
**
3D secure is an XML-based security protocol for online credit and debit card transactions. 3D Secure adds an authentication step for online payments, making it possible for cardholders to authenticate their online transactions with their card issuers, using a password or OTP.
Benefits of using 3D secure *
Reduces fraudulent debit & credit card transactions processed through online platforms Gives the merchants and acquiring bank liability protection
3D secure providers *
CyberSource Bankserve
3D secure with iVeri *
High: 3D secure – If a merchant is deemed high risk, the acquiring bank can set merchants on this level. Merchants that want lowest possible risk can also opt for this level. Medium: 3D secure/attempted- This option gives merchants a broader reach in the cards the
Create Code *
**
Function: Generate a transactional code that can then be paid for by a cardholder. This code can be represented as a QR code, transferred using NFC or manually entered a device. The code can also be used as part of an In-App payment.
/Create Code Parameters/*
Request
Parameter
Description
MasterPassAction
Mandatory, The action to perform.
MasterPassMerchantID
Mandatory, The merchant id as captured on MasterPass.
MasterPassShortDescription
Mandatory, This will be displayed to the consumer at the time a code
is scanned. Length is 5 to 45 characters
MasterPassCodeExpiryDate
Optional. If this is empty the code will by default expire in 30
minutes from issue. If this value is 0 the code will never expire. This time
is specified in epoch.
Amount
Mandatory, To use a variable amou
*** Requirements ***
With the API, merchants are able to generate payment requests to their clients by implementing the “DebitRequest” command and include the specific data parameters that are expected in the message request to the Gateway. The data elements required in the “DebitRequest” command are covered in the Enterprise Documentation
In order to implement the DebitRuquest method, the following should be downloaded or in place.
Reference the Divert Specification Guide Reference the using the “RequestDebit” method in the Enterprise Documentation Merchant Agreement with an acquirer with Divert as the solution which will result in a merchant profile on the Gateway
/ Nedbank Gateway /* – Applicable for Nedbank acquired merchants located in South Africa, Zimbabwe, Namibia, Lesotho and Swaziland
Website *
URL *
Port *
BackOffice *
[1] https://backoffice.nedsecure.co.za/
443 *
Lite
[2] https://portal.nedsecure.co.za/Lite/Authorise.aspx
Authorization Information
[3] https://portal.nedsecure.co.za/Lite/AuthoriseInfo.aspx
/ CIM Hosted Gateway /* – Applicable for merchants acquired by CIM Finance in Mauritius
Website *
URL *
Port *
BackOffice *
[4] https://backoffice.merchant.cim.mu/
443 *
Lite
[5] https://portal.merchant.cim.mu/Lite/Authorise.aspx
Authorization Information
[6] https://portal.merchant.cim.mu/Lite/AuthoriseInfo.aspx
/ CSC Hosted Gateway */– Applicable for merchants that acquired by banks af
The iVeri range of payment solutions, developed by iVeri Payment Technologies (Pty) Ltd provides proven credit card payment solutions for businesses that have online or physical presence. LIte is an online payment product.
Query Code *
**
Function: Query a code that has been created.
Query Code Parameters *
Request
Parameter
Description
MasterPassAction
Mandatory, The action to perform.
MasterPassMerchantID
Mandatory, The merchant id as captured on MasterPass.
MasterPassCode
Mandatory, The result code that must be queried
Response
Parameter
Description
MasterPassAction
The action that was performed
MasterPassShortDescription
Short decription linked to the code
MasterPassCodeExpiryDate
Date until the code is valid. This is in epoch time.
MasterPassMerchantName
The name of the merchant as captured on MasterPass
Amount
Amount linked to the code.
Currency
The currency is tied to the merchant setup.
MerchantReference
Linked to the code.
Query Code – REST Sample *
Request
Response
{
"Version" : "2.0" ,
"Certifica
*** The Divert Batch Upload Data Elements ***
* The Divert Batch XML upload file uses the following logic: *
The <Divert> element can occur multiple times The <DivertItem> element can occur multiple times under a <Divert> element The Application ID used in the <DivertItem> elements should be the same through-out the <Divert> element
* Divert attributes *
Tag Name
Length
Data Type
Format
Description
Amount
<=12
Numeric
The sum of the Amount sub-element values of all the <DivertItem> sub-elements
Count
<=6
Number
The number of <DivertItem> sub-elements
*Divert sub-elements*
Tag Name
Length
Data Type
Format
Description
Date
8
Numeric
YYYYMMDD
The date when the batch was created (in which case the batch will be processed on the upload date) or a future date on which the batch should be process