Professional Documents
Culture Documents
!!
!!
FINGERPRINT TEMPLATE
Template is a digital form of ngerprint pacerns generated from the ngerprint registra?on process. This template is a text format (string)
so it is easy to be stored and distributed. Template instead of ngerprint images. Templates can not be converted into a ngerprint image.
Template is unique, meaning that if the same nger repeatedly registered then generates the templates are dierent. Templates should
not be changed because it would lead to the failure of the verica?on process. Make sure the string is stored template perfectly without
any addi?on or subtrac?on. There is only one way to compare the scanned nger on the device to the registered template by using the
verica?on func?on provided by FlexCode SDK.
!!
FINGERPRINT REGISTRATION
Fingerprint Registra?on is the process to create a template of the nger prints are scanned in the device. The same nger will be scanned
four ?mes. FlexCode SDK will generate a unique template for the nger. FlexCode SDK comes with a special algorithm to reduce the error
when the registra?on process is done, for example, scanned images are not clear enough ngers or nger posi?ons dierent in the four
ngerprint image capture. Within certain limits FlexCode SDK can s?ll produce a good and accurate template of the registra?on process
was not perfect.
!
!
Ager the declara?on, do command to ll the ac?va?on code so that the device can be used in FlexCode SDK. This ac?va?on is unique,
meaning that each device has a dierent ac?va?on code with other devices.
FPReg.DeviceInfo device_serial_number, verification_code, activation_code
For secure templates are created, the template is encrypted by using a key word that can be dened by yourself. The same keywords will
be used when the process of verica?on.
The next step, a same nger should be scanned four ?mes. Ideally fourth scanned images must be clear with the same rela?ve posi?on. In
some cases it may be FlexCode SDK will ask several repeated scans to produce a becer image, so it takes more than four ?mes in the nger
scanned on device. FlexCode SDK inform the number of ngerprint images need to generate a template through FPSampleNeeded event. So
scan your nger un?l FPSampleNeeded return a zero value.
When the ngerprint image has been created, FlexCode SDK will generate FPRegistrationImage event. Fingerprint images are available in
accordance with the dened path in PictureSamplePath. If necessary ngerprint images for documenta?on, this image can be saved by
changing the name or rename the le. Because the ngerprint template instead of the template image and can not be converted into an
image. Please add the command lines to save / change the image le name.
!2
Once the registra?on process is completed when the event returns a value of zero then FPSampleNeeded, So FPRegistrationStatus will
return r_OK value and templates will be generated in the event FPRegistrationTemplate. Furthermore, the template can be saved to your
database or le and distributed as needed.
!
!
!
!!
FINGERPRINT VERIFICATION
Verica?on is the process of comparing between the scanned nger and the ngerprint template. Verica?on can be done 1 to 1, which
means one nger scan compared with one par?cular template. Verica?on can also be done 1 to N or more suitable called iden?ca?on,
which means one nger scans compared to some of the template so that it can be determined whether there is a template that matches
the scanned nger. FlexCode SDK can do both of these means of verica?on.
!
!
FlexCode SDK can handle up to 10.000 devices ac?va?on code. Using the mul? devices in one computer is not to speed up the verica?on
process because only one device that can actually be used at a ?me.
FPVer.AddDeviceInfo(device_serial_number, verification_code, activation_code)
Next is the load ngerprint templates that will be used in the verica?on process to the SDK. Here is the command to load the ngerprint
template, FPVer.FPLoad (id, finger_index, finger_template, "MySecretKey")
This command can be called repeatedly, un?l all the required template in the SDK. FlexCode can handle up to 30000 templates in a single
verica?on. The more the number of templates are listed in the verica?on process it takes a longer ?me to be able to recognise
ngerprints scanned on device. So load templates as needed. Templates are already loaded in the SDK can be used for next verica?on
process.
To remove a template from the template list, use the command FPVer.FPUnload (id, finger_index). Use FPVer.GetFPCount command to
determine the number of templates that have been registered. To redene or eliminate the en?re templates from the SDK \ memory, use
the command FPVer.FPListClear.
The verica?on process FlexCode SDK can be done in the background, meaning that remain ac?ve even FlexCode SDK applica?on running
in non-ac?ve condi?on for example applica?on is minimized. This command requires administrator privileges on Windows Vista, 7 and 8. In
other words, you have to run the applica?on in a state run as admin. Give true value in order to arrange FlexCode WorkingInBackground
SDK can s?ll be used even if the applica?on is minimized, otherwise give a false value.
Ager the templates are load to SDK, then the verica?on process can begin. To begin the verica?on process using command
FPVer.FPVerificationStart or FPVer.FPVerificationStart id. If id not informed the SDK will verify FlexCode 1 to N, otherwise it will
verify 1 to 1. Upon this command, FlexCode SDK in a state wai?ng for a nger scanned on device.
When a nger is scanned, the FlexCode SDK will inform you if the ngerprint image is ready to be displayed through FPVerificationImage
event. If there is a template that matches the nger are scanned , then FPVerificationID event will inform the id and finger_index . If it
turns out there is more than one template that matches the scanned nger FPVerificationID the event will be called repeatedly. It is
important to prevent the registra?on of the same or similar template using dierent id or finger_index. To determine whether the nger
is recognise or not it is successful ager the process is completed, FPVerificationStatus event return v_OK if the nger is recognise and
there is only one template matching of all exis?ng templates in the SDK , v_NotMatch status if the nger is not recognise , the status
v_MultiplelMatch if there is more than one template that matches the scanned nger and other statuses in the event of failure of
verica?on or cancella?on .
!
!!
The SDK is ready for the next nger scan or do FPVerificationStop command calling for stop verica?on process. When you call
FPVerificationStop command, the loaded templates is s?ll in memory, so you can call FPVerificationStar any?me.
To start a scan of a nger, please use the FPImageStart, then the ngers can be scanned over the device. When ready ngerprint image is
displayed, FlexCode SDK will inform through FPImage event, please stored the displayed picture accordance with the purposes. To dismiss
the process of shoo?ng, calling FPImage.FPImageStop command.
!
!!
!!
In the event of failure to capture an ngerprint image, SDK will inform you via FPImageStatus event.
ATTENTION!
Do not run the registra?on, verica?on or ngerprint image class together. One moment only one class is allowed to use the device.
!!
!!
!
!!
!!
!
!!
!!
!!
!!
4.