Visa Paywave Implementation Overview (Sri Lanka)

Visa payWave
Implementation Overview
Lim, Woo Jung
Implementation Service
Notice of confidentiality
This presentation is furnished to you solely in your capacity as a customer of Visa Inc. and/or a
participant in the Visa payments system. By accepting this presentation, you acknowledge that
the information contained herein (the “Information”) is confidential and subject to the
confidentiality restrictions contained in Visa’s operating regulations and/or other confidentiality
agreements, which limit your use of the Information. You agree to keep the Information
confidential and not to use the Information for any purpose other than in your capacity as a
customer of Visa Inc. or as a participant in the Visa payments system. The Information may only
be disseminated within your organization on a need-to-know basis to enable your participation
in the Visa payments system. Please be advised that the Information may constitute material non
public information under U.S. federal securities laws and that purchasing or selling securities of
Visa Inc. while being aware of material non public information would constitute a violation of
applicable U.S. federal securities laws.
2 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

Agenda
• Introduction
• How it works
• Issuing Implementation
• Acquiring Implementation
• References

Introduction

Overview
• Its fast!
• Just wave and Go.
• No counting change, fumbling for
cash or worrying if you have
enough for the purchase.
• No PIN, no signature *
• All with Visa’s security promise
of 100% Payment Protection **
* For transactions under Contactless CVM limit defined by country
** Visa’s Zero Liability Policy

Speed is paramount
Cash payment
Produce Hand-over Cashier validates Cash placed Hand-back Customer
cash to cashier & counts in till Receipt & change collects & counts
Timing
Hand-over 12 – 14 sec Hand-back
Select Card Customer waves Authorisation, Hand-back

card by reader receipt printed receipt copy
3 – 4 seconds 1 - 2 sec
Wave Authorisation Hand-back
Visa payWave offline
payment
4 – 6 sec
Based on Deloitte field study findings at QSR in Taipei and Malaysia in Oct 2006
36 executives interviewed from 6 banks, 5 merchants, 4 Technology vendors and 2 Visa country offices

How it works

Setup
Reader at
back of screen

Visa payWave Transaction Flow
Visa payWave Reader Terminal

Card
Issuer VisaNet Acquirer

Systems Host

Key Features of VCPS cards
1. Multiple possible pathway for a
single transaction
• qVSDC online
• qVSDC offline
• qVSDC with CVM
2. Minimize message flow between
reader and card to speed up “tap
time”
3. Utilize EMV cryptographic method
• fDDA (Fast DDA) for offline
• TDES (ARQC) for online
4. Support contact VSDC
Sample Transaction Flow Diagram from

Transaction Acceptance Device Guide

Key Features of qVSDC
1. Combines authentication and authorization into single message for

offline
2. Compresses multiple EMV commands into as few commands as possible
to save time
3. Uses EMV strong security cryptographic for offline and online
authentication
4. Uses secure online cryptogram
5. Fast (less than 500ms) and output is EMV data

qVSDC Transaction Flow
Preliminary Processing
• Takes place before the contactless card is read

• Amount is entered
• Amount is checked against default reader
contactless limit
– Floor limit
– CVM limit

Terminal Transaction Qualifiers (TTQ) Tag 9F66
Byte Bit Definition

1 8 '1' – Contactless magnetic stripe (MSD) supported
'0' – Contactless magnetic stripe (MSD) not supported
7 RFU – b'x'
6 '1' – Contactless qVSDC supported

'0' – Contactless qVSDC not supported
5 '1' – Contact VSDC (EMV chip) supported
'0' – Contact VSDC (EMV chip) not supported
4 '1' – Reader is Offline Only
'0' – Reader is Online Capable
3 '1' – Online PIN supported
'0' – Online PIN not supported
2 '1' – Signature supported
'0' – Signature not supported
1 '1' – Offline Data Authentication (ODA) for online authorization supported
'0' – Offline Data Authentication (ODA) for online authorization not supported

Terminal Transaction Qualifiers (TTQ) Tag 9F66
Byte Bit Definition

