Purpose of this form

wanderooswarrenAI and Robotics

Nov 21, 2013 (3 years and 11 months ago)

210 views




Mobile MasterCard

PayPass

Secure Element Registration Form v2.4



MOBILE MASTERCARD
PAYPASS
SECURE ELEMENT
REGISTRATION FORM v2.4

1

Purpose of this form

This form has been created to enable the registration and coordination of approval requests relating to
SWP UICC, SWP MicroSD and embedded secure elements complete
with optimised Operating Systems
that support Payment Applications and the Payment Applications themselves.


This form is made up of six sections:

1.

Registration Information

2.

Secu
re Element details (IC, OS, Payment Application)

3.

Payment Application capabilities

4.

Protocol Attributes

5.

Archite
cture Specific Attributes

6.

Additional Applications

MasterCard will advise on the correct method of filling in the forms if required.

About the registration process

The filename of your submitted registration form
must follow the following format:

For embedded SE:

SERForm_[SE Name]_[SE Version]_1.docx or .doc

For SWP UICC:

UICCRForm_[UICC Name]_[UICC Version]_1.docx or doc

For SWP MicroSD:

SWPSDRForm_[SD Name]_[SD Version]_1.docx or doc

It is recommended that the
filename contains the technical or commercial SE name specified in the registration form
along with the version. The number 1 at the end of the filename indicates first registration form submitted for this
SE. If subsequent registration forms need to be su
bmitted for the SE due to errors in the first submission or changes
of SE details, the number specified at the end of the filename should be incremented accordingly otherwise the
registration form will be rejected.

Please fill in each gray zone of the docu
ment. When entering information for a field, press “F1” to receive additional
help on how to complete the field. Use Tab key to navigate between fields.

The form will be reviewed by MasterCard and the result will be a registration of the submission comple
te with a
unique identifier and entry into the Mobile MasterCard database.

MasterCard will issue a Mobile Evaluation Plan Summary (MEPS) which defines the tests and evaluations that are
required for the registered

Secure Element

based on the information su
bmitted in this form.

A MEPS is typically issued within 5 business days after receiving the correct registration form.

These procedures supplement other written
MasterCard
policies and procedures that apply to this subject.
Accordingly, compliance with these procedures does not remove the obligation to comply with such other
MasterCard
policies and procedures.

Submitting the form


E
-
mail the completed form to:
mobilepartner@mastercard.com

and
cast@mastercard.com


Revision History

Please record changes made between different versions of the registration form



MOBILE MASTERCARD
PAYPASS
SECURE ELEMENT REGISTRATION FORM v2.4

2


Date

Version

Author

Com
ments


























































































































Registration Information

Fields in
Red

are Mandatory. Fields in
Blue

are Conditional depending on the product type.

Submitting entity details

A.1

Company Legal Name







A.2

Company Address (including ZIP/Postal code)







A.3

Contact name







A.4

Contact Email Address







A.5

Contact Telephone Number







Submission Details

A.6

Submission date

(mm
-
dd
-
yyyy)







A.7.1

Registration Type

(Indicate if LoA is

purpose of the registration or not)


Formal Type Approval (LoA)


Formal Selective Testing for Trial/Pilot (Waiver)


Renewal of LoA


End of Life LoA

A.7.2

Public or Private product
.

(
If approved
,

Public products will be listed on
MasterCard’s web site.
)



A.8

Product Architecture Submitted



A.8.1

If
SWP
UICC Form
factors for which approval is
sought


mini
-
SIM (2FF)


micro
-
SIM (3FF)


nano
-
SIM (4
FF)

A.9

Is this p
roduct a variant of a previously
registered/approved product due to hardware or


(If yes please complete A.9.1


A.9.2)



MOBILE MASTERCARD
PAYPASS
SECURE ELEMENT REGISTRATION FORM v2.4

3


software changes?

A.9.1

Registration

number of previously
registered/approved product







A.9.2

Brief description of hardware/software differences

(Additional information can be supplied in a
separate document

e.g. architecture document
showing the changes
)







Product Summary

A.10

Product Manufacturer Name if different from
Company Legal Name (A.1)







A.11

Product Technical Name and Version.

Note : Thi
s must be unique for each product update

Name






Ver.






A.12

Product Commercial Name and Version

Name







Ver.






A
.
13

OS Type



A.14

Operating System (OS) Technical Name and
Version

Name






Ver.






A.15

Global Platform :
Product Reference with Version
Number

Name






Version






A.16

Payment Application Name and Version

Name






Ver.






A.17

Application Specification Type




A.18

Manufacturing Facility Name and Location







A.19

