Provides feature-rich, high-level “Biometric Service Provider” APIs for fingerprint enrollment and verification, with optimized, self-contained UI widgets for quick development and short time-to-market

Features

Easy to Integrate
SecuGen SDKs make it quick and easy to integrate SecuGen fingerprint scanning, template generation (minutiae extraction), and template matching functions (both one-to-one and one-to-many) into almost any type of software application.

Flexible for Most Development Needs
SecuGen SDKs are available as low-level API (“FDx”) and high-level API (“BSP”) packages that support a wide range of operating systems and development environments.

Support for Leading Biometric Standards
Many SecuGen SDKs support U.S. and international biometric standards and include algorithms that have been intensively tested by NIST for compliance.

Complete Documentation
Every SDK includes full documentation to assist with development and deployment.

Available Free of Charge
SecuGen SDKs are available free of charge using our online request form.

Additional Information

One-to-one (1:1) matching is typically used in cases where security is a high priority. This method is more secure than 1:N because 1:1 matching requires the person to present information that identifies themselves, as described below.

Using a 1:1 template matching algorithm is called “authentication.” This means that something is already known about a person. This information can be a customer ID, name, driver’s license number, etc., and it is stored with that person’s fingerprint template in a database. Using that information, the programmer obtains that person’s fingerprint template from the database and then attempts to match that template with a template created from a newly captured fingerprint. If they match, then the person’s identity is said to be verified or authenticated.

One-to-many (1:N) matching is typically used in cases where convenience is a high priority. This method is fast and requires no previous knowledge of the person.

Using a 1:N template matching algorithm, such as SecuSearch, is called “identification.” In this situation, no information about the person is required for the matching process except that their fingerprint must have been previously enrolled in the SecuSearch database. To identify a person, a new fingerprint is captured, and the template extracted from this fingerprint is compared to the fingerprint templates stored in the SecuSearch database. If a match is found, then the person is said to be identified.

FDx SDK provides low-level APIs giving you maximum flexibility in designing custom built applications. The tools provided give you complete, more detailed control of the SecuGen fingerprint reader such as brightness, auto-on, liveness detection levels, device information and image size. Pre-made UI are not provided with the FDx SDK.