2 8 '1' – Online cryptogram required
'0' – Online cryptogram not required
7 '1' – CVM required
'0' – CVM not required
6 '1' – (Contact) Offline PIN supported
'0' – (Contact) Offline PIN supported not supported
5-1 RFU – b'xxxxxx'
3 8 '1' – Issuer update supported
'0' – Issuer update not supported
7 '1' – Mobile functionality supported
'0' – Mobile functionality not supported
6-1 RFU – b'xxxxxxxx'
4 8-1 RFU – b'xxxxxxxx'

Reader and Card Interaction and Application Selection
Activate the card
Read lists of contactless

application on the card
Select the application
Return Application Program

ID
• Reader performs risk parameter checking again if there is a matching

Application Program ID

Card Requests Terminal and Transaction Data
Request data from reader
Response with data elements

Card Risk Management
Performs risk management

and response to reader with
transaction decision

Card Additional Processes Tag 9F68
Byte Bit Definition

1 8 '1' = Low Value Check supported
'0' = Low Value Check not supported
7 '1' = Low Value AND CTTA Check supported
'0' = Low Value AND CTTA Check not supported
6 '1' = Count qVSDC online transaction
'0' = Do not count qVSDC online transaction
5 '1' – Streamlined qVSDC supported
'0' – Streamlined qVSDC supported not supported
4 '1' – PIN Tries Exceeded Check supported
'0' – PIN Tries Exceeded Check not supported
3 '1' – Offline transactions are allowed
'0' – Offline transactions are not allowed
2 '1' – Card Prefers Contact VSDC (EMV chip) for online transactions
'0' – No Card Contact VSDC (EMV chip) Preference for online
transactions
1 '1' – Return Available Offline Spending Amount
'0' – Do not return Available Offline Spending Amount

Card Additional Processes Tag 9F68
Byte Bit Definition

2 8 '1' – Include country code to determine international transaction
'0' – Do not include country code to determine international transaction
7 '1' – International transaction are not allowed
'0' – International transactions are allowed
6 '1' – Disable ODA for online transaction
'0’ – Enable ODA for online transaction
4 ‘1’ – Do not count qVSDC offline transactions
‘0’ – Count qVSDC offline transactions
3-1 RFU – b'xxx'
3 8 '1' – Online PIN supported for domestic transaction

'0' – Online PIN not supported for international transaction
7 '1' – Online PIN supported for domestic transaction
'0' – Online PIN not supported for international transaction
6 '1' – Offline PIN (contact) supported
'0' – Offline PIN (contact) not supported
5 '1' – Signature supported
'0' – Signature not supported
4-1 RFU – b'xxxx'
4 8 RFU – b'x'
7 ‘1’ - MSD Legacy-only
6-1 RFU – b'xxxxxx'

Transaction Outcome
• Transaction Approved Offline

• Transaction Sent Online
• Transaction Declined Offline
• Transaction Terminated

VCPS Card to Reader Flow - qVSDC
Online
Select PPSE (Proximity Payment System Environment)
List of AIDs (Application Identifiers)
Select VSDC AID
PDOL (Processing Options Data Object List)
VCPS 2.1.x Card

Get Processing Options Devices support full chip
data
+ TTQ (Terminal Transaction Qualifiers)
qVSDC AIP (Application Interchange Profile) +

Track 2 + ARQC* + Data
* The cryptogram (ARQC-Authorization Response cryptogram) is generated with CVN10

VCPS Card to Reader Flow - qVSDC
Offline
Select PPSE (Proximity Payment System Environment)
List of AIDs (Application Identifiers)
Select VSDC AID
PDOL (Processing Options Data Object List)
Get Processing Options

VCPS 2.1.x Card + TTQ (Terminal Transaction Qualifiers) Devices support full chip
data
qVSDC AIP (Application Interchange Profile) + AFL (Application File Locator)
+ Track2 + TC* (Transaction Certificate) + Data + DSAD
Read Record
Data to be signed for fDDA
* The offline cryptogram (TC) is generated with CVN10

Issuing Implementation

Business Rules

Visa payWave Business Rules Summary
• If transaction value is less than or equal to LKR 5,000, Cardholder

