FUJ00002169
FUJ00002169
Horizon - LINK Mapping Project: EMV - Banking and Retail
COMMERCIAL IN CONFIDENCE Doc Ref: NB/IFS/033
. .
EMV — Banking and Retail
Horizon - LINK Mapping
Role NAME AREA OF I SIGNATURE Date
RESPONSIBILITY
Authors Chris Bailey on behalf I Business
of Post Office Ltd Architecture
Product
Deployment
Technical
Architecture
DA Sign-off David Gray Design
(Peer Reviewer) Authority
Project Graham Bevan Project
Manager Delivery
Fujitsu David Court
Services Sign-
off
Created on 30/04/2010 Version 4.0 Page 1 of 10
© Post Office™ 2004-2010
Project:
Horizon - LINK Mapping
Doc Ref:
COMMERCIAL IN CONFIDENCE
FUJ00002169
FUJ00002169
EMV - Banking and Retail
NB/IFS/033
1 Document Control
1.1 Document Information
Horizon Release No:
HNG-X Release 2
Document Title:
EMV Banking and Retail — Horizon - LINK Mapping
Document Type:
Application Interface Specification
Abstract: This document details the mapping of messages between Horizon and
LINK.
Document Status: Approved
Originator & David Gray
Department:
Design Authority
Contributors:
Post Office
Distribution:
Design Authority - David Gray
POL Document Control — Post Office Programme Office
Supplier Distribution:
LINK — Geoff Barker
Fujitsu Services — David Court
Client Distribution:
N/A
Table 1: Document Information
1.2 Document History
Version I Date Reason for Issue Associated
s WP /CT
0.1 28 May 2004 _ First working draft. Based on document supplied by IBM,
“Network Banking Engine Horizon - LINK Mapping",
but changed to map the messages processed by NBX,
and to include ICC fields.
0.2 07 Jul 2004 Minor corrections and changed to the form of a Post
Office document.
0.3 21 Oct 2004 Corrections resulting from review.
0.4 29 Oct 2004 Minor amendments resulting from AIS and business
parameter changes.
1.0 4 Nov 2004 Minor clarification and issued for Approval
1.1 26 May 2005 Updated for CT 363 and for minor corrections discovered I CT 363 /
during testing prior to initial release at Horizon release I CP 3997
$75
1.2 3 Aug 2005 Corrections from review cycle and LINK re-accreditation
testing.
Created on 30/04/2010 Version 4.0 Page 2 of 10
© Post Office™ 2004-2010
FUJ00002169
© Post Office™ 2004-2010
FUJ00002169
Horizon - LINK Mapping Project: EMV ~ Banking and Retail
COMMERCIAL IN CONFIDENCE Doc Ref: NB/IFS/033
2.0 15 Aug 2005 _ Issued for Sign-off
2.1 5 Dec 2006 Add in PIN Change Functionality for LINK CT 573/
Migration from LIS 2005-1 to 2007-1 for LINK. CP 4295
2.2 9 Jan 2007 Corrections resulting from review
3.0 19 Mar 2007 _ Issued for Sign-off
3.1 28 Oct 2009 I Changes for LIS5 2008-1 XR2 CP409
3.2 31 Mar 2010 — Corrections resulting from review
4.0 30 Apr 2010 Issued for Approval
Table 2: Document History
1.3 Change Process
Any changes to this issued version of this document will be made, controlled and distributed by: -
IT_Controlled_Document_reviewf GRO I
1.4 Review Details
Review
Comments by :
Review Chris Bailey, Fujitsu Services
Comments to :
Mandatory Review Authority Name
Post Office Ltd Richard Cowan
Security Manager Sue Lowther
Fujitsu Services Ltd
Solution Design / Development
Agent and Web Services Andy Williams
Counter, BAL/OSR, Audit Steve Evans
Host Online Systems Andy Beardmore
Host Dev Management David Harrison
ssc Tony Little
Optional Review / Issued for Information
Post Office Ltd Bob Booth, Seamus Scullion
Fujitsu Services Ltd
Analysis & Solution Specification Gareth Jenkins
Security Architect tbs
Security & Risk Team CSPOA.Securit
Infrastructure Design Pat Lywood (or nominees)
Applications Architecture David Johns
Testing Manager Debbie Richardson
LST John Rogers
SV&l Manager Chris Maving
Test Design George Zolkiewka
Created on 30/04/2010 Version 4.0 Page 3 of 10
Horizon - LINK Mapping Project:
COMMERCIAL IN CONFIDENCE Doc Ref:
FUJ00002169
FUJ00002169
EMV - Banking and Retail
NB/IFS/033
Programme Manager Geoff Butts
LST Manager Sheila Bamber
RV Manager James Brett (POL, JTT)
VI Manager Mark Ascott
1.5 Changes in this Version
Version I Changes
4.0 Issued for sign-off
3.2 Corrected terminology — Horizon Online in place of Horizon, NBS in place of NBX
Corrected references to documents
Corrected typos and various documentation discrepancies with the system.
Project Manager (POL) replaced lan Oakley by Graham Bevan
3.1 Updated reviewers
Added response code 85 to mappings
Amended details of Point of service data (field 061) (add fields 14, 15, 16) inR1
message
Removed Track 2 data (field 035) from E1 (0420/0421) messages
3.0 Issued for Sign-off
2.2 Added PI to list of abbreviations
Corrected message type in cell A2 on PIN Change Reversal Request worksheet
Changed mapping of field 123 for PIN Change Reversal Request
Corrected RRN length to precisely 12 where it was given as “..12”
Changed note on Amount_Confirmed for PIN Change Reversal Request
Corrected conditionality of field 142 for PIN Change Reversal Request
21 Add PIN Change functionality
Add PIN Change Request and PIN Change Response Tabs to spreadsheet
Add Change Reversal (E1) and Pin Change Reversal Response (E2) Tabs to
spreadsheet
Remove Hidden columns from spreadsheet
Add Reversal Reason 23
Add subfield 13 to field 061 for migration to LISS 2007-1
2.0 Gill Jackson added as signatory for Fujitsu Services
1.2 Some reviewer names and the copyright statement updated.
Balance Enquiry worksheet — Point of Service Data (bitmap ref 061): subfields 9 and 12
updated to reflect change in the AIS, NB/IFS/024. Note that this reflects on to the
Withdrawal and Deposit worksheets. [FS Peaks 123730 & 123623]
1.1 Section 1.1 —- Horizon Release updated to S80R.
Balance Enquiry worksheet — Authorisation Data (bitmap ref 123): removed from 0100
message. [POL Incident 1153; FS Peak 108959]
Created on 30/04/2010
© Post Office™ 2004-2010
Version 4.0
Page 4 of 10
FUJ00002169
FUJ00002169
Horizon - LINK Mapping Project: EMV - Banking and Retail
COMMERCIAL IN CONFIDENCE Doc Ref: NB/IFS/033
Table 3: Changes in this Version
1.6 Key Contacts
Name I Position I Phone Number
Bob Booth Solutions Architect
Michael Abendstern Technical Specialist
Chris Bailey Business Analyst
Table 4: Key Contacts
1.7 Associated Documents
Reference Version Date Title Source
LISS 2008-1 Vsn LISS Switch Service Interchange VocaLink
1.7 Standard — LISS 2008-1
NB/IFS/024 NBS-LINK Application Interface Post Office
Specification (AIS)
DES/APP/IFS/0006 RAC Message Flows in HNG-X Fujitsu
Services
Table 5: Associated Documents
Unless a specific version is referred to above, reference should be made to the current approved versions
of the documents.
1.8 Abbreviations/Definitions
Abbreviation Definition
Authorisation Agent —_I The part of the NBS which interfaces to Fls and carries out the
message mapping.
BCD Binary Coded Decimal
Fl Financial Institution
NBE Network Banking Engine
NBS The term used to describe the NBE functionality absorbed into the
Horizon domain.
PI Process Interface, the processing component in an FI
Table 6: Abbreviations/Definitions
In addition, the message names [A1], [R3], [E1], [E2] and the abbreviations for their field formats are used as
in ref [2], while the names and field format abbreviations for the messages [R1], [A3], [CO] are as in ref [3].
Created on 30/04/2010 Version 4.0 Page 5 of 10
© Post Office™ 2004-2010
FUJ00002169
FUJ00002169
Horizon - LINK Mapping EMV ~ Banking and Retail
COMMERCIAL IN CONFIDENCE
Table of Contents
1 DOCUMENT CONTROL 2
1.1. Document Information 2
1.2. Document History 2
1.3. Change Process 3
1.4 Review Details 3
1.5. Changes in this Version 4
1.6 Key Contacts 5
1.7 Associated Documents 5
1.8 Abbreviations/Definitions 5
2 INTRODUCTION 7
2.1. Scope 7
2.2 Structure 7
3 NOTES ON THE SPREADSHEET 8
4 MESSAGE MAPPING SPREADSHEET 9
Created on 30/04/2010 Version 4.0 Page 6 of 10
© Post Office™ 2004-2010
FUJ00002169
FUJ00002169
Horizon - LINK Mapping Project: EMV - Banking and Retail
COMMERCIAL IN CONFIDENCE Doc Ref: NB/IFS/033
2 Introduction
This document identifies the data mapping between the various message elements of the message sets where
NBS acts as the conduit between Horizon and LINK. It should be used in conjunction with the AIS (Ref [2]).
Any translations that need to be performed to convert from one particular message format to another are
identified, together with how the translation is achieved, where possible. In addition, the data that is required
by a message, but which is not present in the source message from another message set, is identified together
with an alternative source.
The following sources can be used to populate a message:
Transaction messages Data is mapped from a message element in one message to a
corresponding message element in another, possibly undergoing
translation.
Configuration The exact locations of configuration data will be specified in the design
documentation, but the essential property of values that are stated to be
configurable is that they can accommodate rapid amendment or
extension as required. Note that where a field is common to a number of
messages, configurable mappings are based on configuration data that is
also common to all the messages. So the mapping of such common
fields can be configured only once and applies to all LINK messages, it is
not configured individually on a per-message basis.
System Date The date as held on the NBS Authorisation Agent system.
System Time The time as held on the NBS Authorisation Agent system.
Fixed Value Data that always has a fixed value
2.1 Scope
The document considers the following message mappings:
Balance Enquiry [R1] to [R3] 0100
PIN Change [R14] to [R3] 0100
Withdrawal {R1] to [R3] 0200
Deposit [R11] to [R3] 0200
Balance Enquiry Response [A1] 0110 (or [R1]) to [A3]
PIN Change Response [A1] 0110 (or [R1]) to [A3]
Withdrawal Response [A1] 0210 (or [R1]) to [A3]
Deposit Response [A1] 0210 (or [R1]) to [A3]
Financial Reversal Request [R3],[A1] and possibly [CO] to [E1] 0420/0421
PIN Change Reversal Request [R3],[A1] and possibly [CO] to [E1] 0624/0625
Response Codes
Reversal Reason Codes
Reversal Request Response [E2] messages received from LINK are only used internally within the NBS (i.e.
they are not mapped to a Horizon message), and so are not within the scope of this document.
2.2 Structure
The message mappings are contained in an Excel spreadsheet, which has been embedded in this document.
To open the spreadsheet, double-click on the attachment icon. The first sheet contains a summary of the
message mappings that are included in the scope of this document. Subsequent sheets detail each of the
mappings in turn.
Created on 30/04/2010 Version 4.0 Page 7 of 10
© Post Office™ 2004-2010
FUJ00002169
FUJ00002169
Horizon - LINK Mapping Project: EMV - Banking and Retail
COMMERCIAL IN CONFIDENCE Doc Ref: NB/IFS/033
3 Notes on the Spreadsheet
For each message pair, the triggered message is shown on the left, with the triggering (or source) message on
the right. The exception to this is the “Reversal Request” [E1] message, which can be triggered either by a
[CO] message, or by a late [A1] Approve response from LINK, and is populated from a number of other
messages. In this case the right of the sheet contains elements from each of these messages, and an
additional column has been included to indicate which message the element comes from.
The “Source” column contains the details of how the message element in the triggered message is populated,
including the mapping between message elements in each of the messages where applicable. The “Source”
column also includes a description of any translations that need to take place in the NBS.
A greyed out row in the triggering message indicates that there is a field in the triggered message that is not
populated from data contained in that source message. In these cases, the triggered message field may be
populated from a different message, determined by the NBS or taken from Reference Data. Fields that have
been identified as being not required in the NBS — LINK Application Interface Specification document,
Reference [2], have not been included in the message.
A greyed out row in the triggered message column indicates that there is a field in the triggering message that
has no corresponding field in the triggered message.
For example, fields provided in a LINK message that do not map onto a Horizon field, are not passed on by
the NBS, but are logged.
Similarly there are fields provided in a Horizon message that do not map onto a LINK field, and are not passed
on. The full list of fields in Horizon messages and their definitions and uses can be found in [3]; the following
fields which are not directly mapped to LINK messages are nevertheless relevant to NBS for the following
purposes:
Clerk_Identity Records identity of clerk operating at the outlet workstation (also
known as node or counter). This is required for audit purposes.
Client_Id Identifies a client of POL that is the end bank (card issuer) for a
transaction. This element is needed for reconciliation and reports.
Issuer_Scheme_Id A code to identify the Issuer Scheme, set from Reference Data at
the counter.
Message_Type Classifies the type of message being sent. e.g. R1 or CO.
Routing_Gateway Use to route transactions to the correct logical PI
Transactions are uniquely identified in the system by a combination of the Riposte Group ID and Node ID of
the originating counter, together with the receipt transaction date (year and day), and the last 6 digits of the
message number component of the Horizon_Txn_Num field of the message which originated the transaction.
In messages to LINK this information is held in the form of the Terminal Identification (which is made up from
the Riposte Group ID and Node ID) and the Retrieval Reference Number (which includes the receipt
transaction date and message number information).
The following point should be noted with regard to the use of binary coded decimal fields in ICC data: in
communication with the counter this data is transferred using one character for each decimal digit, but if there
is an odd number of digits, an extra padding character, a zero, is included at the start of the number. It follows,
for example, that a field shown in the spreadsheet as having 3 BCD digits would actually be transmitted as 4
characters, the first being a zero used for padding. This encoding facilitates the counter's communications with
the Pin Pad. The spreadsheet indicates in such cases whether or not the padding is retained when mapping
the messages.
Created on 30/04/2010 Version 4.0 Page 8 of 10
© Post Office™ 2004-2010
FUJ00002169
FUJ00002169
Horizon - LINK Mapping Project: EMV - Banking and Retail
COMMERCIAL IN CONFIDENCE Doc Ref: NB/IFS/033
4 Message Mapping Spreadsheet
“Horizon - LINK
Mapping.xis"
END OF DOCUMENT
Created on 30/04/2010 Version 4.0 Page 9 of 10
© Post Office™ 2004-2010