Is the chip used inside this product licensed by
Cryptography Research Inc. (CRI) under CRI's patent
portfolio related to differential power analysis (DPA) and
related external monitoring

attacks?



C
AST Evaluation Details (Supply A
.2
1 and A
.2
2 (for
pre
-
existing CAST) or A
.2
1 & A
.2
3~A.28
(for CAST
Registration) )

A
.2
0

CAST status


I have a pre
-
existing CAST


I need to register a new CAST

A
.
21

Product Name and Version used for CAST
registration

Name






Ver






A
.2
2

CAST Mobile Payment Certificate Number (MPCN)







A
.2
3

Evaluation Laboratory









MOBILE MASTERCARD
PAYPASS
SECURE ELEMENT REGISTRATION FORM v2.4

4


A
.
24

Report Number







A
.
25

Contact Name







A
.
26

Telephone







A
.
27

Anticipated date for report submittal to Lab (mm
-
dd
-
yyyy)







A
.
28

User Guidance Details.

Document description & Unique References(s)









MOBILE MASTERCARD
PAYPASS
SECURE ELEMENT REGISTRATION FORM v2.4

5


Secure Element Details

IC Details

B.1

IC supplier Name







B.2

IC
Product Name and Version







B.3

IC
Manufacturing Facility (City and Country)







B.4

Product Name and Version used for EMVCo
approval







B.5

EMVCo IC Certificate Number (ICCN)







IC Technical Data (approximate values are acceptable)

B.6

ROM Size (KB)







B.7

RAM Size (KB)







B.8

EEPROM/Flash Size (KB)







B.9

CPU Type (8, 16 or 32 bit)



B.1
0

RSA Crypto co
-
processor present?



B.11

Default Power Setting
-

According to EMV20
00
-

Book1
-

Amendment 1 which class is the card
compliant with?



Secure Element Operating System Details

B.12

OS Vendor Name if different from Company Legal
Name (A.1)

(If
different please complete B.12.1


B.12.4)







B.12
.1

OS Vendor Address







B.12
.2

OS Vendor Contact Name







B.12
.3

OS Vendor Contact Email Address







B.12
.4

OS Vendor Contact Telephone Number







B.13

EMVCo P
latform Certificate status



B13.1

If PCN “Complete” please provide EMVCo Platform
Certificate Number (PCN)







B.14

Java
Card
API version



B.15

Global Platform
Specification

Version




B 15
.
1

Global Platform

Configuration

supported





MOBILE MASTERCARD
PAYPASS
SECURE ELEMENT REGISTRATION FORM v2.4

6


B.1
5
.
2

If GP v2.2, is Amendment A implemented?



B.1
5
.
3

If GP v2.2, is Amendment B implemented?



B.15.4

If GP v2.2, is Amendment C implemented?



B.15
.
5

If
Amd C =
“P
artially


please indicate features
supported


User Interaction Management

(CREL, CRS)



Contactless Protocol Management

Other:






B.1
5
.
6

If “No” please indicate if GP Adm. C CRS
Equivalent
feature is implemented.







B.1
5
.
7

If GP v2.2, is Amendment D implemented?



B.1
5
.
8

If GP v2.2, is Amendment E implemented?



B15.9

GP
Letter of Qualification
(LoQ) status



B15.10

If GP LoQ “Complete” please provide the
Letter of
Qualification

ref ( e.g. GP_QC_XXXX)







B.1
6

Comments







B.1
7

User EEPROM Size available (after OS loading)
(KB)







B.1
8

For MULTOS OS

AMD version:






B.19

Logical
Channel Supported by the application on
the
Secure Element?



B.19
.
1

Logical channel supported on
Management
Interface (ISO 7816 interface [UICC]/ Host
dialog [SE])?



(If yes please complete B.
19
.1.1


B
.19
.1.3
)

B.
19
.1.1

ISO 7816 MANAGE C
HANNEL command
where P2 is set
with the Logical Channel
number is supported



B.19
.1.2

ISO 7816 MANAGE
CHANNEL command
where P2 is set

to 0 and the UICC/SE
responds with the Logical Channel number
is supported



B.
19
.1.3

ISO 7816 SELECT command with the Class
byte

(bit 2
-
1)
indicating the Logical Channel
to open (without any previous Manage
Channel command) is supported



B
.19
.2

Logical channel supported on Payment
Interface (Contactless)?



(If yes please complete B
.19
.2.1


B
.19
.2.3
)

B.
19
.2
.1

ISO 7816 MANAGE CHANNEL

command
where P2 is set

with the Logical Channel
number is supported



B.
19
.2
.2

ISO 7816 MANAGE C
HANNEL command




MOBILE MASTERCARD
PAYPASS
SECURE ELEMENT REGISTRATION FORM v2.4