Verification Method (CVM) is not required
• Applies to all merchant category codes
• Receipt is optional and printed upon cardholder’s request for no CVM
transactions
For Detail, Please refer to Visa Product and Service Rules - Visa Easy Payment Service (VEPS) Maximum Transaction Amounts ID# 0027503
and Consecutive Offline Chip Authorization Counters Requirement – AP Region ID# 0029282

Visa payWave Requirements
• Card manufacturers must be Visa

certified vendors
• Contactless cards must be tested and
certified by Visa
• Chip Card Testing and Renewal Policy is
the same as Contact Chip Card
• Cards must be personalized to support
qVSDC
* Note: Some of approved products is not listed as public information, please check with your Implementation Manager to confirm

Visa payWave AP Requirement
Visa Product and Business Rules
• All new cards must support VCPS 2.1 or later
• Must be personalized with the Application Program ID (APID)
• Must be personalized with the Form Factor Indicator (FFI)
• Must support cardholder verification method (CVM)
• Must not include the cardholder name on the contactless portion of the
chip. The cardholder name must either be omitted or a generic value must
be used in its place.
• Must not support MSD
• All contactless Chip Cards issued must support offline data
authentication with Online Authorization using either fast Dynamic Data
Authentication or transit-only static data authentication, as specified in Visa
Contactless Payment Specification version 2.1 and later.

Branding

Visa payWave Card Design
• Card design needs to be approved by Visa

– Comply with Visa International Cards &
Marks Specifications
– Comply with Visa Asia Pacific Card Design
Guide
– Submit card design via Visa Online - Brand
Management Approval System (BMAS)
• Issuer needs to consider
– Location of contact plate (same as EMV)
– Location of Antenna (fourth line embossing)
– Visa payWave identifier
– Contactless symbol
• For enquiry, please contact
apcards@visa.com
• Visit Product Standards site at
www.productbrandstandards.com for
detail
29 | Presentation Title | Month XX, Year Visa Confidential
Implementation

Visa payWave Issuing Infrastructure
Visa payWave Card Reader Terminal
Issuer Host VisaNet Acquirer Host

Choosing what chip to use
• Both the chip and the card must be Visa certified
• Chip needs to be certified as a VCPS compliant
• Cards need to be certified to ensure:
– Antenna construction and endurance
– Signal strength
– Radio frequency performance
• Request bureau or card vendor to provide the Visa approval letter
• Visit Visa Technology Partner site at https://technologypartner.visa.com for approved
products*
• If selected products were approved under the earlier Chip Card Testing and Renewal
Policy, client has to ensure its “Renewal Date” is still valid according to APML 33/10
• If selected products were approved under the existing policy#, client has to ensure it’s
“Lifecycle End Date” is valid and beyond the card validity and the expiry date of the
signed Issuer Public Key.
*Some of approved products is not listed as public information, please check

with your Implementation Manager to confirm
#For Detail, please refer to VBN - Chip Card Lifecycle Management Policy
and Related Visa Rules Will Be Updated (10 Dec 2015)

Visa payWave Chip Parameters
Name Tag Description
VLP Available Funds 9F79 • A counter decremented by the amount
authorized in an offline payWave
transaction
• Reset after a successful online authorized
contact VSDC transaction
VLP Funds Limit 9F77 • Value to which VLP Available Funds [9F79]
is reset to upon authorized contact VSDC
transaction
VLP Single Transaction 9F78 • Transactions exceeding this limit requires
Limit online authorization
• Card enforces rule during transaction time
according to transaction amount

Visa payWave Chip Parameters
Name Tag Description
Card Additional Processes 9F68 • Defines additional card contactless
transaction behavior
Application Program ID 9F5A • Value used by reader to identify applicable
risk parameters
Format:
Byte 1: “40”
Byte 2-3: currency code
Byte 3-4: country code
Form Factor Indicator 9F6E • Used to indicate the type of contactless
interface which the transaction was
conducted

Visa payWave CVM Behavior
• Reader will request Visa payWave transaction to be carried out with CVM
when the transaction amount is higher than reader’s CVM limit
• Possible CVM includes Online PIN, Offline PIN (Contact) or Signature
• Online PIN always take precedence over signature
• CVM must be supported by both card and device
• Contactless transaction cannot be performed if no matching CVM is found

