Your web application
Shows the user interface and sends an instruction when enrollment or identification is needed.
PalmVein01 · Web integration
Bring palm vein recognition into your web application.
Keep your existing web workflow. A Windows background service built with the C++ SDK handles palm scanning, while your application decides when to start and what to do with the result.
No direct Web SDK.
Your web app sends instructions to the Windows service; the service manages scanner instructions.
BioWavePass PalmVein01
USB · RGB + IR
1
Web application
Controls the business workflow
Controls the business workflow
2
Windows C++ service
Controls palm scanning
Controls palm scanning
3
Your architecture
Determines where matching runs
Determines where matching runs
The integration path
How does PalmVein01 work with a web application?
The browser does not call the biometric SDK directly. Your Windows program acts as a bridge between the web workflow and the USB scanner.
Windows palm service
A C++ program you build with the SDK receives the request and manages the scanner-level instructions.
PalmVein01
Captures the palm data required by the selected biometric workflow. The service returns the outcome to your app.
Your web application manages service-level instructions. The Windows service manages palm-scanning instructions.
Choose the matching location
Cloud or local matching?
The version you need depends on where biometric matching takes place. A server that only distributes features between local devices is different from a server that performs matching.
Match on your server
Choose this route when matching runs on infrastructure you control, including a private server or private cloud.
- Designed for centralized or multi-location systems
- Plan the algorithm model around your enrolled-user count
- Above 10,000 users, plan for the large-model architecture and migration of original enrollment images
Match on the Windows PC
Choose this route when the local device environment performs matching. A local server may distribute enrolled features between devices; it does not perform the match.
- Local matching takes place on the Windows device
- Supports up to 10,000 enrolled users per device
- Capacity does not expand beyond that local limit
Decision guide
Which PalmVein01 version fits your system?
Start with the matching location, then check the size of your enrolled population.
Matching on your cloud or private server
PalmVein01 Cloud
Matching directly on the local Windows PC
PalmVein01 Local
More than 10,000 enrolled users
Cloud · large-model architecture
Up to 10,000 users matched on each local device
PalmVein01 Local
End-to-end workflow
From a web request to a business decision.
Keep device control and business logic in their proper places.
STEP 01
Request
The web app asks the Windows service to start a scan.
STEP 02
Control
The service sends scanner instructions through the C++ SDK.
STEP 03
الالتقاط
PalmVein01 captures the presented palm.
STEP 04
تطابق
Matching runs locally or on your server, according to your architecture.
STEP 05
Continue
The result returns to the web app for the next business step.
Plan your integration
Discuss your integration →
Not sure which architecture you need?
Tell us where your application runs, where you want matching to happen, and how many users you expect to enroll. We can help you evaluate the PalmVein01 version and SDK approach.