Visa VCBP Card Personalization Data

This document describes card data that Issuers need to prepare to personalize Visa VCBP card applet. The card data is described
in TLV format with defined tags, defined lengths, and sample values. The card data in TLV format is organized in DGIs contained in
Store Data APDU commands used to personalize the card applet.
Visa VCBP card applet can be personalized to support both qVSDC and MSD transactions. Personalization data to support qVSDC
transactions are mandatory. Personalization data to support MSD transactions are optional.
SimplyTapp Defined Card Personalization Data
Data Description

Tag

Length

Attribute

Sample Value

DGI(s)

Maximum Number of Live Transactions: Maximum
number of dynamic account parameters (1-255)
that is stored in the card agent at any time.
Each set of dynamic account parameters can only
be used for one transaction. So this number
also represents the maximum number of
transactions that can be performed without
replenishing dynamic account parameters.

‘DF30’

1

Optional
Default = 1

‘08’

‘4000’

Minimum Threshold Number of Live Dynamic
Account Parameters: When the number of dynamic
account parameters stored in the card agent
that remains unused for transactions reaches
this minimum threshold (1-255), the card agent
will attempt to replenish dynamic account
parameters.

‘DF31’

1

Optional
Default = 1

‘04’

‘4000’

Time to Live Check Interval [in minutes]: The
interval (0=never or 1-255 minutes) which the
card agent continuously checks expiration of
dynamic account parameters.

‘DF39’

1

Optional
Default = 0
(never)

‘0A’

‘4000’

Time to Live [in hours]: The number of hours
(0=forever or 1-255 hours) a set of dynamic
account parameters is active for making a
transaction. The expiration time is calculated
when dynamic account parameters are generated.

‘DF3A’

1

Optional
Default = 0
(forever)

‘01’

‘4000’

range of records) of the application elementary files for qVSDC transaction. ‘94’ var. range of records) of the application elementary files for MSD transaction. ‘82’ 2 Conditional to Support MSD ‘00C0’ ‘9206’ Application File Locator (AFL) [for MSD]: Indicates the location (SFI. ‘A5’ var. Transaction verification logs are saved in a queue. Conditional to Support MSD ‘80010100’ ‘9206’ AIP [for qVSDC]: Indicates the capabilities of the card to support specific functions for qVSDC transaction. Mandatory ‘500B56495341204352454449549 ‘9102’ F38189F66049F02069F03069F1A0 295055F2A029A039C019F3704BF0 C089F5A050000000000’ Application Interchange Profile (AIP) [for MSD]: Indicates the capabilities of the card to support specific functions for MSD transaction. Mandatory ‘08030300’ ‘9207’ Visa Defined Card Personalization Data . ‘DF3B’ 1 Optional Default = 0 ‘10’ ‘4000’ Data Description Tag Length Attribute Sample Value DGI(s) File Control Information (FCI) Proprietary Template: Identifies the data object proprietary to VCBP in the FCI template according to ISO/IEC 7816-4. ‘94’ var. ‘82’ 2 Mandatory ‘0040’ ‘9207’ AFL [for qVSDC]: Indicates the location (SFI.Data Description Tag Length Attribute Sample Value DGI(s) Maximum Number of Transaction Verification Logs: The maximum number of transaction verification logs (0-255) that can be stored and available for post payment processing.

Data Description Tag Length Attribute Sample Value DGI(s) Issuer Application Data (IAD): Contains proprietary application data for transmission to the issuer in an online transaction. up to 32 Mandatory ‘1F4301002000000000BBBBBBBB0 ‘9200’ DDDDDDD000000000000000000000 000000000’ Track 2 Equivalent Data: Contains the data elements of track 2 according to ISO/IEC 7813. up to 19 Mandatory ‘4761739001010010D1012201AAA ‘0101’ AAAACCCCCCF’ ‘0E01’ Cardholder Name: Indicates cardholder name according to ISO/IEC 7813. excluding start sentinel. • Length Indicator = ‘1F’ • CVN = ‘43’ • Derived Key Indicator • Card Verification Result [partially dynamically updated during transaction] • Digital Wallet Provider ID (BBBBBBBB) • Derivation Data (0YHHHHCC) [dynamically updated during transaction] • Issuer Discretionary Data Format = ‘00’ • Issuer Discretionary Data = ‘0000000000000000000000000000’ ‘9F10’ var. ‘5F20’ 2-26 Optional ‘4558414D504C452F504552534F’ ‘0101’ ‘0103’ ‘0E01’ Application Usage Control (AUC): Indicates issuer’s specified restrictions on the geographic usage and services allowed for the application. as follows: • Primary Account Number • Field Separator = 'D' • Expiration Date (YYMM) • Service Code • Account Parameters Index (YHHHHCC) [dynamically updated during transaction] • Decimalized Cryptogram (CCCCCC) [dynamically updated during transaction] • Pad with one Hex 'F' if needed to ensure whole bytes ‘57’ var. and Longitudinal Redundancy Check (LRC). ‘9F07’ 2 Mandatory ‘0080’ ‘0103’ . end sentinel.

up to 32 Optional ‘01083132333435363738’ ‘0103’ Token Requestor ID (TRID): Uniquely identifies the pairing of Token Requestor with the Token Domain. up to 252 Optional ‘00000000000000001F00’ ‘0E01’ . if a given Token Requestor needs Tokens for multiple domains. Each element in CED consists of a 1-byte proprietary identifier. Consists of one or more issuer elements. ‘5F28’ 2 Mandatory ‘0840’ ‘0103’ Customer Exclusive Data (CED): Contains certain data element unique to that consumer or card (such as a loyalty number or reward number.Data Description Tag Length Attribute Sample Value DGI(s) Issuer Country Code: Indicates the country of the issuer according to ISO 3166. ‘5F34’ 1 Mandatory ‘01’ ‘0E01’ Card Transactions Qualifiers (CTQ): This element is personalized (using bits 5 and 6 of byte 1) to establish what action the card should take when Offline Data Authentication fails. The current identifiers that have been defined are ‘01’ = issuer proprietary. ‘9F6C’ 2 Mandatory ‘0100’ ‘0E01’ Cardholder Verification Method (CVM) List: Identifies a method of verification of the cardholder supported by the application. 1-byte length. one for each domain. ‘8E’ var. It is an 11-digit numeric value assigned by the Token Service Provider and is unique within the Token Value. it will have multiple Token Requestor IDs. unique to each Token Service Provider • Positions 4-11: Assigned by the Token Service Provider for each requesting entity and Token Domain ‘9F19’ 6 Optional ‘012312345678’ ‘0103’ Application Primary Account Number (PAN) Sequence Number (PSN): Identifies and differentiates cards with the same PAN. ‘9F7C’ var. etc). all other values are RFU. Thus. and a value. • Positions 1-3: Token Service Provider Code.

N/A 3-8 Mandatory ‘95C5A8187FDA9947’ ‘9000’ UDK [for MSD]: TDES key used to derive Limited Use Key that is used for MSD cryptogram generation. N/A 3-8 Conditional to Validate UDK [for MSD] ‘95C5A8187FDA9947’ ‘9001’ .Data Description Tag Length Attribute Sample Value DGI(s) Unique Derived Key (UDK): TDES key used to derive Limited Use Key that is used for cryptogram generation. Always used for qVSDC transactions. N/A 16 Optional encrypted ‘8001’ UDK Key Check Value [for MSD]: Used to validate recovered UDK [for MSD]. N/A 16 Mandatory encrypted ‘8000’ UDK Key Check Value: Used to validate recovered UDK. Used for MSD transactions if DGI ‘8001’ is not personalized.