Visa payWave Transaction Snapshot
VLP Funds Limit VLP Single Reader CVM VLP Available

Transaction Limit Funds
Limit
$160 $80 $80 $160
Transaction Online/Offline CVM Required Funds Available

Shirt - $60 Offline No $100
Laptop - $850 Online Yes $100
Books - $70 Offline No $30
Movie Ticket - $27 Offline No $3
Can of coke - $4 Online No $3
Contact / VSDC Transaction (Issuer approved) $160

Visa payWave AP Requirement for Acquirers
Visa Product and Service Rules
• Enable the VLP Funds Limits and VLP Available Fund according to the
values defined in the country specific offline limits

AP Perso Templates overview
Version 4.0.1
• Main features
– qVSDC and streamlined qVSDC (online only profile)
– DDA
– Online PIN and/or Signature
Contactless
Contact (qVSDC)
Online DDA Online fDDA
Template 4D X X
Template 4DF X X X X

Visa payWave Issuer Host Changes
• Full Data Option

– VIP forwards all chip data to Issuers
• Early Data Option
– For Issuers currently issuing contact chip cards on Early Data option
– VIP drops contactless chip data from the message prior to forwarding the
message to Issuer
– VIP validates chip cryptogram
– Issuer is still required to perform transaction authorization
• No new fields for either options
• Must be able to receive Tag 9F6E—Form Factor Indicator (FFI) in Field 55
TLV format only and TCR 7 position 151-158

Issuers – New Values in Existing Fields
• POS Entry Mode (Field 22 / TCR 0 position162-163)

– “07” – transaction from qVSDC reader
• Terminal Entry Capability (Field 60.2 / TCR 0 position 158)
– “5” for readers connected to chip capable terminals
– “8” for readers connected to proximity read capable only terminals
• Use Cryptogram Version 10

Card and Host Testing

Testing Requirement
• White plastic review Testing Type Testing Fee

– Fully personalized with chip profile
White Plastic USD1,000 per BIN
and test keys
(up to four cards)
– Minimum 2 cards per BIN
– 10 working days turnaround per Host Testing USD350 per hour
review cycle
– Issuer may choose to perform
internal test before submitting
white plastics e.g. using Barnes
tools
• Issuer Host Testing
– Host testing is required
– For existing EMV issuer, testing
focuses on Visa payWave
transaction handling
– VTS-VIP connected to contactless
reader* for unattended testing
– Base II testing is not required *For detail & recommended model, please refer to Visa VTS User Guide

Self Testing using VTS-VIP Simulator
• Test configuration during client

software development
• Contactless reader
– Connected to VTS-VIP
• Supported models*:
VTS-VIP – QProx / QP3000S
VisaNet
(VCMS)
Issuer *For detail & recommended model, please refer to Visa VTS User Guide

Acquiring Implementation

Business Rules

Visa payWave Business Rules Summary
• Reader transaction limit is prohibited

• If transaction value is less than LKR 5,000, Cardholder Verification Method
(CVM) is not required
• Applies to all merchant category codes
• Receipt is upon cardholder’s request for no CVM transactions
For Detail, Please refer to Visa Product and Service Rules - Visa Easy Payment Service (VEPS) Maximum Transaction Amounts ID# 0027503

Visa payWave Requirements
• Reader configuration can be in the form of

Integrated Device or “Intelligent” Reader
connected to a VSDC POS device
• Device must be tested and certified by
EMVCo and Visa
• Device must support qVSDC

• All new readers must support VCPS 2.1.3 or later
• Effective 1 January 2018, existing readers must support VCPS 2.1.3 or later
• Must support the Application Program ID (APID)
• Must disable the reader contactless transaction limit
• Must include the Form Factor Indicator (FFI) in authorization messages and
clearing records when it is provided by the card
For Detail, please refer to Visa Product and Service Rules

