Field Definition DE59 - DE67

Field #59 – Echo Data

Field No	Format	Attr
59	LLLVAR	ans…255

Contains data from the originator of the message that shall be returned unaltered in the response message

Field #60 – Payment Information

Field No	Format	Attr
60	LLLVAR	ans…999

This data element contains information relating to bills payments and token (recharge cards, tickets etc) purchases. This data element carries tagged data items. The tags defined for this data element are as listed in the table below:

Transaction Type	Tag	Description	Length	Presence Indicator	Request/Response
Payment for Bills	*41	Biller Identification Code	015	Mandatory	Request
	45	Product Identification Code		Conditional
	**50	Customer Subscription Information		Mandatory
	**50	Customer Subscription Information		Optional	Response
Purchase of Token (Recharge Card, ticket etc)	*41	Biller Identification Code	015	Mandatory	Request
	45	Product Identification Code		Conditional
	**50	Customer Subscription Information (or products)		Optional
	****51	Token (e.g. PIN or Voucher)		Conditional	Response
	**50	Customer Subscription Information		Optional

Field #62 – Private Field, Management Data 1

Field No	Format	Attr
62	LLLVAR	ans…999

This data element carries tagged data items. The tags defined for this data element are listed in the table below. Tagged data items are structured in the following manner: a tag identifying the type of data, followed immediately by a three-digit length (LLL) identifying the length of the data, followed immediately by the data itself.

Tag + LLL + data.

Field #62 – Private Field, Management Data 1

Transaction Type	Tag	Description	Length	Request/Response
Terminal Parameter Download	01	POS/Payment Channel Serial Number		Request
	02	CTMS Date and Time	014	Response
	03	Card Acceptor Identification Code	015
	04	Timeout (maximum time interval to wait for response – in seconds)	002
	05	Currency Code	003
	06	Country Code	003
	07	Call home time (maximum time interval idleness for which a call – home must be done – in hours)	002
	52	Merchant Name and Location	040
	08	Merchant Category Code	004
Call – Home	01	POS/Payment Channel Serial Number		Request
	09	POS/Payment Channel Application Version	003
	10	POS Terminal/Payment Channel Model	020
	11	Call – Home Merchant Information/Complaint/Comments
	12	Communications Service Provider
Biller List Download	01	POS/Payment Channel Serial Number		Request
	*41	Biller Identification Code	015	Response
	42	Biller Name
Biller Subscription Information Download	01	POS/Payment Channel Serial Number		Request
	*41	Biller Identification Code	015
	43	Required Information Name		Response
	44	Default Value
Product List Download	01	POS/Payment Channel Serial Number		Request
	*41	Biller Identification Code	015
	45	Product Identification Code		Response
	46	Product Name
	47	Product Amount	012
Payment Validation	01	POS/Payment Channel Serial Number		Request
	*41	Biller Identification Code	015
	***48	Payment Code
	***49	Payment Validated Information		Response
Base Derivation Key (BDK) Request	01	POS/Payment Channel Serial Number		Request
	57	Key Serial Number	020
Dynamic Currency Conversion	01	POS/Payment Channel Serial Number		Request
	58	Cardholder Preferred Currency	003
	59	Local Country Currency	003
	60	DCC Identification Code	015
	58	Cardholder Preferred Currency	003	Response
	60	DCC Identification Code	015
	61	Rate

Note:

*Tag 41: Biller Identification Code is in the format below:

1st position – transaction type the biller is setup for:

4 – Token (e.g. Recharge Card) Sales

5 – Bill Payments

2nd – 4th position – VAS Provider Code

5th – 8th position – Merchant Category Code

9th – 15th position – Unique Number identifying the Biller

**Tag 50: Customer Subscription Information, if more than one, it should be separated by ‘||’ e.g. name=Halima Eze Ajayi||customerid=00001||prod1=3||prod2=4

From the example, name and customerid are values downloaded during Biller Subscription Information Downloadrequest and the values the customer entered are after the equals signs. prod1 and prod2 are products while values 3 and 4 after the equals signs are the quantities.

***Tag 48: Payment Code and ***Tag 49: Payment Validated Information can be used inter – changeably. Format is same as tag 50.

Note: For receipt printing of mCash Transactions on POS, send the Customer Information in the format of Tag 50 as above. For example:

SellerCode=0731170253||Phone=07069302232||RefNo=10012344546567||Amount=1000.23

****51: Token, if more than one, should be separated by comma ‘,’

Field #63 – Private Field, Management Data 2

Field No	Format	Attr
63	LLLLVAR	ans…9999

This data element carries tagged data items. The tags defined for this data element are listed in the table below. Tagged data items are structured in the following manner: a tag identifying the type of data, followed immediately by a three-digit length (LLL) identifying the length of the data, followed immediately by the data itself. Each block of data is separated by “~”.

Tag + LLL + data.

Transaction Type	Tag	Description	Length	Request/Response
EMV Application AID Download	01	POS/Payment Channel Serial Number		Request
13	AID Index		Response
14	Application Internal Reference Number
15	Application Identification Number (EMV AID)
16	Match	001
17	EMV Application Name
18	EMV Application Version
19	EMV Application Selection Priority
20	EMV DDOL
21	EMV TDOL
22	EMV TFL Domestic
23	EMV TFL International
24	EMV Offline Threshold Domestic
25	EMV Max Target Domestic
26	EMV Max Target International
27	EMV Target Percentage Domestic
28	EMV Target Percentage International
29	Default EMV TAC Value
30	EMV TAC Denial
31	EMV TAC Online
CA Public Key Download	01	POS/Payment Channel Serial Number		Request
32	Certificate Authority (CA) Key Index		Response
33	CA Key Internal Reference Number
34	CA Key Name
35	EMV RID
36	Hash Algorithm
37	EMV CA PK Modulus
38	EMV CA PK Exponent
39	EMV CA PK Hash
40	Public Key Algorithm
Daily Transaction Report Download	01	POS/Payment Channel Serial Number		Request
53	Transaction Date and Time		Response
54	Response Code
55	Amount
56	Transaction Type

Field #64 – Primary Message Hash Value

Field No	Format	Attr
64	AN	64

This data element carries the hash value for the messages subject to no secondary data elements (DE65 through DE128) are included in the message. The algorithm is SHA-256.

If the message contains secondary data elements, data element DE128 is used to carry the hash value. If the hash value is carried in data element DE128, data element DE64 is not included in the message.

Field #67 – Extended Payment Code

Field No	Format	Attr
67		n 2

The number of months that the cardholder prefers to pay for this item if permitted by the card issuer.