PosPort BackOffice User Guide
**
PosPort is a card-present solution designed to facilitate secure and efficient card payments in face-to-face environments through a standalone terminal. This comprehensive solution not only empowers merchants to seamlessly accept both contact and contactless transactions but also expands the horizon of transaction possibilities, offering a diverse and extended range of transaction sets.
PosPort is tailor-made for Small and Medium Enterprises (SMEs) operating in the retail spaces where merchants accept and process face-to-face transactions, using a teller or cashier-operated standalone device.
Point 1.
Point 2.
Point 3.
Point 4.
* Terminology *
*
This document uses certain iVeri specific terminology which can be referenced in Parameter Description
* Merchant Requirements *
*
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, with the actual physical certificate available as optional means to authenticate merchant requests. Test Mode should be used during integration, testing, and validation. Test application ID must be used with Mode Test
File Transfer Parameters *
**
Debit/Sale *
**
The possible transaction sequence flow with an initial Debit is the following
EMV Parameters *
*
Parameter
Node Type
Data Type
Min Length
Max Length
Description
EMV_AuthorisationRequestCryptogram
Tag
Hex
16
EMV tag 9F26
EMV_ApplicationIdentifier
Tag
Hex
32
EMV tag 9F26
EMV_ApplicationInterchangeProfile
Tag
Hex
4
EMV tag 82
EMV_CardSequenceNumber
Tag
Hex
2
EMV tag 5F34
EMV_ApplicationTransactionCounter
Tag
Hex
4
EMV tag 9F36
EMV_ApplicationVersion
Tag
Hex
4
EMV tag 9F08
EMV_CardHolderVerificationMethodResult
Tag
Hex
6
EMV tag 9F34
EMV_CryptogramInformationData
Tag
Hex
2
EMV tag 9F27
EMV_IssuerApplicationData
Tag
Hex
64
EMV tag 9F10
EMV_TerminalCapabilities
Tag
Hex
6 or 8
EMV tag 9F33
EMV_TerminalType
Tag
N
2
EMV tag 9F35
EMV_TransactionType
Tag
N
2
EMV tag 9C
EMV_TerminalVerificationResult
Tag
Hex
10
EMV tag 95
EMV_UnpredictableNumber
Tag
Hex
8
EMV tag 9F37
EMV_Trans
Pre-Auth – “Authorisation with PAN” *
**
Reserve or withhold funds on the cardholders related card account
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" : "Authorisation" ,
"Mode" : "TEST" ,
"MerchantReference" : "20221108_1042" ,
"MerchantTrace" : "DIAAAY4QW2" ,
"Currency" : "ZAR" ,
"Amount" : "3000" ,
"ExpiryDate" : "1025" ,
"PAN" : "4242424242424242"
}
}
< soap:Envelope xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd = "http://www.w3.org/2001/XMLSchema"
xmlns:soap = "http://schemas.xmlsoap.org/soap/envelope/">
< soap:Body >
< E
Checklist – Cardinal & Admin Website Quality Check
**
What to check *
How to Check it *
*
1. Check
Profile Creation *
Check if the profile is completed accurately. Go to Merchant Profile >> Update >> General.
*
2. Check
Billing *
Check if charges are applied properly based on what has been agreed, (i.e. net settlement
or EFT etc). Merchant Profile >> Update
>> Parameters .
*
3. BackOffice Services Update *
Check if all the Service updates are done for Merchant Admin,
Cardinal and iVeri Backoffice . Go to Merchant Profile >> Update >> Back Office
Services .
*
*
4. Cardinal Authentication method *
Check if the merchant has been
properly created in cardinal to create the link between IYS and Cardinal for iVeri to be the
Payment Provider. Go to
Cardinal Admin
>> Merchant Login >> Login in as