BioWavePass FAQs

Ensure your server IP and port (e.g., 8080 or 443) are externally accessible. The free small-scale algorithm supports IP + Port access only, not domain-based access. Domain access requires an upgrade to the licensed large-scale algorithm.

The free small-scale algorithm supports only direct IP access. Full domain-based communication is supported only after upgrading to the paid large-scale algorithm license.

Clients must generate and configure their SSL certificates. Example commands:

openssl genpkey -algorithm RSA -out private.key -pkeyopt rsa_keygen_bits:2048
openssl req -new -key private.key -out csr.pem
openssl x509 -req -in csr.pem -signkey private.key -out public.crt -days 365

Verify the server deployment and endpoint configuration are complete, correct, and the IP + port are accurate. Correct endpoint access example:

https://<your_server_ip>:<port>/palm/query

A non-404 response indicates the server is reachable.

For database-level integration, ensure MySQL port 3306 is open and accessible externally.

Yes. BioWavePass supports remote testing. After deploying your server, contact the X-Telcom team. We’ll remotely test registration and authentication using our Palm Vein Reader to confirm data reaches your server.

• Palm Vein Scanner captures RGB+IR images
• RGB+IR feature strings are extracted
• Feature strings are sent to the algorithm server for registration
• Algorithm server returns a featureId
• Bind featureId with user information and store it in your enterprise database

• Small-scale projects (<10,000 users): Only RGB+IR feature strings are necessary
• Large-scale projects (>100,000 users): Pre-saving RGB+IR images is recommended for future upgrades

Saving images ensures users won't need to re-register when upgrading to the large-scale algorithm.

No. Feature strings are extracted directly from live captures only. Images saved are for future upgrades to the larger-scale algorithm.

This indicates the palm feature already exists on the algorithm server. Use the deleteId API to delete existing data before re-registration.

Typically due to incorrect installation or insufficient permissions, not version compatibility. Verify with commands:

mysqld --version
sudo systemctl status mysql

No. The current version requires MySQL installation directly on the host server, Docker containers are not supported.

Yes, by modifying the provided DbManager.java demo code to support remote MySQL. This is essential for building an enterprise backend system.

• Android-based Palm Vein Reader hardware
• Palm recognition algorithm server (small-scale free model and licensed large-scale model)
• Android SDK and PalmClient demo application
• Remote testing, integration guidance, and customized APK testing
• Assistance in building and deploying MVP versions

Supports Android, Linux, and Windows.

Yes. It can be done through a plugin. A plugin layer needs to be built for use in a Flutter app.

The original Palm Vein SDK is developed in Java, while Flutter uses the Dart language—so they are based on different technology stacks and are not directly compatible.

However, some clients have successfully integrated the SDK by using Flutter’s platform channel to call Java methods, enabling palm vein registration and identification. Alternatively, a plugin layer can be built for Flutter integration.

Currently, we do not provide native Flutter support and only offer a Java-based SDK. You have two options:

• Your Flutter engineers can develop a middleware plugin to invoke Java SDK methods (e.g., bind and retrieve palm-user data);
• Or contact [email protected] — our Indian developer team can evaluate your app architecture and offer a paid Flutter plugin development service.

The Palm Vein SDK is designed for Java environments and comes with a reference demo showcasing:

• Palm registration linked to a custom User ID
• Palm identification to return the associated User ID
• A full demonstration of business logic for rapid system integration

The SDK includes interfaces for database interaction (e.g., storing and matching feature IDs). Matching occurs locally on the client’s private server.

We support up to 10,000 users during the MVP testing phase for free. If your user base exceeds this, you may purchase a large-scale matching algorithm package for enhanced accuracy and image-based matching.

There are no server fees—all processing runs on your own infrastructure. You are also welcome to customize the demo source code and integrate your own APIs or business workflows.