9F30
Biometric Solution IDBiometric Solution ID names which specific biometric verification solution - whose fingerprint algorithm, whose matching technology - card or terminal actually implements, since EMV's biometric CVM support, the online and offline biometric options already flagged in Terminal Capabilities (9F33, covered earlier), is deliberately solution-agnostic at the protocol level: EMV defines how biometric verification fits into the transaction flow, not which specific biometric technology has to be used. It's related to the Biometric Data Template (7F60, covered alongside it here), which is where the actual biometric data and this solution identifier travel together as a package. Because different biometric solutions aren't necessarily interoperable with each other, a card and terminal that both support biometric CVM in principle still need matching Biometric Solution IDs for that CVM method to actually work between them - a mismatch here means biometric verification silently isn't a viable CVM option for this particular card-terminal pairing, regardless of what Terminal Capabilities otherwise claims. See EMV 4.4 Book 3.
Interactive decoder
Paste a hex value for this tag to decode it in your browser. Nothing is sent anywhere.
Binary (3): 010203
This tag is not a bitmap; the decoder shows a format-based interpretation.
Decoded example
Example value: 010203
Related tags
Properties
| Tag | 9F30 |
|---|---|
| Name | Biometric Solution ID |
| Format | Binary |
| Length | 3 bytes |
| Source | Terminal |
| Templates | — |
| Books | EMV 4.4 Book 3 |
Frequently asked questions
- What is EMV tag 9F30?
- Biometric Solution ID names which specific biometric verification solution - whose fingerprint algorithm, whose matching technology - card or terminal actually implements, since EMV's biometric CVM support, the online and offline biometric options already flagged in Terminal Capabilities (9F33, covered earlier), is deliberately solution-agnostic at the protocol level: EMV defines how biometric verification fits into the transaction flow, not which specific biometric technology has to be used. It's related to the Biometric Data Template (7F60, covered alongside it here), which is where the actual biometric data and this solution identifier travel together as a package. Because different biometric solutions aren't necessarily interoperable with each other, a card and terminal that both support biometric CVM in principle still need matching Biometric Solution IDs for that CVM method to actually work between them - a mismatch here means biometric verification silently isn't a viable CVM option for this particular card-terminal pairing, regardless of what Terminal Capabilities otherwise claims. See EMV 4.4 Book 3.
- What format and length does EMV tag 9F30 use?
- Tag 9F30 uses the Binary format and is normally 3 bytes long.
- Is tag 9F30 provided by the card or the terminal?
- Tag 9F30 (Biometric Solution ID) is provided by the Terminal.
Sources
- EMV_v4.4_Book_3_Application_Specification, p. 141
Receive site updates
Subscribe to receive site updates directly to your email
We won't send spam. You can unsubscribe at any time.