Blog Home

How the fingerprint reader works in the ISO8583 payments simulator

Posted on 20th Oct 2018 4709 views

fingerprint enrolled issuer

In the simplest form, the fingerprint reader will be called to read a fingerprint when you use the keyword **FINGERREADER** in the field where you want the fingerprint data to be populated.

But let us start from the beginning.

A fingerprint verification is done by checking 2 fingerprints: the capture fingerprint is verified against the enrolled fingerprint. This means that in order to do this, you need to start with enrolling a fingerprint.

1. Enroll fingerprint

The Issuer must have a fingerprint enrolled in order to be able to verify a fingerprint. In the ISO8583 payments simulator this is done by calling function "performFingerPrintVerification()" which will do two things: enroll a finger and verify a finger.

The Enroll will ask you to put your finger 5 times on the reader so it can capture as much information as possible about your fingerprint. The more detailed this is, the more likely it is to get a match when you verify.

The Verify in this step is just to make sure that everything works correctly and in case of a verification, we are successful.

The result of the enrollment is showed in the console as a hashed fingerprint, as a string. This is the Enrollment fingerprint.

2. Save fingerprint

The Issuer must possess the enrolled fingerprint if it needs to be able to perform a verification. In order to do this, in a testing situation, we simply copy the Enrolled fingerprint from the console, and we save it in the card details sheet.

In the Issuer Payments simulator we can simply paste this value next to the card ID/number that we want to have this fingerprint enrolled. In case of an authorization system, we place this in the card record, in the database.

3. Capture fingerprint

The Acquirer must be able to capture a fingerprint in order to send it to the Issuer for verification.

The keyword **FINGERREADER** must be placed the ISO8583 field where we want the fingerprint to be loaded. In this case 113. That is it.

When the simulator will start building the fields, it will find this keyword, will call the core to get a fingerprint from the user, the core will activate the reader, capture a fingerprint (correctly), store it in the field, and continue to build the message.

4. Verify fingerprint

The Issuer has the capability to verify the received fingerprint in DE113.

When the message contains a value in field 113, the Issuer starts to perform the verification. First, it looks up the fingerprint in the card row or record. If the row has **NOVALUE** then it just writes that fingerprint verification cannot be performed. 

If it does find a fingerprint in the card row/record, then it performs a comparison between the received value and the stored value, automatically.

 

 

 

 


LinkedIn

Top Read Articles


BIN List & Range for MasterCard, Visa, Amex, Diners, Discover, JCB, CUP
83350 views

Read smart card chip data with APDU commands ISO 7816
47712 views

ISO8583 Response Codes for Transaction processing
29064 views

ISO8583 Message Types for Transaction Processing
19038 views

ISO8583 Processing Codes for Transaction Processing
17106 views

Run the neaPay ISO8583 simulator
16054 views

Deploy, run and generate with neaPay Card Data Generator
15889 views

ISO8583 payments message format, programmers guide
14144 views

MCC Codes - Merchant Category Codes to use in ISO8583 Field 18
13619 views

ISO8583 message: The list of ISO 4217 currency codes for data elements 49 and 52
12068 views

ISO8583 Message Converter JSON and XML interface specification mapping
9852 views

Asking for defects support for the neaPay products: converter, switch, issuer, simulator
7125 views

Create a new test case in the neaPay ISO8583 simulator Video guide
7083 views

Cards and Banks Training
6860 views

Deploy the neaPay ISO8583 simulator - video guide
6820 views

Log Files in BASE24 classic
6617 views

BASE24 documentation to read
6008 views

BASE24 classic interview questions
5923 views

Performance testing at 500, 1000 and 1500 TPS
5908 views

BASE24 classic vs BASE24-eps
5883 views

ISO8583 converter to JSON XML SQL to HTTP host - message flow - video guide - Part.2
5264 views

EMV explained for programmers
5148 views

Connect the neaPay ISO8583 Acquirer simulator to your own host or Issuer
5005 views

ISO8583 converter to JSON XML SQL to HTTP Host - host unavailable - video guide- Part.3
4933 views

Card readers supported by neaPay payments simulator, CHIP and NFC
4748 views

Adding your own card to the Payments simulator to test your system
4744 views

ISO8583 converter to JSON XML SQL to HTTP host - start& run - video guide - Part.1
4743 views

BASE24 classic screens examples explained
4741 views

ISO8583 ATM POS Crypto API integration with exchanges like Coinbase or Binance
4721 views

Run the neaPay ISO8583 converter to JSON, XML, SQL, in a test environment
4720 views

Run One, Run Scenario, Run All, Run Load in the neaPay ISO8583 Simulator - Use guide
4717 views

Changing fields definitions in the ISO8583 simulator and message converter
4712 views

Enabling traces in the payments simulator
4712 views

Load Test enabling and performance testing at 1TPS and 100TPS
4712 views

Altering test cases in Excel for the ISO8583 simulator
4710 views

How the fingerprint reader works in the ISO8583 payments simulator
4710 views

Deploy the neaPay ISO8583 Payments converter in a test environment
4710 views

Sample Recommended design for an Acquirer test cases suite, Scenarios and Regression
4708 views

Regression Testing in 1 click with instant Analytics and CSV report
4663 views

Deploy the Payments Switch Router in a test environment
4561 views

BASE24-eps interview questions
4489 views

BASE24 classic ATM configuration Tutorial in ATD and XPNET with examples
4328 views

Deploy the neaPay HSM simulator in a test environment
4266 views

Add extra custom fields to the ISO8583 simulator
4085 views

BASE24 classic cards configuration tutorial with Examples
3686 views

BASE24-EPS ACI DESKTOP tutorial - Getting started
3367 views

PCI compliant with neapay switch
2859 views

ISO8583 Message Converter to XML SQL CSV interface specification mapping
2796 views

Getting started with BASE24. Compiling your first TAL program
2737 views

BASE24 classic prefix configuration tutorial CPF with examples
2667 views

BASE24 classic tracing of transactions. Audits, configuration, enabling and opening
2647 views

Getting started with Base24 development. TAL tutorial
2636 views

ACI BASE24 classic automatic extract configuration
2609 views

BASE24 classic interchange configuration with examples
2431 views

BASE24 classic balance file configuration PBF with example
2357 views

Java versions for neapay products: Simulator, Converter, Switch, Authorization, Cards Issuer - ISO8583
2339 views

BASE24 classic Institution configuration Tutorial with example
2318 views

First steps with BASE24 Classic
2120 views

Base24-eps how to create journals with esbldjnl
1942 views

Getting started with using Prognosis for BASE24 and BASE24-eps
1909 views

BASE24 classic External Message File configuration EMF with examples
1821 views

BASE24 classic host configuration tutorial HCF with examples
1725 views

POS simulator format SPDH HPDH Verifone and custom
943 views

Trace configuration in neaPay Simulator, Converter, Switch, Authorization and Cards Issuer
519 views

Iso8583 - articles


Are you ready to start or need help?


Ready to start your next project with us? Give us a call or send us an email and we will get back to you as soon as possible!

Download and Use the software yourself


Download software

Read Documentation and Start guides


Get started