7


where P2 is set
to 0 and the UICC/SE
responds with the Logical Channel number
is supported

B.
19
.2.3

ISO 7816 SELECT command with the Class
byte

(bit 2
-
1)


indicating the Logical Channel
to open (without any previous Manage
Channel command) is supported



Payment Application

B.20

Payment Application Vendor Name if different from
Company Legal Name (A.1)

(If different please complete B.2
0
.1


B.2
0
.4)







B.2
0
.1

Application Vendor Address







B.2
0
.2

Application Vendor Contact Name







B.2
0
.3

Application Vendor Contact Email Address







B.2
0
.4

Application Vendor Contact Telephone
Number







B.2
1

Payment Application Code Location



B.2
2

What is the state of the payment application when
leaving the SE Manufacturing Facility site?



B.23

Application Footprint (before personalisation)







KB

B.2
4

Application Footprint (after personalisation)







KB



MOBILE MASTERCARD
PAYPASS
SECURE ELEMENT REGISTRATION FORM v2.4

8


Payment Application Capabilities

Application

Configuration and Capabilities

C.1

Is Multi
-
Instantiation supported



C.2

Are “Partial Select” and “Select Next” supported?



Application Data Sharing Capabilities

C.3

Is PIN sharing supported?



C.4

Is other EMV data sharing supported?



C.4.1

If yes, which data?







Application Session Key Capabilities

C.5

Session Key Derivation method supported



C.5.1

If ‘Other’ please specify







Application RSA Capabilities

C.6

Odd RSA Key length supported?



C.7

Maximum Certificate length supported for
Static Data
Authentication(
SDA
)







Bytes

C.8

Maximum Key length supported for
Combined
DDA/Generate AC (
CDA
)







Bytes

A dedicated card profile will be requested when odd RSA key length is supported (i.e. profile 1’ )

Application Offline PIN Management

C.9

Is Plain text Offline PIN supported?



A dedicated card profile will be requested when personalization of the reference PIN is optional (i.e. profile 10)

C.10

Is Enciphered Offline PIN supported?



(If yes please complete C.10.1


C.10
.2)

C.10
.1

Is the application able to manage a
dedicated RSA key for PIN encryption?



C.10
.2

Maximum RSA Key length supported for PIN
encryption?







Bytes

M/Chip 4 based Application Capabilities

C.11

Please provide us with the (or one)
Application File
Locator

(
AFL
)

that will be used for the test cards







Please select into this AFL a file and a record for which the maximum length (memory size reserved) is longer


MOBILE MASTERCARD
PAYPASS
SECURE ELEMENT REGISTRATION FORM v2.4

9


than the length used by your personalization.

C.12

Short File Identifier

(
SFI
)


if possible SFI 1







C.13

Record (if possible Record 1)







Mobile Mastercard
PayPass

M/Chip 4 Application Capabilities

C.14

Maximum Card Layout Description (CLD) length







C.15

For SWP UICC :
Is the

Low Power


mode
supported?



C.16

When log feature is not supported is it possible to have the following data object not present?

C.16
.1

SFI11



C.16
.2

Log Format



M/Chip 4 based Application & Mobile Mastercard
PayPass

M/Chip 4 Application Capabilities

C.17

Maximum record length supported (between 180 and
247 (decimal))







According to EMV an issuer may chose a record length up to 180. An M/Chip 4 application is then requested to
support such length.

C.18

Maximum number of entries (records) in the Log file

10 (Default value)

C.19

Maximum CDOL 1 Related Data Length
.

(CDOL =Card risk m
anagement Data Object List
)

53 (minimum value)

C.20

Please add any useful comments, for instance the
list of points
that have been previously discussed
with MasterCard







Personalization Capabilities

C.21

Does the application implement proprietary
Data
Group Identifiers (
DGIs
)
?



C.21
.1

Is the personalization of these proprietary
DGIs mandatory for the application to be
functional?



C
.
22

Does the application
require
a specific order for the

DGIs?



C.22.1

If a specific DGI order is require please supply the
ordering.









MOBILE MASTERCARD
PAYPASS
SECURE ELEMENT REGISTRATION FORM v2.4

10


Protocol Attributes

Contactless Interface

D.1

What is the contactless Communication Protocol
Specification version supported?



D.2

Contactless Protocol Type supported by the
Secure Element (i.e. ISO/IEC 14443 Type A or
Type B or both)



D.3

Frame Waiting time Integer (FWI) v
alue







(Must be < 14, Recommended Value 7)

D.4

Is
Card I
d
entifier (
CID
)

Supported?



D.5

Can the device operate with CID disabled?



D.6

