“Which device fits what we are building?”
Start with the host equipment and customer interaction. A USB scanner, a dedicated terminal and a payment POS serve different integration needs.
Your Palm, Your ID
From a palm scan
From a palm scan
to a working
customer journey.
Building palm vein payment or identity verification? Define the device, application and backend responsibilities before you start integrating.
For product teams, developers and solution providers.
Start with the problem
A scanner is one part
A scanner is one part
of the solution.
Customers need a complete journey: enrol a user, recognise their palm, identify the right account and complete the intended action. Make each responsibility clear.
“What does the SDK do, and what do we build?”
Separate palm capture and matching from your account database, middleware, cashier connection and payment decisions.
“Can we start small without losing the path to scale?”
Use a defined pilot to validate the journey. Plan identifiers and required source images before a later large-model migration.
Choose by use case
Tell us where
Tell us where
the palm scan happens.
Select the closest scenario to see a starting route. Final compatibility depends on your hardware, operating environment and workflow.
Explore the USB scanner route
PalmVein01 / PalmVein01 Pro can be assessed for integration with a compatible host. Confirm USB data access, power supply, OS and SDK requirements before choosing.
Explore a dedicated palm vein terminal
WavePass500 can be evaluated for a dedicated registration or identity workflow. Your application and backend still need to be integrated for your business use case.
Assess AirOne for your payment workflow
AirOne combines a POS platform with palm vein capture. Confirm payment application integration, acquiring requirements and the intended checkout experience with your payment team.
A POS USB port must support data communication and the required host permissions. A charging-only port cannot provide a scanner integration.
Windows, Linux and Android SDK options are available. Confirm the exact SDK, language and model requirements for your project.
Understand the integration boundary
Palm recognition supplies a result.
Palm recognition supplies a result.
Your platform decides the action.
For server-side palm vein authentication, keep biometric matching and your business workflow connected through a clearly defined integration.
01 / Terminal
Capture the palm
Use the supplied SDK to capture palm data and extract device-side features.
02 / Your backend
Route the request
Manage authentication, account context and communication with the algorithm service.
03 / Algorithm service
Return the match
Provide the biometric matching result, including the matched user identifier when successful.
04 / Your application
Complete the workflow
Apply your account, transaction or access logic and display the outcome.
| Component | Role in the project |
|---|---|
| BioWavePass hardware & SDK | Palm capture, device-side feature extraction and documented integration interfaces. |
| Algorithm service | Biometric matching under the selected architecture and registered-user capacity. |
| Your application & middleware | User interface, account binding, API formats, callbacks, authentication and business workflow. |
| Your payment platform | Payment processing and transaction decisions within your payment or wallet integration. |
For palm vein payment, a successful match is an input to your authorisation process. It does not itself execute or approve a financial transaction.
A practical entry point
Validate a real journey.
Validate a real journey.
Start with a small pilot.
10,000
registered IDs
Free small-model algorithm deployment on your own server, with no licence expiry date.
- Define one initial use case.
- Test registration and account binding.
- Validate matching and error handling.
- Review the actual user experience.
The free offer covers the small-model algorithm deployment. Hardware, infrastructure and application development are separate.
Your pilot checklist
What is ready
What is ready
before testing begins?
0 of 5 preparation items reviewed
Use this as a discussion checklist. It does not certify production readiness.
Make future migration easier
Prepare the data
Prepare the data
before the user base grows.
Moving from the small model to the large model is more than changing a licence. Your data, SDK integration and account mappings need a migration plan.
Keep registration identifiers in your own backend. For a future large-model migration, retain the required RGB and IR source images under your approved data-handling policy. If those images are unavailable, users may need to re-enrol.
Validate before switching traffic
The services are independent. The same terminal application can support both with the necessary integration. Test the new flow before retiring the old one.
Map featureId to user_id
Update small-model featureId bindings to the corresponding large-model user_id. Stop old-service requests and securely delete retired biometric data when appropriate.
Practical integration FAQ
Resolve the questions
Resolve the questions
that hold projects back.
Focused answers for the team building the application, not just selecting the scanner.
12 questionsCan we connect a USB palm vein scanner to an existing POS?
Only if the POS supports the required USB data connection, host permissions and power supply. Many POS USB ports are designed only for charging. Provide the make, model and operating system for compatibility assessment.
Which operating systems can we integrate with?
SDK options are available for Windows, Linux and Android. Confirm the specific SDK package and development language before implementation. Host-system USB permissions and restrictions must also be checked.
Can we customise the API requests and payment workflow?
Your team can design middleware APIs, request and response formats, authentication, callbacks and payment logic. Changes to core SDK or algorithm-service interfaces need a separate custom-development assessment.
Does the SDK store our registration identifiers?
The SDK does not retain registration feature IDs for your business platform. Your backend must store the returned identifiers and bind them to the appropriate user or account.
What is included in the free small-model option?
A free algorithm deployment on your own server supports up to 10,000 registered user IDs with no expiry date. Hardware, server infrastructure and application/backend development are separate.
Can we delete users and register new ones?
Yes. Deleting a registered user frees capacity for another registration. The capacity is not a cumulative count of payment transactions or all registrations ever performed.
Do we need original palm images for the large model?
The large-model workflow requires the relevant RGB and IR source images in addition to its feature workflow. Plan image retention before migrating from the small model. If required images are unavailable, re-enrolment may be necessary.
Can one application support the small and large models during migration?
Yes, the services are independent. The terminal application can support both with the necessary SDK and backend integration. Validate identifier mappings and the target workflow before switching business requests.
Will server-side palm vein matching work without connectivity?
Server-side matching requires a network path to your backend and algorithm service. Offline server installation does not provide device-local matching. Discuss local matching separately if that is your requirement.
Does a successful palm match complete a payment?
No. The algorithm supplies the biometric matching result. Your backend and payment application decide how to use it for account verification and transaction authorisation. Payment processing stays within your payment integration.
Can BioWavePass help develop or review our application?
Additional support can be assessed after you provide detailed tasks, the existing architecture and expected deliverables. Scope, implementation time and commercial terms depend on those requirements.
How long will our integration take?
There is no universal integration timeline. Hardware compatibility, developer familiarity, backend readiness and business requirements all affect delivery. Algorithm deployment estimates should not be treated as a complete application-development schedule.
Move from questions to scope
A clearer brief.
A clearer brief.
A more useful discussion.
Share your intended workflow and technical environment so the right products, integration support and deployment approach can be assessed.
Additional application development or platform review requires specific requirements and expected deliverables before a timeline or cost can be estimated.
This planner runs in your browser. Nothing is submitted until you choose to send an email.
BioWavePass project enquiry
Application: Existing PC, kiosk or ATM
Initial population: Up to 10,000 users
Project details: To be provided
Please confirm: host model and OS, development team, server/matching requirements, pilot location and timeline.
Discuss your project ↗