Light Card Capabilities Form – User Guide - PayPass

belchertownshuffleΤεχνίτη Νοημοσύνη και Ρομποτική

21 Νοε 2013 (πριν από 3 χρόνια και 10 μήνες)

84 εμφανίσεις

Light CCF
User Guide


v1.10


July 4, 2011

©2010 MasterCard

Worldwide

Page
1
/
2



Light

Card Capabilities Form



User Guide

v1.
1
1



January, 2013

1.

Purpose of this document

As part of the
Vendor Product Approval
Process,
the Light Card Capabilities F
orm
aim
s

at

gather
ing

in a very
synthetic document the features
required to request a Letter of Approval
in case the product already passed the
Interface and Application Testing and the Compliance Assessment and Security Testing.


In other words, a Card Vendor must submit this form if it wants to request a Letter of Approval for a product that
already passed the aforementioned
steps
.


Th
is
Light
Card
Capabilities
Form (
Light
CCF)

shall be provided to MasterCard
in a
Microsoft Word

f
ormat only
at
:

chip_certification_chd@mastercard.com


T
his form does not require the Vendor to define the
value of the
parameters of the application

but we

warn the
Vendor that the parameters
shall
have the same values as the ones used to personalize the product for the Interface
and Application
Testing
during the initial approval. Therefore we consider that when providing the Light CCF the
Vendor acknowledges that the configuration of the prod
uct is
strictly identical to
the one used during the
initial
approval
. The parameters will still be checked during the CPV

session
.


This document will provide explanations over several fields of the
Light CCF
and
help the Vendors to fill it in.


2.

Product
Identification


Filename

of the Light CCF

The name of the product and the version of the Light CCF
(not the template version)
shall appear somehow into the
filename.

This version is very helpful to track the updates.

This version shall be incremented into
the filename for
each
update of the
Light CCF
.


A5. Product Technical Name and Version

This field provide
s

the name and the version that will be used to identify the product. Name and version have to be
unique. Therefore we will not accept name and version strictly identical to the ones of the father product.

When the name of the product is inspired
with
the
name of the father product we recommend adding into this field a
few characters identify
ing

the Vendor itself.


A6. Product Commercial Name and Version

There is no constraint about this field.


A6b. Product Name and Version used for CAST registration

The
value of this field must be the same

as the one that appears under the field ‘Master Product Name’ of the Cast
Certificate.


A8 vs.
A8b.

A8 defines the specification used for the development of the payment application while A8b defines how the product
will be used in the field.

E.g. a Vendor might want to get an M/Chip 4 LoA for a product based on an application developed
according to
the
PayPass



M/Chip 1.3.1 specification.


A28. Update History

A
ny updated

field shall be
indicated in field A28
. This
field
will be used to quickly track the changes

from one file
version to another.


A29. Integrated Circuit licensed by Cryptography Research Inc.

The checkbox in field A29 aims at confirming that the Integrated Circuit used in your product has been
licensed by
Cryptography Research Inc.



Light CCF
User Guide


v1.10


July 4, 2011

©2010 MasterCard

Worldwide

Page
2
/
2



3.

Product
Definition

A22. Registration Number of the father product

Registration Number of the product which passed the IAT and CAST.


4.

Technology Identifier

T1.
Product Type


This field defines the manufacturing
model used for the product




CT: Usual EMV Contact only
ID
-
1 card model




CL: Usual
PayPass



Mag Stripe Contactless only
ID
-
1 card model



DI1: Dual Interface
ID
-
1 card model
where the chip is embedded after card body manufacturing (currently
usual ID
-
1
product)



DI2: Dual Interface
ID
-
1 card model
where the chip is added to inlay before lamination


Suffixes ‘
-
DIS/C’ and ‘
-
DISP/U’ respectively refer to Connected and Unconnected Display Cards.



Components identification table




The following table shows
which lines have to be filled in according to the Product Type:




CT: lines ‘Chip’, ‘Module’, ‘Card Body’ and ‘Embedding’ have to be filled in



CL: lines ‘Chip’, ‘Module’, ‘Antenna’, ‘Inlay’ and ‘Lamination’ have to be filled in



DI1: lines ‘Chip’, ‘Module’,
‘Antenna’, ‘Card Body’ and ‘Embedding’ have to be filled in



DI2: lines ‘Chip’, ‘Module’, ‘Antenna’, ‘Inlay’ and ‘Lamination’ have to be filled in


Component Identification

CQM Label

CT

CL

DI1

DI2

Chip

IC

x

x

x

x

Module

ICM

x

x

x

x

Antenna

n/a


x

x

x

Inlay

PIL


x


x

Lamination

PIC


x


x

Card Body

CB

x


x


Embedding

ICC

x


x





Lines that do not have to be filled in must be cleared (
they shall not contain
any information).




Only the pertinent information
must be filled in
.
No
additional wording
sha
ll be
added
.




The default value into the ‘Label’ column refers to the CQM workshop involved and then is the first digit of the
label to fill in.




‘Supplier’: We request the name of the company performing the manufacturing, not the name of a company
that
would request the manufacturing




‘Production Site (City / Country)’: We request to fill in only the name of the city and the country where the
manufacturing facility is. E.g.: ‘Waterloo / Belgium’




‘Component (Name / Version)’:
W
e request the version number of the component as well when available.
We
always require the Revision of the chip.


T26. Antenna size for ID
-
1 products

A MasterCard product supports 4 lines of embossing. Therefore with regular technologies a full antenna al
lows 3
lines of embossing while a half antenna allows 4 lines.