Is
Node A
d
dress (
NAD
)

Supported?



D.7

Are
Frame Waiting Time (
FWT
)

Extension
Requests Used?



Type A Parameters

(See response to D.1
)

D.8

Answer To
reQ
uest
, t
ype A (
ATQA
)

value







D.9

Unique I
d
entifier (
UID
)

size (single
, double or
triple)



D.10

Select AcKnowledge (
SAK
)

value







D.11

Last

SAK for double and triple UID s
ize







D.12

Answer To Select (
ATS
)

value







D.13

Frame Size for proximity Card Integer (
FSCI
)

value







D.14

Start
-
up Frame Guard t
ime Integer (
SFGI
)

value







D.15

Historical Bytes value (if any)







D.16

Is chaining s
upported?



D.16
.
1

If Yes is Block Size Fixed?



Type B Parameters

(See response to D.1
)

D.17

Answer To
reQ
uest
, t
ype B (
ATQB
)

value







D.18

Application Data Field value







D.19

Max Frame Size value







D.20

Application Data Coding

(
ADC
)

value (2 bits)









MOBILE MASTERCARD
PAYPASS
SECURE ELEMENT REGISTRATION FORM v2.4

11


D.21

Is the
PICC selection command, Type B

(ATTRIB)
Response value defined in the UICC?



D.22

ATTRIB Response value (if defined in UICC)







D.23

HaLT command, Type B
(
HLTB
)

Response value







D.24

Higher Layer Command/Response Feature



(If yes please complete D.24.1


D.24
.
2)

D.24
.1

Specify command supported by Card?







D.24
.2

Specify response sent by Card?







D.25

Is chaining supported?



D.25
.1

If Yes is Block Size Fixed?



MIFARE parameters

D.26

Does the chip
support MIFARE?



D.27

Which MIFARE type is supported?






MOBILE MASTERCARD
PAYPASS
SECURE ELEMENT REGISTRATION FORM v2.4

12


Architecture Specific
Attributes

SWP Specific Information

(If A.8 = SWP UICC or SWP microSD)

E.1

Single
-
Wire Protocol(
SWP
)

Spec version (of ETSI TS
102.613)







E.2

Host Controller Interface(
HCI
)

Spec version (of ETSI
TS 102.622)







E.3

SWP Data Rates Supported







E.4

Supported
Java Specifiction Request(
JSRs
)


JSR 118

JSR 177


JSR 188

JSR 257

E.5

Contactless Protocol Type configurable in SE or
Payment Application(s) (i.e. ISO/IEC 14443 Type A
or Type B or both):



E.6

SWP
/HCI protocol verified with
GP SWP/HCI Test
Suite



UICC Specific Information

(If A.8 = SWP UICC)

E.7

Target Market/Operator







E.8

Is
Bearer Independent Protocol (
BIP
)

supported?



E.9

Is Smart Card Webserver supported?



Embedded Secure Element Information

(If A.8 = eSE)

E.10

Name and version of module containing NFC
controller and embedded secure element









MOBILE MASTERCARD
PAYPASS
SECURE ELEMENT REGISTRATION FORM TEMPLATE v2.4







13

Additional Applications

Additional Applications

F.1

Are there
payment related
applications available on this card other than the payment
application under test?



F.2

Can several EMV payment applications (the application that is submitted to the type
approval) be personalized on the card (multi
-
instantiation of Mobile MasterCard PayPass
M/Chip
applet for instance)?



F.3

Please list all configurations (combination of applications) you would like to market. For each
of them complementary tests may be run. The
test report will repeat this list







If "Yes" please fill the following table taking into account the following instruction:



Application Name:

The technical name of the application shall be provided here. It could be either a MasterCard application or a non
-
MasterCard application.



AID:

The Application Identifier shall be provided here. If the AIDs are not yet defined, the value to be entered is
a plausible value that will be used during the
approval session.



Short Description:

A brief description of the application shall be provided here.



Does this application share the PIN and/or other Data with M/Chip?



Does this application act as a filter?

-

A
n application is considered as a filter if it intercepts all incoming or outgoing commands (APDU or R
-
APDU) even if it just
forwards the command or (and) the response without modifying it (them).



Is this application a default application?

-

A default appli
cation is an application implicitly selected during the card initialization (power on). Such an application
may interfere during the EMV selection mechanism


Application Name

Application
Version

AID

Short Description

Selectable
over
contactless
interface?

Does this
application share
the PIN and/or
other Data with
M/Chip?

Does this
application act
as a filter

Is this
application a
default
application?

F.4
































F.5
































F.6
































F
.7
































F.8
































F.9
































F
.10
































F.11
































F.12
































F.13