ADVT Known Issues List

TO: ACQUIRER DEVICE VALIDATION TOOLKIT USERS

FROM: VISA INTERNATIONAL SERVICE ASSOCIATION
SUBJECT: KNOWN ISSUES IN ADVT – VERSION 5.0
DATE: OCTOBER 8, 2008

This bulletin serves as an addendum to the Acquirer Device Validation Toolkit (ADVT) –
Version 5.0. It provides users with a detailed description of minor errors noted or changes
required to the current version of the toolkit, and with Visa’s plans for resolution.

Documentation Change:

The following errors have been noted or changes are required to the ADVT document.

# Section Error Description Changes Required

1 Section 4.5 Test A documentation error was The following documentation

Card Profiles – found within the PDOL Value. change is required (in bold):
Test Card 6
In the “Contact VSDC
Application Data” section for
Test Card # 6:
9F 02 06 9F … 02 9F 66 10

Visa Public ADVT Known Issues List – Version 5.0 - Revision 1 1

 # Section Error Description
2 Section 4.5 Test A documentation error was
Card Profiles – found with duplicate Signed
Test Card 16 Static Application Data and
Issuer Public Key Certification
values. The first set of values
for each should be ignored.
Visa Public ADVT Known Issues List – Version 5.0 - Revision 1
Changes Required
The following documentation
change is required:
In the Test Card Profile
section for Test Card 16 after
the "Track 1 Discretionary
Data," delete the following:
Signed Static Application
Data Value:
69 2B A8 63 D6 35 F9 68 4B
F1 D5 13 BE 1C 4F F2 61 BA
A9 79 9C 9F D9 95 D2 06 BA
E0 3A 3D 21 1D E6 92 83 28
CE 74 77 EE C4 98 67 7A 19
5A 41 C4 39 9F 30 69 B8 1F
60 8C D7 3F 31 DC C2 3E 26
BB 70 43 87 59 59 18 75 C7
D5 54 81 06 D2 30 CF 01 89
DC CB E2 76 0C 5D C2 95
86 F5 B2 E8 EA 6D 0D F0 E1
5C 66 2E 48 CC C9 06 A8 61
7C 29 3F 19 CA
Issuer Public Key
Certificate Value:
1B 1E 70 58 CA D3 0A 63 73
C5 B9 49 50 30 4E 74 44 67
91 D9 DF 04 FE 41 60 6C A5
2F DD 01 9E A5 56 C6 13 C5
8E 6F B3 4D E6 BA C0 6C 63
89 0E E7 D8 A7 47 2F EF 5E
68 19 B2 6C D8 5C 96 69 4B
A9 3D A2 27 3C 12 F5 D4 A5
9C FC 1F EA FB A4 8F AC
68 97 55 C0 B9 71 33 29 64
E7 5D 78 10 76 19 FD 8B 63
9E 52 F3 BC 30 47 6B AB 0D
55 19 9A DB A7 10 45 AF 1B
6B B8 D1 0D 63 C4 98 6E F8
2E 8B EE
2
 # Section Error Description
3 Section 5.1.2 "Corrections to VIS 1.4.0"
Chip Data for the document (dated Feb 2002)
Baseline Card clarified that the DES keys
must be an odd parity. This
matters since the UDK is used
as data in PIN encryption and
could be an issue on how
parity checking affects the
operation of PIN change on a
VSDC card.
Card Errors:
The following errors have been noted on the current ADVT cards.
# Card # Error Description
Visa Public ADVT Known Issues List – Version 5.0 - Revision 1
Changes Required
The following document
change is required:
In the “Value” information for
the Master MDK B data
update to:
52D0 BAC2 4685 0B37
E9FD 234C DF29 DFF1
Note: VIS requires that the
three derived keys be odd
parity.
In the “Value” information for
the UDK data update to:
52D0BBC3 46840A36
E8FD234D DE28DEF0
Correction Required
3
 # Card # Error Description Correction Required

1 Card # 1 The Issuer Authentication Revised cards will be

functionality from Test Card provided in the interim that
#25 was added to this card will be re-personalized using
when Card # 25 was removed. applet version 2.4.0.
The VSDC Applet version
The feature will be
2.4.0 used on the cards that
reintroduced in the next
supported the previous version
release of the VSDC applet.
of the toolkit (V4.0), supported
a feature “If Issuer
Authentication was set to
mandatory and no ARPC was
returned, decline the
transaction” in ADA Byte 1 –
Bit 6. VSDC Applet version
2.5.1 is now used on most of
the cards supporting ADVT
V5.0. In this version of the
applet, the feature has been
removed, making this bit
setting ‘Reserved for Future
Use (RFU). Some users have
come to rely on this feature to
detect situation where a
response cryptogram (ARPC)
is being returned by VisaNet
but the Acquirer Host or
terminal fails to pass it through
to the card, resulting in a
declined transaction.

2 Card # 3 The record containing the A revised card will be

Signed Static Application Data provided by Visa that will
has been erroneously coded resolve this problem.
with the incorrect data record
length.. SFI 2 – Record 3 is
currently personalized with
(152) 70 81 92 93 81 90… The
correct coding should be (152)
70 81 93 93 81 90…

3 Card # 18 This tests for acceptance of This will be corrected in the

Visa Low-Value Payment next release.
(VLP) however this feature is
not functioning on the card.
Note: Currently this is an
optional VSDC service.

Visa Public ADVT Known Issues List – Version 5.0 - Revision 1 4

 # Card # Error Description Correction Required

4 Card # 22 When the second application This error appears to be the

on this card (Visa Debit) is
selected and a transaction is
attempted, the transaction
terminates on as a result of the
card returning error Status
Words (6F 00) in response to
the 1st Generate AC
command.
result of a personalization
sequencing error. Revised
cards will be provided that
correct this problem. A
revised card will be provided
by Visa that will resolve this
problem.

5 Card # 29 Attempts to perform The failure appears to be an

Enciphered Offline PIN incorrectly personalized ICC
verification or Dynamic Data Private Key. A revised card
Authentication fail on this card. will be provided by Visa that
will resolve this problem.

Resolution Plan

All errors identified above will either be resolved in the next release of the Acquirer Device
Validation Toolkit or once a solution is found.

Note: The documentation change for Section 5.1.2 Chip Data for the Baseline Card will
be corrected in Version 6.0 of the Acquirer Device Validation Toolkit.

Visa Public ADVT Known Issues List – Version 5.0 - Revision 1 5