Posted on 20th Oct 2018 6950 views
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.
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.
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.
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.
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.
BIN List & Range for MasterCard, Visa, Amex, Diners, Discover, JCB, CUP 165510 views
ISO8583 Response Codes for Transaction processing 67162 views
Read smart card chip data with APDU commands ISO 7816 63801 views
ISO8583 Processing Codes for Transaction Processing 31368 views
ISO8583 Message Types for Transaction Processing 31360 views
Deploy, run and generate with neaPay Card Data Generator 21438 views
MCC Codes - Merchant Category Codes to use in ISO8583 Field 18 20975 views
Run the neaPay ISO8583 simulator 20907 views
ISO8583 payments message format, programmers guide 18430 views
ISO8583 message: The list of ISO 4217 currency codes for data elements 49 and 52 17576 views
ISO8583 ATM POS Crypto API integration with exchanges like Coinbase or Binance 17060 views
ISO8583 Message Converter JSON and XML interface specification mapping 14003 views
Cards and Banks Training 13626 views
Java version for neapay products Simulator Converter Switch Authorization Cards Issuer 10691 views
Support for the neaPay products: Authorization, Switch, Converter, Simulator, Issuer 10118 views
Log Files in BASE24 classic 9819 views
Create a new test case in the neaPay ISO8583 simulator Video guide 9092 views
BASE24 classic vs BASE24-eps 8784 views
BASE24 documentation to read 8629 views
BASE24 classic interview questions 8558 views
Deploy the neaPay ISO8583 simulator - video guide 8499 views
EMV explained for programmers 8189 views
ISO8583 Simulator neapay- Performance testing at 500, 1000 and 1500 Transactions per second 8114 views
ISO8583 converter to JSON XML SQL to HTTP host - message flow - video guide - Part.2 7773 views
ISO8583 converter to JSON XML SQL to HTTP Host - host unavailable - video guide- Part.3 7298 views
Adding your own card to the Payments simulator to test your system 7146 views
ISO8583 converter to JSON XML SQL to HTTP host - start& run - video guide - Part.1 7142 views
Card readers supported by neaPay payments simulator, CHIP and NFC 7073 views
Changing fields definitions in the ISO8583 simulator and message converter 7054 views
Connect the neaPay ISO8583 Acquirer simulator to your own host or Issuer 7031 views
Run the neaPay ISO8583 converter to JSON, XML, SQL, in a test environment 7028 views
BASE24 classic screens examples explained 7021 views
Run One, Run Scenario, Run All, Run Load in the neaPay ISO8583 Simulator - Use guide 6975 views
Load Test enabling and performance testing at 1TPS and 100TPS 6973 views
Sample Recommended design for an Acquirer test cases suite, Scenarios and Regression 6965 views
Enabling traces in the payments simulator 6959 views
How the fingerprint reader works in the ISO8583 payments simulator 6951 views
Altering test cases in Excel for the ISO8583 simulator 6942 views
Deploy the neaPay ISO8583 Payments converter in a test environment 6938 views
BASE24-eps interview questions 6877 views
Deploy the neaPay HSM simulator in a test environment 6797 views
Regression Testing in 1 click with instant Analytics and CSV report 6656 views
Deploy the Payments Switch Router in a test environment 6538 views
BASE24 classic ATM configuration Tutorial in ATD and XPNET with examples 6242 views
Add extra custom fields to the ISO8583 simulator 6148 views
BASE24 classic cards configuration tutorial with Examples 6138 views
Trace configuration in neaPay Simulator, Converter, Switch, Authorization and Cards Issuer 6117 views
PCI compliant with neapay switch 5728 views
ISO8583 Message Converter to XML SQL CSV interface specification mapping 5691 views
BASE24-EPS ACI DESKTOP tutorial - Getting started 5525 views
BASE24 classic prefix configuration tutorial CPF with examples 4091 views
BASE24 classic tracing of transactions. Audits, configuration, enabling and opening 3950 views
ACI BASE24 classic automatic extract configuration 3644 views
BASE24 classic Institution configuration Tutorial with example 3608 views
BASE24 classic balance file configuration PBF with example 3522 views
POS simulator format SPDH HPDH Verifone and custom 3468 views
First steps with BASE24 Classic 3369 views
Getting started with using Prognosis for BASE24 and BASE24-eps 3087 views
ISO8583 simulator Visa MasterCard Amex CUP configuration demo video 315 views
Swift Message Structure ISO 15022 and ISO 20022 72 views
SWIFT Message types complete list reference 72 views
ISO8583 simulator scheduling tasks and test regressions 69 views
POS Transaction types explained 66 views
Convert ISO8583 to JSON XML SQL
ISO8583 Interface Handler
Convert ISO20022 to ISO8583 ...
Build ISO8583 from scratch
ISO8583 Router by criteria
Authorize cards and ledger
Acquiring host from devices
Generate and issue cards
ISO8583 HISO98 HISO87 simulator
ISO20022 & SWIFT simulator
POS protocols simulator
Web API tester Performance
Get a free quote, Ask for details
Get help
Try the software yourself
Download
Read Documentation and Start guides
Online Tools Overview