Command emv.adddata

Knowledge about the EMV standard is required to use this command.

The command emv.adddata is used to pass parameters to the EMV Kernel on commands emv.inittransaction, emv.processtransaction and emv.finishtransaction.

Parameters

1. parameter [string]
   Parameter name to be sent. (see table below)
2. type [string]
   Possible types:
   
   • init
   • process
   • finish
3. value [string]
   Parameter value.
4. variablereturn [integer]
   Return codes:
   
   • 0: OK
   • -1: Error. Type, key or value doesn't exist.

Allowed parameters:

For the type 'init' <emv.inittransaction/>

Parameter	Description	Contact	Cless
bAcquirerID	Acquiring Network Identifier	x
bReqApplication	99 - All applications 0 - Only application selections in waAppArray	x
baInitialValue	Initial value (Amount authorized). 12 characters with 0 padding to the left, example: “000000005000”(50,00)	x
baDate	Date of the transaction (“AAMMDD”)	x	x
baTime	Time of the transaction (“HHMMSS”)	x	x
baTimeStamp	Timestamp for the tables (“DDMMAAAASS”), where SS is ​any sequential number. The Telium EMV Kernel validates the timestamp.	x
iAppCount	Number of entries on the list waAppArray	x
waAppArrayX	Array containing the acquiring network identifier + table index of EMV parameters. Where X is the sequential number of the application, starting from 1. Example waAppArray1, waAppArray2...	x

For the type 'process' <emv.processtransaction/>

Parameter	Description	Contact	Cless
baAmount	Value of the transaction (Amount, authorized); may include new values presented after the instruction emv.inittransaction. 12 characters with 0 padding to the left, example: “000000005000”(50,00).	x	x
baAmountOther	Withdrawl value or change - cashback (Amount, other). 12 characters with 0 padding to the left, example: “000000005000”(50,00).	x	x
bfRefund	Cancel the previous transaction 1 - yes 0 - no		x
bBlackList	Results of querying the blacklist (EMV) 0 - PAN not blacklisted 1 - PAN blacklisted.	x
bMustConnect	Mandatory connection 0 - Transaction can be made offline 1 - Transaction can only be made online.
bRequirePIN	PIN entry 0 - Not required 1 - Required.	x
bKeyMode	Encryption mode to capture PIN online 2 - DUKPT DES(8 bytes) 3 - DUKPT 3DES(18 bytes)	x	x
bManageRisk	EMV Risk Management 0 - Do not make a risk assessment 1 - Make a risk assessment.	x
dwFloorLimit	Terminal Floor Limit (in cents).	x	x
dwThresholdValue	Threshold Value for Biased Transaction Selection (in cents).	x
bMaximumTarget	Maximum Target Percentage to be used for Biased Transaction Selection.	x
bMandatoryTagsLen	Field size of baMandatoryTags.	x	x
baMandatoryTags	List of the tags necessary to assemble the field 55 of the ISO-8583 message. (Hex)	x	x
bOptionalTagsLen	Field size of baOptionalTags.	x	x
baOptionalTags	List of desirable tags to be retrieved in the operation. (Hex)	x	x
bPinBypass	Bypass on PIN through EMV library 0 - No 1 - Yes	x	x

For the type 'finish' <emv.finishtransaction/>

Parameter	Description	Contact	Cless
bCommStatus	Communication status with the Host 0 - Successful Communication 1 - Failed to communicate with the host.	x	x
bIssuerType	Issuer type 0 - EMV “Full-Grade” 1 - EMV “Partial-Grade”.	x	x
baInitialValue	Authorization Response Code (em ASCII). Standard definitions: 00 - Approved 01 - Denied Y1 - Offline approved Y3 - Offline declined Z1 - Unable to go online, offline approved Z3 - Unable to go online, offline declined	x	x
iTLVDataEMVLen	Field size of baTLVDataEMV.	x	x
baTLVDataEMV	Tags list returned by the issuer. (Hex)	x	x
bMandatoryTagsLen	Field size of baMandatoryTags.	x	x
baMandatoryTags	List of mandatory tags to be retrieved in the operation. (Hex)	x	x

Example

---

The example above demonstrates an example for each parameter type, init, process and finish.

The example shown here is fictitious, since in order to succeed with a full EMV transaction it is necessary to meet several other requirements such as having an ISO-8583 answer from the card issuer, keys injected into the terminal and other requirements defined by the EMV standard.