Fujitsu Services
EMV Retail: User Interface Design Proposal Ref:
COMMERCIAL IN-CONFIDENCE Date:
FUJ00001933
FUJ00001933
NB/REQ/003
Version: 2.0
21" April 2005
Document Title:
Document Type:
Release:
Abstract:
Document Status:
Originator & Dept:
Contributors:
Internal Distribution:
External Distribution:
Approval Authorities:
EMV Retail — User Interface Design Proposal
User Interface Design Proposal
S70
This document presents a proposal for the user interface
(dialogue, activity flows and screen flows) to be developed at the
Counter Application for EMV Retail
This document is presented on a Subject to Contract and
Without Prejudice basis.
APPROVED
Roger Donato, APDU Design
Chris Bailey, Roger Donato, Mike Jenkins, Dave Johns, Ramesh
Kallidai, Steve Lewin, Peter Lucas, Helen Pharoah
Fujitsu Services Document Management, Reviewers
Bob Booth, Vicky Gray
Name
Position
Signature
Date
Tony Drahota
RASD Director
Post Office Account
Fujitsu Services
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 1 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
0.0 Document Control
0.1 Document History
Version No. I Date Reason for Issue Associated
CP/PinICL
0.1 24/09/03 First draft for internal comments
0.2 29/09/03 Second draft for informal PO comments
0.3 12/11/03 Third draft for informal PO comments
0.4 13/11/03 Fourth draft for informal PO comments
0.5 20/11/03 Fifth draft for PO comments
1.0 03/02/04 Baselined CP 3647
Ll 11/03/04 New draft version Addition of application selection I CP 3648
from the counter, and card removal dialogue at CP 3658
completion of session
1.2 05/04/04 New drafi version applying changes from internal
review comments
13 25/04/04 New draft version applying changes from internal
and external review comments
14 28/05/04 New draft version. Re-alignment due to new PIN pad
application documentation.
15 30/06/04 New draft version applying changes from internal CP 3738
and external review comments
1.6 23/07/04 Intermediate version
17 03/09/04 Intermediate version
18 29/03/05 Version incorporating changes from the changes PC0104918
supplement NB/REQ/004 v1.0 PC0106457
PC0106872
PC0107169
PC0107395
PC0107635
PC0107687
PC0107924
PC0107925
PC0107973
PC0108087
PCO0108091
PC0108093
PC0108094
PCO0108098
PC0108331
PC0108350
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE Page: 2 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
Ref:
Version:
Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
PC0108773
PCO109175
PC0109176
PCO0109178
PC0109179
PC0109180
PCO109181
PCO109182
PC0109482
PC0109587
PC0109600
PCO109858
PCO0109901
PCO110095
PCO110135
PCO110282
PCO110480
PCO110822
PCO110989
PCO111064
PCO112069
PCO114477
2.0 21/04/2005 Baselined
0.2 Review Details
Review Comments by: I Not applicable
Review Comments to :
Mandatory Review Authority Name
Fujitsu Services
Peter Lucas*
Post Office Ltd Bob Booth* , Vicky Gray*
Optional Review / Issued for Information
SI Design Roger Donato, Chris Bailey, Dave Johns
SI Development
Matt Arris, Trish Morris*
SI Test
Julie Havard
ITU Debbie Richardson, Hermia Figueiredo,
Eric Jennings*, Janusz Hollender
Programmes Stephen Probert, Gill Jackson
IPDU Simon Fawkes
Post Office Ltd
Bob Booth* , Vicky Gray*
(*) = Reviewers that returned comments
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 3 of 224
Fujitsu Services
EMV Retail: User Interface Design Proposal Ref:
Version:
COMMERCIAL IN-CONFIDENCE Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
0.3 Associated Documents
Reference Version I Title Source
AS/DPR/008 Design Proposal for DDA - PIN Entry Device I Fujitsu
Audio System Services
AS/DPR/009 Design Proposal for EMV, TDES and NBE Fujitsu
Replacement Services
BD/CDE/001 EMV - Banking and Retail - Conceptual Design I Post Office Ltd
CR/CDE/009 Conceptual Design for DDA Beeps Post Office Ltd
NB/HLD/012 I 0.10 EMV Retail and Banking, Counter, High-Level I Fujitsu
Design Specification Services
NB/PRP/004 EMV Banking User Interface Design Proposal I Fujitsu
Services
NB/REQ/004 I 1.0 EMV Retail User Interface Design Proposal— I Fujitsu
Changes Supplement Services
NB/SPE/003 Network Banking Counter Dialogue — Activity I Fujitsu
& Screen Flows Services
NB/SPE/013 Debit Card: Counter Dialogue — Activity and Screen I Fujitsu
Flows Services
NB/SPE/009 Network Banking / Reference Data Rules and Post Office Ltd
RDP/TEC/977 Values
Unless a specific version is referred to above, reference should be made to the current
approved versions of the documents.
0.4 Definition of Terms
An ‘*’ following the Term, e.g. “Counter*”, indicates that the definition is taken from the
codified agreement.
Term
Definition
Button
Icon on the Riposte Desktop which can be selected by the user via
the touch-screen or equivalent keyboard function key to invoke a
particular action
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 4 of 224
Fujitsu Services
FUJ00001933
FUJ00001933
EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Cancel
A transaction that is terminated before a Request message is
generated at the counter is cancelled. Cancel includes:
- Transactions that cannot proceed i.e. require no action from the
Clerk
- Transactions that require the Clerk to cancel them by using a
function on the screen
In all cases no record of the transaction is maintained by the counter
system.
Cardholder
Verification Method
Different methods of Cardholder Verification are possible :
e Verification by Signature
e Verification by PIN
© No verification
For EMV Retail the verification method is determined by the card
contents and the Hypercom application: (the prime one is normally
verification by PIN)
Chip and PIN
Authentication and verification of an ICC card using EMV standards
and a PIN
Clerk Any person who serves customers at a Counter Position in a Post
Office.
Client* An organisation on behalf of which Post Office Ltd provides a
service to Customers at Outlets.
Counter* A serving position in a Post Office, where a Customer transacts
business with a Counter Clerk.
Counter Application
An application resident within the counter processor that contains
the business logic controlling the dialogue with the Clerk.
Counter Dialogue
The dialogue between the Post Office Clerk and the Horizon
platform in the Post Office.
Customer*
A person transacting, or seeking to transact business with Post
Office Ltd through any of the supported Services.
Customer Receipt
The Receipt handed to the Customer
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE Page: 5 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
FUJ00001933
FUJ00001933
EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Decline
A transaction is declined when it does not proceed as per the initial
customer request. Decline includes:
- Transactions that cannot proceed because a decline response has
been received at the counter.
- Decline by counter due to timeout, i.e. no response received to
the request
- Decline by PIN pad, irrespective of institutional verdict (by
AAC)
- Decline because PIN pad cannot process request even though
response has been received to request — where Card has been
removed
In all cases a record of the transaction is maintained by the counter
system.
EMV Transaction
A Retail Transaction which uses an ICC and which conforms to the
EMV protocol as specified in Europay Mastercard Visa Books I to
4,
First Generate AC
The GENERATE AC is a command executed by the PIN pad which
sends transaction-related data to the ICC, which computes and
returns a cryptogram. The cryptogram determines the subsequent
action to take place by application.
The Horizon application has been implemented so that a normal card
transaction uses two GENERATE AC commands: the first
command follows PIN entry and determines whether the transaction
should cancel at that point, fallback to an alternative verification
method, or proceed by going on line to the financial institution: the
second command takes place after the authorisation response is
received from the financial institution and determines whether the
transaction is approved or declined.
Detailed explanations of these commands appear in EMV Integrated
Circuit Card Specifications for Payment Systems (the published
standard for EMV)
Horizon
The service implemented by Fujitsu Services for Post Office Ltd per
the contract awarded in May 1996, and amended in May 1999
following the withdrawal of the DSS.
Merchant Acquirer
A central third party computer system [(contracted for by POL)]
which facilitates the handling of DC messages interfacing between
the POL Service Infrastructure and [Card Issuers / Banks] as
necessary
Method of Payment The form of payment recorded against a transaction involving a
(MOP)* customer.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 6 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Mode Environment within the Riposte Desktop where a transaction is
processed.
Office / Outlet
A Post Office or any other location where Post Office Ltd (whether
directly or by means of agents) transacts business with customers.
Office Receipt
The transaction receipt retained in the Outlet.
Off-line
Where a system elects not to communicate with another system —
typically the counter having the rules held locally to enable it to
complete the transaction.
Off-line Indicator
A mechanism by which the Clerk can detect that an on-line
transaction will not be successful due to network failures prior to
swiping a card or manually entering the card details.
On-line
Where a system attempts to communicate with another system —
typically the counter seeking authorisation from a Client.
PAN Sequence
Number
Means of differentiating between different cards sharing the same
PAN
Receipt
A printed record of the transaction at the office. Both office and
customer receipts are produced.
Reference Data*
A set of agreed parameters and relationships controlling the
operation of Post Office Ltd Services.
Response Code
Code returned in the Authorisation message or created by the
Counter if no Authorisation message is returned. It contains the
outcome of the request. These codes and their meanings are defined
in Section 6.
Retail Payment Card
A credit, debit or bankcard (either magnetic stripe or EMV) used for
settling a Retail Transaction.
Retail Transaction
A Transaction supported in accordance with paragraph [4.2.1] of the
Debit Card Functional Description which states :
DC Transaction Types
Purchase
Refund to card
Implicit Reversal
Explicit Reversal
Second Generate AC
See First Generate AC
Serve Customer Mode
Desktop environment for conducting a customer transaction.
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE Page: 7 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
FUJ00001933
FUJ00001933
EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Session Receipt
Receipt produced at end of customer session containing a summary
of the transactions carried out during that session: it contains details
of purchases, refunds and settlement. In some instances the session
receipt may be optional, but it will always be printed if any of the
items is marked in reference data as requiring a receipt. It is intended
that debit card settlement products will be marked as requiring a
receipt so a session receipt will always be produced with all debit
card transactions
Settlement Mode
Desktop environment for conducting a customer retail transaction.
Transaction*
A recorded and auditable instance of business activity, involving
service provision or stock movement across organisational or service
boundaries.
0.5 Abbreviations
Abbreviation Definition
[A] Authorisation
AID Application Identifier
AAC Application Authentication Cryptogram. Message type sent by the
PIN pad to the counter which declines the transaction regardless of
whether the merchant acquirer has authorised or declined the
transaction
ACK Acknowledgement. Message type sent by the Counter to the PIN
pad
ARP An abbreviation for the message which is sent from the client host
system in response to an online request for authorisation the
message contains amongst other things the ARPC cryptogram and
the authorisation response code.
ARQ Application Request. Message type sent by the PIN pad to the
counter
BI3 Banking Increment 3.
[Cc] Confirmation
[Co] Null Confirmation
CVM Cardholder Verification Method
DC Debit Card
DSP. Display. Message type sent by the PIN pad to the counter
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE Page: 8 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
EPOSS Electronic Point of Sale Service
EFT Electronic Funds Transfer. Message type sent by the counter to the
PIN pad to launch a new financial transaction: this triggers the PIN
pad to ask for a card to be inserted (unless already present) and to
process that card
EMV Europay Mastercard Visa
GenAC Generate Application Cryptogram (see First Generate AC / Second
Generate AC)
ICC Integrated Circuit Card
JIN Issuer Identification Number
KBD Keyboard and Display Request. Message type sent by the PIN pad to
the counter
MA Merchant Acquirer
MOP Method of Payment
MSR Magnetic Stripe Reader
NBS Network Banking Service
PAN Primary Account Number
PED PIN Entry Device
PIN Personal Identification Number
PKE PAN Key Entry
STA Status. Message type sent by the PIN pad to the counter
TC Transaction Confirmed. Message type sent by the PIN pad to the
counter for successful financial transaction
TDR TLV Response. Message type sent by the PIN pad to the counter
which provides data in response to a TLV message
TLV Tag length variable: data format used by the PIN pad. Also the name
of a message type sent by the counter to the PIN pad asking for
information
VEY Verify. Message type sent by the PIN pad to the counter
0.6 Changes in this Version
Version Changes
0.2 e Changes made as a result of internal comments to structure of
document and activity flows
0.3 ¢ Changes arising from walk-through with PO and internal design
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 9 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
© review
0.4 ¢ Changes arising from discussions with Hypercom:
e PIN Length check for Capture PIN removed
e Introduced section 7.2 for variations of messages of screen
ERP2 depending on PIN-retry counter
0.5 © Changes to flow charts and screens as per discussions with PO at
workshop on 14/11/03
e Added Annexe A and B
© Deleted Section 6
e Added Table for Audio Cues in Section 6.3 (renumbered after
deletion of the original section 6)
e Added Function Key activity table for PIN pad screens
e Declined Transactions Receipt expanded
1.0 ¢ Document ownership transferred from Ramesh Kallidai to Roger
Donato
¢ Section 1.1 — Disclaimer and Copyright statements added
© Section 2.2 - Flowchart in Figure 2 Activity Flows for EMV
Retail — Transaction Start redrawn as Figure 2 Transaction Start
and Figure 3 Swipe Card. Changes:
¢ other settlement options shown
e screen EB1 wording modified
¢ screen EB2 removed
e ICC card not allowed as MSR transaction (fallback) unless
card has been rejected in PIN pad or PIN pad is broken
e Section 2.2 - Flowchart in Figure 3 Activity Flows for Retail —
Offline Checks renumbered as Figure 4
e Section 2.3 - Flowchart in Figure 4 Activity Flows for EMV
Retail — Amount Capture renumbered as Figure 5
© Section 2.3 - Flowchart in Figure 5 Activity Flows for EMV
Retail — Application Selection renumbered as Figure 6. Changes:
© — options introduced for signature verification and No CVM as
result of [CP 3647]
e — logging of failed chip cards so that they can be re-tried as
MSR
© Section 2.3 - Flowchart in Figure 6 renumbered as Figure 7
Activity Flows for EMV Retail — PIN Verification. Changes:
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE Page: 10 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
FUJ00001933
FUJ00001933
EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
e clerk allowed to select bypass option on ER4 screen
© processing allowed to continue in PIN bypass mode when
PIN is locked: (so long as card allows)
¢ clerk also allowed to try EMV card as swipe card following a
failure in the PIN pad
© Section 2.3 — New flowchart added for signature verification
in Figures 8 as result of [CP 3647]
¢ Section 2.3 - Flowchart in Figure 7 Activity Flows for EMV
Retail — Process Response renumbered as Figure 9. Changed to
support Signature verification as result of [CP 3647]
¢ Section 2.3 — New flowchart added for Print Receipt for
Signature in Figure 10 as result of [CP 3647]
¢ Section 2.3 — New flowchart added for Reprint Receipt for
Signature in Figure 11 as result of [CP 3647]
¢ Section 2.3 — New flowchart added for Completion in Figure 11
¢ Section 2.3 - Flowchart in Figure 8 Cancel Flows for EMV
Retail renumbered as Figure 13
¢ Section 2.4 - Flowchart in Figure 9 Activity Flows for System
Decline renumbered as Figure 14. Also PIN pad message was
been removed to give card to clerk for retention
e Section 3 — Receipt layout changed
© Section 5.1.4 — Screen ER4 Waiting for PIN added to replace
screen 3. New screen allows clerk to cancel or to bypass PIN
entry
e Section 5.2 — PIN Pad layouts for PIN entry and retry changed
¢ Section 6.1.1 - message text altered to be consistent with ER1
screen
e Section 6.1.2 — PIN entry and PIN locking code changes
e Section 6.3 — modified to provide more information on the
audio beeps on the PIN pad
e Section 7.1.1 — counter screen EB1 (Proceed as Chip Card)
reworded
e Section 7.1.2 — counter screen EB2 (Only Proceed as Chip Card)
removed
e Section 7.2.7 — PIN pad screen EBP8 (Please hand card to
assistant) removed for card retention
e Section 7.2.11 — PIN Pad layout for PIN entry moved to section
§.2
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE Page: 11 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
e Section 8.1 — Existing screens from Network Banking added to
this document
Screen 11: Office Receipt Printing
Screen 13: Check Signature
Screen El: Signature Receipt OK
Screen E2: Signature Check (2nd Receipt)
Screen E3: Signature Check (2nd attempt)
Screen ES: Signature Checks Failure Options
Screen E6: Print Preview
e Section 8.1.1 — Existing screen 3 Waiting for PIN now removed:
replaced by screen ER3 in section 5.1.3
e Section 8.1.13 — Existing screen E4 Invalid Card will also now
also report on cards not read in PIN pad
Ll e Document changed to support the following
e Application selection from the counter [CP 3658]
¢ Reminding customer to remove card from PIN pad at
conclusion of transaction [CP 3648]
¢ PIN bypass to be switched off at the counter by reference
data
e Application of comments received from version 1.0
The detailed changes are as follows:
e Section 2.3 - Flowchart in Figure 6 — Application Selection
replaced by
e Figure 6 — Insert Card to PIN pad
e Figure 7 — Fallback Processing
e Figure 8 — PIN pad AID selection
e Figure 9 — Counter AID selection
Changes required by [CP 3658]: Counter Clerk Selection of PIN
Pad Application
e Section 2.3 - Flowchart in Figure 7 — PIN Verification replaced
by
e Figure 10— PIN Verification
e Figure 11 — PIN already locked
e Figure 12 — Enter PIN
e Figure 13 — Customer locks PIN
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 12 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Changes made to provide clarification
e Section 2.3 — Figure 8 - Signature Verification renumbered as
Figure 14
© Section 2.3 - Figure 9 - Process Response renumbered as Figure
15
e Section 2.3 — Figure 10 - Print Receipt for Signature
renumbered as Figure 16
e Section 2.3 — Figure 11 - Reprint Receipt for Signature
renumbered as Figure 17
© Section 2.3 — Figure 12 — Completion Flows for EMV Retail
renumbered as Figure 18
© Section 2.3 - Figure 13 Cancel Flows for EMV Retail
renumbered as Figure 19
© Section 2.4 - Figure 14 - System Decline renumbered as Figure
20
e Section 2.4 - Figure 21 — Remove Card added. To remind clerk
to tell customer to remove card from PIN pad: this change
required as result of [CP 3648]
e Section 3 — Receipt layouts modified
© Section 5.1.1 — Screen ER1 Jnsert Card — renamed as Insert
Card (First attempt) and wording modified
e Section 5.1.2 — Screen ER2 Multiple Cards — wording modified
e Section 5.1.3 — Screen ER3 PIN Locked — wording modified and
action sequence modified in right hand panel
e Section 5.1.4 — Screen ER4 Waiting for PIN (2 buttons) —
wording modified
e Section 5.1.5 — Screen ERS Waiting for PIN (1 button) — added
e Section 5.1.6 — Screen ER6 Card cannot be read by PIN pad
added. New screen allows clerk to cancel or use card as
magnetic swipe
¢ Sections 5.1.7 and 5.1.8 New screens ER7 and ER8 which
monitor problems being experienced by the customer getting his
card read by the PIN pad
e Section 5.1.9 — Screen ER9 Remove Card — added [CP 3648]
¢ Section 5.1.10 — Screen ER10 Application Selection — added
[CP 3658]
e Section 5.2.1 to 5.2.3 — PIN pad screens EBP12a, EBP12b,
EBP12c used for PIN entry reformatted according to Hypercom
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE Page: 13 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
¢ Retail application
e Section 5.2: following screens removed:
5.2.4 ERP2a PIN Locked — Remove Card
5.2.5 ERP2b PIN Locked — Don’t Remove Card :
5.2.6 ERP2c PIN Now Locked — Remove Card
5.2.7 ERP2d PIN Now Locked — Don’t Remove Card
and replaced by single screen ERP2 PIN BLOCKED
¢ Section 5.3 — table amended to be consistent with screens
¢ Section 6.1.1 - message text altered to be consistent with screens
e Section 6.3 — audio beep for 0-9 corrected to 2kHz to be
consistent with AS/DPR/008 - Design Proposal for DDA - PIN
Entry Device Audio System
¢ Section 7.2 - PIN pad screens modified in response to comments
from the Post Office and technical data received from Hypercom
e Section 7.2.4 — screen EBP4 no longer output by PIN pad
¢ Section 7.2.12 screen EBP13 added for application selection at
the counter: change required by [CP 3658]
© 7.2.13 to 7.2.18 following PIN pad screens added relating to
card insertion
Screen EBP14: Remove & Re-insert Card (1)
Screen EBP15: Re-insert Card (1)
Screen EBP16: Remove & Re-insert Card (2)
Screen EBP17: Re-insert Card (2)
Screen EBP18: Remove & Hand Card to Cashier
Screen EBP19: Hand Card to Cashier
Screen EBP20: Cancelled.
e Section 8.1 — Existing screens from Network Banking added to
this document
Screen 5: Waiting for Authorisation
e Section 8.1.14 — Screen E4: Invalid Card. Messages modified
1.2 ¢ Section 2.2 — Figure 2 — Transaction Start modified
¢ Section 2.3 — Figure 7 — Fallback Processing modified
e Section 2.3 — Figure 8 — PIN pad AID selection modified
¢ Box 8.9 altered to allow on line authorisation for cards
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 14 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
e where from date and/or expiry date are out of range
e Clarification of cancel by the customer
e Section 2.3 — Figure 10— PIN Verification modified
e Screen ER13 Please Wait added at box 10.11 when clerk
touches Cancel on Waiting for PIN screen
e Section 2.3 — Figure 11 — PIN already locked modified
e Screens ERI1 Please Wait and ER12 Please Wait added at
boxes 11.5 and 11.7 when clerk touches Bypass on Waiting
for PIN screen
¢ Section 2.3 — Figure 12 — Enter PIN modified
¢ Box 12.4 single panel screen EB4 Customer Cancelled used
instead of double panelled screen 19
¢ Correction at box 12.11
¢ Section 2.3 — Figure 13 — Customer locks PIN modified
¢ Box 13.1 PIN pad screen ERP2 used instead of EBP11
¢ Section 2.3 — Figure 14 - Signature Verification. Title modified
¢ Screens ERI1 Please Wait and ER12 Please Wait added at
boxes 14.4 and 14.14
e Process boxes added at 14.5, 14.6 14.15 and 14.16 to
provide more details of message flows between Counter and
PIN pad
¢ Section 2.3 — Figure 15 — Process Response modified. Flow for
non CVM corrected at box 15.7
= Section 3 — line 17 of receipt layouts corrected to remove
reference to “Parcel Traffic” which will never appear on a retail
card receipt
= Section 3.2.5.1 Receipt outcome messages: references to
magnetic swipe and PIN removed
= Section 5.1.1 — Screen ER1 /nsert Card — Prev button removed,
wording modified, and right hand panel amended
= Section 5.1.2 — Screen ER2 Multiple Cards — Prev button
removed and wording modified
= Section 5.1.3 — Screen ER3 PIN Locked — Prev button removed
and wording modified
= Section 5.1.4 — Screen ER4 Waiting for PIN (2 buttons) — Prev
button removed and wording modified
= Section 5.1.5 — Screen ERS Waiting for PIN (1 button) — Prev
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 15 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
= button removed and wording modified
= Section 5.1.6 — Screen ER6 Card cannot be read by PIN pad
Prev button removed and wording modified
= Section 5.1.7 — Screen ER7 Insert Card (Second Attempt) —
Prev button removed, wording modified, and right hand panel
amended
= Section 5.1.8 — Screen ER8 /nsert Card (Third Attempt) — Prev
button removed, wording modified, and right hand panel
amended
= Section 5.1.9 — Screen ER9 Remove Card from PIN pad — Prev
button removed and wording modified
= Section 5.1.10 — Screen ER10 Application Selection — Prev
button removed, and right hand panel amended
= Section 5.1.11 - Screen ER11 Please Wait — Signature CVM
added
= Section 5.1.12 - Screen ER12 Please Wait — No CVM added
= Section 5.1.13 - Screen ER13 Please Wait added
= Section 7.1.1 — Screen EB1 Proceed as Chip Card? — Prev
button removed
= Section 7.1.2 — Screen EB2 Transaction Cancelled by the
Customer — Prev button removed
= Section 7.2.12 — PIN pad Screen EBP/3: Application Selection
at Counter — Function key actions corrected
= Section 8.1 - Screen E11 — No Services Available. Screen added
1.3 © Section 2.3 — Figure 2 — Transaction Start
- Completion of Fast Cash and Fast Cheque settlements
now routed to Figure 18 — Complete Non EMV
- step 2.21 modified
© Section 2.3 — Figure 3 — Swipe Card minor change
e Section 2.3 — Figure 8 — PIN pad AID selection minor wording
change
© Section 2.3 — Figure 11 — PIN already locked simplified to fit in
with Figure 14
¢ Section 2.3 — Figure 12 — Enter PIN changed
- now includes PIN pad screens ERP3 and ERP4
- Screen 5 Waiting for Authorisation added
- extra boxes to show messages between PIN pad and
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 16 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
- counter
- support multiple verification methods
e Section 2.3 — Figure 14 — Signature Verification & No CVM
simplified to have single entry points
© Section 2.3 — Figure 15 — Process Response changed: PIN pad
screen EBP10 Approved / Remove card repositioned (in line
with changes made to Figures 16 and 18
© Section 2.3 — Figure 16 — Check Signature: step removed to
display PIN pad screen EBP10 Approved / Remove card: (in line
with change made to Figure 15
© Section 2.3 — Figure 18 — Completion: changed
- Completion of Retail card transaction now always returns
to settlement menu
- step removed to display PIN pad screen EBP10 Approved
/ Remove card: (in line with change made to Figure 15
¢ Section 2.3 — Figure 20 — System Decline diagram corrected to
reverse “Y” and “N” flows out of step 20.14
e Section 3.2.5 , 3.3.5 & 3.4.5 — Electronic Funds Transfer
Sequence Number added to Session Receipt
© Section 3.2.5.1 Receipt Outcome messages extended to support
multiple verification methods
e Section 3.5.5 — Application ID. PAN Sequence Number, and
Electronic Funds Transfer Sequence Number added to Office
Signature Receipt
e Section 5.1.7 — Screen ER7 Jnsert Card (Second attempt) -
wording modified
© Section 5.1.9 — Screen ER9 Card in PIN pad - wording modified
and Cancel button changed to OK
e Section 5.1.11 - Screen ER11 Signature CVM — title changed
and wording modified
e Section 5.1.12 - Screen ER12 No CVM - title changed and
wording modified
e Section 5.1.13 - Screen ER13 Cancelled - title changed and
wording modified
e Section 5.2.5 - PIN pad screen ERP3 Incorrect PIN - Retry
introduced
¢ Section 5.2.6 - PIN pad screen ERP4 Incorrect PIN — Last Retry
introduced
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 17 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
FUJ00001933
FUJ00001933
EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
1.4 ¢ Section 2.2 — Figure 3 — Tests adjusted for migration status.
e Section 2.2 — Figure 4 — 4.6 removed as redundant.
¢ Section 2.3 — Figure 8 — Additional test for No applications.
e Section 2.3 — Figure 5 — 5.14 removed as redundant.
¢ Section 2.3 — Figure 8 — 8.24 removed as redundant.
¢ Section 2.3 — Figure 11 — 11.9 removed as redundant.
e Section 2.3 — Figure 12 — 12.5 and 12.17 removed as redundant.
¢ Section 2.3 — Figure 13 — 13.8 removed as redundant.
e Section 2.3 — Figure 20 — 20.26 removed as redundant.
¢ Section 2.3 — Figure 21 - has been changed to use error message
screen ER14.
¢ Section 2.3 — Figure 8 — the Send END message box was
incorrectly placed and has been relocated in Figure 21.
© Section 2.3 — Figure 19 — missing PIN pad messages and a
Timeout path have been included.
e Section 2.3 — Figure 11 — END from PIN pad described too
early — box removed.
© Section 2.3 — Figure 12 — ARQ processing amalgamated with
figure 14.
¢ Section 2.3 — Figure 14 — ARQ path duplication removed.
e Section 2.3 — Figure 17 — PIN pad dialogue for signature added.
¢ Section 2.3 — Figure 18 — PIN pad dialogue for signature added.
e Section 2.3 — Figure 10 — New screens added for PIN entry.
e Section 2.3 — Figure 12 — PIN Verification off page markers
changed.
¢ Section 2.3 — Figure 7 — Add the remove card message to the
dialogue.
1.5 ¢ Section 2.2 — figure 2 — Show the existence of card insertion
timeout.
© Section 1.5 introduced to following comment by BB on absence
of application selection rules statement.
¢ Section 2.2 — figure 3 — Notes 3.5 and 3.6 changed.
¢ Section 2.3 — figure 6 — New card inserted screen inserted into
the flow 6.27.
¢ Section 2.3 — figure 7— Document card removal process i.e. PIN
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE Page: 18 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
FUJ00001933
FUJ00001933
EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
e pad beeping, beep override button, following PIN pad action and
customer action.
¢ Section 2.3 — figure 8 - PIN pad timeout for application
selection removed. No such thing.
¢ Section 2.3 — figure 8 — New screen ER22 for card decline
before RAC authorisation sequence.
¢ Section 2.3 — figure 9 — New screen ER23 for pause between
clerk application selection and PIN entry.
¢ Section 2.3 — figure 10 and 12 — The flow charts document the
PIN retry process incorrectly. New symbols have been added to
figure 10 and existing symbols removed from figure 12
¢ Section 2.3 — figure 12 - New screen ER22 added to the flow to
document card sponsored declines as a result of card action
analysis. I.e. decline as a result of an attempt to bypass PIN
entry for a card, which does not allow it.
© Section 2.3 — figure 13 — Notes — correction to off page marker
comment.
¢ Section 2.3 — figure 15 — Document TLV/TDR dialogues.
© Section 2.3 — figure 16 — Document printer and clerk actions.
e Section 2.3 — figure 17 — new symbol to document printer re-
print action.
¢ Section 2.3 — figure 18 — Write [C1] box removed as misleading.
¢ Section 2.3 — figure 19 — PIN pad timeout off page marker
moved to include screen EB4.
© Section 2.3 — figure 20 — Decline is only performed once that
card has been removed form the PIN pad. The Remove card off
page marker has therefore been replaced with and end of process
symbol.
© Section 2.3 — figure 20 — 20.20 replaced with Print Error
Message report. Print Customer Slip was incorrect.
© Section 2.3 — figure 21 — New End Process off page marker
added.
© Section 2.3 — figure 21 — Remove Card 2 off page marker
added.
¢ Section 2.3 — figure 19 — Remove Card 2 off page marker
diverted to Remove Card 2.
¢ Section 2.3 — figure 21 — 21.12 clerk acknowledged symbol
removed the step was repeated at 21.6.
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE Page: 19 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
FUJ00001933
FUJ00001933
EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
¢ Section 2.3 — figure 21 — Document counter action when clerk
acknowledges the ER9 screen.
e Section 2.3 — figure 21 — 21.19 added to test if declined
processing is required. If so off page marker takes the flow to
the Decline page.
e 3.2.5 —keyed indicator added to receipts.
© 3.3.5 — keyed indicator added to receipts.
e 3.4.5 — keyed indicator added to receipts.
e 5.1.20 — New screen ER20 Partner Bank. This is to be displayed
when the system recognises that the card in the PIN pad can be
used for banking as well as retail.
© 5.1.21 —New screen ER21 Card Inserted. Displayed when an
ICC card has been recognised and read.
e 5.1.22 — New screen ER22 for transactions, which are declined
by the card before authorisation.
* 6.0—several changes to message texts.
¢ Section 3.2.5 - Date and time of payment added to receipts
© Section 3.3.5 - Date and time of payment added to receipts
e Section 3.4.5 - Date and time of payment added to receipts
¢ Section 3.5.5 - Date and time of payment added to receipts
e 7.2.13 changed to include customised statement.
e 7.2.14 changed to include customised statement.
© 7.2.15 changed to include customised statement.
e 7.2.16 changed to include customised statement.
e 7.2.18 changed to include customised statement.
e Assorted message text changes.
e Section 2.2 — figure 2 — changed to bring the PIN pad back to a
stable state following card insert timeout.
e Section 2.2 — figure 2 — Changed to add EFT PIN pad
command.
¢ Section 2.2 — figure 4 —- Remove Card Process added.
¢ Section 2.3 — figure 6 — Omitted PIN pad screens added.
© Section 2.3 — figure 6 - STA 8 command added.
¢ Section 2.3 — figure 7 — Diagram modelled with extra branches.
¢ Section 2.3 — figure 8 — Remove Card process added.
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE Page: 20 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
e Section 2.3 — figure 8 — STA 9 command added.
© Section 2.3 — figure 8 — addition of Application selection PIN
Pad screen.
© Section 2.3 — figure 12 —- Remove Card process added.
¢ Section 2.3 — figure 11 - removed and amalgamated into figure
13
e Section 2.3 — figure 12 — 12.8 and 12.28 removed. Clerk cancel
is handled in figure 10.
¢ Section 2.3 — figure 13 - renamed PIN Blocked.
© Section 2.3 — figure 14— AAC decline processing added to first
generate AC level code.
© Section 2.3 — figure 14 — Remove Card process added.
¢ Section 2.3 — figure 14 — PIN ok branch relocated to this figure.
e Section 2.3 — figure 15 — new branch added for customer cancel
by card removal whilst waiting for authorisation.
© Section 2.3 — figure 15 — forced decline paths added.
¢ Section 2.3 — figure 15 — Remove Card process added.
¢ Section 2.3 — figure 21 — Removal of customer cancel to figure
15.
1.7 ¢ Section 2.3 — figure 8 — Off page marker changed from fallback
processing 2 to fallback processing.
e Section 7.2.3 — Application selection PIN pad screen changed to
agree with the PIN Pad application which shows a better format.
¢ Section 2.3 — figure 2 — card insertion timeout diagram moved
to figure 6.
© Section 2.2 — figure 2 EFT command moved to figure 5.
© Section 2.2 — figure 4 —- Remove Card process removed because
of relocation of insert card and insert card timeout.
e Section 2.3 — figure 6 — beeps symbols included at Peter Clerk’s
request.
© Sections 3.1.5 - Customer Session Receipt (Non debit card),
3.2.5 - Customer Session Receipt (with debit card), and 3.3.5
Duplicate Customer Session Receipt - MoP Value field width
increased from 13 to 16.
1.7 e Figure 2 — 2.25 EFT moved to figure 5 — 5.13.
e Figure 2 — card insertion flow moved to figure 6a.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 21 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
FUJ00001933
FUJ00001933
EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
e Figure 3 — 3.9 and 3.10 swapped.
e Figure 4 — 4.6 removed.
e Figure 5 — 5.13 changed to jump to Insert Card 1.
e Figure 6 — Removed and replaced by Figures 6a, 6b and 6c. This
was to include PIN pad beeps and card removal flows.
e Figure 7 — 7.3 moved to figures 6 and 8.
e Figure 7 — restructured to show card removal paths and beeps.
e Figure 7 — renumbered.
e Figure 8 — new 8.26 added to show PIN pad informing an MSR
fallback situation.
¢ Figure 8 — 8.15 and 8.16 moved to Figure 9.
e Figure 8 — New 8.22 End Command Process added.
e Figure 8 — 8.11 and 8.12 changed 8.12 now goes to PIN entry or
CVM Processing.
e Figure 8 — new 8.28 now goes directly to PIN Pad AID
Selection marker.
e Figure 8 — renumbered.
e Figure 9 — new 9.1 and 9.2 moved from Figure 8.
e Figure 9 — new 9.6, 9.7, 9.8 included for Clerk cancel.
¢ Figure 9 - renumbered.
e Figure 10 —new 10.7 goes to CVM processing.
e Figure 10—new 10.29, 10.30,10.31,10.32 clerk cancel process
added.
e Figure 10— new 10.12 loops back to 10.1 for PIN retry.
e Figure 10 — Renumbered.
e Figure 11- replaced by new Figure 11- CVM Processing. This
new diagram shows more closely how the counter dialogues are
determined by the PIN pad dialogue.
e Figure 12 — removed as functionality is described in new Figure
ll.
e Figure 13 — removed as functionality is described in new Figure
ll
e Figure 14 — old 14.25 removed as functionality is described in
Figure 11.
¢ Figure 14 —new 14.2and 14.10 added to show action analysis
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE Page: 22 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
FUJ00001933
FUJ00001933
EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
e checks in the PIN pad before showing the CVM screens ERI1
or ER12. These screens should not be displayed if the PIN Pad
declines the transaction.
e Figure 14— TLV/TDR dialogues not required in the AAC path
as we have not sent an RI at this stage. Therefore no Recov2,
CO and C1 required.
e Figure 14 — PIN processing marker added.
* Figure 14 — End Command Process 14.21 added in AAC path.
e Figure 14 — renumbered.
e Figure 15 — new 15.12, 15.13 Remove card and End Command
processing moved before signature verification test.
© Figure 15 — When card removed by customer while waiting for
authorisation, PIN pad shows the decline ( AAC ) then sends an
STA 6 cancel. 15.19,15.20,15.21 and 15.24,15.25,15.26 now
show this in better detail with the use of screen ER22.
e Figure 15 - 15.23 End Command Processing included in the
decline path.
e Figure 15 — new authorised screen implemented at 15.12 for
PIN and NoCVM transactions.
e Figure 15 — renumbered.
e Figure 16 — 16.5, 16.7, 16.9 new clerk direction symbols added.
e Figure 16 - new authorised screen implemented for signature
and combination transactions.
e Figure 16 — renumbered.
e Figure 17 — 17.17 and 17.18 removed as this functionality is
performed in Figure 15.
e Figure 17 renumbered.
e Figure 18 — 18.1 and 18.2 removed as this functionality is
performed in Figure 15.
e Figure 18 — renumbered.
e Figure 19 — 19.1 and 19.2 removed as Clerk cancels are handled
with their individual circumstances. Clerk Cancel marker
removed.
e Figure 19 — new 19.6, 19.8 and 19.9 added these are processes
which perform the same function.
e Figure 19 — renumbered.
¢ Figure 20 — Rearranged with End command processing
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE Page: 23 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
© separated out into a Figure of its own.
¢ Figure 20 — renumbered.
e Figure 21 — new Figure to introduced End Command
Processing. A process which encapsulates the handling of the
End command and any error processing.
© Section 3.2.5.1 — new RT codes added for payment/refund not
verified by cardholder.
© Section 3.2.5.2 — message texts for new RT codes.
¢ Section 5.1.3 — PIN Locked now reads PIN Blocked to bring it
in line with the PIN Pad display.
© Section 5.1.14 — additional text to explain %Reason%.
e Section 5.1.24 — Additional screen ER24 Card Insertion
Timeout.
© Section 5.1.25 — Additional screen ER25 Action Analysis
Approval Screen.
« Section 3 — Welsh receipt texts have now been included.
¢ PCnnn_Welsh/English receipt variants (3.2.5, 3.3.5, 3.4.5, 3.5.5)
Population with translations.
e@ ~PCnnn_MoP value (enhancement to accommodate longer MoP name)
3.1.5, 3.2.5) Clarification of the character positions for MoP values
of up to and more than 99999.99,
¢ ‘Keyed? indicator (3.2, 3.4, 3.5
¢ ‘Keyed indicator’ renamed ‘entry indicator’ as it now has
‘ICC’ and ‘swiped’ options.
The indicator on the Declined Receipt and Signature Slip extended to
include the ‘ICC’ or ‘swiped’ options.
Typographical corrections:
Customer Session Receipt (With debit card payment) (3.2.5) and Duplicate
(3.3.5): In English illustrations, two blank lines before ‘Thank You”
instead of one.
Office Debit Card Receipt for Signature (3.5.5) In illustration, ‘PAN Seq
No’ fieldname moved one space right to match character positions
given in field definition table.
e A new Figure, Figure 23 has been introduced to show card
removal for an authorised, non-signature transaction.
© Section 8.1.14 - Additional text added to screen 5.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 24 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
« Anew screen ER25 has been introduced to cover transaction
authorisation with card removal.
e Figure 20 — redrawn to omit redundant threads.
1.8 Application of changes from NB/REQ/004 v1.0 EMV Retail: User
Interface Design Proposal - Changes Supplement
¢ Section 1.2: Comment added to Scope concerning existence of
diagnostic screens (PC0106457)
© Section 2.1.5: Paragraph reworded to cover scope of the PIN
pad screens that have been documented within the flowcharts
(PC0104918)
© Section 2.2 Transaction Start: clarification of notes to - Figure
3 (PC0110480)
© Section 2.3.1 Amount Capture - screen ER26 Multiple Cards
(Refund) added to Figure 5 (PC0109179)
e Section 2.3.2 Card Insertion: Figures 6a, 6b, 6c modified
- position of PIN pad beeps altered on card insertion
(PC0108773)
- flow for counter detected timeout included (PC0112069)
- PIN pad screens EBP7 Cancelled Please Remove Card and
EBP11 Processing Please Wait displayed when Clerk
cancels transaction (PC0107169)
- Card removal timeout shown (PC0106872)
© Section 2.3.3 Fallback Processing: Figures 7 modified
(PC0106872)
¢ Section 2.3.4 Application Selection Figure 8 modified:
- Screen ER27 Declined (Refund) added (PC0109179)
- Screen ER28 Application Selection inserted after PIN pad
screen EBP3 in the 'Customer required to confirm’ flow
(PC0109176)
- Screen ER20 Partner Bank added (CP3738) (PC0109182,
PCO110282)
- PIN pad screens added EBP23 Card Blocked and EBP22
Application Blocked added (PC0110822)
- TLV /TDR messages removed
© Section 2.3.5 PIN Verification - Figure 10 modified:
- Correction of flows concerning the number of attempts at
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 25 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
- PIN entry
- Test added to flow to show effect of customer cancel from
the PIN pad
© Section 2.3.6 CVM Processing — Figure 11 modified:
- PIN pad screen added EBP21 Processing (PC0107635)
- Wait step shown
© Section 2.3.6 CVM Processing — Figure 14 modified:
- Replacement of screens ER11 and ER12 by screen 5
(EMV) Waiting for Authorisation (PC0109180)
- Routing to allow fallback to MSR after PIN entry
(PC0108350)
© Section 2.3.7 Process Response — Figure 15 modified:
- Split into separate flows Figure 15a and Figure 15b
- Flows for Chip and Signature updated to be in line with
implementation (PC0107395 & PC0107973)
- TLV /TDR messages removed / added
© Section 2.3.7 Process Response — Figure 16: updated to include
display and processing of screen 4 Card Checks (PC0109175)
© Section 2.3.10 Declined Transaction — Figure 20 modified:
- Allow for card retention if requested by Merchant Acquirer
- Counter logic changed where request and authorisation
amounts are unequal (PC0109482)
e Section 2.3.11 Card Removal and End Processing - Figure 21:
minor clarification
© Section 2.3.11 Card Removal and End Processing - Figure 22:
minor clarification
¢ Section 3.2.5 — Customer session receipt text changed to meet
Streamline requirements
- Addition of “Transaction confirmed” text (PC0107687)
- Addition of cardholder signature text on signature CVM
(PC0109587)
- Addition of cardholder signature text on combination
CVMs (PC0107925)
e Section 3.5.5: Office debit card receipt text changed for
combination CVM (PC0107924, PC0108331)
e Section 4.2.1: Response code 81 added (PC0111064)
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE Page: 26 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
© Section 4.2.2: Transaction Result Codes now shown and
definition of code 02 changed to include customer cancel
(PCO111064)
e Section 5.1: Prototype screen shots replaced by screen dumps
from live system
e Section 5.1.1: Message text changed on screen ERI Card
Insertion (PC0108087)
© Section 5.1.2: Message text and button definition changed on
screen ER2 Multiple Cards (Payment) (PC0109179,
PC0109901)
e Section 5.1.3: Message text changed on screen ER3 Pin Locked
(PC0109182)
e Section 5.1.4: Message text changed on screen ER4 Waiting for
PIN (2 buttons) (PC0109182)
© Section 5.1.5: Message text changed on screen ERS Waiting for
PIN (1 button) (PC0109182)
© Section 5.1.6: Tab heading in left hand panel changed on screen
ER6 Card Cannot be Read By PIN pad (PC0109182,
PC0109858)
e Section 5.1.7: Message text changed on screen ER7 Jnsert Card
(Second attempt) (PC108091, PC0109182)
e Section 5.1.8: Message text changed on screen ER8 Jnsert Card
(Third attempt) (PC0108093, PCO109182)
e Section 5.1.95.1.5: Message text and button definitions changed
on screen ER9 Remove Card from PIN pad (PC0109181,
PC0109182, PCO109858)
¢ Section 5.1.10: Tab heading in left hand panel changed on screen
ER10 Application Selection from the Counter (PC0108094)
e Section 5.1.11: Screen ER11 Signature CVM Selected removed
from flows and replaced by screen 5 (EMV) Waiting for
Authorisation (PC0109180)
© Section 5.1.12: Screen ER12 No CVM Selected removed from
flows and replaced by screen 5 (EMV) Waiting for
Authorisation (PC0109180)
e Section 5.1.13: Tab heading in left hand panel changed on screen
ER13 Cancelled (PC0108098)
e Section 5.1.15: Message text and help text changed on screen
ER15 Remove Card From PIN Pad (PC0109182, PC0109600)
e Section 5.1.16: Message text changed on screen ER16 PIN
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE Page: 27 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
e Entry — PIN Re-try (2 buttons) (PC0109182)
e Section 5.1.17: Message text changed on screen ER17 PIN
Entry — PIN Re-try (1 button) (PC0109182)
© Section 5.1.18: Message text changed on screen ER18 PIN.
Entry — Last Try (2 buttons) (PCO0109182)
e Section 5.1.19: Message text changed on screen ER19 PIN
Entry — Last Try (1 button) (PC0109182)
¢ Section 5.1.20: Message text and button definitions changed on
screen ER20 Partner Bank (PC0109182, PCO109858,
PCO110282)
© Section 5.1.22: Message text changed on screen ER22 Declined
(Payment) (PC0109179 / PCO109182)
e Section 5.1.24: Message text changed on screen ER24 Card
Insertion Timeout (PC0109182)
© Section 5.1.25: Message text and button definitions changed on
screen ER25 Transaction authorised remove card (PC0109181 /
PC0109182)
© Section 5.1.26: Insertion of screen ER26 Multiple Cards
(Refund) (PC0109179, PC0109901)
© Section 5.1.27: Insertion of screen ER27 Declined (Refund)
(PC0109179)
¢ Section 5.1.28: Insertion of screen ER28 Application Selection
(PC0109176)
e Section 5.1.29: Insertion of screen 5 (EMV) Waiting for
Authorisation (PC0109180, PC0109858)
e Section 5.2.2: minor change to line 2 on PIN Pad Screen
ERP 12b: Re-enter PIN - First Retry (PC0110095)
e Section 5.3: screens EBP20, EBP21, EBP21 added to list of PIN
displays shared with EMV Banking (PC0110822)
e Section 6.1.1:
- Revision to screen ERI (PC0108087)
- Revision to screens ER2 and ER22 for refund (PC0109179)
- Revision to screens ER3, ER4, ERS, ER6, ER7, ER8,
ERIS, ER16, ERI7, ER18, ER19, ER20, ER22, ER24,
ER25 (PC0108091, PC0108093, PC0109182, PCO109600,
PC0109858, PCO110282)
- Revision to button definitions on screens ER9 and ER25
(PC0109181)
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 28 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
FUJ00001933
FUJ00001933
EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
- Revision to button definitions on screens ER10, ER21 and
ER23 (PC0110989)
- Revision to screens ER13 (PC0108098)
- Addition of screens ER26 and ER27 for refunds
(PC0109179)
- Addition of screen ER28 Application Selection
(PC0109176)
- Addition of message definitions for amended left hand panel
of screen 5 (PC0109180)
e Section 7.1.2: Comment added relating to contents of Screen
EB4: Transaction cancelled by Customer (PC0114477) when
the customer removes card from the PIN pad too soon
e Section 7.2.5: Footnote added to description of PIN Pad Screen
EBPS: Remove Card
e Section 7.2.10: Comment added concerning the conditions under
which PIN Pad Screen EBP11: Processing is displayed
(PC0104918)
© Section 7.2.17: “Clerk” replaces “Cashier” in PIN Pad Screen
EBP18: Remove & Hand Card to Clerk (PC0109178)
© Section 7.2.18: “Clerk” replaces “Cashier” in PIN Pad Screen
Pad Screen EBP19: Hand Card to Clerk (PC0109178)
e Section 7.2.20: Insertion of PIN Pad Screen EBP21: Processing
(PC0107635)
e Section 7.2.21: Insertion of PIN Pad Screen EBP22: Application
Blocked (PC0110822)
© Section 7.2.22: Insertion of PIN Pad Screen EBP23: Card
Blocked (PC0110822)
e Section 8.1.2: Insertion of screen 4 Card Checks ) (PC0109175)
© Section 8.1.3: Comment added to show that screen 5 Waiting
for Authorisation will only be used for MSR transactions
(PC0109180)
¢ Section 10.1: Error code 08057 added to Annexe D - PIN Pad
error messages and Screen ER14 clerk messages (PCO1 10822)
e Section 11.1: new section added on PIN Pad Timeouts
(PCO110135)
2.0 Minor typographical corrections
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 29 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
0.7 Changes Expected
Changes
None
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 30 of 224
Without Prejudice and Subject to Contract
FU.
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
FUJ00001933
IJ00001933
0.8 Table of Contents
1.0 INTRODUCTION...
1.1. Privacy and Confidentialit 36
Accuracy.
1.3 Structure of this document
1.4 Overview of EMV functionality.
1.5 Application Selection.............
2.0 EMV USER INTERFACE...
Overview Description.
EMV Transaction Stages.
Stage 1.
Stage 2. ese
DC EMV Screen Flows.
Inclusion of PIN pad Displays in the Screen Flow
Conventions used within the flowcharts. .
" Stage 1: EMV Transaction Start & Off-line Check
Stage 2: EMV Card Payment/Refund...
Amount Capture.
Card Insertion.
Fallback Processin;
Application Selection.
PIN Verification.
CVM Processing.
Process Respons¢
Add Authorised Transaction to Stack.
Cancel Transaction...
Decline Transaction.
Card Removal and End Processin;
3.0 RECEIPT:
Customer Session Receipt (Non debit card)
Purpose.
Frequency.
Notes...
Sequence.
Layout and Example Content.
Customer Session Receipt (With debit card payment
Sequence.
5 Layout and Example Content........
Duplicate Customer Session Receipt.
Purpose...
Frequency
Notes...
Sequence.
3 Layout and Example Content.
3.4. Customer Debit Card Payment/Refund Receipt — Declined Transaction...
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 31 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Sequence.
3 Layout and Example Content.
3.5 Office Debit Card Receipt for Signatur
3.5. Purpose...
Sequence.
Layout and Example Content
4,0 I RESPONSE CODES AND THEIR EFFECTB..........
41 Screens.
4.1.1 Fixed screens, no response code based text.
4.1.2 Soft screens, based on response code.
4.2 Receipts...
4.2.1 Receipt Messages by response code/outcom
4.2.2 Transaction result codes.
5.0 SCREEN LAYOUTS......
5.1 EMV specific counter screens...
wl. Screen ERI: Card Insertion (First attempt).
‘aiting for PIN (2 buttons)
Screen ERS: Waiting for PIN (1 button)..
Screen ERG: Card cannot be read by PIN pad..
Screen ER7 Insert Card (Second attempt).......
Screen ER8 Insert Card (Third attempt
Screen ER9: Remove Card from PIN pat
Screen ER10: Application Selection from Counter
Screen ER11: Signature CVM Selecte«
Screen ER12: No CVM Selecte
Screen ER13: Cancelled - Please Wait
Screen ER14: PIN pad Error Screen...
Screen ER15: Remove Card from PIN pad.
Screen ER16: PIN Entry - PIN Re-try(2 buttons).
Screen ER17: PIN Entry - PIN Re-try (1 button
Screen ER18: PIN Entry — Last Try(2 buttons).
Screen ER19: PIN Entry — Last Try (1 button)..
Screen ER20: Partner Bank.
Screen ER21: Card Inserte:
Screen ER22: Declined (Payment).
Screen ER23: Application Selected Screen.
Screen ER24: Card Insertion Timeout.....
Screen ER25: Transaction Authorised Remove Card Screen..
Screen ER26: Multiple Cards (Refund).
Screen ER27: Declined (Refund).
Screen ER28: Screen ER28: Application Selectio:
Screen 5 (EMV): Waiting for Authorisation.
wl. Counter Screens shared with EMV Banking.
5.2. EMV Specific PIN displays....
5.2.1 PIN Pad Screen ERP 12a: Enter PIN.
5.2.2 PIN Pad Screen ERP12b: Re-enter PIN - First Retry.
5, PIN Pad Screen ERP12c: Re-enter PIN - Last Retry.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 32 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
5.2.4 PIN Pad Screen ERP2: PIN Blocked.
5.2.5 PIN Pad Screen ERP3: Incorrect PIN - Retry.
5.2.6 PIN Pad Screen ERP4: Incorrect PIN — Last Retry.
5.3 PIN displays shared with EMV Banking
6.0 EMV SPECIFIC MESSAGE TEXTS...
6.1 Message Collections...
6.1.1 Collection: MessageDe:
6.2. PIN pad messages...
6.3 Audio Cues at PIN Pad.
6.4 Help Text for data selection and inpu'
7.0 ANNEXE A.... eseeee:
7.1 Counter Screens Shared with EMV Banking.
1 Screen EBI: Proceed as Chip Card?.....
.2_ Screen EB4: Transaction cancelled by Customer
PIN Pad Screens shared with EMV Banking.
PIN Pad Screen EBP1: Welcome Screen.
PIN Pad Screen EBP2: Please Insert Car
PIN Pad Screen EBP3: Application Selection PIN pa
PIN Pad Screen EBP4: Card Invalid.
PIN Pad Screen EBPS5: Remove Card.
PIN Pad Screen EBP7: Cancelled - Remove Card.
PIN Pad Screen EBP8: Return Card?. .
PIN Pad Screen EBP9: Declined — Remove Card.
PIN Pad Screen EBP10: Approved — Remove Car
PIN Pad Screen EBP11: Processing.
PIN Pad Screen EBP12: Enter PIN.. oe
PIN Pad Screen EBP13: Application Selection at Counter.
PIN Pad Screen EBP14: Remove & Re-insert Card (1)..
PIN Pad Screen EBP15: Re-insert Card (1
PIN Pad Screen EBP16: Remove & Re-insert
PIN Pad Screen EBP17: Re-insert Card (2)...
PIN Pad Screen EBP18: Remove & Hand Card to Clerk.
PIN Pad Screen EBP19: Hand Card to Clerk.
PIN Pad Screen EBP20: Cancelled.
PIN Pad Screen EBP21: Processing.
PIN Pad Screen EBP22: Application Blocked.
PIN Pad Screen EBP23: Card Blocked...
8.0 ANNEXE B.......
8.1 Screens for EMV Retail used from existing NBS Applications.
1.1 Screen 3: Waiting for PIN...
Screen 4 Card Checks.
Screen 5: Waiting for Authorisation.
Screen 7: Other Decline.
Screen 9: Card Retaii
Screen 10: Transaction Failuri
Screen 11: Office Receipt Printing
Screen12: Tear off Error Message Instruction.
Screen13: Check Signature.
Screen 14: Printing Receip
Screen 19: Cancel Message.
Screen El: Signature Receipt OK...
Screen E2: Signature Check (2" Receipt
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 33 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Screen E3: Signature Check (2 attempt).
Screen E4: Invalid Card...
Screen ES: Signature Checks Failure Options...
Screen E6: Print Preview
Screen E7: Error Message.
Screen E8: Error Message.
Screen E9: Error Message.
Screen E10: Error Message...
Screen E11 — No Services Available.
8.2 Screens for EMV Retail used from existing DCS Applications
Screen D1: Amount Capture.
Screen D2: Error Message.
Screen D5: Nothing to Settl
8.2.4 Screen D6: Error Messagi
9.0 ANNEXE C.....
9.1 PIN Pad Commanda............. . cesteeseeeees
10.0 ANNEXE D.....
10.1 PIN Pad error messages and Screen ER14 clerk messages...
11.0 ANNEXE E..
11.1 PIN Pad Timeouts.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 34 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
1.0 Introduction
1.1 Privacy and Confidentiality
1.1.1 Accuracy
Fujitsu Services endeavours to ensure that the information contained in this document is
correct but, whilst every effort is made to ensure the accuracy of such information, it accepts
no liability for any loss (however caused) sustained as a result of any error or omission in the
same.
1.1.2 Copyright
© 2004 Fujitsu Services. All rights reserved. No part of this document may be reproduced,
stored or transmitted in any form without the prior written permission of Fujitsu Services.
1.2 Scope
The Post Office requirements for EMV are incorporated in BD/CDE/001 EMV - Banking and
Retail - Conceptual Design, and the overview response from Fujitsu Services is documented
in AS/DPR/009 - Design Proposal for EMV, TDES and NBE Replacement.
This particular document describes the User Interface Design Proposal for the Retail Payment
Card application resulting from the introduction of EMV cards using Chip and PIN
authentication and verification at the Post Office counter (at BI3 S70). The Debit Card
counter dialogues (prior to the introduction of EMV cards) are described in Debit Card:
Counter Dialogue — Activity and Screen Flows (NB/SPE/013). This document describes the
changes to the flow of activities, screen displays and prompts, and receipt layouts at the
counter described in the above document as a result of the introduction of EMV cards. It will
refer back to the above document for the flows, screens and prompts of both magnetic card
swiped operations and manual entry of card details that do not change as a result of the
introduction of EMV.
The primary purpose of the flow charts in this document is to define the User Interface, and in
particular, to define the sequence of screens displayed. They are not intended to be definitive
statements of the low-level design of the counter application.
The screens in this document are only for the purpose of understanding the information
content on the screens, and do not constitute a statement of low-level design.
The document describes only the screens seen during typical business transactions, including
error cases that can arise in normal processing. There are, however, additional diagnostic
screens that are not described within this document. These screens are only displayed in
exceptional cases, e.g. software, reference data configuration or exceptional hardware errors.
Such screens are beyond the scope of this document.
1.3 Structure of this document
This document is structured as follows:
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 35 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Section 2 provides the list of unique counter dialogues that are supported for EMV cards (BI3
$70) and describes the changes arising as a result of the introduction of EMV. For each
dialogue, there is a top level flow chart, which references further common sequences as
necessary.
Section 3 provides the layout of the Office and Customer receipts for those receipts that have
changed as a result of EMV functionality.
Section 4 is a table mapping the response codes returned to the counter in the [A] into system
actions with associated Clerk messages, receipt text and outgoing result code within the [C]
message.
Section 5 lists the unique screens that are supported for EMV, and defines the type of data
that appears on each screen.
Section 6 contains details of new messages/receipt text and help text.
Annexe A contains those screens that are shared between EMV Retail and EMV Banking and
found originally in EMV Banking — User Interface Design Proposal [NB/PRP/004]
Annexe B contains those screens that are not affected by the introduction of EMV Retail and
found originally in either Debit Card: Counter Dialogue — Activity and Screen Flows
(NB/SPE/013) or Network Banking: Counter Dialogue - Activity & Screen Flows
[NB/SPE/003].
1.4 Overview of EMV functionality
In line with the rest of the payments service industry Post Office Limited will be migrating
to the acceptance of EMV cards using Chip and PIN authentication for added security and
reduction of fraud. The counter service is therefore being enhanced to support Chip and
PIN authentication and verification. Existing services based on magnetic stripe card will be
continued for as long as there is a client demand.
For EMV transactions, the customer retains control over the card and interacts with the
existing PIN pad and integral smartcard device on the customer side of the counter. The
clerk is able to offer support to the customer, where required, through a series of prompts
by the system to the clerk indicating the sequence of operations to be followed and the
current status of the transaction.
EMV transactions will normally be supported by a CVM (Cardholder Verification
Method) of PIN entry but additional verification methods of Signature and No CVM will
also be supported. CVMs of Signature and No CVM may be offered when the PIN is
locked on the card. Some cards for disabled people may be set up with no support for PIN
entry but will instead use Signature CVM as the main verification method.
For magnetic stripe based transactions, including EMV cards operating in fallback mode,
the transaction is conducted by the clerk using the magnetic stripe reader on the clerk side
of the counter.
The counter provides receipt printing capability using industry standard counter printer
devices.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 36 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
1.5 Application Selection
In an application selection scenario, where the customer’s card contains multiple applications
and some of those applications are also supported by PED reference data then the PIN pad
will assemble a candidate list of mutually supported applications. The list may be in priority
order or in the order in which the applications are listed on the card. The candidate list will be
the intersection of the two sets of application identifiers, one from the PIN Pad and the other
from the card.
If the card is set up to make the selection on a priority basis then the highest priority
application will be selected.
If the card is not set up to make a selection on priority basis then as the Hypercom terminal
supports cardholder selection of application, the PIN pad will present the candidate list to the
customer.
When the customer has made their choice, that choice will be the application used for the
transaction. In a situation where the PIN pad detects that the chosen application is unusable
then a new candidate list will be assembled minus the unusable application and the new list will
be presented to the customer for selection. This process may continue until a successful
candidate has been chosen or until the list is exhausted. If no application is successfully
selected then this is a recognised fallback situation and MSR will be allowed for this card.
Application selection will be performed by the PIN pad as per EMV book 1.
An option to allow clerk selection of application will be provided for customers with a
disability. This facility is totally within the control of the customer and selection will be
performed by agreement with the customer.
2.0 EMV User Interface
The transaction flows in this section show the points at which screens are displayed to the
Clerk. These screens are used to inform and prompt the Clerk at appropriate steps in the
process of each transaction. The flow charts cover both Settlement mode (payment) and
Reversal mode (refund) transactions.
2.1. Overview Description
2.1.1 EMV Transaction Stages
EMV Transactions have two main stages:
1. Transaction Start & Token Validation
2. Transaction Service, Customer Verification, Receipt Printing and Transaction Completion
2.1.2 Stage 1
The normal start point for an EMV transaction is where the Clerk selects the appropriate
menu button from the settlement menu while the customer inserts the EMV card in the PIN
pad. However, if the card is swiped instead, and the service code in the Track 2 data indicates
that the card has an ICC, then the clerk will be given a warning that the card should be used in
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 37 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
the PIN pad: the clerk will then remove the card from the magnetic swipe reader and hand it
back to the customer to insert in the PIN pad.
If the EMV card cannot be read in the PIN pad the customer will be asked to retry as it may
have been inserted incorrectly. If it still fails or if there are no usable ICC applications on the
card then the clerk may fall back to swipe the card in the magnetic stripe reader.'
The description of data capture through magnetic stripe and manual PAN entry are the same
as described in Debit Card: Counter Dialogue — Activity and Screen Flows NB/SPE/013.
2.1.3 Stage 2
The activity and screen flows in this stage show the customer verification and transaction
service for EMV Cards.
2.1.4 DC EMV Screen Flows
The numbering convention for screens in this document is as follows:
Dx: — Debit Card screen from NB/SPE/013 that is not affected by introduction of EMV
Ex: Error message screen from NB/SPE/013 that is not affected by introduction of EMV
Px: PIN pad screen from NB/SPE/003 that is not affected by introduction of EMV
ERx: A new Retail Payment Card Counter screen
ERPx: A new PIN pad screen for EMV Retail
EBx A counter screen used for EMV Banking (from NB/PRP/004) shared with EMV Retail
EBPx A PIN pad screen used for EMV Banking (from NB/PRP/004) shared with EMV
Retail
Where ‘x’ is an integer that uniquely identifies each screen
2.1.5 Inclusion of PIN pad Displays in the Screen Flows
The flowcharts within this document only contain references to the primary PIN Pad screens
that are displayed to the customer during the EMV transaction flows. There are further
additional points within the flows where the PIN pad may display additional information
screens, such as EBP11 Processing Please Wait which is displayed whilst the PIN pad is busy
or waiting for a response from the Counter software. It is not within the scope of these flow
charts to document every potential sequence where the PIN Pad can display one of these
screens.
Network Banking / Reference Data Rules and Values [NB/SPE/009] will be updated to
include two new permitted methods of entry for “PIN pad read” and “Mag swipe fallback for
ICC card.”
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 38 of 224
Without Prejudice and Subject to Contract
Fujitsu Services EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00001933
FUJ00001933
Ref: NB/REQ/003
Version: 2.0
Date: 21" April 2005
2.1.6 Conventions used within the flowcharts
Customer PIN pad
Activity Activ Description
Terminator
Parallel Mode
operations
Off page Connector
On page Connector
Process
Decision
Display
Manual Operation
flowchart
Document
Manual Input
Parallel Screens
Represents manually input data,
Indicates the start or completion of a process flow
Represents the synchronisation of two or more parallel
Represents an entry to or exit from one part of the flowchart
to another on a different page.
Represents an entry to or exit from one part of the flowchart
to another on the same page. A single letter denotes the
corresponding end of the connecting flow
Represents a processing funetion
Represents a decision or switching function in a flowchart
This may represent either a system or manual decision
Represents displayed data such as data display panels and
prompts on a monitor screen
Represents an operation performed by any person in a
Represents readable data such as printed output. Where it is a
print the standard options around print failure come into play
and as a last resort, print preview will be used to allow a
manual transcription of the print.
A counter sereen followed by a PIN pad screen usually
indicates a parallel screen.
Figure 1: Flow chart conventions used in this document
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 39 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
2.2 Stage 1: EMV Transaction Start & Off-line Checks
Pre conditions
1. The system must be displaying a Settlement menu in Serve Customer Mode or in Existing
or New Reversal Modes. There cannot be any other transaction in progress?
2. The Token has an Integrated Circuit Chip meeting EMV standards
Post conditions
1. Transaction progresses to Stage 2, or
2. Transaction cancelled.
Description
The system validates the EMV token that is placed on the integrated smartcard reader on the
PIN pad by the customer and progresses to Stage 2. If the ICC card is not read, the clerk may
opt to read the card using the MSR.
? The current customer session may be a swapped session.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 40 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal NB/REQ/003
2.0
COMMERCIAL IN-CONFIDENCE 21" April 2005
_
24
Clerk selects
Eastcash
ao
27
Clerk selects
Easicheau
2.10
Clerk selects
Slow cash
313
Clerk selects
Jow cheaus
__
216 217
Clerk selects Transaction addedI
voucher to stack
2.20
Clerk selects
Customer
hands card
\ icc bution /
options
Figure 2: Activity Flows for EMV Retail — Transaction Start
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 41 of 224
Without Prejudice and Subject to Contract
Fujitsu Services EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
Ref:
Version:
Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
Notes on Figure 2
21 Clerk navigates to settlement screen.
2.2 Clerk decides to settle to Fast Cash.
2.3. Clerk takes money from (or gives money to) customer.
2.4 Clerk selects Fast Cash.
Transaction ends and system continues from 2.17.
2.5. Clerk decides to settle to Fast Cheque.
2.6 — Clerk takes cheque from customer.
2.7 Clerk selects Fast Cheque.
Transaction ends and system continues from 2.17.
2.8 Clerk decides to settle to “slow” Cash.
2.9 Clerk takes money from or gives money to customer.
2.10 Clerk selects “slow” Cash and enters amount.
Processing continues from 2.17.
2.11 Clerk decides to settle to slow Cheque.
2.12 Clerk takes cheques from customer.
2.13 Clerk selects slow Cheque and enters amount.
Processing continues from 2.17.
2.14 Clerk decides to settle to voucher.
2.15 Clerk takes voucher from customer.
2.16 Clerk selects voucher and enters amount.
2.17 Transaction is added to stack and system continues from Figure 18 - Complete Non
EMV Transaction.
2.18 Clerk decides to settle by card.
2.19 Ifcustomer hands card to clerk he swipes it in the magnetic stripe reader and
processing continues from Figure 3 - Swipe Card.
2.20 Otherwise, clerk selects the ICC button on the settlement screen. This effectively
launches the EMV transaction.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 42 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
NB/REQ/003
2.0
21" April 2005
FUJ00001933
FUJ00001933
( msrstaget_)
Clerk swipes
card in
MSR
Card does not need 10
‘go through PIN pad
unless service code is
defined in reference
data and the value on
the card begins with 2
or6
“ard previous!
failed in
RIN pad,
3.7
Screen EBI
Give card back
to customer
Failures are logged in
step 7.8
Figure 3: Activity Flows for EMV Retail — Swipe Card
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Page: 43 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes for Figure 3
3.1
3.2
3.3
3.4
3.6
3.7
3.8
3.9
The Clerk inspects card and may hand back to customer if it is deemed to be a chip
card.
The Clerk swipes card in the Magnetic stripe reader.
The Counter derives the IIN from the magnetic stripe and using reference data
determines the Service Code from the Track 2 data.
If reference data indicates a Service Code in the track 2 data and the Service Code
begins with 2 or 6 then the card is an ICC card and processing continues from 3.5.
Otherwise, the processing continues as for existing debit card processing as defined in
NB/SPE/013 Debit Card Counter Dialogues — Activity & Screen Flows. Method of
Entry will be recorded as 2 in this case (Non ICC Magnetic Stripe Read).
If EMV retail functionality is enabled at the Counter then the card must be handed
back to the customer and used in the PIN pad card reader. Such transactions unless a
failure in the PIN pad occurs will be treated as Method of Entry 4 (Integrated chip
card in chip read mode). Otherwise, the processing continues as for existing DCS
processing as defined in NB/SPE/013 Debit Card: Counter Dialogues — Activity &
Screen Flows. Method of Entry would be set in this case to 3 (Integrated chip card in
magnetic stripe fallback mode).
If the PIN pad has previously failed to read the card during the same transaction then
again the system will allow it to be treated as a magnetic stripe card. Method of Entry
will be recorded as 3 in this case (Integrated chip card in magnetic stripe fallback
mode). This could be caused by chip damage or because the customer has not been
able to insert the card correctly in the PIN pad.
Note: if the PIN pad has failed to read the card then the system will allow it to be
treated as a MSR card. If the clerk goes on to swipe a card then if the SVC is 2 or 6
the MOE will be 3. However, if the SVC of the card which is swiped is not 2 or 6 then
the MOE will be 2.
Otherwise, the counter displays screen EB1 (see 7.1.1) asking the clerk to launch the
card as a chip card or to cancel.
Tf the clerk decides to cancel, then the transaction ends and system returns to the
settlement menu.
The card is returned to the customer to insert in the PIN pad.
{Transactions which are successfully processed by the PIN pad will be recorded with
Method of Entry set to 4 (Integrated chip card in chip read mode)}.
If the clerk pushes the Continue button on the EB1 screen, this launches the EMV
transaction. The effect is equivalent to pressing the [CC_Settlement button on the
settlement menu.
Processing continues from Figure 4: Off line check.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 44 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
42
Screen E7 or
ES error
message
43
Print error
message?
4.
Print error
message
Enter
amount
Figure 4: Activity Flows for EMV Retail — Offline Checks
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 45 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes for Figure 4
41 System checks whether it is still on line to the data centre.
If the system is off line, processing continues from 4.2.
Otherwise, processing continues at Figure 5 - Enter Amount.
4.2 The system is off line so the counter displays screen E7 (see 8.1.18) or screen E8
(8.1.19), as appropriate. Both screens have options to continue or to print an error
report.
4.3 Ifthe clerk continues without an error report then the counter returns to the
Settlement Menu.
4.4 Ifthe clerk selects the print option an error report is printed.
i The counter displays screen 12 Tear Off Error Message Instruction (see 8.1.8) asking
the clerk to tear off the report.
The clerk acknowledges the instruction. The counter returns to the Settlement Menu.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 46 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
2.3 Stage 2: EMV Card Payment/Refund
This section covers the main activities for a Card Payment or Refund. Note there is no
operational difference between these 2 transactions. Whether any particular transaction
operates as a Payment or a Refund is determined by the current transaction mode. For a
transaction to operate as a Refund the counter must be in cither New Reversal or Existing
Reversal mode.
Pre conditions
1. System is on-line
2. Transaction proceeds as chip card
Post conditions
1. The transaction is added to the EPOSS stack, or
2. The transaction is cancelled.
Description
The Clerk enters the transaction amount, the customer enters a PIN and the customer
verification and transaction are authorised on-line.
Please note that if the Card has been removed, then even if the MA has issued an approval for
the transaction, the PIN pad will be unable to return a TC, and the transaction fails.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 47 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
2.3.1
Amount Capture
5.1 Calculate
‘maximum and
default amounts
Anything 10
settle?
‘een ER2/ER26
Only one card
Per transaction
fully in
ne sett
3.12
Clerk
acknowledges
5.6
Screen DI
‘Amount
capture
Sl
Error message
Sereen D2, D6
Y
58
Use defiult
amount
cd
Dialogue: clerk
enters amount
I
5.13
send EFT comman
“ith transaction dat
to PIN pad
Figure 5: Activity Flows for EMV Retail — Amount Capture
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 48 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes for Figure 5
5.1 System calculates minimum, maximum and default amounts: (in some instances the
customer will be allowed to pay more than the settlement value remaining on the stack:
for example, if during the session he has withdrawn money with a banking transaction
and has purchased some other items).
5.2 If there is something to settle processing goes to 5.4.
5.3. Otherwise, counter displays screen D5: Nothing to Settle (see 8.2.3).
The clerk acknowledges
Processing returns to the Settlement Menu.
5.4 Counter checks whether any retail card transaction (i.e. ICC, magnetic swipe, or PKE)
has been successfully used for settlement in the same customer session: (this also
prevents the same card being used twice in the same session).
If no other card has been used processing continues from 5.6.
5.5 Otherwise, for a payment transaction counter displays screen ER2 Multiple Cards —
Payment (see 5.1.2), or for a refund transaction screen ER26 Multiple Cards — Refund
(see 5.1.26).
The clerk acknowledges. Processing returns to the Settlement Menu.
5.6 Counter displays screen D1 Amount Capture (see 8.2.1).
This contains a default amount but can be overwritten by the clerk.
5.7 Ifclerk overwrites the default amount processing goes to 5.9.
5.8 Otherwise, the default amount is used and processing goes to 5.13.
5.9 Clerk enters the amount.
5.10 System checks the entered value.
If the amount is valid it is accepted and processing continues from 5.13.
5.11 If amount is invalid the counter displays one of the following:
¢ screen D2 — amount entered is too much (see 8.2.2)
e screen D6 — amount entered must exceed zero (see 8.2.4)
5.12 Clerk acknowledges the message and processing returns to 5.6
5.13 Counter provides amount and transaction type to PIN pad (in the EFT message) and
this launches the PIN pad retail application.
Processing continues from Figure 6a: /nsert Card (1).
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 49 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
2.3.2 Card Insertion
Py
ye ary
>—— < Card Present >
SO
x
ran" _ =
1 Puvpadsends I Comer ends vocntnyn
[STA Gmesage I een ay at
om dp commer to PIN pad. en
ro eas m4
6a.14 [PIN pad sends
Log card failed for} p STA I message i
swipe enablement ‘= so cpr 1
6a.15
End Command
Processing
Customer
Hands card
4 '
CS
Aird Insert
S Timeout, Card
Ne
~-48_,
\ 6a9
Counter sends \ costoner f
ACK(cancel) inserts car
J. Ea N
ssa SPIN pad eas
Screen EBP7 S ard
VS Concelies [Lo SP
rast) inn 5 1 sain es
7 ene, I aeoh PIN pad sees I 1 PINpad beeps H
somes Unga TT
7 rah
1 PINpad sends I
6a21
Ent Command] fo 1 STAZ message f
ovessing
: PIN pad]
AID
ley
Figure 6a: Activity Flows for EMV Retail — Insert Card (1)
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 50 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes for Figure 6a
6a.1 When the PIN pad is idle a blank screen is displayed.
6a.2__ The PIN pad is triggered into life either by the clerk pushing the ICC button on the
settlement screen or by pressing Continue on the EB1 screen (see 7.1.1): both of
these actions cause an EFT message to be sent from the counter to the PIN pad to
launch the transaction.
The PIN pad tests whether a card is present.
If the card is present processing goes to 6a.10a.
6a.3__ PIN pad displays screen EBP2 Please Insert Card (see 7.2.2).
6a.4 Step deleted’.
6a.5 The PIN pad sends a STA I message to the counter to indicate that the customer’s
card needs to be inserted in the PIN pad.
6a.6 The counter displays screen ERI Card Insertion (see 5.1.1). This screen has a cancel
button which may be used to abort the transaction. If it is not used then the ERI screen
remains there until card is inserted into PIN pad or a card insertion timeout occurs.
6a.7 Ifclerk cancels processing goes to Figure 6a: Cancel.
6a.7a If the counter detects that card insertion has exceeded timeout, processing continues
from 6a.22. (This test was introduced as a workaround for an error on the PIN pad).
6a.8 If card insertion times out then processing continues at Figure 6a: Card Insertion
Timeout,
6a.9 The customer inserts the card into the PIN pad — first attempt
6a.10 Ifthe PIN pad can read the card then processing continues from 6a.10a.. Otherwise,
processing continues at Figure 6b: Jnsert Card (2).
6a.10a The PIN pad beeps once to indicate that the expected card has been correctly inserted.
6a.11 When the card is inserted into the PIN pad, the PIN pad sends an STA 2 message to
the counter to indicate that the card has been successfully inserted. The PIN pad beeps
once to show that the card has been read successfully.
6a.12 The counter displays screen ER21 Card Inserted (see 5.1.21). Processing continues at
Figure 8: PIN pad AID selection.
6a.13_ The PIN pad sends an STA 6 command to the counter indicating a cancel at the PIN
Pad.
6a.14 Set a flag to show that an attempt to use the card in the chip reader was made, so that
a subsequent swipe operation will be allowed.
6a.15 The process Figure 22: End Command Processing is performed.
6a.16 The counter displays the card insertion timeout screen ER24 (see 5.1.24).
6a.17 The customer hands the card to the clerk for the swiping. Processing continues at
Figure 3 — Swipe Card.
Step 6a.4 PIN pad beeps now moved to 6a.10a.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 51 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
6a.18 The counter sends an ACK(cancel) command to the PIN pad aborting the transaction.
6a.18a The PIN pad displays screen EBP7 Cancelled Please Remove Card (see 7.2.6).
6a.18b The PIN Pad displays screen EBP11 Processing Please Wait (see 7.2.12).
6a.19 The PIN pad sends an STA 6 command to the counter indicating a cancel from card
removal.
6a.20 The counter displays screen ER13 7ransaction has been cancelled (see 5.1.13).
6a.21 The process Figure 22: End Command Processing is performed. The counter returns
to the Settlement Menu.
6a.22 The counter displays screen ER13 7ransaction has been cancelled (see 5.1.13).
6a.23 The counter sends an ACK (cancel) message to the PIN pad.
6a.24 The PIN pad displays screen EBP7 Cancelled Please Remove Card (see 7.2.6).
Processing continues from 6a.14.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 52 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Insert
card 2
NZ
rte,
7 Seren EBPLA
‘\ Remove and
ae-insgrad 7
173-5
I PIN pad sends
1 STAS message
‘= to pinter I
®
Ad Insert
S Giimeouy,
Ne
Card
Insertion
inserts card U Siancout
\, Customer
Pd
eR SN
SPIN pad reads >
S gary 7
gard
Y
Y -
> 1
D> VPN pad waits I
NLL JSseconds
Liar oar
[PIN pad sends
[STAD command !
— Wherouptcn I
1 6b.1Sa
1 PIN pad beeps Ly
--s--!
io adn - 1
1 PIN pad sends
STA2 message F
= bop
1 ws %
L____.f scrcen EBPIS. J
NRe-insertcard y
r= B75
I PIN pad sends
j STAI message i]
— to copntcr
Figure 6b: Activity Flows for EMV Retail — Insert Card (2)
Notes for Figure 6b
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 53 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
6b.1 PIN pad displays screen EBP 14 Remove & Re-insert card - first failure (see 7.2.13).
PIN pad beeps for a configurable period (15 seconds) or until card is removed or the
transaction aborted.
6b.2_ The PIN pad sends a STA 8 message to the counter to indicate that the card needs to
be removed and re-inserted in the PIN pad with the correct orientation.
6b.3. The counter displays screen ER7 informing the clerk that the customer is having
problems inserting their card with the correct orientation.
6b.4 ‘If the card is removed then processing continues at 6b.8.
6b.5 The PIN Pad waits for a configurable period (15 seconds) before displaying the next
screen and sending an STA D command. During this time it beeps.
6b.6 If the clerk presses the cancel button on the ER7 screen then processing continues at
Figure 6a: Cancel.
6b.7_ The PIN pad sends an STA D command to the counter signalling card removal
timeout. Processing continues at Figure 7: Card Removal Timeout.
6b.8 PIN pad displays screen EBP15Re-insert card (see 7.2.14).
6b.9 Step deleted’.
6b.10 The PIN pad sends a STA 1 command to the counter to indicate that the card needs to
be inserted in the PIN pad.
6b.11 Counter displays screen ER1 Card Insertion (see 5.1.1).
Steps 6b.10, 6b.11, 6b.12 and 6b13 may not actually occur. If the customer is quick
about re-inserting their card then the PIN pad may not send the STA I message and
the counter will correspondingly not display the ER1 screen.
6b.12 Ifclerk presses the Cancel button then processing continues at Figure 6a: Cancel.
6b. 12a If the counter detects that card insertion has exceeded timeout, processing continues
from Figure 6a: Counter Detected Timeout. (This test was introduced as a workaround
for an error on the PIN pad).
6b.13 If card insertion times out then processing continues at Figure 6a: Card Insertion
Timeout.
6b.14_ The customer inserts the card into the PIN pad — second attempt.
6b.15 If the PIN pad fails to read the card then processing continues at Figure 6c: /nsert
Card (3).
6b.15a The PIN Pad beeps once to indicate that the expected card has been correctly inserted.
6b.16 When a card is inserted into the PIN pad and is successfully read then the PIN pad
sends an STA 2 command to the counter to indicate that the card has been successfully
inserted.
6b.17 The counter displays screen ER21 Card Inserted (see 5.1.21). Processing continues at
Figure 8: PIN pad AID selection.
* Step 6b.9 PIN pad beeps now moved to 6b. 15a.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 54 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00001933
FUJ00001933
Ref: NB/REQ/003
Version: 2.0
Date: 21" April 2005
cern
7 Screen EBP16
\ Remove and
se-inserteaud 7
[ee aie
[PIN pad sends
p STA 8 message 1
— so conicr
1 pin padwaits 5
115 seconds
PO G7 TH
J PIN pad sends
J STAD message i]
— contr I
6s
(_4f screen EBPI7_ }
NRe-insert card y
tm teh 5
PIN pad sends
p STA 1 message 1
= ste coynicr I
y
eo
1 6etsa st
1 PIN pad beeps 1
ete
PA eH 7
[PIN pad sends
STA 2 message
_ 0 sper — 1
6¢.17
Screen ER21
Card Inserted
Ged Inserts
S Timeout,
N ve
. 2
5 i
/
Y
6.18 1
' pin pad beeps 4
IL for 15 seconds
rats
Screen EBP18
Remove and
‘handover.cant 7
7 Be 7
1 PIN pad sends
STA9 message I
0 ape =!
alba!
rocessin
Figure 6c: Activity Flows for EMV Retail — Insert Card (3)
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 55 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes for Figure 6c
6c.1
6¢.2
6c.3
60.4
6¢.5
6c.6
6¢c.7
6c.8
6c.9
6c.10
6c.11
6c.12
6c.12a
6c.13
6c.14
6c.15
6c.1Sa
6c.16
The PIN pad displays screen EBP16 Remove & Re-insert card (see 7.2.15) - second
failure). The PIN pad beeps for a configurable period (15 seconds) or until the card is
removed or the transaction is aborted.
The PIN pad sends an STA 8 message to the counter to indicate that the card needs to
be removed and re-inserted in the PIN pad with the correct orientation.
The counter displays screen ER8 (see 5.1.8) informing the clerk that the customer is
still having problems inserting their with the correct orientation.
If the card is removed then processing continues at 6c.8.
The PIN Pad waits for a configurable period (15 seconds) before displaying the next
screen and sending an STA D command. During this time it beeps.
If the clerk presses the cancel button on the ER8 screen then processing continues at
6c.8.
The PIN pad sends an STA D command to the counter signalling card removal
timeout. Processing continues at Figure 7: Card Removal Timeout.
PIN pad displays screen EBP17 Re-insert card (see 7.2.16).
Step deleted®.
The PIN pad sends an STA 1 command to the counter to indicate that the customer’s
card needs to be inserted into the PIN pad.
The counter displays screen ER1 Card Insertion (see 5.1.1).
Steps 6c.10, 6c.11, 6c12 and 6c.13 may not actually occur. If the customer is quick
about re-inserting their card then the PIN pad may not send the STA 1 command and
the counter will correspondingly not display the ER1 screen.
If clerk presses the cancel button on screen ERI then processing continues at Figure
6a: Cancel.
If the counter detects that card insertion has exceeded timeout, processing continues
from Figure 6a: Counter Detected Timeout. (This test was introduced as a workaround
for an error on the PIN pad).
If card insertion times out then processing continues at Figure 6a: Card Insertion
Timeout.
The customer inserts the card into the PIN pad — third attempt.
If the PIN pad fails to read the card processing continues from 6c.18.
The PIN Pad beeps once to indicate that the expected card has been correctly inserted.
When the card is inserted into the PIN pad and successfully read then the PIN pad
sends an STA 2 command to the counter to indicate that the card has been successfully
inserted.
* Step 6c.9 PIN pad beeps now moved to 6c. 15a.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 56 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
6c.17
6c.18
6¢.19
6c.20
The counter displays screen ER21 Card Inserted (see 5.1.21). Processing continues at
Figure 8: PIN pad AID selection.
PIN pad beeps for a configurable period (15 seconds) — card removal beeps.
PIN pad displays screen EBP18 Remove and handover card (see 7.2.17 - third failure).
The PIN pad sends an STA 9 command to the counter signalling that fallback to swipe
and signature processing is allowed.
Processing continues from Figure 7: Fallback Processing. Method of Entry would be
set in this case to 3 (Integrated chip card in magnetic stripe fallback mode).
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 57 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00001933
FUJ00001933
Ref: NB/REQ/003
Version: 2.0
Date: 21" April 2005
2.3.3
Fallback Processing
Ta
Sereen ERIS
Remove Card
TS
Counter Sends
ACK (cancel) to
PIN pad.
r-soh--
1 PiNpadsends
STA6 message I
— AP copter I
—
cry 1
1 povpadvwais I
15 seconds
L Bsmt I
FT TN
1 Screen EBPI9 J
peoke- Handover card y
PIN pad sends
[STAD message
~ eae
7.6
End Command)
Processing
Counter logs
that card fai
2
Screen ER6
card cannot be
N
Swipe
card
7.11 Clerk
touches Cancel
Figure7: Activity Flows for EMV Retail — Fallback Processing
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 58 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes for Figure 7
7A
7.2
73
74
7.6
77
78
79
710
Counter displays screen ER15: Remove the card and hand it to the clerk (see 5.1.15).
If the clerk presses the OK button to stop the PIN pad from beeping then processing
continues from 7.13.
If the card is removed from the PIN Pad then processing continues at 7.12.
The counter waits for a configurable period (15 seconds) whilst the PIN pad beeps.
After the timer expires then the PIN Pad stops beeping and will return an STA D
command to the counter.
The PIN pad sends a STA D command to the counter to indicate card removal
timeout.
The process Figure 22: End Command Processing is performed.
Step deleted.®
The Counter sets a flag to indicate that the card failed in the PIN pad: this is so that the
card swipe flow passes the test in step 3.6.
Counter displays screen ER6 Card cannot be read by PIN pad (see 5.1.6).
If the customer gives the card to the clerk then the processing continues at Figure 3:
Swipe Card.
The clerk touches Cancel on the ER6 screen. The counter returns to the Settlement
Menu.
The PIN pad displays screen EBP19 Hand Card to Clerk (see 7.2.18). Processing
continues from 7.6.
The counter sends an ACK( cancel ) to the PIN pad to cause the PIN pad to stop the
beeping.
The PIN pad sends a STA 6 message to the counter to indicate clerk cancel of card
removal beeping. Processing continues from 7.6.
6 The PIN pad displays the welcome screen in Figure 22: End Command Processing.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 59 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref; NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
2.3.4 Application Selection
ein ET ery
. Asplication Me. PIN pad sends ‘Screen EBPIS
en a STAD message ‘Remove and /—
Y 1. eeu 1 tandoven cant 7
eth LN ys
<Grstioacl —— . -ar-\ -mE-5 fs
ars a ro rs Gasiomer re juice Screen EBP3 PIN pad sends
y PIN pad removes seeing eS Sila m 1 nyo 1 Recess
ee Nb \ apni: 1 wouncr 1
To fiamgbediss 1
nn a ry
ro 4 Screen ERIS
[System selects App Selection
te aeration I
eS <n 74
Loner nosy —d comes
sgssistnep, ARI —
Noo cn > “ie
en iE toa its
yo vs Toomer selec Mo sap [ie
1 focance!
more srg, os Valin ~
S Kon card 734
s ’
~e < Application > a
N © Sigs —— Fe
a oe I customer presses!
ross OS 1 Cangeh boon!
1 PINpadsends ee sic
STAC tv Nine
Counter sends
Hack cance! messag
Te
Clerk touches
ren
‘Screen EBP22 3
\ Anpiction Ack mosge TI
ed ee to PIN pad Counter sends ot
irranceage Clerk touches
821 Pat
Remove Adon ait
Card s sas- —
ve
I 2nd
vr = 32 <a rig >
Screen EBP23 End Command pourra Tse"
Card Processing q PIN pad sends
Becked AAC message
: 1. meus i
Figure 8: Activity Flows for EMV Retail — PIN pad AID Selection
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Page: 60 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes for Figure 8
8.0 The PIN pad checks whether the card is blocked and if it is, processing continues from
8.0a: otherwise, processing continues from 8.1.
8.0a_ The PIN pad displays screen ERP23 — Card Blocked (see 7.2.22). (An error code of
08018 is returned with the STA 7 message in step 8.21).
Processing continues from 8.21.
8.1 If the EMV card contains no AIDs which can be matched with those in the PIN data
then (the transaction may fallback to MSR) and processing continues from 8.26.
8.2 If the cardholder is required by ICC settings to confirm the application to be used
processing continues at 8.14: (typically this happens when the customer needs to make
a selection from a list of retail applications which are on the card, but it can also
happen if the card contains a single retail application that needs to be confirmed by the
customer).
8.3. The PIN pad automatically selects the application.
8.4 If the selected application is found by the PIN pad to be unusable possibly as a result
of the PAN not being supported by POL reference data then processing continues at
8.28.
8.4a The PIN pad checks whether the application is blocked and if it is, processing
continues from 8.4b: otherwise, processing continues from 8.5.
8.4b The PIN pad checks whether there are further applications on the card to be
considered and if there are, processing continues from 8.28.
8.4c Otherwise, the PIN pad displays screen ERP22 — Application Blocked (see 7.2.21).
(An error code of 08057 is returned with the STA 7 message in step 8.21).
Processing continues from 8.21
8.5 The PIN pad sends a STA C command to the counter containing the selected
application label.
8.6 PIN pad displays the selected application label.
8.7. Step deleted’.
8.8 Step deleted.
8.9 The counter checks the card data —and if there is an error processing continues from
8.19.
(There is no check on effective date or expiry date and the request is still sent to the
Merchant Acquirer even if the application seems to be out of date).
8.9a The counter checks whether the card is a Partner card and if it is processing continues
from 8.9b. Otherwise, processing continues from 8.10.
8.9b The counter displays Partner Bank screen ER20 (see 5.1.20).
7 Steps 8.7 and 8.8 previously concerned the passing of TLV and TDR messages between the counter and the
PIN pad: steps were removed from main processing flow to improve performance.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 61 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
8.9c If the clerk intends to ask the customer whether he wants to use Banking later
8.9d.
8.9e
8.10
8.11
8.14a
8.14b
8.18a
8.19
8.20
processing continues from 8.9d. Otherwise, processing continues from 8.9e.
The clerk touches the Yes button and processing continues from 8.10.
The clerk touches the No button and processing continues from 8.10.
The counter sends an EFT2 command back to the PIN pad to continue processing
If the action analysis phase of EMV processing indicates a failure then processing
continues from 8.23.
If the first usable ( supported ) CVM on the card is a PIN entry CVM then processing
continues from Figure 10: PIN verification: otherwise, processing continues at
Figure 11: CVM processing,
The cardholder is presented with a list of applications on screen EBP3 (see 7.2.3): (it is
possible that the PIN pad will display only a single application in instances where there
is no choice but the card dictates that the only application needs to be confirmed by the
customer).
The PIN pad sends an STA B command to the counter indicating that customer
application selection is in progress.
The counter displays screen ER28 (see 5.1.28) to inform the clerk that the PIN pad is
prompting the customer to perform application selection. Screen has a cancel button:
otherwise, the screen remains there until application selection has completed at the
PIN pad, or the clerk cancels the transaction.
If the customer needs help processing continues from 8.16: otherwise, processing
continues from 8.17.
If the customer needs help with application selection he may allow the clerk to perform
that operation for him. This is achieved by the customer pressing the CLR button on
the PIN Pad. The clerk will explain this to the customer. Processing continues from
Figure 9: Counter AID Selection.
If the customer decides to cancel processing continues from 8.18: otherwise,
processing continues from 8.18a.
The customer cancels by pushing the cancel button or taking the card out before the
transaction is finished. Processing continues from Figure 19: Customer Cancel.
The customer selects application. Processing continues from 8.4.
The counter displays one of a number of error screens. As this is part of the existing
system process it will not be expanded here. See NB/SPE/013 for details.
Range checking will also be carried out here for the amount, to ensure that it falls
within the bounds set out by reference data. The screens E9 (see 8.1.20) and E10 (see
8.1.21) will be used to display bound check errors.
e screen E9 - amount entered is outside limits supported for this card
e screen E10 - amount entered isn’t a correct multiple: (unlikely depends on
reference data).
The counter sends an ACK cancel command back to the PIN pad
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 62 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
8.21 The Remove Card process is performed — Figure 21.
8.22. The End Command Processing process is performed — Figure 22. The counter
returns to the Settlement Menu.
8.23 The PIN pad sends an AAC command to the counter.
8.24 The counter displays the ER22 screen (see 5.1.22 - for a payment transaction) or ER27
screen (see 5.1.27- for a refund transaction) showing a transaction declined message.
8.25 The counter sends an ACK cancel command back to the PIN pad. Processing
continues from 8.21.
8.26 The PIN pad sends an STA 9 command to the counter indicating an MSR fallback
scenario.
8.27 PIN pad displays screen EBP18 Remove and handover card (see 7.2.17). Processing
continues from Figure 7: Fallback Processing.
8.28 The unusable application will be removed from the application candidate list and
application selection will begin again at PIN Pad AID selection. If the list is found to
be empty then fallback to MSR will be allowed.
Processing continues from 8.1.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 63 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
NB/REQ/003
2.0
21" April 2005
FUJ00001933
FUJ00001933
3.1
Screen EBP13 \
‘App selection I
“ee ca
--%--1
1 PINpadsends 1
KBD message I
— te counter
d - ny
Y v9
+] Clerk selects
appligation
as”
Clerk selects
ancel
App selected
Please wait
Cancels
N
v5
‘ounter Sends ACK]
(cancel) command
to PIN pad
ome
Counter sends ACK
App Id message
io. BIN pad.
97
Remove Card
t
os
[End CommandI
Processing
Cheek
plicatio
Figure 9: Activity Flows for EMV Retail — Counter AID Selection
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 64 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes for Figure 9
91 The PIN pad displays screen EBP 13 Selecting application for payment (see 7.2.12).
9.2 The PIN pad sends a KBD command to the counter informing the counter that the
customer has pressed the CLR key: the KBD command contains a list of the
application labels from the card who’s corresponding AIDs have matched AIDs
supported by the PIN pad.
9.3 In response to the KBD command from the PIN pad the counter displays screen ER10
(see 5.1.10). This is a pick list screen, which lists the matched application labels listed
in the KBD command: additionally another choice available to the clerk is the
CANCEL option.
9.4 The clerk discusses the available options with the customer.
If the customer selects an option then processing continues from 9.9.
9.5 The clerk selects Cancel.
9.6 The counter sends an ACK cancel command to the PIN Pad.
9.7 The process Figure 21: Remove Card is performed.
9.8 The process Figure 22: End Command Processing is performed. The counter returns
to the Settlement Menu.
9.9 The clerk selects the appropriate application.
9.10 The counter displays the ER23 screen (see 5.1.23). As there is a pause between
application selection and PIN entry this screen informs the clerk and offers the
opportunity, if needed, to cancel the transaction.
9.11 Ifthe clerk presses the Cancel button on the ER23 screen then processing continues
from 9.6.
9.12 The counter sends an ACK command back to the PIN pad informing the PIN pad of
the selected application.
Processing continues from Figure 8: Check Application.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 65 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21° April 2005
2.3.5 PIN Verification
: Last attempt at First attempt ay—e/, Seren ERP3 J
Sy antge Spyienge™— Neorest PIN
y Y L
eto S “ints yf eS 7 i026
PN AZ Tisttime SN pf Screen ERPS J screen ERP
Nigigte Sion N incorrect PIN y No pivectry y
ait “are
¥ 027 XN
7 T0387
4 Screen ERPI2a
NFintPIN ty y
7 Screen ERPI2¢ }
NiLast PIN try y
03
1 poypadrenens
T KBD to counter
i
N Clerk
dlecides to,
__
cancelled ToPIN pad I
1
10.32
' (bypass)
Processing ee
J 10.11 Customer I
Bees
wecind S
A ATTTANTA!AS PIN Ok
vor.
:
Figure 10: Activity Flows for EMV Retail — PIN Verification
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE Page: 66 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes for Figure 10
10.1. The PIN pad checks whether the PIN is already blocked before PIN entry is attempted.
10.2
10.3
10.4
10.5
10.6
10.7
10.8
If card is OK processing continues to 10.22.
If PIN is locked processing continues to Figure 11: CVM Processing
The PIN pad returns the KBD command to the counter. This indicates to the counter
which of ‘PIN Entry’, ‘PIN Retry’ or ‘Last Try’ PIN attempts is currently in process.
This is dependant on the PIN Retry Counter on the card.
The Counter checks whether the clerk is allowed to select the Bypass option: this is
controlled by Counter reference data.
If the bypass option is available processing continues from 10.18.
Otherwise, processing continues to 10.14
Counter displays screen ER4 Waiting for PIN (see 5.1.4).
The clerk has 3 options
© a button on the screen allows the clerk to select the bypass option
¢ a button on the screen allows the clerk to select cancel
e alternatively the clerk can wait until the PIN has been entered at the PIN pad.
At the same time as the counter is displaying screen ER4 (or ERS), the customer is
attempting to enter his PIN on the PIN pad screen ERP12a (see 5.2.1). The normal
path would be for the customer to successfully complete PIN entry but it is possible
for either the clerk or customer to cancel the transaction before the PIN is entered.
Counter screen ER4 (or ERS, ER16, ERI7, ER18 or ER19) will only disappear:
¢ onsuccessful PIN entry
e when customer cancels or pulls card
e on PIN entry timeout
e when counter clerk touches Bypass
¢ when counter clerk touches Cancel.
If the clerk chooses to press the bypass button then processing continues from 10.6.
Otherwise, processing continues from 10.9.
The clerk presses the bypass button.
The counter sends an ACK command back to the PIN pad indicating that the bypass
option has been selected.
Processing continues from Figure 11: CVM Processing.
Counter displays screen ERS Waiting for PIN (see 5.1.5).
This screen is similar to screen ER4 but only presents the clerk with 2 options
¢ a button on the screen allows the clerk to select cancel
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 67 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
e alternatively the clerk can wait until the PIN has been entered at the PIN pad.
(See comments for note 10.4).
10.9 Ifclerk decides to cancel processing continues from 10.29.
Otherwise, processing continues from 10.10.
10.10 The clerk waits until the PIN is entered at PIN pad.
10.10a If the customer decides to cancel, processing continues from Figure 19: Customer
Cancel. (The customer cancels explicitly by pushing the cancel button or taking the
card out before the transaction is finished, or implicitly if the customer does not enter
the PIN within the PIN Entry timeout period).
10.11 The customer enters their PIN number.
10.12 Ifthe PIN is not valid then processing continues at 10.1.
Otherwise, processing continues at Figure 11: CVM Processing.
10.14 Ifthe KBD command has a screen id of 07 (PIN Entry re-try in progress) then
processing continues at 10.16.
Otherwise, processing continues from 10.15.
10.15 Ifthe KBD command has a screen id of 08 (Last PIN Entry in progress) then
processing continues at 10.17.
Otherwise, processing continues from 10.8.
10.16 The counter displays screen ER17 Pin Entry Retry — one button (see 5.1.17).
Processing continues at 10.9.
10.17 The counter displays screen ER19 PIN Entry Last Try — one button (see 5.1.19).
Processing continues at 10.9.
10.18 Ifthe KBD command has a screen id of 07 (PIN Entry re-try in progress) then
processing continues at 10.20.
Otherwise, processing continues from 10.19.
10.19 Ifthe KBD command has a screen id of 08 (Last PIN Entry in progress) then
processing continues at 10.21.
Otherwise, processing continues from 10.4.
10.20 The counter displays screen ER16 Pin Entry Retry — two buttons (see 5.1.16).
Processing continues at 10.5.
10.21 The counter displays screen ER18 PIN Entry Last try — two buttons (see 5.1.18).
Processing continues at 10.5
10.22 Ifthe ICC indicates this is the last permitted PIN entry attempt, processing continues
at 10.22a. Otherwise, processing continues at 10.23.
10.22a If this is the first (and last) PIN entry attempt this transaction, processing continues at
10.27. Otherwise, processing continues at 10.25.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 68 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
10.23 If this is the first PIN entry attempt this transaction, processing continues at 10.28.
Otherwise, processing continues at 10.24.
10.24 There has already been at least one PIN attempt this transaction. The PIN pad displays
screen ERP3 Incorrect PIN ~ retry (see 5.2.5). Processing continues at 10.26.
10.25 The PIN pad displays screen ERP4 Jncorrect PIN — last try (see 5.2.6) to indicate this
is the last attempt for PIN entry. Processing continues at 10.27.
10.26 The PIN pad displays screen ERP12b Re-enter PIN — First Retry (see 5.2.2).
Processing continues at 10.2.
10.27 The number of PIN retries have been exhausted, this is the last permitted attempt at
PIN entry. The PIN pad displays screen ERP12c Re-enter PIN — Last Try (see 5.2.3).
Processing continues at 10.2.
10.28 The PIN pad displays screen ERP 12a Enter PIN (see 5.2.1). Processing continues at
10.2.
10.29 Ifthe clerk presses the cancel button on one of the PIN entry screens then the counter
sends an ACK(cancel) command to the PIN pad.
10.30 The counter displays screen ER13 Cancelled - Please wait (see 5.1.13).
10.31 The process Figure 21: Remove Card is performed.
10.32 The process Figure 22: End Command Processing is performed.
The counter returns to the Settlement Menu.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 69 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
NB/REQ/003
2.0
21" April 2005
FUJ00001933
FUJ00001933
2.3.6
CVM Processing
rr I
U pan pad returns
1
LVE¥ to counter
n2
Counter sends an
ACK to PIN pad
PIN entry
timeout
ws coon
le cancel
xs a
NoCVM I
Bs
N
es
a
/ 7 TETE
Screen ERP} Receipt Text or
NopINiocked y I Cardholder PIN Signan
ee sified
i
Ta TN
4 Seccen EBP21 J
Processing y
118
Screen ER3
PIN locked
1.
Clerk touches,
continue
Figure 11: Activity Flows for EMV Retail — CVM Processing
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 70 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes for Figure 11
1.1
The PIN pad sends a VFY command to Counter. This informs the counter of the
outcome of CVM processing.
The VFY command returns one of the following status indicators:
e PIN ok or NoCVM.
If this status is returned then either the PIN number has been entered correctly
or the CVM is NoCVM. This could include the case where the clerk has
bypassed PIN entry to the next available CVM and that CVM is NoCVM. It
could also include the case where there is no further CVM.
e Signature Verification Required.
If this status is returned then the CVM in use is signature. This may include the
case where the clerk has bypassed PIN entry and the next available CVM is
signature.
In the case of combined CVM even though the PIN is entered correctly, the
VFY command will not return PIN entry Ok. Having satisfied itself that PIN
entry was successful it will behave from that point as if the CVM had been
signature. The indication returned on the VFY would be CVM signature.
e PIN Blocked, Signature Verification Required
If this status is returned then the card is blocked. That is, the PIN try counter
has reached zero. It could have been blocked to begin with or as a result of
inaccurate attempts at PIN entry in this session. In this case the next available
CVM is signature and the card does not prevent its use in a PIN blocked
situation.
e PIN blocked, no CVM required
If this status is returned then the card is blocked and either the next available
CVM is NoCVM or there are no further CVMs in the CVM list.
11.2 Counter returns ACK command to the PIN pad.
11.3 If the PIN pad times out due to the PIN number not being entered in a timely fashion.(
Le. within the duration set in reference data for PIN entry timeout) then processing
continues at Figure 19: PIN Entry Timeout.
11.4 If the customer cancels by pressing the cancel button or by pulling their card
prematurely, then processing continues at Figure 19: Customer Cancel.
11.5 Ifthe VFY command returned PIN_Ok or NoCVM then processing continues at
11.10.
11.6 Ifthe VFY command returns Signature Verification Required then processing
continues at 11.11.
11.7. Ifthe VFY command returns a blocked CVM indication, then the screen ERP2 PIN
Blocked (see 5.2.4) will be displayed by the PIN pad. If the returned status is neither
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 71 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
11.7a
11.8
11.8a
11.9
PIN_Ok or NoCVM nor Signature Verification Required then by default it is a PIN
blocked situation.
PIN pad displays screen EBP21 Processing (see 7.2.20).
The counter displays the ER3 PIN Blocked screen (see 5.1.3). When the continue
button is pressed then processing continues at 11.9.
System waits until clerk touches Continue.
If the VFY command returns PIN Blocked, Signature Verification Required then
the processing continues at Figure 14: Signature Verification.
If the VFY command returns PIN Blocked, NoCVM Required then processing
continues at Figure 14: NoCVM Verification.
11.10 Ifafter analysis the CVM is NoCVM then processing continues at Figure 14: NoCVM
Verification. If the CVM is PIN then the processing continues at Figure 14: PIN
Processing.
11.11 Ifthe CVM is a combination CVM then processing continues at 11.12. If not a
combination CVM then processing continues at Figure 14: Signature Processing.
11.12 A flag is set to cause the receipt text ‘Cardholder PIN Verified’ to be printed on the
session receipt. Processing continues at Figure 14: Signature Verification.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 72 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
FUJ00001933
FUJ00001933
treated in same way as
abandon
s
ruts ano
4 ‘ustomer ¥
Cancels 7
, S
ean
Action Analy
Decline #
Sve jI_—___#
N
143
Signature CVM .
selected Anas
“Fallback to
aku S MSRY,
N etction Anal Ss ue I
\ Decline N 1s
N27 p DIN pad ends
2 STA9 message
> .
“urs v Ps oy
y = ioegunics
SFattacceo cao tomer — 1
~S MSRz, [+ Fallback to I
Nr SiysRe one,
s ° 7 Scteen EBPIS
N
poote- \ Remove and
iad ‘bandover cad 7
¥ pin pad returns
T ARQ to. t --na7
4-7 PIN pad sends
1 STA 9 message 1
---'--- T= tocoumis 1
1 oun 4
1 PINpad beeps 4 14a
for 15 seconds p--te- NoCVM
= —— 14.17a 1 selected
V pay pad retums 4 T
nr -\ TAAC to counter a
7 Screen EBPIS fete tee “Dt
Remove and PIN pad returns
andovercan! 7 THE 1 ARQ to counter
Counter sends eee I
ae _. ACK message to
1 TT 1 PIN pad.
PIN pad sends
I stadmessage
1 wom 1
14.13
Screen 5 (EMV)
Waiting for
authorisation
Waiting for Ts
authorisation ae
Card
tee I rhs
Go online and Go on-line and
wait for 1421 wait for
End Comman
Processing i
End Fesponse,
Figure 14: Activity Flows for EMV Retail — Signature Verification & No CVM
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 73 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes for Figure 14.
14.1 Ifcustomer cancels processing continues at Figure 19 - Customer Cancel. (The
customer cancels by pushing the cancel button or taking the card out before the
transaction is finished).
14.2 If the PIN pad detects an action analysis failure then processing continues at 14.17.
14.3. The counter prepares to display ‘Signature CVM’ message on screen 5 (EMV).
14.4 If fallback to MSR is required processing continues from 14.22. (This is a rare event
but has to be catered for).
14.4a The PIN pad sends ARQ command to the counter, indicating a requirement to go on-
line to obtain authorisation.
14.5 Step removed*.
14.6 Step removed.
14.7 The counter displays screen 5 (EMV) Waiting for authorisation (see 5.1.29).
14.8 The counter goes on line to the merchant acquirer and waits for authorisation.
Processing continues to Figure 15: Process Response.
14.9 If customer cancels processing continues at Figure 19: Customer Cancel. (The
customer cancels by pushing the cancel button or taking the card out before the
transaction is finished).
14.10 Ifthe PIN pad detects an action analysis failure then processing continues at 14.17.
This includes the following situations:
e ACVM bypass finds no alternative usable CVM in the CVM list and the card is
set to cause a decline in such situations.
« A PIN blocked fallback finds no alternative usable CVM in the CVM list and the
card is set to cause a decline in such situations.
14.10a If fallback to MSR is required processing continues from 14.22. (This is a rare event
but has to be catered for).
14.11 The counter prepares to display ‘No CVM’ message on screen 5 (EMV).
14.12 The PIN pad sends ARQ command to the counter. Indicating a requirement to go
online to obtain authorisation.
14.13 Step removed’.
14.14 Step removed.
14.15 The counter displays screen 5 (EMV) Waiting for authorisation (see 5.1.29).
* Steps 14.5, and 14.6 connected with TLV and TDR messages have been removed as the result of performance
improvements to the main paths.
° Steps 14.13, and 14.14 connected with TLV and TDR messages have been removed as the result of
performance improvements to the main paths.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 74 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
14.16
14.17
The counter goes on line to the merchant acquirer and waits for authorisation.
Processing continues to Figure 15: Process Response.
Tf fallback to MSR is required processing continues from 14.22. (This is a rare event
but has to be catered for).
14.17a The PIN pad returns an AAC command to the counter, showing action analysis
14.18
14.19
14.20
14.21
14.22
14.23
14.24
decline.
The counter sends an ACK to the PIN pad acknowledging the AAC command.
The counter displays screen ER22 Declined (see 5.1.22).
The process Figure 21: Remove Card is performed.
The process Figure 22: End Command Processing is performed.
The counter returns to the Settlement Menu.
The PIN pad beeps for 15 seconds until the card is removed or until the clerk touches
OK on the EB12 screen in step 7.1.
PIN pad displays screen EBP18 Remove and handover card (see 7.2.17).
The PIN pad sends an STA 9 command to the counter indicating an MSR fallback
scenario.
Processing continues from Fallback Processing in Figure 7.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 75 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
COMMERCIAL IN-CONFIDENCE
EMV Retail: User Interface Design Proposal
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
2.3.7 Process Response
Process
response,
Tsast
Force a decline
By setting comms
‘ail
Tsast
Force a decline
by setting failing
th
I
as
vy, 7nd SN
-
Response
sae
Ne
2 Signature
‘ Xesiteatign °
oe
N
7 Screen EBP10
Approved
>
ty
Ul
ope ¢
1Sa.12
Approved
Remove Card
1sa.13
End Comman
Processing
TS
Process response
and pass to
EIN aad rm 5
I PIN pad passes
ras p TC message
Lb PiNpad - oops — 1
J Processes
- -! T5a,
Counter sends
ACK message
to PIN pad
y elite
> Ta 4
PIN pad sends
PAAC message to
— courte
Counter sends
ACK message
du
2
einen
1 Coste
ied 3
N
Taga
* ‘Sercen EBP9
Declined y
154.27
IEnd Commani
Processing
Sercen EBP20
NV. Cancelled y
r™ TBatom
[PIN pad passes
STA 6 message
— do coynucr I
Tada
Counter sends
TLV message
to PIN pad.
7 Tat 1
I PIN pad passes
1 TDR message
— do cope I
Acknowledges
Figure 15a: Activity Flows for EMV Retail — Process Response
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 76 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes for Figure 15a
1Sa.1
1Sa.2
1Sa.3
15a.4
15a.5
15a.6
15a.7
15a.8
15a.9
15a.10
1Sa.11
15a.12
15a.13
15a.14
15a.15
15a.16
15a.17
15a.18
15a.19
15a.20
15a.21
If the authorisation request times out then processing continues at 15a.33.
The counter compares the [R] amount against the [A] amount. If they are not the
same processing continues from 15a.32.
The counter passes the authorisation response data through to the PIN pad as an
ACK command.
The PIN pad processes the authorisation response.
The PIN pad decides whether to accept the authorisation response. The card and PIN
pad may even in the event of a successful authorisation response, decide to decline
the transaction. If the decision is to accept the transaction then the PIN pad generates
and issues a TC command and processing continues from 15a.6. If the decision is to
decline the transaction then the PIN pad generates and issues an AAC command and.
processing continues from 15a.19.
The PIN pad generates and sends a TC command to the counter.
Step removed".
Step removed.
The counter acknowledges the TC command by sending an ACK command to the
PIN pad.
If the CVM was signature or a combination CVM then further proof of identity is
required, so the counter solicits a proof by signature from the cardholder and
processing continues at Figure 15b: Chip & Signature.
PIN pad displays screen EBP10 Approved / Remove card (see 7.2.9).
The process Figure 23: Approved Remove Card is performed.
The process Figure 2:
continues at Figure 18:
End Command Processing is performed. Processing
Jomplete EMV Txn.
Step removed: now covered by Figure 15b.
Step removed: now covered by Figure 15b.
Step removed: now covered by Figure 15b.
Step removed: now covered by Figure 15b.
Step removed: now covered by Figure 15b.
The PIN pad generates and sends an AAC command to the counter.
Step removed'!.
Step removed.
! Steps 15a.7 and 15a.8 previously concerned the passing of TLV and TDR messages between the counter and
the PIN pad: steps were removed from main processing flow to improve performance.
" Steps 15a.20 and 15a.21 previously concerned the passing of TLV and TDR messages between the counter
and the PIN pad: steps were removed from main processing flow to improve performance.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 77 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
15a.22_ The counter acknowledges the AAC command by sending an ACK command to the
PIN pad.
15a.23 If the card was removed by the customer before the authorisation cryptogram was
generated processing will continue at 15a.28.
15a.24 The PIN pad displays screen EBP9 Declined / Remove card (see 7.2.8).
15a.25 The counter displays screen ER22 Declined (see 5.1.22).
15a.26 The process Figure 21: Remove Card is performed.
15a.27_ The process Figure 22: End Command Processing is performed.
Processing continues at Figure 20: Decline.
15a.28 The PIN pad displays EBP20 Cancelled (see 7.2.19).
15a.29 The PIN pad sends an STA 6 command to the counter indicating that the customer
has aborted the transaction by pulling their card from the reader before an
authorisation cryptogram was generated.
15a.29a The counter solicits TLV information from the PIN Pad by sending a TLV
command”.
15a.29b The PIN pad responds to the TLV command satisfying the request for TLV data.
(Note: this exception path still includes a TLV /TDR dialogue between the PIN pad
and the counter).
15a.30 The screen EB4 Transaction cancelled by the customer (see 7.1.2) is displayed by
the counter.
15a.31 When the clerk acknowledges reading the EB4 screen processing continues at
15a.27.
15a.32 The counter forces a local authorisation decline by altering the authorisation response
code which is passed to the PIN pad.
Processing continues from 15.3
15a.33 The counter forces a local authorisation decision by informing the PIN pad of comms
failure.
Processing continues from 15.3.
" Although TLV and TDR messages between the counter and the PIN pad have been removed from the main
processing flow to improve performance they are still required in exception paths.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 78 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
Ref:
Version:
Date:
NB/REQ/003
2.0
21" April 2005
7 i010
Seren EBPIS.
N Hand wo clerk y
rts
1 PIN pad sends
[STAT message tol
- se ees i
rr ea I
PINpad starts
I beeping
2 tths
Gard alread? y
S Removed, #
NY
N
= BT Ay
Screen EBPI8
Remove card
dandjoded
15b.8 1
V pin pad waits 4
1 for 13seconds
y
Counter sends
ACK message
nee I
~ah-- toninn a
tL pwpatves I 1 PINpad sends I
1 PINE STA 6 message I
s i
t = do copie J
15b.13 1
I pom soce
1 beeping
ee I
7 Tom 4 TST:
I PIN pad sends Counter sends
KBD command F *) ACK message
— boomer F Jo PES pack
150.16
fend Command
Processing
Che
signature
Figure 15b: Activity Flows for EMV Retail — Chip & Signature
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 79 of 224
FUJ00001933
FUJ00001933
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes for Figure 15b
15b.1 The PIN pad sends STA 7 message to the counter to inform the counter that the card
is still in the PIN pad.
15b.2_ The PIN pad beeps for a configurable period (15 seconds) to remind the customer to
remove their card.
15b.3__ If the card has been removed from the PIN pad processing continues from 15b.5.
15b.4 The PIN pad displays Screen EBP18 Remove card and hand to clerk (see 7.2.17).
15b.5 Counter displays screen ER25 Transaction authorised remove card (see 5.1.25).
The screen has an acknowledge button which the clerk can use to stop the PIN pad.
from beeping and to move the PIN Pad to its next operation.
15b.6 If the card is removed then processing continues at 15b.10.
15b.7 If the clerk touches the Continue button on the ER25 screen then processing
continues at 15b.11.
15b.8 The PIN pad waits for a configurable period (15 seconds): (this is a reference data
setting).
15b.9 The PIN pad sends STA D command to the counter to tell the counter that the
remove card timeout has expired. Processing continues from 15b.13.
15b.10 The PIN Pad displays screen EBP19 Hand card to clerk (see 7.2.18). Processing
continues from 15b.13.
15b.11 The counter returns an ACK command to the PIN pad. This will stop the beeping.
15b.12 PIN pad sends an STA 6 command to the counter to inform the counter that the card
removal loop has been aborted.
15b.13_ PIN pad stops beeping.
15b.14_ The PIN pad sends a KBD command to the counter. This is the trigger for the
counter to invoke signature checking.
15b.15 The counter returns an ACK command to the PIN pad to acknowledge the KBD
message.
15b.16 End command processing is carried out. Processing continues from Figure 16: Check
Signature.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 80 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal NB/REQ/003
2.0
COMMERCIAL IN-CONFIDENCE 21" April 2005
16.1
Screen 4
card checks
16.6
Printer prints
office receipt
Clerk Hands
Receipt to
Clerk takes
receipt fiom,
an
id sigan
y
Clea etuns
Card
Complete]
retry xn
Figure 16: Activity Flows for EMV Retail — Print Receipt for Signature
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 81 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes for Figure 16.
16.1 Counter displays screen 4 (see 8.1.2) prompting the clerk to conduct card checks.
16.2 Clerk takes card from customer.
16.3 Clerk performs card checks.
16.4 Selecting the Yes (card passes checks) option then processing continues at 16.5.
Selecting the No (card fails checks) option goes to Figure 20: Decline.
16.5 Counter displays screen 11 Office receipt printing (see 8.1.7) to show that the office
receipt is being printed.
16.6 The printer prints the office receipt for the customer to sign.
16.7 Counter displays screen 13 (see 8.1.9) asking clerk to confirm whether the office
receipt has been successfully printed and to verify the customer’s signature.
16.8 The clerk hands the receipt to the customer to sign.
16.9 The customer signs the receipt.
16.10 Clerk takes receipt from customer and compares the signature on the office receipt
against the signature on the back of the card.
16.11 The clerk returns the card to the customer after verifying that the customer’s signature
on the office receipt agrees with the signature on the back of the customer’s card.
16.12 Selecting the Yes (good signature) option then processing continues at 16.13.
Selecting the No (bad signature) option goes to Figure 17: Signature Retry.
16.13. The clerk hands the card back to the customer and processing continues at Figure 18:
Complete EMV Txn.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 82 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Versio 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
175
Printer re-prints
7.1 office reciept
Screen ES
ailure options
17-6
Screen El
17.4
Screen 11
Reprint office
receipt
No signature 17.3
Signature
Fail?
Screen E2
Signature check,
Figure 17: Activity Flows for EMV Retail — Reprint Receipt for Signature
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 83 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes for Figure 17
17.1 The counter displays screen E5 Signature check failure options (see 8.1.16) which lists
the failure options:
e Signature fail
¢ No customer signature
e Reprint
17.2 If the clerk selects the Reprint option then processing continues at 17.4.
17.3. Ifthe clerk selects the Signature fail option then processing continues at 17.13.
If the clerk selects the No customer signature option then processing continues at
Figure 20: Decline.
17.4 The counter displays screen 11 (see 8.1.7) to show that the office receipt is being
printed again.
17.5 The printer re-prints the office receipt.
17.6 The counter displays screen E1 (see 8.1.12) asking clerk to confirm whether the office
receipt has been successfully printed.
17.7 If the clerk selects Yes then processing continues at 17.11.
If the clerk selects No then processing continues at 17.8.
17.8 The counter displays screen E6 the print preview screen (see 8.1.17).
17.9 The clerk manually writes out the office receipt.
17.10 The clerk exits print preview screen by pushing the End button.
17.11 The counter displays screen E2 (see 8.1.13) to request clerk to get the customer to
sign the receipt and compare the signature against that on the back of the card.
17.12 Ifthe clerk selects the Yes (good signature) option then processing continues at
Figure 18: Complete EMV Txn
If the clerk selects the No (bad signature) option then processing continues at 17.13.
17.13. The counter displays screen E3 (see 8.1.14) to request that the clerk ask the customer
to sign the receipt a second time and compare the signature against that on the back of
the card.
17.14 Ifthe clerk selects the Yes (good signature) option then processing continues at
Figure 18: Complete EMV Txn.
If the clerk selects the No (bad signature) option then processing continues at Figure
20: Decline.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 84 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
2.3.8 Add Authorised Transaction to Stack
iw Y
181
Append
ransaction detail
10 EPOSS receipt
182
Commit
Transaction to
stack
18.6
Print session
receipt
Figure 18: Completion Flows for EMV Retail
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 85 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes for Figure 18
18.1 The Transaction details for the Retail Card transaction are stored so that they can be
added to the bottom of the EPOSS receipt when is produced: (this applies to EMV,
magnetic stripe and PKE).
18.2 The Transaction is added to the stack and counter returns to the settlement menu.
18.3. On completion of non-retail card transactions the counter checks whether the
transaction just completed was to Fast Cash or Fast Cheque.
If it was not then fast settlement processing continues at 18.2
Otherwise, processing continues at 18.4.
18.4 For fast settlement the counter checks whether any retail card settlement (ICC,
magnetic stripe, or PKE) has also taken place during the session.
If it has, a session receipt is required and processing continues from 18.6.
18.6 Otherwise, the counter checks whether there is any other requirement to print a session
receipt: if there is, then processing continues at 18.6.
If no receipt is required, the transaction is completed, the stack is cleared and the
counter returns to the serve customer menu.
18.6 The Session receipt is printed. The stack is cleared and the counter returns to the serve
customer menu.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 86 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
FUJ00001933
FUJ00001933
EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
2.3.9
Cancel Transaction
1 PIN pad sends
I AnSTA 6to
1__ the counter
Noy oss
7 Wan Y 4 19.7 \
7. Card in PN Screen EBPT y
RIN pad? \ Cancelled,
s --r-
vn»?
on
19.5 \ 19.8
« Sereen EBP20 y Remove
Card
19.6 19.9
nd CommanI ind Comman,
Processing Processing
Note: The customer can press his cancel button to end
the transaction at any point between EFT and ARQ
After the EPT has been sent but before the ARQ has
been generated the Cancel button is available. Please
refer to tables in each PIN pad screen in section 5.2 and
Annexe A for more details of Function keys
Figure 19: Cancel Flows for EMV Retail
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 87 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes for Figure 19
19.1 I The customer has either selected the cancel button or removed their card from the PIN
pad. Processing continues at 19.4.
19.2 The PIN pad sends an STA 6 to the counter. This indicates that the customer has
cancelled the transaction.
19.3. Screen EB4 Transaction cancelled by customer (see 7.1.2) is displayed to inform the
clerk that a cancel has occurred and the transaction is being aborted.
19.4 If the card is still in the PIN pad then an attempt to have it removed will follow and
processing continues at 19.7.
19.5 The PIN pad displays the screen EBP20 Cancelled (see 7.2.19).
19.6 The process Figure 22: End Command Processing is performed. The counter returns
to the Settlement Menu.
19.7 The PIN pad displays the screen EBP7 Cancelled Remove Card (see 7.2.6).
19.8 The process Figure 21: Remove Card is performed.
19.9 The process Figure 22: End Command Processing is performed. The counter returns
to the Settlement Menu.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 88 of 224
Without Prejudice and Subject to Contract
Fujitsu Services EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
2.3.10 Decline Transaction
tie I
Clerk specifies
fcand tetained
Ex aed
20.14
System records
Screen 7 Clerk
\pectine Sereen J acknowledg«
card retained
20.2
Write [CO]
reversal
P26
Clerk
acknowledss
I
208
I Clerk
acknowledge
Sereen 10
Do Not call
——
20.9
Clerk
acknowledes
Error
Message
20.11 System sets
Transaction value
to zero
G
20.12
Print customer
Slip screen 14
20.13
[Transaction added
To stack
Figure 20: Activity Flows for System Decline
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 89 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes for Figure 20
20.1 System checks response from Financial Institution to see whether card is to be
retained.
If the card is not to be retained processing continues from 20. le.
20.1a Ifthe card is the be retained counter displays screen 9 Retain Card (see 8.1.5).
20.1b Clerk specifies whether card is retained or not.
20.1c Ifcard is retained processing continues from 20.1d.
Otherwise, processing continues from 20.11.
20.1d The system records that card is retained: processing continues from 20.11.
20.le The system checks whether there has been a decline from the Merchant Acquirer. If
the merchant acquirer declines the transaction then no reversal [CO] is required and
processing continues at 20.1f: otherwise, processing continues at 20.2.
20.1f The counter displays screen 7 to show that the transaction has been declined.
20.1g The clerk acknowledges the message: processing continues from 20.11.
20.2 The counter records a [CO] to message store as a reversal.
20.2a The system checks whether [R] Amount = [A] Amount: (effectively the system checks
the Auth response set by step 15.32). If they are the same processing continues from
20.2b: otherwise, processing continues at 20.3.
20.2b The counter displays screen 7 Other decline (see 8.1.4) to show that the amounts are
unequal.
20.2c The clerk acknowledges the message: processing continues from 20.11.
20.3. Ifa Help desk call is required processing continues from 20.7.
20.4 Counter displays screen E8 (see 8.1.19) telling the clerk to call the Help desk.
20.5 If the clerk chooses not to print out the error message processing continues from 20.9
20.6 The counter prints an error message from screen E8 (see 8.1.19).
20.7 Otherwise, the counter displays screen 10 Transaction failure (see 8.1.6) telling the
clerk NOT to call the Help desk.
20.8 The clerk acknowledges the message and processing continues at 20.11
20.9 The clerk acknowledges the message and processing continues at 20.11
20.10 Counter displays screen 12 (see 8.1.8) asking the clerk to tear off the slip, processing
continues from 20.11
20.11 The system sets the transaction value to zero.
20.12 The system prints the customer slip.
20.13 The transaction is added to the stack, the transaction ends and the counter returns to
the Settlement Menu.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 90 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00001933
FUJ00001933
Ref: NB/REQ/003
Version: 2.0
Date: 21" April 2005
2.3.11 Card Removal and End Processing
oN
2nd
Remove Card
NL - -
an
1 21.2 '
1 PINpad beeps
Liman liar
[PIN sends an
STAT command
—tauhecpustee, T
TIT
Counter sends
ACK message
Lo PIN pad.
Pork Po in 4
I PIN pad sends 1 PIN pad sends
STAD command ! STA 6 command
‘—‘ashcgounte, 1 fathecounter, I
P3577
Vo opwvpad 5
1_ stops beeping
{One ofthe PINpad I
I sereens EBPS,EBP7, I
{ EBP9orEBPIS.
Figure 21: Activity Flows for Remove Card
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 91 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes for Figure 21
21.1 A remove card screen will be displayed on the PIN Pad. This may be any one of the
screens EBP5S, EBP7, EBP9 or EBP18 depending on the outcome of previous PIN Pad
processing.
21.2 The PIN pad beeps for a configurable period (15 seconds) to remind the customer to
remove their card.
21.3 PIN pad sends STA 7 command to the counter to inform the counter that the card is
still in the PIN pad.
21.4 Counter displays screen ER9 Remove card from PIN pad (see 5.1.9).
The screen has an acknowledge button which the clerk can use to stop the PIN pad
from beeping and to move the PIN Pad to its next operation.
21.5 Ifthe card is removed then processing continues at 21.9.
21.6 The clerk touches the OK button on the ER9 screen then processing continues at
21.10.
21.7 The PIN pad waits for a configurable period (15 seconds): (this is a reference data
setting).
21.8 PIN pad sends STA D command to the counter to tell the counter that the remove
card timeout has expired.
21.9 PIN pad stops beeping and the process exits.
21.10 The counter returns an ACK command to the PIN pad. This will stop the beeping and
break the PIN pad out of its card removal loop.
21.11 PIN pad sends an STA 6 command to the counter to inform the counter that the card
removal loop has been aborted. Processing continues at 21.9.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 92 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00001933
FUJ00001933
Ref: NB/REQ/003
Version: 2.0
Date: 21" April 2005
TIN pad returns
LEND to counter
rae.
7 screen EBPL
\ Welcome 7
\ ssercem
‘Approved
Transactio:
22.7 Clerk
presses continue
Figure 22: Activity Flows for End Command Processing
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 93 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes on Figure 22
22.1 The PIN Pad sends an END command to the counter.
22.2 The PIN Pad displays the welcome screen EBP1.
22.3 If the transaction has been approved then the process exits.
22.4 Ifthe END command does not carry a failure code then the process exits.
22.5 Ifa declined or a cancelled screen has been shown to the clerk already then the process
exits.
22.6 The counter displays screen ER14 PIN pad error screen (see 5.1.14) describing the
reported error. If the error code is an error then an event will also be logged to the
event log.
The ER14 screen will only be displayed if the PIN pad has returned an error code on
the END command and no other cancel or decline screen has been shown: so it won’t
appear if screen 7 Other decline (see 8.1.4) or screen 10 Transaction failure (see
8.1.6) has appeared earlier.
22.7 The clerk presses the continue button and the process exits.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 94 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00001933
FUJ00001933
Ref: NB/REQ/003
Version: 2.0
Date: 21" April 2005
Br TN
© EBPIO oD
Remove Card J
23.2 !
1 PINpad beeps i]
m7
1 PINsends an
1STA7 command ¥
‘—touhecpunter, 1
23.4
ER25 Approved
emove Card
237
1 prpadwais, I
at
‘Counter sends
INCK mesage
terieecons pL tabpspad
eee ieee a eam ad
1 PINpad sends 1 PINpad sends
STA D command! STA 6 commai
1 stops vesing, i
Figure 23: Activity Flows for Approved Remove Card
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 95 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Notes for Figure 23
23.1 Screen EBP10 Approved remove card (see 7.2.9) will be displayed on the PIN Pad.
23.2 The PIN pad beeps for a configurable period (15 seconds) to remind the customer to
remove their card.
23.3. PIN pad sends STA 7 command to the counter to inform the counter that the card is
still in the PIN pad.
23.4 Counter displays screen ER25 Transaction authorised remove card (see 5.1.25).
The screen has an acknowledge button which the clerk can use to stop the PIN pad
from beeping and to move the PIN Pad to its next operation.
This screen also confirms to the clerk that the transaction has been authorised.
23.5 If the card is removed then processing continues at 21.9.
23.6 The clerk touches the OK button on the ER25 screen then processing continues at
21.10.
23.7 The PIN pad waits for a configurable period (15 seconds): (this is a reference data
setting).
23.8 PIN pad sends STA D command to the counter to tell the counter that the remove
card timeout has expired.
23.9 PIN pad stops beeping and the process exits.
23.10 The counter returns an ACK command to the PIN pad. This will stop the beeping and
break the PIN pad out of its card removal loop.
23.11 PIN pad sends an STA 6 command to the counter to inform the counter that the card
removal loop has been aborted. Processing continues at 23.9.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 96 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
3.0 Receipts
At release S70 the customer receipt will be incorporated as part of the session receipt. Only
where a signature is required will there be an outlet “receipt”.
All debit card products will be set up so as to force the printing of a session receipt for
successful transactions.
For declined transactions, a Customer receipt will be printed immediately (since it results in a
Zero value transaction on the stack), and the data for the declined transaction will not be
included in the session receipt.
This section describes the following receipts:
3.1 Customer Session Receipt (Non debit card)
3.2 Customer Session Receipt (With debit card payment)
3.3 Duplicate Customer Session Receipt
3.4 Customer Debit Card Payment/Refiund Receipt — Declined Transaction
3.5 Office Debit Card Receipt for Signature
The circumstances in which the debit card receipts are printed as follows:
Result Verification Card details Office Customer
on session Receipt? Receipt?
receipt?
Approved Chip & PIN Yes No No
‘Approved Magnetic swipe & signature Yes Yes No
Approved. Chip and Signature Yes Yes No
Approved Chip and PIN and Signature Yes Yes No
‘Approved No CVM Yes No No
Abandon before [R] All No No No
MA decline All No No Yes
PIN pad decline Chip & PIN No No Yes
PIN pad decline No CVM No No Yes
Decline network fail All No No Yes
Card check fail Magnetic swipe & signature No Yes Yes
Signature fail Magnetic swipe & signature No Yes Yes
Signature fail Chip & signature No Yes Yes
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 97 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
3.1 Customer Session Receipt (Non debit card)
3.1.1 Purpose
This particular section covers non debit card sessions.
3.1.2 Frequency
Ad hoc.
3.1.3 Notes
A receipt is only available for the last completed session.
3.1.4 Sequence
Receipts and Payments (excluding filtered products) in chronological order, then MoP
(including filtered products).
The data shown in the examples is illustrative only —
the exact text can change, and so differ from that in the examples.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 98 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL
'(ONFIDENCE
Ref:
Version:
Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
3.1.5
English text
Layout and Example Content
1 2 3
4
123456789012345678901234567890123456789012
Post Office Ltd.
Your Receipt
Feltham Post Office
1, The Walkway
Kings Parade
Middle of Town
Feltham
Middlesex
TW1 3DD
VAT REG No. 243 1700 02
11/02/2003 13:54
SESSION : 1-6774-1
Stmp bk 1st x 10
1 @ 2.60 2.60
Postage stmp
1 @ 3.00 3.00
Colour TV lic
1 @ 97.50 97.50
US Dollar @1.6121 USD/GBP
60- 32.22-
Commission 5.00
TOTAL DUE TO POST OFFICE 75.88
Cheque FROM CUSTOMER 75.88
BALANCE 0.00
Thank You
T 2 3 4
123456789012345678901234567890123456789012
© 2004 Fujitsu Services
Without Prejudice and Subject t
COMMERCIAL IN-CONFIDENCE
fo Contract
Page: 99 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL '(ONFIDENCE Date: 21" April 2005
Welsh/English text
1 2 3 4
123456789012345678901234567890123456789012
01 Swyddfa’r Post Cyf.
02 Post Office Ltd.
03 Eich Derbynneb
04 Your Receipt
05 I Feltham Post Office
06 I1, The Walkway
07 IKings Parade
08 IMiddle of Town
09 I Feltham
10 I Middlesex
11 I Twi 3DD
12
13 Rhif COF.TAW/VAT REG No. 243 1700 02
14 11/02/2003 13:54
15 SESIWN/SESSION : 1-6774-1
16
17
18
19
20 IStmp bk 1st x 10
21 {1 @ 2.60 2.60
22 I Postage stmp
23/1 @ 3.00 3.00
24 I Colour TV lic
25 I1 @ 97.50 97.50
26 IUS Dollar @1.6121 USD/GBP
27 =I 60- 32.22-
28 I Commission 5.00
29
30 I CYF DYLEDUS I SWYDDFA’R POST
31 I TOTAL DUE TO POST OFFICE 75.88
32
33 I Siec GAN Y CWSMER
34 I Cheque FROM CUSTOMER 75.88
35 I BALANS/BALANCE 0.00
36
37
38
39 Diolch Yn Fawr
40 Thank You
41
1 2 3 4
123456789012345678901234567890123456789012
Field Name English Welsh/English I Length I Contents
Line I Char I Line I Char
No. I Pos’ns I No. I Pos’ns
Welsh Header I 01 - - Blank.
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 100 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Ol 13-31 19 “Swyddfa’r Post Cyf.’.
English Header I 02 14-29 I 02 14-29 16 “Post Office Ltd.’
Welsh Text - - - Suppressed.
03 15-28 14 “Eich Derbynneb’.
English Text 03 16-27 I 04 16-27 12 “Your Receipt’.
Office Name 04 01-30 I 05 01-30 30 Branch name, up to 30
characters: (000...)
Address 05- I 01-40 I 06- I 01-40 I 40 Branch address: a variable
1,2,3,4,5 09 10 number of lines up to a
maximum of five.
Postcode 10 01-08 I 11 01-08 8 Branch postcode: pppp ppp
Date 13 13-29 I 14 13-29 17 Date and time:
dd/mmiyyyy hh:mm
Session ID 14 21-31 I 15 27-37 11 Session ID.
Message 17 01-42 42 Blank or ‘REVERSAL’
or ‘Recovery’.
18 01-42 42 Blank or ‘DIR YMU/
REVERSAL’ or
‘Recovery’.
Field Name English Welsh/English I Length I Contents
Line I Char I Line I Char
No. I Pos’ns I No. I Pos’ns
Non-MoP Repeated as necessary.
Product:
Non-BdeC
txn:
Product
Additional data
Qty
Unit Price
Value
BdeC txn:
© 200 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 101 of 224
Currency code Without Prejudice and Subject to Contract
Currency code
Qty
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00001933
FUJ00001933
Ref: NB/REQ/003
Version: 2.0
Date: 21" April 2005
Only present if applicable.
19 01-16 I 20 01-16 I 16
19 21-42 I 20 21-42 22 E.g. Girobank account
number
20 01-05 I 21 01-05 I 5
20 10-18 I 21 10-18 9
20 29-40 I 21 29-40 12
Only present if applicable.
25 01-16 I 26 01-16 16
25 19-30 I 26 19-30 12 At most, 4 decimal places.
25 32-34 I 26 32-34 3 Changed currency.
25 36-38 I 26 36-38 3 Local currency.
26 O1-15 I 27 O1-15 15 Negative for a buy
transaction.
26 29-40 I 27 29-40 12 Negative for a buy
transaction.
27 29-40 I 28 29-40 12 If zero, whole line is blank.
Non-MoP
Detail:
Non-MoP - - 30 01-26 26 “CYF DYLEDUS I
Session Effect SWYDDFA’R POST?’ or
(Welsh) ‘CYF DYLEDUS I’R
CWSMER’.
Non-MoP 29 01-26 I 31 01-26 I 26 ‘TOTAL DUE TO POST
Session Effect OFFICE’ or ‘TOTAL DUE
(English) TO CUSTOMER’.
Non-MoP 29 29-40 I 31 29-40 12
Value
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 102 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
MoP Detail:
MoP Name - - 33 01-16 16 E.g. ‘Siec’
(Welsh)
MoP Name 31 O1-16 I 34 01-16 16 E.g. ‘Cheque’.
(English)
MoP Session I - - 33 18-30 I 13 “GAN Y CWSMER’ or ’R
Effect (Welsh) CWSMER’.
MoP Session I 31 18-30 I 34 18-30 I 13 ‘FROM CUSTOMER’ or
Effect ‘TO CUSTOMER’.
(English)
MoP Value Amount:
31 32-40 I 34 32-40 9 For not more than 99999.99
For more than 99999.99
31+1 I 29-40 I 34+1 I 29-40 12
Non-MoP
Total 32 29-40 I 35 29-40 12
Welsh Footer I 36 - Blank.
39 14-27 14 ‘Diolch yn Fawr’.
English Footer I 37 16-24 I 40 16-24 I 9 “Thank You’.
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 103 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
3.2 Customer Session Receipt (With debit card payment)
3.2.1 Purpose
This section covers the new format for the customer session receipt at S70 where settlements
have used debit cards. The new format will cover settlement by PIN and settlement to the
fallback scenarios of chip and signature, and magnetic swipe and signature or PAN Key entry
and signature.
3.2.2 Frequency
End of customer session when debit card transaction has taken place.
3.2.3 Notes
The circumstances in which the debit card receipts are printed are given in Section 3.
A Horizon parameter defines a filter, which determines the Post Office Ltd products that are
printed below the TOTAL DUE TO POST OFFICE line. For example, debit card
payments/refunds appear below this line and not as part of the transaction listing.
The additional debit card portion will contain the following:
Card Number, Issue Number, Authorisation Code, MID, TID, Application ID, Application
Effective Date, Application Expiry Date, Pan Sequence Number, Transaction Sequence
Number and the Amount of the debit card transaction, issuer scheme name, EFT number, an
entry indicator, and the date and time of payment.
3.2.4 Sequence
Printed at end of session.
The data shown in the examples is illustrative only —
the exact text can change, and so differ from that in the examples.
3.2.5 Layout and Example Content
This is a change to the customer session receipt (with debit card payment) to meet Streamline
requirements:
e Fora combination CVM (both PIN & signature), instead of RT201/203, two new
outcome messages (RT206/207), containing the words ‘Cardholder signature’, have been
provided
e For signature CVM outcome messages RT200/202 now include the words ‘Cardholder
signature’
e For all CVMs, the words ‘Transaction confirmed’ has been appended to the receipt text.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 104 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal Ref;
Version:
COMMERCIAL IN-CONFIDENCE Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
English text - Payment
1 2 3 4
123456789012345678901234567890123456789012
Post Office Ltd.
Your Receipt
Feltham Post Office
1, The Walkway
Kings Parade
Middle of Town
Feltham
Middlesex
TW1 3DD
VAT REG No. 243 1700 02
11/02/2003 13:54
SESSION 1-6774-1
Stmp bk 1st x 10
1 @ 2.60 2.60
Postage stmp
1 @ 3.00 3.00
Colour TV lic
1 @ 97.50 97.50
US Dollar @1.6121 USD/GBP
60- 32.22-
Commission 5.00
TOTAL DUE TO POST OFFICE 75.88
Cheque FROM CUSTOMER 25.88
Card Payment FROM CUSTOMER 50.00
BALANCE 0.00
Payment
Visa
Card Number: *#** *#** *4** pppp Issue:nnn
kkkkk
Auth Code: nnnnnn EFT No: wwww
Merchant ID: rrrrrrrrrrrrrrr
Terminal ID: tttttttt
Application ID: aaaaaaaaaaaaaaaa
From: MM/YY Expiry: MM/YY PAN Seq No: mm
Transaction ID: nnannannnnannnnnnnnnannnnan
Date/Time of Payment: 11/02/2003 13:53
Amount: £50.00
Your account will be debited with the
above amount. Cardholder PIN verified.
uuuuuUuuuuUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUE
uuuuuUUuUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUE
uuuuuuuuuuUUuUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
uuuuUuuUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUE
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 105 of 224
Fujitsu Services
EMV Retail:
Version:
COMMERCIAL PE
CONFIDENCE
User Interface Design Proposal Ref:
Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
uuuuuuuuuUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUE
uuuuuuuuuUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUE
ff£fffFrfffffrfrfffrfrffrfrffffffrfrfffrfffrffffrfffe
fLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLE
Please retain for future reference
Thank You
1 2 3 4
123456789012345678901234567890123456789012
- Refund
1 2 3 4
123456789012345678901234567890123456789012
Post Office Ltd.
Your Receipt
Feltham Post Office
1, The Walkway
Kings Parade
Middle of Town
Feltham
Middlesex
TW1 3DD
VAT REG No. 243 1700 02
11/02/2003 13:54
SESSION 1-6774-1
REVERSAL
Stmp bk 1st x 10
1 @ 2.60 2.60
Postage stmp
1 @ 3.00 3.00
Colour TV lic
1 @ 97.50 97.50
US Dollar @1.6121 USD/GBP
60- 32.22-
Commission 5.00
TOTAL DUE TO CUSTOMER 75.88
Cash TO CUSTOMER 25.88
Card Payment TO CUSTOMER 50.00
BALANCE 0.00
Refund
Visa
Card Number: **** **** **** pppp Issue:nnn
kkkkk
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 106 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
39 I Auth Code: nnnnnn EFT No: wwww
40 IMerchant ID: rerrrrrrrrerrrr
41 I Terminal ID: tttttttt
42 I Application ID: aaaaaaaaaaaaaaaa
43 I From: MM/YY Expiry: MM/YY PAN Seq No: mm
44 I Transaction ID: nannnnannnnnnnnnannnnnnnnn
45 I Date/Time of Refund: 11/02/2003 13:53
47 I Amount: £50.00
49 IYour account will be credited with the
50 I above amount. Cardholder PIN verified.
51 I wuuuuuuuuuuuuuuuuuuuuuUUUUUUUUUUUUUUUUUUUU
52 I wuuuuuuuuuuuuuuuuuUuUUUUUUUUUUUUUUUUUUUUUUL
53 I uuuuuuuuuuuuuuuuuuuuuuuUUUUUUUUUUUUUUUUUUU
54 I wuuuuuuuuuuuuuuuuuuuuuuuuuUUUUUUUUUUUUUUUL
55 I wuauuuuuuuuuuuuuuuuuuuuuuUUuUUUUUUUUUUUUUUUU
56 I wuuuuuuuuuuuuuuuuuuuuuUUUUUUUUUUUUUUUUUUUL
58 I f£f£fffFffFLFLLfLLLLLLLLLLLLLfLLLFLLLLLLLLLLLLEL
59 I ££f£ffLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLEL
60
61
62 Please retain for future reference
63
64
65 Thank You
66
1 2 3 4
123456789012345678901234567890123456789012
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 107 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal Ref;
Version:
COMMERCIAL PE
CONFIDENCE Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
Welsh/English text - Payment
1 2 3 4
123456789012345678901234567890123456789012
01 Swyddfa’r Post Cyf.
02 Post Office Ltd.
03 Eich Derbynneb
04 Your Receipt
05 I Feltham Post Office
06 I1, The Walkway
07 IKings Parade
08 I Middle of Town
09 I Feltham
10 I Middlesex
11 I Twi 3pD
12
13 Rhif COF.TAW/VAT REG No. 243 1700 02
14 11/02/2003 13:54
15 SESIWN/SESSION : 1-6774-1
16
17
18
19
20 IStmp bk 1st x 10
21 {1 @ 2.60 2.60
22 I Postage stmp
23 I1 @ 3.00 3.00
24 IColour TV lic
25 I1 @ 97.50 97.50
26 IUS Dollar @1.6121 USD/GBP
27 =I 60- 32.22=
28 I Commission 5.00
29
30 IC¥F DYLEDUS I SWYDDFA’R POST
31 I TOTAL DUE TO POST OFFICE 75.88
32
33 I Siec GAN Y CWSMER
34 I Cheque FROM CUSTOMER 25.88
35 I Taliad Cerdyn GAN Y CWSMER
36 I Card Payment FROM CUSTOMER 50.00
37 I BALANS/BALANCE 0.00
38
39 Taliad/Payment
40 I Visa
41 I Rhif Cerdyn: Cyhoeddiad:
42 I Card Number: **** #*** 44% pppp Issue:nnn
43 I wwwww/kkkkk
44 I Cod Awdurdodi: Rhif EFT:
45 I Auth Code: nnnnnn EFT No: wwww
46 I ID y Masnachwr:
47 IMerchant ID: rerrrrrrrrrrrrr
48 IID y Derfynell:
49 ITerminal ID: tttttttt
50 I ID Cais:
51 I Application ID: aaaaaaaaaaaaaaaa
52 I0: Diweddu: Rhif Cyf PAN:
53 I From: MM/YY Expiry: MM/YY PAN Seq No: mm
54 I ID y Gweithrediad:
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 108 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL '(ONFIDENCE Date: 21" April 2005
55 ITransaction ID: nnnnnnnnnnnnnnnnnnnnnnnnnn
56 I Dyddiad/Amser y Taliad:
57 IDate/Time of Payment: 11/02/2003 13:53
59 I Swm/Amount: £50.00
61 IDebydir eich cyfrif gyda’r swm uchod.
62 I Gwiriwyd PIN deiliad y cerdyn.
63 IYour account will be dedited with the
64 I above amount. Cardholder PIN verified.
65 I wy
66 I vwy yyy yyy
67 I vwy yyy VV
68 I yyy yyy VV
70 I ££f£ff£f£LfLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL
V1 =I £ff£f£ffffffrfKrQLQfrffrLfrffrffffrfrfrfffffffffftffe
72
73 I Cadwch i gyfeirio ati, os gwelwch yn dda
74 Please retain for future reference
75
76
77 Diolch Yn Fawr
78 Thank You
79
1 2 3 4
123456789012345678901234567890123456789012
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 109 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal Ref;
Version:
COMMERCIAL IN-CONFIDENCE Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
Welsh/English text - Refund
1 2 3 4
123456789012345678901234567890123456789012
Swyddfa’r Post Cyf.
Post Office Ltd.
Eich Derbynneb
Your Receipt
Feltham Post Office
1, The Walkway
Kings Parade
Middle of Town
Feltham
Middlesex
TwWl 3DD
Rhif COF.TAW/VAT REG No. 243 1700 02
11/02/2003 13:54
SESIWN/SESSION 1-6774-1
DIRYMU/REVERSAL
Stmp bk ist x 10
1 @ 2.60 2.60
Postage stmp
1 @ 3.00 3.00
Colour TV lic
1 @ 97.50 97.50
US Dollar @1.6121 USD/GBP
60- 32..22-
Commission 5.00
CYF DYLEDUS I’R CWSMER
TOTAL DUE TO CUSTOMER 75.88
Siec I'R CWSMER
Cheque TO CUSTOMER 25.88
Taliad Cerdyn I'R CWSMER
Card Payment TO CUSTOMER 50.00
BALANS/BALANCE 0.00
Ad-daliad/Refund
Visa
Rhif Cerdyn: Cyhoeddiad:
Card Number:
wwwww/kkkkk
Joie Joon sno pppp Issue:nnn
Cod Awdurdodi: Rhif EFT:
Auth Code: nnnnnn EFT No: wwww
ID y Masnachwr:
Merchant ID: rerrrerrerrrerr
ID y Derfynell:
Terminal ID: tttttttt
ID Cais:
Application ID: aaaaaaaaaaaaaaaa
0: Diweddu: Rhif Cyf PAN:
From: MM/YY Expiry: MM/YY PAN Seq No: mm
ID y Gweithrediad:
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 110 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
55 I Transaction ID: nnnnnnnnnnnannnnannnnnnnnnn
56 IDyddiad/Amser yr Ad-daliad:
57 IDate/Time of Refund: 11/02/2003 13:53
58
59 I Swm/Amount: £50.00
60
61 I Credydir eich cyfrif gyda’r swm uchod.
62 I Gwiriwyd PIN deiliad y cerdyn.
63 I Your account will be credited with the
64 I above amount. Cardholder PIN verified.
65 I WWW
66 I vue yyy
67 I vwy yyy yyy
68 I vey yyy
69
10 I ££EfELELLELLLLELELLELELLLLELELLELELLELEL
71 =I ££ff£ff£fftffrfKfFffLfLTrTfffLLfLfLfLffLffLffLfLLLL
72
73 I Cadwch i gyfeirio ati, os gwelwch yn dda
74 Please retain for future reference
75
76
77 Diolch Yn Fawr
78 Thank You
79
1 2 3 4
123456789012345678901234567890123456789012
Field Name English Welsh Length I Contents
Line I Char I Line I Char
No. I Pos’ns I No. I Pos’ns
Welsh Header I 01 - - Blank.
01 13-31 19 “Swyddfa’r Post Cyf.’
English Header I 02 14-29 I 02 14-29 16 “Post Office Ltd.’
Welsh Text - - - Suppressed.
03 15-28 14 ‘Eich Derbynneb’.
English Text 03 16-27 I 04 16-27 12 “Your Receipt’.
Office Name 04 01-30 I 05 01-30 30 Branch name, up to 30
characters: (000...)
Address 05- I 01-40 I 06- I 01-40 I 40 Branch address: a variable
1,2,3,4,5 09 10 number of lines up to a
maximum of five.
Postcode 10 01-08 I 11 01-08 8 Branch postcode: pppp ppp
Date 13 13-29 I 14 13-29 17 Date and time:
dd/mm/yyyy hh:mm
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 111 of 224
Without Prejudice and Subject to Contract
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Session ID 14 21-31 I 15 27-37 11 Session ID.
Message 17 01-42 42 Blank or ‘REVERSAL’
or ‘Recovery’.
18 01-42 42 Blank or ‘DIR YMU/
REVERSAL’ or
“Recovery”.
Field Name English Welsh Length I Contents
Line I Char I Line I Char
No. I Pos’ns I No. I Pos’ns
Non-MoP Repeated as necessary.
Product:
Non-BdeC Only present if applicable.
txn:
Product 19 01-16 I 20 01-16 16
Additional data I 19 21-42 I 20 21-42 22 E.g. Girobank account
Qty number
Unit Price 20 01-05 I 21 01-05 5
Value 20 10-18 I 21 10-18 I 9
BdeC txn: 20 29-40 I 21 29-40 12
Product Only present if applicable.
Rate 25 01-16 I 26 01-16 I 16
Currency code 25 19-30 I 26 19-30 12 At most, 4 decimal places.
Currency code 25 32-34 I 26 32-34 3 Changed currency.
Qty 25 36-38 I 26 36-38 3 Local currency.
26 O1-15 I 27 O1-15 15 Negative for a buy
Value transaction.
26 29-40 I 27 29-40 12 Negative for a buy
Commission transaction.
27 29-40 I 28 29-40 12 If zero, whole line is blank.
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 112 of 224
FUJ00001933
FUJ00001933
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Non-MoP
Detail:
Non-MoP - - 30 01-26 26 ‘CYF DYLEDUS I
Session Effect SWYDDFA’R POST?’ or
(Welsh) “CYF DYLEDUS PR
CWSMER’.
Non-MoP 29 01-26 I 31 01-26 26 ‘TOTAL DUE TO POST
Session Effect OFFICE’ or ‘TOTAL DUE
(English) TO CUSTOMER’.
Non-MoP
Value 29 29-40 I 31 29-40 12
MoP Detail:
MoP Name - - 33 01-16 16 E.g. ‘Siec’
(Welsh)
MoP Name 31 O1-16 I 34 01-16 16 E.g. ‘Cheque’.
(English)
MoP Session - - 33 18-30 13 “GAN Y CWSMER’ or PR
Effect (Welsh) CWSMER’.
MoP Session 31 18-30 I 34 18-30 13 “FROM CUSTOMER’ or
Effect ‘TO CUSTOMER’.
(English)
MoP Value Amount:
31 32-40 I 34 32-40 9 For not more than 99999.99
For more than 99999.99
31+1 I 29-40 I 34+1 I 29-40 I 12
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 113 of 224
Without Prejudice and Subject to Contract
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
MoP Detail:
MoP Name - - 33 01-16 16 E.g. ‘Taliad Cerdyn’
(Welsh)
MoP Name 32 O1-16 I 34 01-16 16 E.g. ‘Card Payment’.
(English)
MoP Session I - - 33 18-30 I 13 “GAN Y CWSMER’ or ’R
Effect (Welsh) CWSMER’.
MoP Session I 32 18-30 I 34 18-30 I 13 ‘FROM CUSTOMER’ or
Effect ‘TO CUSTOMER’.
(English)
MoP Value Amount:
32 32-40 I 34 32-40 9 For not more than 99999.99
For more than 99999.99
32+1 I 29-40 I 34+1 I 29-40 12
Non-MoP
Total 33 29-40 I 37 29-40 12
Field Name English Welsh Length I Contents
Line I Char I Line I Char
No. I Pos’ns I No. I Pos’ns
Title 35 01-42 42 ‘Payment’ or ‘Refund’.
39 01-42 42 ‘Taliad/Payment’ or
“Ad-daliad/Refund’.
Issuer Scheme I 36 01-30 I 40 01-30 30 Issuer Scheme name. For
name cards processed by the PIN
pad this field is obtained
from the application label
from the chip. For MSR the
field will be derived from
Reference data
Card Number I 37 14-32 I 42 14-32 19 Obscured PAN (only last
four digits shown, remaining
digits replaced by asterisks):
formatted with spaces if a 16-
digit PAN, unformatted if
any other length.
Issue Number I 37 40-42 I 42 40-42 I 3 Obtained from card: not
always present
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 114 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00001933
FUJ00001933
Ref: NB/REQ/003
Version: 2.0
Date: 21" April 2005
Entry indicator I 38 01-03 3 “‘ICC’=chip read
(kkk...) English 01-06 6 “‘swiped’=magnetic stripe
read
01-05 6 “keyed’=manual entry
(www... /kkk..) 43 01-07 I 7 ‘ICC/ICC’=chip read
Welsh/English 01-16 16 “sweipiwyd/swiped’=
magnetic stripe read
01-16 16 “bysellwyd/keyed’=manual
entry
Authorisation I 39 12-17 I 44 12-17 I 6 Authorisation code from
code Financial Institution
Electronic 39 32-35 I 44 32-35 4 Number assigned by counter
Funds Transfer and sent in [R] message to
Sequence Merchant Acquirer
Number
Merchant ID" I 40 14-28 I 47 14-28 15 Merchant identifier (r7r...),
when available.
Terminal ID 41 14-21 I 49 14-21 8 Terminal identifier (/7...),
when available.
Application ID I 42 17-32 I 51 17-32 16 Obtained from Application
data from the card as read by
PIN pad: Blank for Swipe
and Signature and PKE.
From Date 43 7-11 53 7-11 5 Obtained from Application
data from the card as read by
PIN pad: or from track 2
data if magnetic swipe card
used
Expiry Date 44 22-26 I 53 22-26 I 5 Obtained from Application
data from the card as read by
PIN pad: or from track 2
data if magnetic swipe card
used
8 Ifan [A] from the Merchant Acquirer has been received the Merchant ID will be available. If there has been
a network problem or timeout or if the transaction was cancelled by the Clerk at the Card Check screen before
the [A] was received neither the Merchant ID nor the Terminal ID will be available
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 115 of 224
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
Ref:
Version:
Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
PAN Sequence I 43 41-42 I 53 41-42 2 Obscured PAN (only last
Number four digits shown, remaining
digits replaced by asterisks):
formatted with spaces if a 16-
digit PAN, unformatted if
any other length.
Transaction ID I 44 17-42 I 55 17-42 26 Unique system-generated
transaction identifier
(ann...).
Date & time of I 45 01-37 I 56, I 01-37 37 The date and time that the
payment 57 payment or refund was made
Amount 47 09-17 I 59 13-21 9 7-digit amount in the format
£99999.99 for the requested
transaction value.
Outcome 49- I 01-42 42 Transaction outcome
message (see 56 message in English (2...
Section up to 8 lines), suppressed if
3.2.5.1) blank.
6l- I 01-42 I 42 Transaction outcome
68 message in bilingual text
(vv... up to 8 lines),
suppressed if blank.
Free text 58, 01-40 I 70, 01-40 40 Free text (fff:.., up to 2
footer 59 71 lines) if provided, or
suppressed.
Please Retain I 61 - Blank.
73 02-41 40 “Cadwch i gyfeirio ati, os
gwelch yn dda’
62 05-38 I 74 05-38 34 “Please retain for future
reference’
Welsh Footer I 64 - Blank.
76 14-27 14 “Diolch yn Fawr’.
English Footer I 65 16-24 I 77 16-24 I 9 “Thank You’.
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 116 of 224
Fujitsu Services
EMV Retail: User Interface Design Proposal Ref:
Version:
COMMERCIAL IN-CONFIDENCE Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
3.2.5.1
Receipt Outcome Messages
The message printed in the ‘Outcome message’ field of the customer copy receipt (see Section
3.2.5) is dependent on a number of circumstances, as shown in the following table.
The Message refs relate to entries in the table in Section 3.
5
.2 that define the text of each
message.
Authorisation Status Outcome Message
Ref.
Authorised OK Payment Authorised by MA and signature matched by clerk I RT200
Payment Authorised by MA and verified by PIN pad RT201
Refund Authorised by MA and signature matched by clerk RT202
Refund Authorised by MA and verified by PIN pad RT203
Payment Authorised by MA and verified by PIN pad and by I RT206
signature
Refund Authorised by MA and verified by PIN pad and by RT207
signature
Payment Authorised by MA and not verified by cardholder RT204
Refund Authorised by MA and not verified by cardholder RT205
Key:
MA = Merchant Acquirer
3.2.5.2
Outcome Message Text
The message text is the same as pre S70 and includes the new authorisation status for
transactions accepted by the Merchant Acquirer but failed by the PIN pad. New codes have
been added to cover combination CVMs.
The text of the outcome message printed is as follows (word wrap as shown):
Mess. I Message Text - English Message Text - Welsh/English
Ref.
RT200 I Your account will be debited with the I Debydir eich cyfrif gyda’r swm ucho
nt will be debited with the
nfirmed.
RI201 nt will be debited with the f gyda’r awn uchod.
saction confirmed. yd y gweithre
Your account will be < 1 with the
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 117 of 224
Fujitsu Services
EMV Retail
COMMERCIAL IN-CONFIDENCE
User Interface Design Proposal
Ref: NB/REQ/003
Version: 2.0
Date: 21" April 2005
RT202
Your account will be credited with the
above amount. Cardholder signature.
Transaction confirmed.
Credydir eich cyfrif gyda’r swm uchod.§
Llofnod deiliad y cerdyn. Cadarnhawyd y
gweithrediad.
Your account will be credited with the
above amount. Cardholder signature.
Transaction confirmed.
RT203
Your account will be credited with the
above amount. Cardholder PIN verified.§
Transaction confirmed.
Credydir eich cyfrif gyda’r swm uchod.
Gwiriwyd PIN deiliad y cerdyn.§}
Cadarnhawyd y gweithrediad.
Your account will be credited with the
above amount. Cardholder PIN verified.f]
Transaction confirmed.
RT204
Your account will be debited with the
above amount. Transaction confirmed.
Debydir eich cyfrif gyda’r swm uchod.§
Cadarnhawyd y gweithrediad.
Your account will be debited with the
above amount. Transaction confirmed.
RT205
Your account will be credited with the
Transaction confirmed.
Credydir eich cyfrif gyda’r swm uchod.§
Cadarnhawyd y gweithrediad.
Your account will be credited with the
above amount. Transaction confirmed.
R206
Your ac
above amount. Cardholder PIN verified.
Cardholder signature. Transaction
confirmed.
unt will be debited with the
Debydir eich cyfrif gyda’r swm uchod.
Gwiriwyd PIN deiliad y cerdyn. Llofnod
deiliad y cerdyn. Cadarnhawyd y
gweithrediad.
Your account will be debited with the
above amount. Cardholder PIN verified.
Cardholder signature. Transaction
confirmed.
RT207
Your account will be credited with the
above amount. Cardholder PIN verified.
Cardholder signature. Transaction
confirmed.
Credydir eich cyfrif gyda’r swm uchod.
Gwiriwyd PIN deiliad y cerdyn. Llofnod
deiliad y cerdyn. Cadarnhawyd y
gweithrediad.
Your account will be credited with the
above amount. Cardholder PIN verified.
Cardholder signature. Transaction
confirmed.
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Page: 118 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
3.3. Duplicate Customer Session Receipt
3.3.1 Purpose
This is a copy of the customer record of the session.
3.3.2 Frequency
Ad hoc.
3.3.3 Notes
Replica of last receipt issued. Any number may be taken, all say ‘DUPLICATE’.
A Horizon parameter defines a filter which determines the Post Office Ltd products that are
printed below the TOTAL DUE TO POST OFFICE line. For example, debit card
payments/refunds appear below this line and not as part of the transaction listing.
3.3.4 Sequence
Receipts and Payments (excluding filtered products) in chronological order, then MoP
(including filtered products).
The data shown in the examples is illustrative only —
the exact text can change, and so differ from that in the examples.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 119 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal Ref;
Version:
COMMERCIAL IN-CONFIDENCE Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
3.3.5
Layout and Example Content
English text - Payment
1 2 3 4
123456789012345678901234567890123456789012
Post Office Ltd.
Your Receipt
Feltham Post Office
1, The Walkway
Kings Parade
Middle of Town
Feltham
Middlesex
TW1 3DD
VAT REG No. 243 1700 02
11/02/2003 13:54
SESSION 1-6774-1
DUPLICATE
Stmp bk ist x 10
1 @ 2.60 2.60
Postage stmp
1 @ 3.00 3.00
Colour TV lic
4 @ 97.50 97.50
US Dollar @1.6121 USD/GBP
60- 32.22-
Commission 5.00
TOTAL DUE TO POST OFFICE 75.88
Cheque FROM CUSTOMER 25.88
Card Payment FROM CUSTOMER 50.00
BALANCE 0.00
Payment
Visa
Card Number: **** *#** **** pppp Issue:nnn
kkkkk
Auth Code: nnnnnn EFT No: wwww
Merchant ID: rrrrrrrrrrrrrrrv
tttttttt
ID: aaaaaaaaaaaaaaaa
From: MM/YY Expiry: MM/YY PAN Seq No: mm
Transaction ID: nnnnnnnnnannnnannnnnnnnnan
Date/Time of Payment: 11/02/2003 13:53
Terminal ID:
Application
Amount: £50.00
Your account will be debited with the
above amount. Cardholder PIN verified.
uuuuUUUUUUUUUUUUUUUUUUUUUUUNUUUUUUUUUUUUE
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 120 of 224
Fujitsu Services EMV Retail: User Interface Design Proposal Ref:
Version:
COMMERCIAL '(ONFIDENCE Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
52 I wuuuuuuuuuuuuuuuuUuUuUUUUUUUUUUUUUUUUUUUUUUL
53 I uuauuuuuuuuuuuuuuuUuuUUUUUUUUUUUUUUUUUUUUUUU
54 I uuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuUUUUUUUUU
55 I uuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuu
56 I wuuuuuuuuuuuuuuuuuuuuuuUuuUUUUUUUUUUUUUUUU
58 I £f£ffffffffTffffrffffffFfffffffLfLffLfFfLfLLfL
59 I ££fffffffffTfKffffffLfTffKfffffffffffffLfffLfLt
60
61
62 Please retain for future reference
63
64
65 Thank You
66
1 2 3 4
123456789012345678901234567890123456789012
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 121 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal Ref;
Version:
COMMERCIAL IN-CONFIDENCE Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
Welsh/English text - Payment
1 2 3 4
123456789012345678901234567890123456789012
Swyddfa’r Post Cyf.
Post Office Ltd.
Eich Derbynneb
Your Receipt
Feltham Post Office
1, The Walkway
Kings Parade
Middle of Town
Feltham
Middlesex
Twi 3DD
Rhif COF.TAW/VAT REG No. 243 1700 02
11/02/2003 13:54
SESIWN/SESSION 1-6774-1
DYBLYGIAD/DUPLICATE
Stmp bk ist x 10
1 @ 2.60 2.60
Postage stmp
1 @ 3.00 3.00
Colour TV lic
1 @ 97.50 97.50
US Dollar @1.6121 USD/GBP
60- 32.22=
Commission 5.00
CYF DYLEDUS I SWYDDFA’R POST
TOTAL DUE TO POST OFFICE 75.88
Siec GAN Y CWSMER
Cheque FROM CUSTOMER 25.88
Taliad Cerdyn GAN Y CWSMER
Card Payment FROM CUSTOMER 50.00
BALANS/BALANCE 0.00
Taliad/Payment
Visa
Rhif Cerdyn: Cyhoeddiad:
Card Number:
wwwww/kkkkk
Joie Joon sno pppp Issue:nnn
Cod Awdurdodi: Rhif EFT:
Auth Code: nnnnnn EFT No: wwww
ID y Masnachwr:
Merchant ID: rerrrerrerrrerr
ID y Derfynell:
Terminal ID: tttttttt
ID Cais:
Application ID: aaaaaaaaaaaaaaaa
0: Diweddu: Rhif Cyf PAN:
From: MM/YY Expiry: MM/YY PAN Seq No: mm
ID y Gweithrediad:
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 122 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL '(ONFIDENCE Date: 21" April 2005
55 I Transaction ID: nnnnnnannnnnnnnnannnnannnnn
56 I Dyddiad/Amser y Taliad:
57 IDate/Time of Payment: 11/02/2003 13:53
58
59 I Swm/Amount: £50.00
60
61 IDebydir eich cyfrif gyda’r swm uchod.
62 I Gwiriwyd PIN deiliad y cerdyn.
63 I Your account will be dedited with the
64 I above amount. Cardholder PIN verified.
65) I vwy yyy
66 I voy yyy
67 I vwy wy yyy VV
68 I vey yyy
69
10 I ££EfELELLELLLLELELLELELLLLELELLELELLELEL
71 =I ££ff£ff£fftffrfKfFffLfLTrTfffLLfLfLfLffLffLffLfLLLL
72
73 I Cadwch i gyfeirio ati, os gwelwch yn dda
74 Please retain for future reference
75
76
77 Diolch Yn Fawr
78 Thank You
79
1 2 3 4
123456789012345678901234567890123456789012
Field Name English Welsh/English I Length I Contents
Line I Char I Line I Char
No. I Pos’ns I No. I Pos’ns
Duplicate 16 01-42 42 ‘DUPLICATE’.
Indicator
17 01-42 42 ‘DYBLYGIAD/
DUPLICATE’
Message 17 01-42 I 18 01-42 42 Blank or ‘Recovery’.
The remaining field definitions are the same as those of the Customer Session Receipt (see
Section 3.2).
The refund layouts are similar to the payment layouts but with the word ‘Refund’ substituted
for ‘Payment’.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 123 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
3.4 Customer Debit Card Payment/Refund Receipt — Declined
Transaction
3.4.1 Purpose
This is the debit card customer receipt for a declined debit card transaction. The receipt format
contains additional data items not present pre S70: Card Issue Number, Authorisation Code,
Application ID, Effective From Date, Effective To Date, PAN Sequence Number, EFT
Number, issuer scheme name, an entry indicator, and the date and time of payment. Less detail
of the card number is now shown.
3.4.2 Frequency
For declined debit card transactions within a customer session.
3.4.3 Notes
The circumstances in which the debit card receipts are printed are given in Section 3.
3.4.4 Sequence
On completion of failed transaction.
The data shown in the examples is illustrative only —
the exact text can change, and so differ from that in the examples.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 124 of 224
Without Prejudice and Subject to Contract
Fujitsu Services EMV Retail: User Interface Design Proposal Ref:
Version:
COMMERCIAL PE
-CONFIDENCE Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
3.4.5 Layout and Example Content
English text
1 2 3 4
123456789012345678901234567890123456789012
o1
02 Post Office Ltd.
03 Your Receipt
04
05 I17/01/2002 11:47:22 CAP:01 BP:01 SU:SH1
06 I Feltham Post Office FAD: 123456X
07 I1, The Walkway
08 IKings Parade
09 IMiddle of Town
10 I Feltham
11 I Middlesex
12 I Twi 3DD
13
14 title
15 I Visa
16 ICard Number: **** **** **** pppp Issue:nnn
17 ‘I kkkkk
18 Auth Code: nnnnnn EFT No: wwww
19 IMerchant ID: rrrrrrrrrrrrrrv
20 ITerminal ID: tttttttt
21 IApplication ID: aaaaaaaaaaaaaaaa
22 I From: MM/YY Expiry: MM/YY PAN Seq No: mm
23 I Transaction ID: nnnnn:
24 I Date/Time of ppppppp: 17/01/2002 11:47
26 I Amount: £99999.99
28 uuuuuuuuUuUuUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
29 wuuuuUUuUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
30 uuuuuuUuUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
31 uuuuUuUuUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUL
32 uuuuuUuUuUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUL
33 uuuuuuuUuuUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUL
34 uuuuuUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUL
35 uuuuuuuuuuUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
37 ff£f£fffFLfLfffLfLfLfLfLLfLfLffffLLfLLLfLLLLLLLLLLfLLL
38 fLLLELLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLE
39
40
41 Please retain for future reference
42
43 This is not a VAT receipt
44
1 2 3 4
123456789012345678901234567890123456789012
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 125 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal Ref;
Version:
COMMERCIAL IN-CONFIDENCE Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
Welsh/English text
1 2 3 4
123456789012345678901234567890123456789012
o1 Swyddfa’r Post Cyf.
02 Post Office Ltd.
03 Eich Derbynneb
04 Your Receipt
05
06 I17/01/2002 11:47:22 CAP:01 BP:01 SU:SH1
07 I Feltham Post Office FAD: 123456xX
08 I1, The Walkway
09 I Kings Parade
10 IMiddle of Town
11 I Feltham
12 I Middlesex
13 I Tw1 3DD
14
15 title
16 Ivisa
17 Rhif Cerdyn: Cyhoeddiad:
18 ICard Number: *#** *#** *#** pppp Issue: nnn
19 I wwwww/kkkkk
20 I Cod Awdurdodi: Rhif EFT:
21 I Auth Code: nnnnnn EFT No: wwww
22 I ID y Masnachwr:
23 IMerchant ID: rerrrrrrererecr
24 IID y Derfynell:
25 ITerminal ID: tttttttt
26 I ID Cais:
27 IApplication ID: aaaaaaaaaaaaaaaa
28 Io: Diweddu: Rhif Cyf PAN
29 I From: MM/YY Expiry: MM/YY PAN Seq No: mm
30 I ID y Gweithrediad:
31 I Transaction ID: nannnnannnnnnnnnnnnnnnnnnn
32 I Dyddiad/Amser wwwwwww:
33 I Date/Time of ppppppp: 17/01/2002 11:47
34
35 I Swm/Amount: £99999.99
36
37 I wwe y yyy
38) I wwe
39 I WWW
40 I wwe yyy
41 I www ww
42 I vow yyy
430 I WwW
44 I wwe yyy
45
46 I £EfELELLELELELLELELELLELELLELELLELELLELE
47 ff£ffftffTfLrfffLfrffQTrfrffrffrffrffrfffffffffffffft
48
49 Cadwch i gyfeirio ati, os gwelwch yn dda
50 Please retain for future reference
51 Nid derbynneb TAW yw hon
52 This is not a VAT receipt
53
1 2 3 4
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 126 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
Ref: NB/REQ/003
Version: 2.0
Date: 21" April 2005
123456789012345678901234567890123456789012
Field Name English Welsh Length I Contents
Line I Char I Line I Char
No. I Pos’ns I No. I Pos’ns
Title 14 01-42 42 “Payment” or ‘Refund’.
15 01-42 I 42 “Taliad/Payment’ or
“Ad-daliad/Refund’.
Issuer Scheme I 15 01-30 I 16 01-30 I 30 Issuer Scheme name (jj/...).
name For cards processed by the
PIN pad this field is obtained
from the application label
from the chip. For MSR the
field will be derived from
Reference data
Card Number I 16 14-32 I 18 14-32 I 19 Obscured PAN (only last four
digits shown, remaining digits
replaced by asterisks):
formatted with spaces if a 16-
digit PAN, unformatted if any
other length.
Issue Number I 16 40-42 I 18 40-42 I 3 Obtained from card: not
always present
Entry indicator I 17 01-03 3 “ICC’=chip read
(kkk...) English 01-06 6 “‘swiped’=magnetic stripe read
01-05 6 “keyed’=manual entry
(www... KKK...) 19 01-07 I 7 ‘ICC/ICC’=chip read
Welsh/English 01-16 I 16 “sweipiwyd/swiped’=
magnetic stripe read
01-16 I 16 “pysellwyd/keyed’=
manual entry
Authorisation 18 12-17 I 21 12-17 I 6 Authorisation code from
code Financial Institution, if present
Electronic 18 32-35 I 21 32-35 I 4 Number assigned by counter
Funds Transfer and sent in [R] message to
Sequence Merchant Acquirer
Number
Merchant ID 19 14-28 I 23 14-28 15 Merchant identifier (rrr...),
when available.
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Page: 127 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00001933
FUJ00001933
Ref: NB/REQ/003
Version: 2.0
Date: 21" April 2005
Terminal ID
20
14-21 I 25 14-21 I 8
Terminal identifier (¢/...),
when available.
Application ID
21
17-32 I 27 17-32 I 16
Obtained from Application
data from the card as read by
PIN pad: or from track 2 data
if magnetic swipe card used
From Date
22
07-11 I 5
Obtained from Application
data from the card as read by
PIN pad: or from track 2 data
if magnetic swipe card used
Expiry Date
22
22-26 I 29 22-26 I 5
Obtained from Application
data from the card as read by
PIN pad: or from track 2 data
if magnetic swipe card used
PAN Sequence
Number
22
41-42 I 29 41-42 I 2
Obtained from Application
data from the card as read by
PIN pad: or from track 2 data
if magnetic swipe card used
Transaction ID
23
17-42 I 31 17-42 I 26
Unique system-generated
transaction identifier (”mn...).
Date & Time
of Payment/
Refund
32 01-37 I 37
Welsh translation of the
following line’s fieldname:
wwwwwww should be set to ‘y
Taliad’ for a payment or ‘yr
Ad-daliad’ for a refund
24
01-37 I 33 01-37 I 37
The date and time that the
payment or refund was made
Ppppppp should be set to
‘Payment’ or ‘Refund’
Amount
26
09-17 I 35 13-21 I 9
7-digit amount in the format
£99999.99 for the requested
transaction value.
Outcome
message (see
Section
3.2.5.2)
28-
35
01-42 42
Transaction outcome message
in English (wa... up to 4
lines), suppressed if blank.
37-
44
01-42 I 42
Transaction outcome message
in bilingual text (vvv... up to 8
lines), suppressed if blank.
Free text
footer
37
38
01-40 I 46, 01-40 I 40
47
Free text (fff..., up to 2 lines)
if provided, or suppressed.
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Page: 128 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal
FUJ00001933
FUJ00001933
Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Footer 40 - Blank.
49 02-39 I 38 “Cadwch i gyfeirio ati, os
gwelwch yn dda’.
41 05-38 I 50 05-38 I 34 “Please retain for future
reference’.
42 - Blank.
51 09-32 I 24 “Nid derbynneb TAW yw
hon’.
43 09-33 I 52 09-33 I 25 ‘This is not a VAT receipt’.
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Page: 129 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
3.4.5.1 Receipt Outcome Messages
The message printed in the ‘Outcome message’ field of the customer copy receipt (see Section
3.3.5) is dependent on a number of circumstances, as shown in the following table.
The Message refs relate to entries in the table in Section 3.4.5.2 that define the text of each
message.
The messages are the same as pre S70 but there is a new authorisation status for transactions
accepted by the Merchant Acquirer but failed by the PIN pad.
Authorisation Status Outcome Message
Ref.
Authorised OK Declined by clerk — no customer signature RTIO1
Declined by clerk — signature fail RTIIS
Declined — authorised amount differs from requested RT113
amount
Declined by PIN pad: (card error or customer cancel) RTH7
Card Check Failure by clerk I Declined RTL16
Declined — Impound Card Clerk confirms that the card has been retained RT102
Clerk confirms that the card has not been retained RT103
Declined — Other MA declined RT104
Failed by Debit Card agent System/network failure RTL10/114
Failed by/at Counter System/network failure RTII
(timeouts)
Failed by/at Counter (other) System/network failure RT112/118
Key:
MA = Merchant Acquirer
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 130 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
COMMERCIAL IN-CONFIDENCE
EMV Retail: User Interface Design Proposal
Ref: NB/REQ/003
Version: 2.0
Date: 21" April 2005
3.4.5.2
Outcome Message Text
The message text is the same as pre S70 and includes the new authorisation status for
transactions accepted by the Merchant Acquirer but failed by the PIN pad.
The text of the outcome message printed is as follows (word wrap as shown):
The transaction has been declined by the
customer's card.
Mess. Message Text - English Message Text - Welsh/English
Ref.
RTIOI, “4 CANCELLED *** *** DIDDYMWYD/CANCELLED ***
RTI3,
RTLS,
RTII6
RT102 *** CANCELLED *** *** DIDDYMWYD/CANCELLED ***
The card has been retained. Cafodd y cerdyn ei gadw.
You may wish to contact the card allai yr hoffech gysylitu & dyroddwr
y cerdyn.
‘The card has been retained.
You may wish to contact the card issuer.
RT103 *** CANCELLED *** *** DIDDYMWYD/CANCELLED ***
The card has been returned. Cafodd y cerdyn ei ddychwelyd.
You may wish to contact the card issuer. I Efallai yr hoffech gysylltu 4 dyroddwr
y cerdyn.
The card has been returned.
You may wish to contact the card issuer.
RT104 *** CANCELLED *** *** DIDDYMWYD/CANCELLED ***
You may wish to contact the card Efallai yr hoffech gysylltu a dyroddwr
y cerdyn.
You may wish to contact the card issuer.
RTO, *** CANCELLED *** *** DIDDYMWYD/CANCELLED ***
RTI Unable to complete the transaction. Yn methu cwblhau’r gweithrediad.
47. Sorry for any inconvenience caused. Ymddiheurwn am unrhyw drafferth.
RTI2, .
RTs Unable to complete the transaction.
ais Sorry for any inconvenience caused.
RTT
RTS *** CANCELLED *** *** DIDDYMWYD/CANCELLED ***
Gwrthodwyd y gweithrediad gan gerdyn y
cwsmer.
The trai
customer’
lon has been declined by the
ard.
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Page: 131 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
3.5 Office Debit Card Receipt for Signature
3.5.1 Purpose
This is to obtain the customer’s signature for verification in a retail card payment/refund
request. The signature slip is retained in the office. The office receipt will be produced when a
signature CVM is required and:
anon ICC card is used in the magnetic stripe reader
an ICC card cannot be processed in the PIN pad and falls back to the magnetic stripe
reader
an ICC card is read by the PIN pad but the PIN pad requests signature verification.
Also, the format of the receipt will be changed for S70.
3.5.2 Frequency
Per debit card transaction requiring a customer signature.
3.5.3 Notes
The circumstances in which the debit card receipts are printed are given in Section 3.
3.5.4 Sequence
Printed prior to signature dialogue.
The data shown in the examples is illustrative only —
the exact text can change, and so differ from that in the examples.
3.5.5 Layout and Example Content
This is a change to the signature slip to meet Streamline requirements. A variable text area will
be provided on the slip so that for a combination CVM (both PIN and signature), the text
“Cardholder PIN verified’ will be printed.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 132 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal Ref;
Version:
COMMERCIAL PE
-CONFIDENCE Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
English text
1 2 3 4
123456789012345678901234567890123456789012
01
02 Post Office Ltd.
03
04 I17/01/2002 11:47:22 CAP:01 BP:01 SU:SH1
05 I Feltham Post Office FAD: 123456X
06 I1, The Walkway
07 IKings Parade
08 IMiddle of Town
09 I Feltham
10 I Middlesex
11 I Twi 3DD
12
13 *#** Office Copy - Retain ***
14
15 title
16 I 9995555IFIIIIFIIIIIIIIIIIIIIII
17 ICard Number: pppp PPPP PPPP PPPP kkkkk
18 I AID: aaaaaaaaaaaaaaaa PAN Seq No: nn
19 I mm/yy mm/yy iii rrerrrrrrrrrrrrr aaaaaa
20 ITerminal ID: tttttttt EFT No: wwww
21 I Transaction ID: nannnnnnnnnnnnnnannnnannnnn
22 I Date/Time of ppppppp: 17/01/2002 11:47
23
24 I wuwuuuuuuuuuuuuuuuuuuuuuuuuuuUUUUUUUUUE
25 I wuguuuuuuzuuuuuuuuuuuuuuuuuuuuuuuUuUUUUE
26 I wuwuuguuuuuuuuuuuuuuuuuuuuUUUUUUUUUU
27) I auguuuuauuauuuuuuuuuuuuuuuuuaUUUUUL
28 I guguuuuuuuuuuauuuuuuuUUUUUUUUUUUUUUUUU
29 I wuguuzuuuuzuuuuuuuuuuUUUUUUUUUUUUUUUE
30 I wugauzuuuuuuuuuuuuuUUUUUUUUUUUUUUUU
310 I wuwuuauuuuuuuuuuuuuuUUUUUUUUUUUUU
32
33 I text
34 I Amount: £99999.99
35 ICardholder’s signature:
36
37
38
39
40
41
42 This is not a VAT receipt
43
T 2 3 4
123456789012345678901234567890123456789012
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 133 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal Ref;
Version:
COMMERCIAL PE
-CONFIDENCE Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
Welsh/English text
1 2 3 4
123456789012345678901234567890123456789012
01 Swyddfa’r Post Cyf.
02 Post Office Ltd.
03
04 I17/01/2002 11:47:22 CAP:01 BP:01 SU:SH1
05 I Feltham Post Office FAD: 123456X
06 I1, The Walkway
07 IKings Parade
08 IMiddle of Town
09 I Feltham
10 I Middlesex
11 I Twi 3pD
12
13 *** Office Copy - Retain ***
14
15 title
16 I 995555FIFFIFIFIIIIIIIIIIIIIIII
17 I Rhif Cerdyn: wowwww
18 I Card Number: pppp Pppp PPPP PPPP kkkkk
19 I AID: Rhif Cyf PAN:
20 I AID: aaaaaaaaaaaaaaaa PAN Seq No: nn
21 I mm/yy mm/yy iii rrrrrrrrrrrrrrrrvaaaaaa
22 I ID y Derfynell: Rhif EFT:
23 ITerminal ID: tttttttt EFT No: wwww
24 IID y Gweithrediad:
25 Ifransaction ID: nnnnnnnnnnannnnnnannnnannn
26 I Dyddiad/Amser wwwwwww:
27 IDate/Time of ppppppp: 17/01/2002 11:47
28
29 I wuwuuzuuuuzuuuuuuuuuuUUUUUUUUUUUUUUUUUE
30 I wuvuuzuuuuuuuuuuuuuuUUUUUUUUUUUUUUU
31) I uwauzuuuuuuuuuuuuuuuUuUUUUUUUUUUUU
320 I auguuuuauuuuuuuuuuuauUuUUUUUUUUUUL
33 I wuwuuzuuuuuuuuuuuuuuuuuUuUUUUUUUBUUUUUUU
34 I wuguuzuuuuwuuuauuuuuuuuuuuUuUUUUUUUUUUUE
35 I wuwuuuuuuuuuuuuuuuuuuuuuUUUUUUUUUUU
36 I wuuuuuuguuuuuuuuuuuuuuUUUUUUUUUUUUUUL
37
38 I Welsh text
39 I text
40 I Swm/Amount: £99999.99
41 ILlofnod deiliad y cerdyn:
42 I Cardholder’s signature:
43
44
45
46
47
48 Nid derbynneb TAW yw hon
49 This is not a VAT receipt
50
T 2 3 4
123456789012345678901234567890123456789012
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 134 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Field Name English Welsh Length I Contents
Line I Char I Line I Char
No. I Pos’ns I No. I Pos’ns
Office Copy 13 09-36 I 13 09-36 I 28 “*** Office Copy — Retain
Text ein
Title 15 01-42 42 ‘Payment’ or ‘Refund’.
15 01-42 I 42 ‘Taliad/Payment’ or
“Ad-daliad/Refund’.
Issuer Scheme I 16 01-30 I 16 01-30 I 30 Issuer Scheme name (jjj...).
name For cards processed by the
PIN pad this field is obtained
from the application label from
the chip. For MSR the field
will be derived from Reference
data
Welsh entry 17 Welsh translation of the
indicator following line’s entry:
(www...) 34-36 I 3 ‘ICC’=chip read
34-42 I 9 “‘sweipiwyd’=magnetic stripe
read
34-42 I 9 “bysellwyd’=manual entry
Card Number I 17 14-32 I 18 14-32 I 19 Un-obscured PAN formatted
with spaces if a 16-digit PAN,
unformatted if any other
length.
Entry indicator I 17 34-36 I 18 34-36 I 3 ‘ICC’=chip read
(kkk...) 34-39 34-39 I 6 “‘swiped’=magnetic stripe read.
34-38 34-38 I 5 “‘keyed’=manual entry
Application ID I 18 06-21 I 20 06-21 I 16 Obtained from Application
data from the card as read by
PIN pad: or from track 2 data
if magnetic swipe card used
PAN Sequence I 18 41-42 I 20 41-42 I 2 Obtained from Application
Number data from the card as read by
PIN pad: or from track 2 data
if magnetic swipe card used
Expiry Date 19 01-05 I 21 01-05 I 5 Card ‘Expires End’ date in the
format mm/vy, or blank.
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Page: 135 of 224
Without Prejudice and Subject to Contract
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Valid From 19 07-11 I 21 07-11 I 5 Card ‘Valid From’ date in the
Date format mm/yy, or blank.
Issue No. 19 13-15 I 21 13-15 I 3 Card Issue Number (iii) or
blank.
Merchant ID 19 17-31 I 21 17-31 I 15 Merchant identifier (rrr...),
when available.
Authorisation 19 34-39 I 21 34-39 I 6 Authorisation code (aaaaaa)
Code or blank.
Terminal ID 20 14-21 I 23 14-21 I 8 Terminal identifier (##7...),
when available.
Electronic 20 32-35 I 23 32-35 I 4 Number assigned by counter
Funds Transfer and sent in [R] message to
Sequence Merchant Acquirer
Number
Transaction ID I 21 17-42 I 25 17-42 I 26 Unique system-generated
transaction identifier (nmn...).
Date & Time 26 01-37 I 37 Welsh translation of the
of Payment/ following line’s fieldname:
Refund wwwwwww should be set to ‘y
Taliad’ for a payment or ‘yr
Ad-daliad’ for a efund.
22 01-37 I 27 01-37 I 37 The date and time that the
payment or refund was made
Ppppppp should be set to
‘Payment’ or ‘Refund’.
Welsh text - - 29 01-35 I 35 For a payment:
“Debydwch fy nghyfrif fel y
dangosir’
01-36 I 36 For a refund:
“Credydwch fy nghyfrif fel y
dangosir’.
Combination 24- I 01-42 42 Verification message in
CVM only: 31 English (a... up to 8 lines),
verification suppressed if blank.
(see belo ) 29- I 01-42 I 42 Verification message in
. 36 bilingual text (vvv... up to 8
lines), suppressed if blank.
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Page: 136 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services
COMMERCIAL IN-CONFIDENCE
EMV Retail: User Interface Design Proposal
Ref: NB/REQ/003
Version: 2.0
Date: 21" April 2005
Text 24 01-32 I 30 01-32 I 32 For a payment:
“Please debit my account as
shown’.
01-33 01-33 I 33 For a refund:
“Please credit my account as
shown’.
Amount 25 09-17 I 31 13-21 I 9 7-digit amount in the format
£99999.99 for the requested
transaction value.
Footer 39 09-32 I 24 “Nid derbynneb TAW yw
hon’.
33 09-33 I 40 09-33 I 25 “This is not a VAT receipt’.
PIN verification message
The text of the verification message printed is as follows (word wrap as shown):
Mess. Message Text - English Message Text - Welsh/English
Ref.
RTISO Cardholder PIN verified. Gwiriwyd PIN dei cerdyn.
Cardholder PIN v
(Note: If RT150 is not printed, its following blank line is also suppressed.)
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Page: 137 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
4.0 Response Codes and their Effects
This section describes only the new response codes which may be returned as a consequence
of using an EMV/ICC card. The responses described in NB/SPE/013 still apply for all existing
response codes.
A new response code 80 is introduced here to describe a situation where the merchant
acquirer approves a transaction but the card reverses that decision. In this case the response
code from the acquirer will be 0 but this will be converted to 80 if the card returns an AAC
cryptogram.
4.1 Screens
4.1.1 Fixed screens, no response code based text
If there are any changes from NB/SPE/013 Section 6.1.1, as a result of new APACS codes,
these will be included in later versions of this document.
4.1.2 Soft screens, based on response code
No change — no new response codes currently identified
4.2 Receipts
4.2.1 Receipt Messages by response code/outcome
See sections 3.2.5.1 and 3.2.5.2 for authorised transactions.
See sections 3.4.5.1 and 3.4.5.2 for declined transactions.
Additional Response codes for EMV.
NB Resp-I Authoris- I Outcome Receipt Outcome Message I Possible
onse ation Message lookup Transaction
Code Status code Result Code
in [C]
80 Declined Declined by I *** CANCELLED *** RT1I18 06
customer’s
card
81 Declined Fall back to. I *** CANCELLED *** RT1I18 07
MSR after
2™ GenAC
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 138 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
COMMERCIAL IN-CONFIDENCE
EMV Retail: User Interface Design Proposal
FUJ00001933
FUJ00001933
NB/REQ/003
Version: 2.0
Date:
21" April 2005
4.2.2 Transaction result codes
These are recorded with the transaction details.
Transaction I Meaning
Result Code
in [C]
01 Authorised by FI and accepted by PIN pad
02 Cancelled ~ either by the clerk or by the customer pushing the cancel button on the PIN
pad or by removing the card too soon
03 Customer Signature Failed
04 Fee Customer Declined
05 Card Check Failed
06 Declined by FI
07 Decline by PIN pad or some other failure
© 2004 Fujitsu Services
Without Prejudice and Subject to Contract
COMMERCIAL IN-CONFIDENCE
Page: 139 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.0 Screen Layouts
5.1 EMV specific counter screens
Screens in this section are EMV specific. That is, only new screens which have been
introduced for the EMV development. Screens which are common to EMV, NBS and DCS
can be found in Annexe B.
5.1.1 Screen ER1: Card Insertion (First attempt)
y
[Serve Customer
)) Card Insertion’ eS I Card Payment
Ask the customerto v
} insert their cardIinithe
PIN pad:
Card Insertion
I Touch Cancel to cancel
the transaction:
Note this screen will only be displayed:
= When the EMV Retail button is selected from the settlement menu, and
= When the card hasn’t been inserted in the PIN pad
The tab heading at the right hand side of the screen will contain “Card Refund” for reversal
transactions.
In the event of card insertion timeout, This screen will be replaced by EB4 cancelled and
subsequently by ER24 Card Insertion Timeout.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 140 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.2 Screen ER2: Multiple Cards (Payment)
(ES Briome
I Aiposte Mis
[Serve Customer [Prev
} Multiple Cards
I A\cardipayment has
I falready been made)in)
this'session:
I Advise customento use
I anjaltermative)method of,
I payment:
{Cancel
This screen is displayed when the counter detects that a second attempt is being made to settle
using a debit card. This is not necessarily the same card. The counter is set to reject use of a
second card.
If a refund is being processed the screen ER26 (see 5.1.26) is used instead.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 141 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.3 Screen ER3: PIN Locked
Jel I Sgro Hip
(2)
}
e Customer. Prev
I PIN Blocked
I dhe PINs blocked:
I Ask thecustomer NOM to) I
remove the card until
promptedito do'so!
hajhe customer may wish
} tolcontact the card
}lissuere
This screen is displayed when the PIN Pad discovers that the customer’s card has been PIN
blocked. This may be from the outset when the customer’s card is already blocked or as a
result of invalid PIN entry. Seeing this screen does not necessarily mean that the transaction
will be declined. It is a decision for the card and PIN pad based on issuer supplied data to
decline or approve usage if such a card.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 142 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.4 Screen ER4: Waiting for PIN (2 buttons)
I Ask the customento
= Entern PIN
= Press ENT
I tolconfirmitransaction
ouch Bypassiif,
customenhas forgotten 7 ) & PIN Entry:
I the PIN/on Cancel ifithey, }
} decide not to proceed:
This screen is used when the clerk is able to select the bypass option. This is under reference
data control and when the bypass option in reference data is switched off the clerk will be
presented with screen ERS instead.
5.1.5 Screen ER5: Waiting for PIN (1 button)
This screen is the same as screen ER4 except that the left hand panel has a single Cancel
button. This screen is used when the clerk is no longer allowed to select the bypass option.
Until that point the clerk will be presented with screen ER4 instead. Reference data determines
whether screen ER4 or ERS is presented to the clerk.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 143 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.6 Screen ER6: Card cannot be read by PIN pad
a S S Home
Ripe A
[Serve Customer [Prev [Bin
j Waiting For Swipe
I dihe card cannot be
I processed by the PIN
pad:
Please Swipe the cardior
} touch Cancellifithe
I customer decides not to
)iproceed:
{Cancel
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 144 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
I
Cx IPOS:
Customer has madelan
}lunsuccessful attempt to
Hinsert the cardiinithe PIN
I Pad: Cardinserntion
Please'give advicevand
ask customentomneinsenm I
I} the card; omtouch Cancel I
I to'cancel/the transaction
This screen is what happens to screen ER1 if the customer has had an attempt at inserting his
card into the PIN pad but it cannot be read. Possible reasons:
= the card has been inserted upside down
= the card has been inserted back to front
= the card is not valid
= the chip is damaged.
The PIN pad allows the customer 3 attempts at inserting the card at which point it will allow
the transaction to fallback to swipe mode.
The tab heading at the right hand side of the screen will contain “Card Refund” for reversal
transactions.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 145 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.8 Screen ER8 Insert Card (Third attempt)
mi {Bin
I Card Insertion I Card Payment
I) (Customer has failed
I twice to insert the card in
Iithe RIN pad:
= : Cardiinserion
II Please give advice and
) ask customento reinsert
\ithe card) on touch Gance
I to cancel/the transaction:
This screen is what happens to screen ER7 if the customer has had 2 attempts at inserting his
card into the PIN pad but it cannot be read.
The tab heading at the right hand side of the screen will contain “Card Refund” for reversal
transactions.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 146 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.9 Screen ER9: Remove Card from PIN pad
[Prev [Bin linto
I Card In PIN Pad
‘
} Gardstilllin PIN) pad!
Please remind the
I customento remove card:
TlouchIOK to proceed:
This screen is returned at the end of a transaction if the card has been left in the PIN pad. At
the same time the PIN pad beeps to remind the customer to remove the card.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 147 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.10 Screen ER10: Application Selection from Counter
[Info, [Susp
ard Payment
CREDIMODEVISA
} I Gancel
It.
This screen is returned when the counter is invited to help the customer select the application.
5.1.11 Screen ER11: Signature CVM Selected
This screen has been removed as a separate screen. The information previously displayed on
this screen is now displayed as additional text within Screen 05 (EMV). See section 5.1.29.
5.1.12 Screen ER12: No CVM Selected
This screen has been removed as a separate screen. The information previously displayed on
this screen is now displayed as additional text within Screen 05 (EMV). See section 5.1.29.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 148 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.13 Screen ER13: Cancelled - Please Wait
f coon jome We : sr (> iP
} Aipaste uae ae } = iQ
[Serve Customer linto
Cancelle
I Transaction has been
) (cancelled:
Please wait: Cardiinsertion
This screen is shown when the transaction is cancelled by the clerk. The right hand panel will
show how far the transaction has progressed: in this particular example the cancel has
happened early on in the dialogue before the customer has inserted his card in the PIN pad.
Screen EB4 (see 7.1.2) is used where the transaction is cancelled by Customer.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 149 of 224
Without Prejudice and Subject to Contract
Fujitsu Services EMV Retail: User Interface Design Proposal Ref:
Version:
COMMERCIAL IN-CONFIDENCE Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21* April 2005
5.1.14 Screen ER14: PIN pad Error Screen
Biicme 7 ee (cael (a
I wom II G2
4 [Prev {Bin tinfo
I PIN Pad Error
I Anfermonhas been
}ireturned bythe’ PIN/pad!
Cardi blocked:
\ilihe transactionihas been I
} cancelled!
This screen is used if the PIN pad returns an error code at the end of an aborted transaction.
The content of the second sentence is determined by the response received from the PIN Pad
in the END command. A table of interpretations can be found in Annexe D.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 150 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.15 Screen ER15: Remove Card from PIN pad
I Card In PIN Pad
The card cannot be
I processedIby the PIN
foxetel,
Please ask the customer
I toinemove) the card and
I hand) itover tor swiping:
I fouch OK to proceed:
This screen is displayed in a recognised MSR fallback situation. The purpose is to inform the
clerk that the transaction cannot continue as an EMV transaction and must fallback to a swipe
and signature transaction. The card here is still in the PIN pad reader and must be removed
and handed to the clerk for further processing. At the same time the PIN pad beeps to remind
the customer to remove the card. The simultaneous PIN pad display will be EPB18.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 151 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.16 Screen ER16: PIN Entry - PIN Re-try(2 buttons)
Titome
[Susp
I Customer is fetrying PIN
I) Cininy
) Touch) Bypass if;
customer has forgotten
} ithe) PIN:
I >¢ PIN Entry,
I dlouch Gancelito cancel
I the transaction:
This screen is used when the clerk is able to select the bypass option. This is under reference
data control and when the reference data is switched off the clerk will be presented with
screen ER17 instead.
5.1.17 Screen ER17: PIN Entry - PIN Re-try (1 button)
This is the same as screen ER16 except that it has no Bypass button: it has a single Cancel
button in the left hand panel. Reference data determines whether screen ER16 or ER17 is
presented to the clerk.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 152 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.18 I Screen ER18: PIN Entry — Last Try(2 buttons)
I
Serve Customer
7
Inform the customerthat I }
I thisiis theimlast attempt I jor
} at: PIN Entry: I
ouch) Bypass if
}icustomen has forgotten
) the PINE
ouch’ Cancel toicancel
the transaction:
This screen is used when the clerk is able to select the bypass option. This is under reference
data control and when the reference data is switched off the clerk will be presented with
screen ER19 instead.
5.1.19 Screen ER19: PIN Entry — Last Try (1 button)
This is the same as screen ER18 except that it has no Bypass button: it has a single Cancel
button in the left hand panel. Reference data determines whether screen ER18 or ER19 is
presented to the clerk.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 153 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.20 Screen ER20: Partner Bank
Home
The cardiinjthe PIN padiis®
) a’Alliance & Eeicester
} card:
: . Card Inserted
When this transaction)
I has completed askjthe
customer -~Dolyou need I
i) any cash today
This screen is displayed when Horizon detects that the debit card being used for a settlement
operation may also be used for banking operations. The screen is presented after application
selection has taken place but before PIN entry occurs. The screen informs the clerk that the
customer’s card may also be used for banking transactions with the Post Office. The screen
has been introduced in response to CP3738. The %card scheme% parameter will be populated
by Horizon when it deduces the partner scheme. When the clerk has absorbed the information
they may resume by pressing the continue button. Processing resumes at PIN entry.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 154 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.21 Screen ER21: Card Inserted
info
Please) Wait
Cardinserted
Note this screen will only be displayed:
= When the EMV Retail button is selected from the settlement menu, and
= When the card has been inserted in the PIN pad
The tab heading at the right hand side of the screen will contain “Card Refund” for reversal
transactions.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 155 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.22 Screen ER22: Declined (Payment)
[Serve Customer Prev [nfo.
[Declined
I Mheltransaction has been
I declined:
I Advise}the customerito
}luselanjalternativie
I method of payment.
jouchIGontinueIto
I proceed:
If a refund is being processed the screen shown in 5.1.27 is used instead.
Action analysis performed by the PIN pad and card has detected a condition, which has caused
the transaction to be declined. This screen is displayed when the PIN pad has informed the
counter of this condition by sending an AAC command.
Pressing Continue will allow the counter to start a card removal operation. When the card has
been removed the settlement menu will be displayed again for a new method of payment to be
chosen.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 156 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.23, Screen ER23: Application Selected Screen
Please Wait i i
[CREDIMODEVISA
Application Selected
In a multiple application situation, a pause may occur; once the application has been selected
but before the PIN pad is ready for PIN entry. This screen has been added to the flow
diagrams to smooth the transition between screens and to prevent confusion. It will also allow
the clerk to cancel the transaction.
Pressing Cancel will cause an ACK( cancel ) command to be sent to the PIN pad aborting the
transaction.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 157 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.24 Screen ER24: Card Insertion Timeout
Prev [Bin info
Time Limit
IThe time permitted for
inseming the card has
beem exceeded!
Please swipe the card or
) touch Cancelito returnito I
) the Settlement menu:
This screen is displayed when the customer has not inserted their card into the PIN pad within
a configurable timeout period. If this occurs then magnetic stripe swipe operations will be
enabled for this card.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 158 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.25 Screen ER25: Transaction Authorised Remove Card Screen
} Transaction
The transaction has/ been)
) authorised!
Please remind the’
customer to remove the
card:
I ouch Continue’ to:
} complete the transaction: :
Continue
Action analysis performed by the PIN pad and card has reached approval for this transaction.
The transaction has therefore been approved. This screen is displayed after the PIN pad has
informed the counter of this condition by sending a TC command and the counter has
acknowledged that TC command. It is not displayed when the CVM is signature or when the
CVM is a combination CVM.
Pressing OK will allow the PIN pad to break out of its card removal loop and complete the
transaction.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 159 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.26 Screen ER26: Multiple Cards (Refund)
[Reversal / Refund
Mul iple Cards
) A card refund has
j already been madeiin
I this Session: Only one
I card refund is permitted
I Persession:
}
Cancel
This screen is displayed when the counter detects that a second or subsequent attempt is being
made to settle using a debit card. This is not necessarily the same card. The counter is set to
reject use of a second card.
This screen is used for refunds: if a payment is being processed the screen shown in 5.1.2 is
used instead.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 160 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.27. Screen ER27: Declined (Refund)
Tome f (G ey (7 es
[Reversal / Refund [Prev linfo
Mhe transaction has been)
I (declined:
I Advisetthe customernto
use analternativie
) method of payment:
I Touch Continue) to
proceed:
This screen is used for refunds: if a payment is being processed the screen shown in 5.1.22 is
used instead.
Action analysis performed by the PIN pad and card has detected a condition, which has caused
the transaction to be declined. This screen is displayed when the PIN pad has informed the
counter of this condition by sending an AAC command.
Pressing Continue will allow the counter to start a card removal operation. When the card has
been removed the settlement menu will be displayed again for a new method of payment to be
chosen.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 161 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.28 Screen ER28: Screen ER28: Application Selection
the customerto select/a
} icardiapplication:
I Ask customerto press
GLRifitheymeed I = Application Selection
assistance; or touch I
Cancel toicanceli/the
transaction:
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 162 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
5.1.29 Screen 5 (EMV): Waiting for Authorisation
For EMV transactions, Screen 5 will be a dual panel screen. The LH panel contains a reminder
to the Clerk that the card must remain in the PIN pad until after authorisation is complete.
Swiped transactions will continue to use the existing screen 5 format where the left hand panel
is not populated.
The content of the LH panel varies according to the verification method.
Pin Verification
The screen will look like this for normal PIN verification:
[info
i Card Payment
I leave the cardIinithe RIN o
pad until prompted:
Please wait forthe
transaction authorisation:
% WaitingIfor authorisation’)
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 163 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
Signature CVM
The screen will look like this for Signature CVM:
itil ig For Authorisa ion \
I Ask the customer to
I leave the! cardiin the RIN
pad Untill prompted:
I Youlwillineed to) verify the’ I
} cardholders signature:
I I I Signature Verification’
IIRleasejwait forthe "Waiting for authorisation
} transaction authorisation:
Combination CVMs
The screen will look like this for combination CVMs:
I Waiting For Authorisation Card Payment
I Askithe!customento:
I leave’ the! cardiin the PIN
I padjuntil prompted:
} Youjwill need to\verity the)
I cardholders signature: I
Please waitforthe == II II Signature Verification
} transaction auithorisation:I
Waiting forauthorisationI
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 164 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal _Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
No CVM
The screen will look like this for No CVM:
IW
lj
[Bin
orisation I Card Payment
I I ss
I Ask the customerto Hied
I leave the card inthe PIN
pad untili prompted:
I Youlwilllnotneedito
I verify the cardholder,
No) Verification
IIBlease)waitiforthe I Waiting for authorisation),
I transaction authorisation:
5.1.30 Counter Screens shared with EMV Banking
The following Counter screens for EMV Banking found in NB/PRP/004 are shared by the
EMV Retail application, and are attached in Annexe A:
Screen Number Particulars
EBI Proceed as Chip Card?
EB4 Transaction cancelled by Customer
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 165 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
5.2 EMV Specific PIN displays
PIN pad Messages for EMV fall into two categories:
e Those which contain the word ‘PIN’, ‘Pin’, ‘pin’, ‘pIn’, ‘PiN’ or ‘piN’. These are
messages used by the Hypercom software and cannot be customised.
© Other messages not related to PIN processing. These may be customized for specific
implementations but must not be changed to contain the word ‘PIN’, ‘Pin’, ‘pin’,
‘pln’, ‘PiN’ or ‘piN’. The messages may be changed by altering a reference data table.
The tables will be held as type C data and changes will be downloaded to the PIN pad
at the start of day they become effective.
5.2.1 PIN Pad Screen ERP 12a: Enter PIN
Li 2) 3) 4; 5I 6 7 8\ 90 2 2:3) 4,56
a £999999999.99R
2ENTER PIN hed Mil Mel Mal
Zand press ENT or
Apress CAN to end
The screen contents cannot be changed since it is a PIN message. R only appears after
amount for refunds. The PIN entry is right justified and the asterisk signs move to the right as
the customer enters an extra digit. If the customer enters more than 7 digits the asterisks are
written over the letters of the text ‘Enter PIN’. If the customer presses CLR to re-attempt PIN
entry the stored PIN will be reset but the PIN Pad display will remain as was at the end of the
previous attempt. A new PIN attempt will start overwriting again from column 16 of line 2.
Function Key Actions for this screen
Key When Pressed Action
ENT Before minimum I Ignore
digits of PIN
entered
ENT After minimum Accept PIN
digits of PIN
entered
CAN Before PIN is Transaction ends
accepted with no record of the
attempted transaction
being recorded
CAN After PIN is Ignored with no
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 166 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
accepted record of the
transaction attempt
being recorded
CLR Before PIN is Clears PIN
accepted
CLR After PIN is Ignored
accepted
BAL Any time Ignored
Up Arrow Any time Ignored
Down Arrow I Any time Ignored
5.2.2 PIN Pad Screen ERP12b: Re-enter PIN - First Retry
11/2; 3, 4'5 6I7' 8 90 12'3'4 5:6
ag £999999999.99R
2RE-ENTER PIN** * *
Zand press ENT or
Apress CAN to end
This screen may appear several times to allow several attempts to re-enter the PIN: the
number of appearances depends on a value set in reference data.
R only appears after amount for refunds.
The screen contents cannot be changed. The PIN entry is right justified and the asterisk signs
move to the right as the customer enters an extra digit. If the customer enters more than 5
digits the asterisks are written over the letters of the text ‘Reenter PIN’.
The Function Key Actions for this screen are the same as for PIN entry (see 5.2.1)
5.2.3 PIN Pad Screen ERP12c: Re-enter PIN - Last Retry
1 2\3 41:56 7'8,'9'0,12'3'415 6
£999999999.99R
2LAST PIN TRY*** *
Zand press ENT or
Apress CAN to end
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 167 of 224
Without Prejudice and Subject to Contract
Fujitsu Services EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
Version:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
This screen appears on the last allowed attempt to enter the PIN: if PIN entry fails on this try
then the card is locked.
R only appears after amount for refunds.
The screen contents cannot be changed. The PIN entry is right justified and the asterisk signs
move to the right as the customer enters an extra digit. If the customer enters more than 4
digits the asterisks are written over the letters of the text ‘LAST PIN TRY’.
The Function Key Actions for this screen are the same as for PIN entry (see 5.2.1).
5.2.4 PIN Pad Screen ERP2: PIN Blocked
1. 2I3:4.5 67 8'9'0'12'3) 4,5 6
PIN
eB wn e
BLOC KED
This screen cannot be customised. The transaction may or may not fail at this point: in some
instances an alternative CVM may be allowed.
Function Key Actions for this screen
Key When Pressed Action
ENT Any time Ignored
CAN Any time Ignored
CLR Any time Ignored
BAL Any time Ignored
Up Arrow Any time Ignored
Down Arrow I Any time Ignored
5.2.5 PIN Pad Screen ERP3: Incorrect PIN - Retry
112:3,4:5 6 7'8'9'0,'12 34156
ak INCORRECT
2PLEASE WAIT
3 TRY AGAIN
4
PIN
TO
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 168 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
This is Hypercom screen 21h: it cannot be customised.
The screen is displayed if the customer has entered an incorrect PIN and several outstanding
retries are allowed. The screen is displayed for a few seconds before being replaced by PIN
pad screen ERP12b. The text of this screen is centred. As the Hypercom documentation does
not show exact column positions this may be an approximation.
Function Key Actions for this screen
Key When Pressed =I Action
ENT Any time Ignored
CAN Any time Ignored
CLR Any time Ignored
BAL Any time Ignored
Up Arrow Any time Ignored
Down Arrow I Any time Ignored
5.2.6 PIN Pad Screen ERP4: Incorrect PIN — Last Retry
1, 2I3;4,°5 6 7'8'9'01' 12:3 45:6
1 INCORRECT PIN
LAST PIN
3 PLEASE WAIT TO
TRY AGAIN
This is Hypercom screen 22h: it cannot be customised.
The screen is displayed if the customer has entered an incorrect PIN but only one more retry is
allowed before the PIN is locked. The screen is displayed for a few seconds before being
replaced by PIN pad screen ERP12c. The text of this screen is centred. As the Hypercom
documentation does not show exact column positions this may be an approximation.
Function Key Actions for this screen
As for screen ERP3.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 169 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
5.3 PIN displays shared with EMV Banking
The following PIN pad screens for EMV Banking found in NB/PRP/004 are shared by the
EMV Retail application and are attached in Annexe A.
Screen Number
Particulars
EBPI
Welcome screen
EBP2 Please Insert Card
EBP3 Application Selection
EBPS5S Remove Card
EBP7 Cancelled — Remove Card
EBP9 Declined — Remove Card
EBP10 Approved — Remove Card
EBPI1 Processing
EBP13 Application selection at counter
EBP14 Remove & Re-insert Card (1)
EBP15 Re-insert Card (1)
EBP16 Remove & Re-insert Card (2)
EBP17 Re-insert Card (2)
EBP18 Remove & Hand card to clerk
EBP19 Hand card to clerk
EBP20 Cancelled
EBP21 Processing
EBP22 Application Blocked
EBP23 Card Blocked
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 170 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL '(ONFIDENCE Date: 21" April 2005
6.0 EMV specific Message texts
This section details only those texts, which are specific to EMV.
6.1 Message Collections
6.1.1 Collection: MessageDefs
The context in column 2 refers to the number defined for the screen in Section 7, Screen
Layouts or Section 8, Screens common to NB and Debit Cards.
Object Name"“/ Context Caption and Message’ Caption and Help Text
Variable
ScreenERI ERI Card Insertion
Ask the customer to insert their card in
the PIN pad.\Touch Cancel to cancel the
Cancel (F1)
Touch this button if the
customer does not wish to
continue.
ICON (cross )
MSG957 ER2 Multiple Cards Cancel (F1)
A card payment has already been made Touch this button to cancel
in this session.IIAdvise customer to use the transaction.
an alternative method of payment.
ICON ( cross )
MSG969 ER3 PIN Blocked Continue (Enter)
The PIN is blocked.IIAsk the customer Touch this button to
NOT to remove the card until prompted continue,
to do so.I[The customer may wish to
contact the card issuer.
ICON ( tick )
" Object names in collection MessageDefs are in the format MSGnnn. Where the object name is not in this
format, then other collections are used, e.g. FTScriptDefs,
'S A vertical bar ‘I’ symbol indicates the start of a new line and two vertical bars ‘II’ indicate a blank line.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 171 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
MSG963 ER4 PIN Entry Bypass (Enter)
Ask the customer toI- Enter PINI- Press — Touch this button to continue
ENTito confirm transactionIITouch using alternative verification.
Bypass if customer has forgotten the PIN
or Cancel if they decide not to proceed. Cancel (F1)
Touch this button if the
customer does not wish to
continue.
ICON (cross )
MSG962 ERS PIN Entry Cancel (F1)
Ask the customer toI - Enter PINI- Press Touch this button if the
ENTIto confirm transactionIITouch customer does not wish to
Cancel if the customer decides not to continue.
proceed.
ICON ( cross )
MSG959 ER6 Waiting For Swipe Cancel (F1)
The card cannot be processed by the PIN Touch this button if the
pad. IjPlease swipe the card or touch customer does not wish to
Cancel if the customer decides not to continue.
proceed.
ICON (cross )
MSG960 ER7 Card Insertion
Customer has made an unsuccessful
attempt to insert the card in the PIN
pad.IIPlease give advice and ask
customer to reinsert the card, or touch
Cancel to cancel the transaction.
Cancel (F1)
Touch this button if the
customer does not wish to
continue.
ICON (cross )
MSG971 ERS& Card Insertion Cancel (F1)
Customer has failed twice to insert the Touch this button if the
card in the PIN pad.II Please give advice customer does not wish to
and ask customer to reinsert the card, or —_ continue.
touch Cancel to cancel the transaction.
ICON (cross )
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 172 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00001933
FUJ00001933
Ref: NB/REQ/003
Version: 2.0
Date: 21" April 2005
MSG958 ERO Card In PIN Pad OK (Enter)
Card still in PIN pad.\IPlease remind the —_ Touch this button to
customer to remove card.I/Touch OK to continue.
proceed.
ICON( tick )
ScreenER10_ ERIO. Application Selection Left hand panel is a pick list
Option and and the Help text for each
ScreenER10_ option:
OptionsElement Touch this button to select
mn
(where ?????? is the option as
presented on the screen)
The option selection box in
the right hand panel has Help
text:
“Please select the required
application from the pick
list.”
ScreenER13 ERI3 Cancelled
Transaction has been cancelled. IIPlease
wait.
MSG981 ERI4 PIN Pad Error OK
An error has been returned by the PIN Touch this button to
pad. I/%reason% I{The transaction has continue.
been cancelled.
MSG972 ERIS Card In PIN Pad OK (F12)
The card cannot be processed by the PIN Touch this button to process
pad. IIPlease ask the customer to remove card swipe.
the card and hand it over for swiping.
\ITouch OK to proceed.
ICON (tick )
MSG973 ERI6 PIN Entry Bypass (Enter)
Customer is retrying PIN entry. IITouch
Bypass if customer has forgotten the
PIN. I{Touch Cancel to cancel the
transaction.
Touch this button to continue
using alternative verification
Cancel (F1)
Touch this button if the
customer does not wish to
continue.
ICON (cross )
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 173 of 224
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00001933
FUJ00001933
Ref: NB/REQ/003
Version: 2.0
Date: 21" April 2005
MSG974 ERI7 PIN Entry Cancel (F1)
Customer is retrying PIN entry. ITouch Touch this button if the
Cancel to cancel the transaction. customer does not wish to
continue.
ICON (cross )
MSG975 ERI8 PIN Entry Bypass (Enter)
Inform the customer that this is their last Touch this button to continue
attempt at PIN entry. [Touch Bypass if using alternative verification
customer has forgotten the PIN. Touch Ga ncgt (F1)
Cancel to cancel the transaction.
Touch this button if the
customer does not wish to
continue.
ICON (cross )
MSG976 ERI9 PIN Entry Cancel (F1)
Inform the customer that this is their last Touch this button if the
attempt at PIN entry. [Touch Cancel to customer does not wish to
cancel the transaction. continue.
ICON (cross )
MSG978 ER20 Partner Bank
The card in the PIN pad is a Ycard
scheme% card.IIWhen this transaction
has completed ask the customer -“Do you!
need any cash today?”
Yes (F9)
Touch this button if you
intend to ask the customer at
the end of the transaction.
ICON (tick )
No (F12)
Touch this button if you do
not intend to ask the
customer at the end of the
transaction.
ICON (cross )
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 174 of 224
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00001933
FUJ00001933
Ref: NB/REQ/003
Version: 2.0
Date: 21" April 2005
ScreenER1_!) ER21 Card Inserted
CardInserted
Cancel (F1)
Touch this button if the
customer does not wish to
continue.
MSG982 ER22 Declined
The transaction has been
declined.IIAdvise the customer to use an
alternative method of payment.I/Touch
Continue to proceed .
Continue (F9)
Touch this button to
continue.
ICON (tick )
ScreenEMVApplic — ER23 Application Selected Cancel
ationSelected Please Wait Touch this button ithe
customer does not wish to
continue.
MSG983 ER24 Time Limit Cancel (F1)
The time permitted for inserting the card Touch this button to return to
has been exceeded.IIPlease swipe the the Settlement menu.
card or touch Cancel to return to the
Settlement menu.
ICON (cross )
MSG988 ER2S Transaction Authorised Continue (Enter)
The transaction has been authorised. Touch this button to
IIPlease remind the customer to remove continue.
the card.I/Touch Continue to complete
the transaction.
ICON (tick )
MSG990 ER26 Multiple Cards Cancel (F1)
A card refund has already been made in Touch this button to cancel
this session. Only one card refund is. the transaction.
permitted per session.
ICON( cross)
MSG991 ER27 Declined Continue(F9)
The transaction has been
declined.I/Touch Continue to proceed.
Touch this button to
continue.
ICON( tick )
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 175 of 224
Fujitsu Services EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00001933
FUJ00001933
Ref: NB/REQ/003
Version: 2.0
Date: 21" April 2005
ScreenER28 ER28
MSG998 Screen 5
(EMV)
Note: MSG998 is
also used for screen
5 (EMV) in
Banking
Application Selection
The PIN pad is waiting for the customer
to select a card application.II Ask
customer to press CLR if they need
assistance, or touch Cancel to cancel the
transaction.
Waiting For Authorisation
Ask the customer to leave the card in the
PIN pad until prompted.II
°%CVMMESSAGE%
Please wait for the transaction
authorisation.
Where %CVMMESSAGE% is
For No CVM:
You will not need to verify the
cardholder.II
For Signature and combination CVM:
You will need to verify the cardholder’s
signature.II
Otherwise blank (i.e. for PIN only):
Cancel (F1)
Touch this button to cancel
the transaction.
ICON( cross )
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 176 of 224
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00001933
FUJ00001933
Ref: NB/REQ/003
Version: 2.0
Date: 21" April 2005
6.2 PIN pad messages
The following table shows the PIN messages associated with PIN entry and PIN blocking:
Screen PIN try status Message Change possible?
ERPI2a First Try £999999999.99R. Standard Hypercom
ENTER PIN ###* message. Messages
containing PIN are
and press ENT or not normally altered.
press CAN to end
ERP12b Retry £999999999.99R Standard Hypercom
RE-ENTER PIN**#* message. Messages
containing PIN are
and press ENT or not normally altered
press CAN to end
ERP12c Last retry £999999999.99R Standard Hypercom
LAST PIN TRY*##* message. Messages
containing PIN are
and press ENT or not normally altered
press CAN to end
ERP2 PIN locked. Customer I PIN BLOCKED Standard Hypercom
not allowed to enter message. Messages
PIN. Transaction may containing PIN are
or may not be allowed not normally altered
to continue
Note: non PIN related messages can be altered by Fujitsu Services by altering a reference data
table. The tables will be held as type C data and changes will be downloaded to the PIN pad
at the start of day they become effective
© 2004 Fujitsu Services
Without Prejudice and Subject to Contract
COMMERCIAL IN-CONFIDENCE
Page: 177 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
6.3 Audio Cues at PIN Pad
The PIN pad will provide distinct audio cues to the Customer for key entries made at the PIN
pad and also at the time of insertion or removal of the Card from the PIN pad.
The Post Office requirements for audio cues are documented in CD/CDE/009 Conceptual
Design for DDA Beeps, and the Fujitsu Services response in AS/DPR/008 Design Proposal
for DDA - PIN Entry Device Audio System. The following will be used for EMV:
PIN Pad Event Signal
Insertion of Card Single beep, 2kHz for 100ms
Card to be removed Beep, 1kHz for 100ms: followed by 100 ms silence and
repeat. Unattended this will continue for a configurable
period (15 seconds) (determined by reference data):
however, the clerk will receive a screen prompt at the same
time on screen ER9 or ER25 which he can acknowledge to
move the transaction along. This also has the side affect of
switching the beeping off — CP 3648).
Customer presses “Enter” Single beep, 2kHz for 600ms
Customer presses “Cancel” 1kHz for 100ms: followed by 100 ms silence and repeated 8
more times
Customer presses “Clear” 1kHz for 100ms: followed by 100 ms silence and repeated 2
more times
Customer presses 0-9 Single beep, 2kHz for 100ms
Others No sound
6.4 Help Text for data selection and input
No change from NB/SPE/013
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 178 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
7.0 Annexe A
7.1 Counter Screens Shared with EMV Banking
The following screens found in NB/PRP/004 will also be used for EMV Retail. The screen
layouts are repeated here for information purposes only: they may require to be changed for
EMV Banking after the document for EMV Retail is baselined. The screen layouts defined in
NB/PRP/004 take precedence over those shown below:
7.1.1 Screen EB1: Proceed as Chip Card?
[Desktop Into [susp
} Chip Card
I Thisiis aichip card.
} Return the card/to the
I customerto insert in) RIN
I pad and touch Gontinue.
I (Otherwise touch Cancel
I tovcancelIthe transaction: I
{Continue
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 179 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
712 Screen EB4: Transaction cancelled by Customer
4 ti Del (78
(Prev (Bin Hinfo. (Susp.
I Cancelled
) the transaction has been}
I ‘cancelled! by the
) customer,
This screen is displayed if the customer pushes the Cancel button on the PIN pad or removes
the card before the [R] message is sent to the Merchant Acquirer.
If the customer removes the card between the time that the [R] message is sent and the [A]
message is received at the PIN pad then the message is changed to “The transaction has been
cancelled by the customer removing the card too soon.”
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 180 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
7.2. PIN Pad Screens shared with EMV Banking
The following screens found in NB/PRP/004 are used for EMV Retail. The text on these
screens are for purpose of illustration and can be changed if required.
7.21 PIN Pad Screen EBP1: Welcome Screen
1) 2I3:'4 5'6:7' 8 9'0,1 2'3'4°5'6
es WN PB
This is Hypercom screen 0Ch customised to meet Post Office requirements. It is intentionally
blank.
Key When Pressed Action
ENT Any time Ignored
CAN Any time Ignored
CLR Any time Ignored
BAL Any time Ignored
Up Arrow Any time Ignored
Down Arrow I Any time Ignored
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 181 of 224
Without Prejudice and Subject to Contract
Fujitsu Services EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
Version:
Ref:
Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
7.2.2 PIN Pad Screen EBP2: Please Insert Card
1/2; 34 5 6 7 8 9 0/1; 2,3) 45,6
1PLEASE
2INSERT
=
4
CARD
This is Hypercom screen 1Bh with line 1 customised to meet Post Office requirements.
Key When Pressed Action
ENT Any time Ignored
CAN Any time Ignored
CLR Any time Ignored
BAL Any time Ignored
Up Arrow Any time Ignored
Down Arrow I Any time Ignored
7.23 PIN Pad Screen EBP3: Application Selection PIN pad
1234567890123456
Appl
Appl
Appl
eB wn eR
Scro
i
i
i
1
catio
catio
catio
1 to
nil
n2
n3
select
Function Key Actions for this screen
Key ‘When Pressed Action
ENT Any time Accept ‘flashing’
application
CAN Any time Transaction Ends
CLR Any time Switches application
selection to Counter
BAL Any time Ignored
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 182 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Up Arrow Any time Selects application
above the currently
‘flashing’ application,
if available. Selected
application flashes
Down Arrow I Any time Selects application
below the currently
‘flashing’ application,
if available. Selected
application flashes.
NOTE:
1. The PIN pad must undertake application selection by AID and partial AID.
2. Ifrequired by ICC setting a list of available applications — identified by
Application label — should be displayed on the PIN pad for selection by the
cardholder.
See screen PIN pad EBP13 and counter screen EB7 for application selection from Counter
7.2.4 PIN Pad Screen EBP4: Card Invalid
Removed.
7.25 PIN Pad Screen EBP5: Remove Card
1234567890123 456
1
2
3 PLEASE
4REMOVE CARD
This is Hypercom screen 08h customised to meet Post Office requirements'®.
Key When Pressed Action
ENT Any time Ignored
CAN Any time Ignored
‘© The text for this screen is supplied by Fujitsu as part of the PIN pad reference data. It is not explicitly
referenced within the activity flows described within this document, but it may be displayed under certain
exception cases.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 183 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref; NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
CLR Any time Ignored
BAL Any time Ignored
Up Arrow Any time Ignored
Down Arrow I Any time Ignored
7.2.6 PIN Pad Screen EBP7: Cancelled - Remove Card
12:3 45,6 7/8 9 0 1 2 3' 45,6
1CANCELLED
2
3PLEASE
4A4REMOVE CARD
This is Hypercom screen 26h customised to meet Post Office requirements.
The same screen is used whether the transaction is cancelled by the clerk or by the customer
and is displayed when the card is still in the PIN pad.
Screen EBP20 (section 7.2.19) is also a cancel screen which is displayed when the card is not
present in the PIN pad.
Function Key Actions for this screen
Key When Pressed I Action
ENT Any time Ignored
CAN Any time Ignored
CLR Any time Ignored
BAL Any time Ignored
Up Arrow Any time Ignored
Down Arrow Any time Ignored
7.2.7 PIN Pad Screen EBP8: Return Card?
Removed.
7.28 PIN Pad Screen EBP9: Declined —- Remove Card
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 184 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
1, 2)3,4 5) 6 7 8 9, 0/4) 2) 3; 4:56
ITDECLINED
2
3 PLEASE
4REMOVE CARD
This is Hypercom screen 04h customised to meet Post Office requirements.
Key When Pressed Action
ENT Any time Ignored
CAN Any time Ignored
CLR Any time Ignored
BAL Any time Ignored
Up Arrow Any time Ignored
Down Arrow I Any time Ignored
7.29 PIN Pad Screen EBP10: Approved — Remove Card
12:3.4.5678901'2:3'4 56
1LAPPROVED
2
3 PLEASE
4REMOVE CARD
This is Hypercom screen 23h customised to meet Post Office requirements.
Function Key Actions for this screen
Key When Pressed I Action
ENT Any time Ignored
CAN Any time Ignored
CLR Any time Ignored
BAL Any time Ignored
Up Arrow Any time Ignored
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 185 of 224
Without Prejudice and Subject to Contract
Fujitsu Services EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
Ref:
FUJ00001933
FUJ00001933
NB/REQ/003
Version: 2.0
Date:
21" April 2005
Down Arrow
Any time
Ignored
7.2.10 PIN Pad Screen EBP11: Processing
1)-2) 3) 4) 5) 6 7) 8 9) 0. 1) 2:3) 415 6
1TPROCESSING
2PLEASE
é}
4
WAIT
This is Hypercom screen 06h customised to meet Post Office requirements. The screen will be
displayed in various scenarios when the PIN pad is busy or waiting for a response from the
counter. Examples are following card insertion and whilst waiting for online authorisation.
The details of all cases where this screen can be displayed are omitted from the detailed
flowcharts in section 2.
Key When Pressed Action
ENT Any time Ignored
CAN Any time Ignored
CLR Any time Ignored
BAL Any time Ignored
Up Arrow Any time Ignored
Down Arrow I Any time Ignored
7.2.11 PIN Pad Screen EBP12: Enter PIN
Removed. Now appears in section 5.2
7.2.12 PIN Pad Screen EBP13: Application Selection at Counter
1). 2) 3) 4) 5) 6; 7) 8/9: 01 1:2) 3) 4) 5) 6
1TSELECTING
2APPLICATION
3 FOR
4
This is Hypercom screen 15h: (not customised).
PAYMENT
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 186 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
Function Key Actions for this screen
Key When Pressed Action
ENT Any time Ignored
CAN Any time Transaction Ends
CLR Any time Ignored
BAL Any time Ignored
Up Arrow Any time Ignored
Down Arrow I Any time Ignored
7.2.13 PIN Pad Screen EBP14: Remove & Re-insert Card (1)
12.3'4:5 6:78) 9:'0'12°3'4'5 6
TREMOVE AND
2RE-INSERT CHIP
3 CARD
4
This screen appears if the customer enters his card wrongly into the PIN pad in response to
the Insert card request in EBP1: e.g. if it were inserted upside down or back to front.
This is Hypercom screen 27h customised to meet Post Office requirements.
Function Key Actions for this screen
As for insert card EBP 1 (section 7.2.1)
7.2.14 PIN Pad Screen EBP15: Re-insert Card (1)
1,2,3/4.5.67°8'9 0:12 3:45
A
2RE-INSERT CHIP
3 CARD
4
This screen appears on first on the first attempt to re-enter the card into the PIN pad after the
first attempt fails: e.g. if it were inserted upside down or back to front.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 187 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
This is Hypercom screen 28h customised to meet Post Office requirements.
Function Key Actions for this screen
As for insert card EBP 1 (section 7.2.1)
7.215 PIN Pad Screen EBP16: Remove & Re-insert Card (2)
1234567890123456
LTREMOVE AND
2RE-INSERT CARD
3 SEE PICTURE NEAR
4cARD ENTRANCE
This screen appears if the customer enters his card wrongly twice into the PIN pad.
This is Hypercom screen 29h customised to meet Post Office requirements.
Function Key Actions for this screen
As for insert card EBP 1 (section 7.2.1)
7.2.16 PIN Pad Screen EBP17: Re-insert Card (2)
1) 2)3'4 5:6 7:8 9'0 12; 3\ 45° 6
d
2RE-INSERT CARD
3SEE PICTURE NEAR
4CARD ENTRANCE
This screen appears on first on the second attempt to re-enter the card into the PIN pad after
the first two attempts have failed.
This is Hypercom screen 2Ah customised to meet Post Office requirements.
Function Key Actions for this screen
As for insert card EBP 1 (section 7.2.1)
7.2.17 PIN Pad Screen EBP18: Remove & Hand Card to Clerk
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 188 of 224
Without Prejudice and Subject to Contract
Fujitsu Services EMV Retail: User Interface Design Proposal Ref:
Version:
COMMERCIAL IN-CONFIDENCE Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
12:3':4.5.6 7.8910 12, 3\4,5 6
LREMOVE CARD AND
2HAND TO CLERK
Ss
4
This screen appears if the customer enters his card wrongly three times into the PIN pad.
Function Key Actions for this screen
As for insert card EBP1 (section 7.2.1)
7.2.18 PIN Pad Screen EBP19: Hand Card to Clerk
1,2I/3'4.5'6 7,8 9:0 12:3) 41/5 6
2HAND TO CLERK
This screen appears after the customer takes his card out of the PIN pad in response to the
EBP18 screen.
This is Hypercom screen 2Ch customised to meet Post Office requirements.
Function Key Actions for this screen
As for insert card EBP 1 (section 7.2.1)
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 189 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
7.2.19 PIN Pad Screen EBP20: Cancelled
1234567890123 456
I1CANCELLED
This is Hypercom screen ODh.
The same screen is used whether the transaction is cancelled by the clerk or by the customer
and is displayed when the card is not in the PIN pad.
Screen EBP7 (section 7.2.6) is also a cancel screen which is displayed when the card is present
in the PIN pad.
Function Key Actions for this screen
As for insert card EBP7 (section 7.2.6)
7.2.20 PIN Pad Screen EBP21: Processing
12I 3.4.5 67 8 9°01 2 3: 45 6
PROCESSING
e WN eR
Function Key Actions for this screen
Key When Pressed Action
ENT Any time Ignored
CAN Any time Ignored
CLR Any time Ignored
BAL Any time Ignored
Up Arrow Any time Ignored
Down Arrow I Any time Ignored
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 190 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
7.2.21. PIN Pad Screen EBP22: Application Blocked
1234567890123456
Application
Blocked
eB wn e
Function Key Actions for this screen
Key When Pressed Action
ENT Any time Ignored
CAN Any time Ignored
CLR Any time Ignored
BAL Any time Ignored
Up Arrow Any time Ignored
Down Arrow I Any time Ignored
7.2.22 PIN Pad Screen EBP23: Card Blocked
1234567890123456
Card Blocked
eB wn eB
Function Key Actions for this screen
Key When Pressed Action
ENT Any time Ignored
CAN Any time Ignored
CLR Any time Ignored
BAL Any time Ignored
Up Arrow Any time Ignored
Down Arrow I Any time Ignored
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 191 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
8.0 Annexe B
8.1 Screens for EMV Retail used from existing NBS
Applications
EMV Retail will also utilize the following screens found in NB/SPE/003 Network Banking
Counter Dialogue —Activity and Screen Flows. The screen layouts are repeated here for
information purposes only: future change controls may require the screens to be changed for
Network Banking after the document for EMV Retail is baselined. The screen layouts defined
in NB/SPE/003 take precedence over those shown below.
In the examples the tab heading on the top right hand side of the screen contains banking
terms such as “Cash Withdrawal”, “Withdraw Limit”, “Balance” etc. For EMV Retails these
will be replaced with retail terms such as “Card Payment” or “Card Reversal” as appropriate:
8.1.1 Screen 3: Waiting for PIN
Screen 3 no longer used: screen ER4 used instead
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 192 of 224
Without Prejudice and Subject to Contract
Fujitsu Services EMV Retail: User Interface Design Proposal Ref:
Version:
COMMERCIAL IN-CONFIDENCE Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21* April 2005
8.1.2 Screen 4 Card Checks
2
Card Checks Balance
= Check card numberon
thejcards the! same as
displayed:
= Check card for
Cardichecks
of fraudulent
eviden
tampering:
Note
= this screen is present to illustrate the contents of the LH panel only. The RH panel will
contain the transaction sequence from the transaction dialogue similar to other EMV
Retail screens.
= the first sentence in the left hand panel is the existing MSG829 and reads ‘Check card
number on the card (if available) is...' (the '(if available)’ was added in Oct 03 for
CP3429).
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
© 2004 Fujitsu Services
Page: 193 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
8.1.3 Screen 5: Waiting for Authorisation
This screen will still be used for MSR transactions: for EMV the screen ER29 Screen 5
(EMV): Waiting for Authorisation (see 5.1.29) will be used instead.
The Tab at the top of the RH panel will contain “Debit Card”. The “Card checks” item will
not appear.
[Serve ¢ z Bin Info
I Card Payment
Waitingifor authorisation I
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 194 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
8.1.4 Screen 7: Other Decline
Balance
been
contact their cand)issuer,
8.1.5 Screen 9: Card Retain
Decline Cash Withdrawal
I MranSaction has been
declined
Eollow the appropnate
procedureto retain the
card:
Advise the customento
contact their cand issuer.
Was the card retained?
Fa
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 195 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
8.1.6 Screen 10: Transaction Failure
This screen is used to report failed transactions. The message text which appears in the left
hand column depends on the response code as defined in
= NB/SPE/003 Network Banking Counter Dialogue — Activity & Screen Flows
= NB/SPE/013 Debit Card: Counter Dialogue — Activity and Screen Flows.
Withdraw Limit
Request unsuc
} retry the tran
oncelonly, then advise
the customer of
jlalternatives:
Rlease do not callithe
Horizon system HelpdesI
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 196 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
8.1.7 Screen 11: Office Receipt Printing
wo @
ein inc
Receipt Printing Card Refund
Tran tionjhasibeen
authonsed:
Please wait while the
Siprinted
8.1.8 Screen12: Tear off Error Message Instruction
CXiposte) is
Desktop int
Tear Off Cash Withdrawal
Tear off error reportiand ~
touch button to continu:
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 197 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
8.1.9 Screen13: Check Signature
Signature Checks Card Refund
I /Reque customers
Signature on office
receipt.
Has the receipt printed
correctly and does the
Signature match the
S ony the cardi?
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 198 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
8.1.10 Screen 14: Printing Receipt
The first part of the text is dependent on the transaction outcome. It may say "authorised" as
in the example below or “declined” if the transaction was declined.
int
Receipt Printing Card Payment
Tran tion has been
auithornsed:
Please wait whileithe
uStomens receipt is
printed
Retain office receipt.
Screen Variations
RH panel, last line may be AUTHORISED or DECLINED
The LH Panel may contain :
e Transaction has been declined. Please wait while the customer’s receipt is printed.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 199 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
8.1.11 Screen 19: Cancel Message
PIN Entry Cancelled Cash Withdrawal
Customer has decided
hot.to enter the PIN:
This transaction/has
been cancelled:
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 200 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
8.1.12 Screen E1: Signature Receipt OK
(2
Card Refund
Signature Checks
Was the receipt printed
correctly?
8.1.13 Screen E2: Signature Check (2™ Receipt)
int
Signature Checks Card Payment
Request customers
Signature on office
receipt
Has the feceipt printed
correctly and does the
ignature match the
becimen on t! FC
COMMERCIAL IN-CONFIDENCE Page: 201 of 224
Without Prejudice and Subject to Contract
© 2004 Fujitsu Services
Fujitsu Services EMV Retail: User Interface Design Proposal Ref:
Version:
COMMERCIAL IN-CONFIDENCE Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21* April 2005
8.1.14 Screen E3: Signature Check (2™ attempt)
[bin [into Susp
I Signature Checks
Rleaselask customer to:
I fe-sign on reverse! of,
} receipt.
I Does second attempt I
} match specimenon) cardi}
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 202 of 224
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
8.1.15 Screen E4: Invalid Card
This screen will be used to display errors when validating the card as follows:
e The check digit(s) on the card are incorrect
e The start date indicates that card is not valid: please tell customer
e The supplied card has expired: please tell customer
e@ = The supplied card is not valid: please tell customer
Card Not Valid
The supplied cardihas
expired:
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 203 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
8.1.16 Screen E5: Signature Checks Failure Options
Signature Check Card Payment
I Signature Fail
No Customer Signature Pleaseichooseinext
action or supply reason
Reprint I for failure
Option
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 204 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
8.1.17 Screen E6: Print Preview
This screen shot provided for background information only and is not necessarily
representative of the user interface for Print Preview screens. The style used for this screen
will be the same as for EPOSS — indeed the same display technology will be used.
For Debit Card Transactions the receipt will be as described in Section 5
"Cash Withdrawals” will be replaced with “Payment” or “Refund”.
For a Card Refund transaction “Please debit my account as shown” will be replaced with
“Please credit my account as shown".
Ty tna
tom
Post Office Ita.
CAP:16 BP:O1 SU:SUL
FaD: 9017777
DUPLICATE
#8 Office Copy ~ Retain **
This is not a VAT receipt
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 205 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
8.1.18 I Screen E7: Error Message
[De sktop
I System Failure
On-lineiservices
Unavailable; advise
I (customer of/altermatives:
lffaccallihas not already,
been logged; contact'the I
I Horizom System) Helpdesk?)
} by,calling the NBSG andI
I quote’ code shown below: I
8.1.19 Screen E8: Error Message
Cash Withdrawal
sstul:
advise customer of
altermatives:
allhhas not already,
beenjlogged) contact the
Horizon system Helpdesk
by/callingithe NBSC and
quote code shown below. I
AT.
ce
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 206 of 224
Without Prejudice and Subject to Contract
Fujitsu Services EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00001933
FUJ00001933
Ref: NB/REQ/003
Version: 2.0
Date: 21* April 2005
8.1.20 Screen E9: Error Message
Desktop nt
Cash Withdrawal
Invalid Amount
The value entered
(£320!00)iis ou
allowedirange:
Amount
Value must be between
£5:'00 andi£200.00!
8.1.21 Screen E10: Error Message
Desktop int
Invalid Amount Cash Withdrawal
The value entered
(£47.00) 1s invalid:
Only multiples of £5:00
icted:
Amount:
may be tric
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE
Page: 207 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
8.1.22 Screen E11 — No Services Available
This screen will be displayed in the following circumstances :
= The card is an ICC card which has been inserted in the PIN pad but reference data
does not allow ICC as a valid method of card entry for the scheme to which the
selected application belongs
= The card is an ICC card and has been read in fallback mode by the magnetic stripe
reader but reference data does not allow fallback magnetic stripe entry as a valid
method of card entry for the scheme to which the card belongs
= The card is not an ICC card and has been read by the magnetic stripe reader but
reference data does not allow magnetic stripe entry as a valid method of card entry for
the scheme to which the card belongs
= The counter has not had a PIN pad installed but all transactions require one. In this
case the text “without a PIN pad” will be appended.
= The card was entered manually but no transactions are available when manually
entered. If there would have been at least one transaction available had the card been
successfully swiped the text “when manually entered” will be appended.
Note: This screen will have a single panel if the transaction started from a card swipe and two
panels if it started from manual input.
lo Services Available
) No transactions are
) available tor this card)
whenimanuallyentered:
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 208 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
8.2 Screens for EMV Retail used from existing DCS
Applications
The following screens found in NB/SPE/013 are used for EMV Retail:
8.2.1 Screen D1: Amount Capture
Amount Card Payment
Session total 13:00
Max: Amount 1/12:60
Amount
For Retail Card payments the Amount is captured before the card is read so Card Number and
Scheme will not appear in the right hand panel.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 209 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
8.2.2 Screen D2: Error Message
amountentered
S greater than.
the maximum) permitted
Session total 13700
The value may not
10 Maxi Amount 30°00
Amount
8.2.3 Screen D5: Nothing to Settle
Card Payment
Theres nothing tt
be settlediwith this
method of:payment
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 210 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21* April 2005
8.2.4 Screen D6: Error Message
Invalid Amount Card Payment
No valle has been
specified:
The value must be
a 0)
greater than)zero ontotal eos
Max: Amount 90:00
Amount
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 211 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
9.0 Annexe C
9.1. PIN Pad Commands
The flow diagrams in section 2 make many references to PIN Pad application commands
either flowing from the counter to the PIN pad or from the PIN Pad to the counter. Their
purpose is to keep the counter informed of the progress of the transaction and to give it the
opportunity to alter the direction of the transaction in defined ways. Whilst the counter is
responsible for starting the transaction, the PIN pad application and the customer’s card , once
the transaction has started, are in complete control. The PIN pad application dialogue is in
essence a framework upon which the counter dialogues are hung. The following table of PIN
pad application commands is provided not as a complete description of those commands but
as a guide to assist the reader in interpreting the flow diagrams. There is no attempt here to
describe the data passed on these commands unless it is essential to explain the meaning. The
description of the commands is also constrained to the context of a financial transaction, i.e.
not administrative transactions( not data loading etc. ).
Command I From To Purpose
Counter I Counter
AAC Y To inform to the counter that the transaction has been
declined. It carries the AAC cryptogram.
ACK Y Multiple purposes, to inform the PIN pad that the counter
has received a command which requires confirmation. Also
to determine a course of action at a defined decision point.
e.g. PIN bypass.
ARQ Y To inform the counter that online authorization is required.
This command passes EMV tag data for the authorization
request. The counter solicits further tag data in TLV format
where that data is required.
DSP Y To carry status and information to the counter. It is a
command which requires acknowledgement. An example of
its us is to carry the Application Label to the counter after
application selection has been performed.
EFT Y To start the EFT transaction. It requires the transaction type
and amount.
END Y To signal the end of the transaction. This may contain error
information where a transaction has failed.
KBD Y Similar to the DSP this command carries data to the PIN
pad. It has a different shape depending on the context of its
use. It requires acknowledgement.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 212 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
STA 1 Y To inform the counter that card insertion is required.
STA 2 Y To inform the counter that an ICC card has been inserted
and read successfully.
STA 6 Y To inform the counter that the transaction has been
cancelled, either by the customer or by the PIN pad.
STA7 Y To inform the counter that card removal has been requested
at the PIN pad.
STA 8 Y To inform the counter that a card read error has been
detected.
STA9 Y To inform the counter that fallback to MSR is required.
STAD Y To inform the counter that the card removal timer has
expired and the PIN pad is moving on to the next event in
the process.
TC Y To inform the counter that the transaction has received
authorization from the merchant acquirer and card. The
command also carries the Transaction Cryptogram. It
requires acknowledgement.
TDR Y To convey the EMV tag data requested ina TLV command
to the counter.
TLV Y To solicit EMV tag data from the PIN pad. TLV/TDR
dialogues are issued when the PIN pad is expecting an
acknowledgment this can cause confusion as a following
acknowledgement may seem to be made to the TDR. In
such situations the acknowledgement is made to the
command which preceded the TLV command.
VFY Y Informs the counter of the outcome of CVM processing. It
requires acknowledgement.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 213 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
EMV Retail: User Interface Design Proposal Ref:
Version:
COMMERCIAL IN-CONFIDENCE Date:
FUJ00001933
FUJ00001933
NB/REQ/003
2.0
21" April 2005
10.0 Annexe D
10.1 PIN Pad error messages and Screen ER14 clerk messages
The following table shows the Hypercom error messages with equivalent messages for clerk
consumption. The clerk messages will be displayed on the ER14 clerk screen. The intent is to
display an error message when PIN pad failures occur but to tailor the message in such a way
that both clerk and customer will not be too confused by the verbosity of the originals. It is
also important that the messages do not convey the wrong meaning or alarm the customer.
Following the display of such messages the system will also log information events to the
event log.
Error I Clerk Message Description Severity
Code ‘
00001 I System error. Communication error E
ERR_COMMUNICATION
00002 I System error. Timeout E
ERR_TIMEOUT
00003 I System error. LRC error E
ERR_LRC
00004 I System error. Parity error E
ERR_PARITY
00005 I System error. Buffer overflow E
ERR_BUFFER_OVERFLOW
00010 I System error. Message code not implemented E
ERR_NOT_IMPLEMENTED
00016 I System error. Data format error E
ERR_FORMAT
00022 I System error. Wrong prefix code E
ERR_PREFIX_CODE
00023 I System error. STAN out of range E
ERR_OUT_OF_
RANGE_STAN
00025 I System error. STAN out of sequence E
ERR_INVALID_STAN
00026 I System error. Remove card, check signature E
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 214 of 224
Fujitsu Services
EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
REMOVE_CARD_CHECK_SIG
00027 I System error. Wrong date/time E
ERR_TIME_DATE_ERROR
00028 I System error. Timer length error E
ERR_TIMER_LENGTHS
00030 I System error. Date error E
ERR_DAY_RANGE
00031 I System error. Hour error E
ERR_HOUR_RANGE
00032 I System error. Minute error E
ERR_MIN_RANGE
00033 I System error. Second error E
ERR_SEC_RANGE
00034 I System error. Invalid length E
ERR_LENGTH
00037 I System error. Other error E
ERR_NOT_OK
00038 I Card error Card not supported.
ERR_CRD_NOT_SUPPORTED
00039 I Operation cancelled. Cancelled
ERR_CANCELLED
00040 I System error. POS device ID incorrect E
ERR_DEV_ID
00041 I System error. STAN error E
ERR_STAN
00042 I System error. Application not supported E
ERR_APP_NOT_PRESENT
00043 I Card error Start sentinel, end sentinel or LRC is
incorrect
ERR_TRACK
00044 I Card error Luhn check digit in last position of the
PAN
ERR_PAN_LUHN
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Page: 215 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933
Fujitsu Services
EMV Retail: User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00001933
FUJ00001933
Ref: NB/REQ/003
Version: 2.0
Date: 21" April 2005
00045 I Card error International Identification Number
(IEN) invalid
ERR_NO_IIN
00046 I Card error PAN length invalid
ERR_PAN_LENGTH
00047 I Card error Start date error
ERR_DATE_START
00048 I Card error Date validity or expired
ERR_DATE_EXPY
00049 I Card error Issue number length invalid
ERR_ISSUE
00050 I Card error Hot card match is found
ERR_HCF
00051 I Card error Service code validation error
ERR_SCDE
00052 I Card error Service code indicates reject
ERR_SCDE_REJECT
00053 I Card error If purchase with cashback
SCDE_NO_CASHBACK
00054 I Card error Transaction type rejected for this terminal
ERR_TXN_TYPE_TERM
00055 I Card error Transaction type rejected for this IIN
ERR_TXN_TYPE_IIN
00056 I Card error PIN required
SCDE_PIN_REQUIRED
00057 I Card error Service code indicates chip should be read
SCDE_PROMPT_ICC
00058 I System error. problem with key data loaded into Public Key I E
ERR_VALIDATE_KEY_ERR
00059 I System error. Error writing data to tag store E
EMV_L2_ERROR
00060 I System error. Public key error E
ERR_PUBLIC_KEY
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 216 of 224
Fujitsu Services
COMMERCIAL IN-CONFIDENCE
EMV Retail: User Interface Design Proposal
FUJ00001933
FUJ00001933
Ref: NB/REQ/003
Version: 2.0
Date: 21" April 2005
05001 I Card error. The contents of Tag 5A (Application
PAN) does not match the PAN in Tag
57 (Track 2 Equivalent Data). The 2
tags should be contained in the data
section of the error message. This
means a bad card or bad chip data.
05049 I System error. Insufficient parameter data E
downloaded to the device - cannot
begin EFT
08001 I System error. System file error E
08002 I System error. EMV level not set to 1 or 2 E
08003 I System error. EMV library initialization error E
08004 I Transaction not allowed. No applications supported I
08005 I This is a swipe card. Magnetic stripe — fallback to MSR
(track data may be appended to error
code)
08006 I Operation cancelled. Customer cancelled/says no to
application selection
08007 I Time limit exceeded. Customer timeout
08008 I Card error. Select application error I
08009 I Invalid PIN. PIN error
08010 I Cardholder verification failure. Cardholder verification error
08011 I Card error. Select application returns non-EMV
08012 I Card error. Select application fails
08013 I Card error. Select application format
08014 I Transaction not allowed. No more applications available
08015 I This is a swipe card. Non EMV - fallback to MSR
08016 I Card not recognised. No issuer match I
08017 I System error. Write tag data to library error — tag E
data may be present after the error
code
08018 I Card blocked. ICC blocked
08019 I Card error. Mandatory data missing
08020 I Card error. Select application library returns bad
format
08021 I Card error. Authenticate data, encryption failure
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Page: 217 of 224
Without Prejudice and Subject to Contract
Fujitsu Services
COMMERCIAL IN-CONFIDENCE
EMV Retail: User Interface Design Proposal Ref:
Version: 2.0
Date:
NB/REQ/003
21" April 2005
FUJ00001933
FUJ00001933
08022 I Card error. Authenticate data, error
08023 I Cardholder verification failure. Cardholder verification, failure
08024 I Transaction not allowed. Transaction type, error E
08025 I System error. Read tag data error WwW
08026 I Cardholder verification failure. Verify at EPOS returned not OK.
08027 I System error. Validate transaction, error I
08028 I Transaction not allowed. Action analysis, failure I
08029 I Transaction not allowed. Action analysis, decline I
08030 I System error. DOL does not contain 9F37 WwW
08031 I System error. Terminal capabilities error (9F33) WwW
08032 I System error. Advice, error W
08033 I The transaction has been Card removed within EMV transaction
cancelled by the customer
removing the card too soon.'”
08034 I Transaction not allowed. Facilities Code for acquirer does not I
allow this transaction
08035 I Transaction not allowed. Facilities Code for card scheme does I
not allow this transaction
08036 I Cardholder verification failure. Refund attempted with bypass on PIN
entry — not successful
08037 I Operation cancelled. Refund attempted with cancel pressed
on keypad by customer
08038 I System error. Refund with PED failure during E
process
08039 I System error. DDOL Index error E
08040 I System error. TDOL Index error E
08041 I System error. Throw error on TC. NACK response I W
to TC, we send AAC
08042 I System error. Error setting ICC reader for EMV txn I E
08043 I System error. Error writing data to additional data E
tag store
08044 I System error. Throw error on RSA key load request I E
08045 I Transaction not allowed. Action analysis, failure 2 I
08046 I Transaction not allowed. Action analysis, failure 3 I
"’ For error code 08033 screen EB4 (see 7.1.2) is output instead of screen ER14 (see 5.1.14).
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 218 of 224
Fujitsu Services
COMMERCIAL IN-CONFIDENCE
EMV Retail: User Interface Design Proposal
Ref:
Version: 2.0
Date:
NB/REQ/003
21" April 2005
08047 I System error. ACK response error for KBD — data E
format not correct
08048 I Transaction no longer available. I Throw error: expired application
08049 I Transaction not yet available. Throw error: application not yet
effective
08050 I This error can occur if the Failure to complete online transaction I W
customer removes the card too (EMV Lvl 2 library cannot complete
soon, txn)
08051 I System error. If end of txn control = 31 or 33, and E
ACK response to KBD for check
signature is negative, then this error
code will appear in END msg.
08052 I System error. Throw error on VISA easy entry card I W
(Track2 equivalent data may be
appended to error code)
08053 I Maximum amount exceeded. Throw error on Terminal Ceiling Limit I I
in General parameter table.
08054 I Operation cancelled 1“ and 2™ instance of new online PIN
do not match
08055 I System error. Format error —Data structure or data E
format incorrect
08056 I System error. 69 85 returned in answer to External E
Authenticate
08057 I Application blocked. Application blocked
08058 I System error. Signature CVM required signature not I E
checked
08059 I Card error. Not accepted — service not allowed
indicated by card in 1st GenAc
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Without Prejudice and Subject to Contract
Page: 219 of 224
FUJ00001933
FUJ00001933
Fujitsu Services
EMV Retail: User Interface Design Proposal Ref: NB/REQ/003
Version: 2.0
COMMERCIAL IN-CONFIDENCE Date: 21" April 2005
11.0 Annexe E
11.1 PIN Pad Timeouts
These are the timeouts used by the PIN pad.
Event
Timeout
Outcome if Timeout Exceeded
Insertion of Card
30 seconds
Counter displays Screen ER24: Card Insertion
Timeout
PIN Entry
120'S seconds
Counter ceases to display the screen it is
currently displaying (i.e. screen ER4 / ERS /
ER16/ERI17/ER18/ ER19) and displays screen
EB4 Cancelled, instead
Card removal
15 seconds
The process for card removal timeout processing
is described in NB/REQ/003 in Figure 21:
Remove Card, and Figure 23: Approved Remove
Card
'* There is currently a restriction with the PIN pad that enforces an upper limit of 99 seconds on the setting of
the PIN Entry timeout value for EMV Retail. (See PCO110135)
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE Page: 220 of 224
Without Prejudice and Subject to Contract
FUJ00001933
FUJ00001933