• Must enable the cardholder • Must enable the reader
verification method (CVM) Limit Contactless Floor Limit and set it
and set it to the value defined in to the value defined in the
the VEPS contactless limit Country Specific Contactless Chip
Floor Limit
For Detail, Please refer to Visa Product and Service Rule - For Detail, Please refer to Visa Product and Service Rule -
Visa Easy Payment Service (VEPS) Maximum Transaction Default and Country Specific Floor Limits - ID# 0026832
Amounts- ID# 0027503

Branding

Visa payWave Acceptance Branding
Refer to Product Brand Standards site at www.productbrandstandards.com

Implementation

Visa payWave Acquiring Infrastructure
Visa payWave Card Reader Terminal
Issuer Host VisaNet Acquirer Host

Terminal Requirements
• EMV level 1 and EMV kernel level 2

certified
• Terminal connected to host capable of
processing full EMV chip data
• Terminal switched on and enabled to
accept contact Chip transactions
• Tested with Visa ADVT Tool kits
(Acquirer Device Validation Toolkit)
using defined configurations

Reader Requirements
• Reader must be EMVCo Contactless

Terminal Level 1 certified (digital and
analogue testing)
• Reader must be VCPS certified
• All approved products are listed on
https://technologypartner.visa.com/Testing
/TestMaterials.aspx#714
• Must support qVSDC
• Tested with Visa Mobile CDET (Contactless
Device Evaluation Toolkit) using defined
configurations

Visa payWave Reader Limits
• Contactless Floor Limit

– US$0
Amount
• Contactless CVM Limit Authorized
– US$0
• Contactless CVM Capability
Always Online
CVM
– Online PIN
– Signature
CVM Limit = US$25
No CVM
Floor Limit = US$0

Visa payWave CVM Behavior
• Reader will request Visa payWave transaction to be carried out with CVM
when the transaction amount is higher than the CVM limit
• Possible CVM includes Online PIN, Offline PIN (Contact) or Signature
• Online PIN always take precedence over signature
• CVM must be supported by both card and device
• Contactless transaction cannot be performed if no matching CVM is found

Visa payWave Acquirer Host Changes
• Full Data Option Only

• No new fields
• New value in existing fields
• POS Entry Mode (Field 22 / TCR 0 position162-163)
– “07” – transaction from qVSDC reader
• PAN Sequence Number (Field 23 / TCR 7 position7-9)
– If personalized on cards to support account with multiple cards with same card
number
• Terminal Entry Capability (Field 60.2 / TCR 0 position 158)
– “5” for readers connected to chip capable terminals
– “8” for readers connected to proximity read capable only terminals
• Tag 9F6E—Form Factor Indicator (Field 55 only / TCR 7 position 151-158)

Terminal/Reader and Host Testing

Visa payWave Acquirer Testing
• Acceptance Device Testing • Acquirer Host Testing

– Terminal and reader considered as a – Host testing is required
single unit for testing – For existing EMV acquirer, testing
– Contact EMV ADVT (review is focuses on Visa payWave
optional) transaction handling
– CDET (review is required for at least – Use Visa Global Acquiring host test
one model) cards
• Download & Install Mobile CDET from – Base II testing is not required
Google Play Store into Android Device
• Refer to
https://technologypartner.visa.com/To
olkits/ for details Testing Type Testing Fee
– ADVT and CDET testing result to be ADVT / CDET USD350 per hour
submitted on CCRT review
– 10 working days turnaround per Host Testing USD350 per hour
review cycle

References

Reference specifications for Visa payWave
• Visa Contactless Payment Specification (VCPS) ver 2.1 May 2009

• Visa Contactless Payment Specification (VCPS) 2.1 Update List ver 4 Jan 2016
• Visa Contactless Payment Specification (VCPS) 2.2 Jan 2016
• Visa payWave Acquirer Implementation Guide for VCPS 2.1
• Visa payWave Issuer Implementation Guide for VCPS 2.1
• Visa Smart Debit/Credit System Technical Manual ver 5.0 Dec 2016
• Visa Product and Service Rules

PMCC Fee - Definition
Service Type Description Fee Waived
Project US $2,500 per

Project Management support from Visa Yes
Management project
New Program US $3,000 per

