Contact Us

Get in touch with our team to discuss your palm vein recognition needs

Privacy Notice: Your information is secure and will only be used to respond to your inquiry. We typically respond within 24 hours during business days.
Solutions / Biometric continuity
BioWavePass

Register today.
Recover and upgrade tomorrow.

Build resilience into Palm Vein Recognition and Palm Vein Payment Technology. Retain original RGB and IR palm images to rebuild biometric features and support large-model upgrades—with less disruption for registered users.

Explore recovery Plan a model upgrade
Contactless palm recognition Illustrative scene
01 / CAPTURE
RGB IR
Two images per hand

Palm print + palm vein

02 / RETAIN
Secure image storage

Linked to the correct user ID

03 / RE-EXTRACT
Rebuild or upgrade

Generate biometric features again

01 / CONTINUITY BY DESIGN

One image retention strategy. Two long-term benefits.

Keep original captures alongside your biometric workflow. When infrastructure fails or your algorithm evolves, retained images provide a source for new feature extraction.

Upgrade algorithms

Use retained images to support new server-side feature extraction without asking users to register again.

Recover lost features

Rebuild biometric features from retained images if the production server or its feature data is lost.

Preserve continuity

Keep the original capture associated with each user as your platform evolves.

02 / UPGRADE WITHOUT STARTING OVER

What each model needs

The original images and the extracted feature vectors serve different purposes.

One registered hand. Two complementary inputs.
RGB CHANNEL
RGB Palm print image Surface patterns
Feature extraction Encode the capture
Palm print features Used for matching
INFRARED CHANNEL
IR Palm vein image Vein patterns
Feature extraction Encode the capture
Palm vein features Used for matching

Keep the source images and user associations so features can be extracted again.

Small model
Large model
End-side features

Matching uses palm print and palm vein feature vectors extracted on the device.

Original images are not required for current matching, but retaining them is recommended.

End-side + server-side features

Uses device-extracted features together with features extracted again on the algorithm server.

Retain both RGB and IR images, plus both feature vectors, to support this model.

03 / REBUILD FROM THE ORIGINALS

Disaster recovery for Palm Vein Recognition

If the production server suffers a complete physical failure, securely retained palm images can support rebuilding the biometric feature database on a replacement server.

From retained images to restored matching
01 Image backup RGB + IR + user ID
02 Replacement server Algorithm + license
03 Rebuild features Re-extract and link
04 Validate matching Then resume service
  1. Retrieve retained RGB and IR images

    Restore the images and their user associations from your backup infrastructure.

  2. Prepare the replacement matching server

    Deploy the algorithm service and arrange the corresponding license.

  3. Re-extract biometric features

    Generate features from the retained images and rebuild their links to user records.

  4. Validate before resuming service

    Check restored records and matching through your backend recovery procedures.

Image retention supports biometric recovery. Your own backend manages the wider data, operations and disaster recovery process.
04 / CHOOSE YOUR BACKUP APPROACH

Does a backup server need its own license?

It depends on whether the BioWavePass algorithm service is deployed on that server. The algorithm service performs palm ID matching and biometric authentication within your platform.

Store the images

RGB + IR images → Backup storage
No algorithm service deployed
No additional algorithm license

Run biometric matching

Algorithm service → Palm ID matching
Deployed and ready for recognition
Corresponding license required
Choose the backup server’s role

No additional algorithm license

The server only stores original palm images for recovery. The algorithm service is not deployed on it.

A corresponding license is required

The algorithm service is deployed on this server and ready to perform biometric matching, so the server requires a corresponding algorithm license.

A storage-only backup does not provide matching. Deploying a matching service during recovery requires the corresponding licensing arrangements.
05 / PLAN YOUR INTEGRATION

Image retention for Palm Vein Payment Technology

For a palm vein payment system, this guide covers the biometric registration and matching layer. Payment processing, user data and disaster recovery remain part of your own backend infrastructure.

  • Save both capture types. Each registered hand has one RGB image and one IR image. Two-hand registration therefore produces four images.
  • Keep quality-approved captures. Retain images that pass the SDK’s registerPalm quality check.
  • Associate images with the user. Store them with a unique user ID and identify the hand and image type.
  • Protect the retained data. Plan secure storage, controlled access and backup procedures within your backend infrastructure.
Where can developers find image-saving sample code?

Refer to the ImageUtils class in the SDK demo project. It demonstrates converting a data stream into a Bitmap and saving it locally. Integrate the image-saving process into your own registration and storage workflow.

Do we have to register both hands?

No. The demo supports two-hand registration, but your application can register one or both hands. Retain one RGB image and one IR image for each registered hand.

Who manages the disaster recovery process?

Your backend infrastructure manages operations, user data, storage and recovery procedures. The BioWavePass algorithm service provides the palm ID matching function within that platform.