FCODE_Processing
FCODE_Processing
CODE
Issuers & Processors impact with
VISA VBSS 1.0.2
07/06/2024
VISA SPECIFICATIONS
Visa documentation
• Visa Biometric Sensor Specification VBSS 1.0.1
• Biometric sensor-on-card products, Global Issuer Implementation Guide Version 1.0
IAD & IDD Issuer Application Data & Issuer Discretionary Data
• Set of supported formats
→ IAD 0/1/3 with IDD Option ‘B’
→ IAD 2 with IDD Option ‘B’ or ‘7’
Biometric CVMs
• Contact : No CVM used for Biometry
→ Biometry details are in IAD / IDD
• Contactless : CDCVM
→ Biometry details are in CVR / IAD / IDD
2
All Information and Intellectual property rights reserved at ©IDEMIA 2024
VISA DETAILS
On IAD Supported :
• Contact : Biometric results available only in IDD or new CVR bits
• Contactless : legacy CDCVM Successfully performed in CVR B2 / b3
3
All Information and Intellectual property rights reserved at ©IDEMIA 2024
VISA
Is there any implementation not requiring host update for a pilot
Limitations :
• No view on Biometry counter lock
• No view on Biometry not performed
• No view on Enrolment not performed
6/7/2024
All Information and Intellectual property rights reserved at ©IDEMIA 2024
WHAT SHOULD ISSUER HOST PROCESSOR DO?
Refer to Biometric sensor-on-card products, Global Issuer Implementation Guide Version 1.0
And then
• Option 1: Do Nothing
• Option 2: Read the Biometric Information Data from IAD
• Option 3: Shortcut method to identify BIO verified/unverified
6/7/2024 5
All Information and Intellectual property rights reserved at ©IDEMIA 2024
OPTION 1
Do Nothing
Pros:
• Visa mentions No development required. Only good for providing biometric card experience.
• Rely on :
→ successful Offline Authentication and valid ARQC cryptogram and accept No CVM transaction on contact
→ CDCVM transaction on contactless
Cons:
• There may be host rules that decline the biometric transaction. Need to identify biometric transactions and
relax those rules.
• Difficult for processor to identify biometric transactions from non-biometric transactions
• No information whether biometric try counter is locked
6/7/2024 6
All Information and Intellectual property rights reserved at ©IDEMIA 2024
OPTION 2
Read the Biometric Information Data from IAD
Pros:
• Processor knows exactly biometric
results, history, biometric count
• Can identify biometric cards that are
locked out and needs re-enrollment.
Cons:
• Extensive development effort
6/7/2024 7
All Information and Intellectual property rights reserved at ©IDEMIA 2024
OPTION 3
Shortcut method to identify BIO verified/unverified
Check value of Issuer Discretionary Data Option ID in IAD for presence of biometric
sensor
• “0B” or “07” means transaction coming from card with biometric sensor
Pros:
• Smaller development effort than Option 2
Cons:
• Information limited to identifying which transactions are biometric or not.
6/7/2024 8
All Information and Intellectual property rights reserved at ©IDEMIA 2024
F.CODE
Issuers & Processors impact with
Mastercard M/Chip Bio 1.2.3
07/06/2024
MASTERCARD BIO SPECIFICATIONS
Mastercard documentation
• Mastercard M/Chip Advance 1.2.3 Bio – Dec 2019
• Mastercard Biometric Card - Issuer Implementation guide 1.1
Biometric CVM
• In Contact : ‘no CVM performed’ ➔ biometric results in CVR
• In Contactless : CDCVM ➔ biometric results in CVR
→ Redefinition of IDD in CVR meaning with : Biometric verification performed & Biometric verification try limit exceeded
→ Redefinition of PIN verification successful to indicate Biometric verification results
→ Backward compatibility is possible ➔ Less or no impact on host but less information are available
Contact transaction
• CVM Results is set to ‘no CVM performed’.
→ CVR bits indicating successful biometric verification for making the authorization response.
Contactless transaction
• “CDCVM supported” bit + CVR new meanings
CVR handling
• Without backward compatibility
→ CVR indicates result of Bio & PIN results
Previous IDD CVR are reused to indicate Biometry verification performed & Biometry verification try limit exceeded
PIN verification Bytes interpretation is changed to indicate Biometry verification results or PIN results
• With backward compatibility
→ When required backward compatibility is supported (CVR interpretation differ)
to MChip 4 V1.1 / MChip4 V1.3.1
to MChip 2 V2.05 or MChip 2 V2.1/2.2
Pros:
• Biometric Card Cardholder Authentication Service can simplify reading biometric status from CVR.
• Similar to Chip On-Behalf Service, the transaction routed through Mastercard service first. Service
interprets CVR bits and a simplified indicator is passed to Issuer’s host to indicate whether Bio was
successful or not.
• Issuer still decides final outcome but will use indicator obtained from Mastercard.
Cons:
• Setup time at Mastercard
• Cost for service
Pros:
• Some Issuers have been lucky to observe no issues with their current host configurations on biometric
transactions. Only good for providing biometric card experience.
• Rely on :
→ successful Offline Authentication and valid ARQC cryptogram and accept No CVM transaction on contact
→ CDCVM transaction on contactless
Cons:
• There may be host rules that decline the biometric transaction. Need to identify biometric transactions and
relax those rules.
• Difficult for processor to identify biometric transactions from non-biometric transactions
• No information whether biometric try counter is locked
Pros:
• Processor knows exactly biometric results, history, biometric count
• Can identify biometric cards that are locked out and needs re-enrollment.
Cons:
• May require extensive development effort
Scenario CVR B1b1 CVR B1b3 CVR B2b2 CVR B4b5 CVR B4b6 AIP B1b5 AIP B1b2
Offline Offline BSOC Offline PIN Offline PIN Cardholder CDCVM is
PIN PIN Verification Verification Verification verification is supported
Verificatio Verificatio Performed Failed Not supported
n n Performed
Successf Performe
ul d
• For contactless transactions, all transactions seen at host have been successfully Bio verified if default profile was chosen. Failed Bio will cause terminal to decline on the spot
and prompt user to insert contact interface. Transaction will not reach host.
Pros:
• Smaller development effort than Option 3
Cons:
• Information limited to identifying which transactions are biometric or not.
www.Idemia.com