Adding new numeric to VisaNet for processing
Installation numeric
Converting numeric (e.g. BINs, RIDs) from an existing

Processor US $3,000 per
processing endpoint to a new processing endpoint,
Conversion numeric
including signature, PIN and/or ATM transactions
Any change to an existing Visa configuration in
General
production or VCMS including authorization, clearing, US $1,500 per
Configuration Yes
settlement, reporting, product, hardware, software numeric
Change
and network changes
US $2,000 per
Configuration Requests to reschedule a previously established numeric or
Reschedule system configuration change scheduled
event
US $4,000 per
Configuration Cancellation of a previously scheduled system numeric or
Cancellation configuration change scheduled
event
Source: 28 April 2016 VBN New Pricing For Client Projects and Configuration Changes

Other Fees
Service Billing Unit Fee USD Waived
ADVT Tool Kit 6.1.1 Per Kit US$1,000 (Exclude
shipping or
miscellaneous fee)
ADVT/CDET Review Per Hour 350 Yes for 1st POS

terminal model
(~Oct 12th 2018)
Attended Testing Fee Per Hour 350 Yes (~Oct 12th
2018)
Chip Card Validation Per BIN (up to 1,000 Yes for 1 Issuing
4 cards) BIN (~Oct 12th
2018)
Test Issuer Public Key Signing Per Certificate 300
Production Issuer Public Key Signing Per Certificate 1000
Expedited Testing Surcharge Per Request 1,000
Expedited Core/Config Setup Per BIN 4,000

Global Client Testing
Visa Technical Team and Escalation contacts
Primary Secondary
Account Management (AM) Malayamkumarath Sreedharan Manikandan Pallavi Narvekar,

mmanikan@visa.com pnarveka@visa.com
AM Escalation Vaibhav Taranekar

vtaranek@visa.com
Project Management (PM) Jeremy Goh Mari Takahashi

jegoh@visa.com matakaha@visa.com
IDD Phone +65 6210-2982 IDD Phone +65 6210-2937
PM Escalation Chung Hao Chin
chchin@visa.com
IDD Phone +65-6210-2954
Angie Tang
mtang@visa.com
IDD Phone +65 6210 2968

Thank you
Visa Confidential

Visa Paywave Implementation Overview (Sri Lanka)

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Visa Paywave Implementation Overview (Sri Lanka)

Încărcat de

Drepturi de autor:

Formate disponibile

Visa payWave

2 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

3 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

4 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

* For transactions under Contactless CVM limit defined by country

** Visa’s Zero Liability Policy

5 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

Select Card Customer waves Authorisation, Hand-back

6 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

7 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

8 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

Visa payWave Reader Terminal

Issuer VisaNet Acquirer

9 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

Sample Transaction Flow Diagram from

10 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

1. Combines authentication and authorization into single message for

11 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

• Takes place before the contactless card is read

12 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

Byte Bit Definition

6 '1' – Contactless qVSDC supported

13 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

Byte Bit Definition

14 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

Activate the card

Read lists of contactless

Select the application

Return Application Program

• Reader performs risk parameter checking again if there is a matching

15 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

Request data from reader

Response with data elements

16 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

Performs risk management

17 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

Byte Bit Definition

18 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

Byte Bit Definition

3 8 '1' – Online PIN supported for domestic transaction

19 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

• Transaction Approved Offline

20 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

Select PPSE (Proximity Payment System Environment)

List of AIDs (Application Identifiers)

Select VSDC AID

PDOL (Processing Options Data Object List)

VCPS 2.1.x Card

qVSDC AIP (Application Interchange Profile) +

* The cryptogram (ARQC-Authorization Response cryptogram) is generated with CVN10

21 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

Select PPSE (Proximity Payment System Environment)

List of AIDs (Application Identifiers)

Select VSDC AID

PDOL (Processing Options Data Object List)

Get Processing Options

Data to be signed for fDDA

* The offline cryptogram (TC) is generated with CVN10

23 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

24 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential

• If transaction value is less than or equal to LKR 5,000, Cardholder

25 | Visa payWave Overview and Implementation | Dec 2017 Visa Confidential