Deptrum Products for Palm Recognition

This Deptrum official resource explains Deptrum Products for Palm Recognition from the perspective of practical project evaluation, helping business, product, and technical teams understand key concepts, deployment questions, and next-step discussion points for palm recognition and biometric terminal projects.

Deptrum products in this portfolio include Deptrum’s palm recognition solutions for B2B deployment: VeinShine 01, VeinShine 02, VeinShine 03, VeinShine 04, HandPass 521, and V6. Together, these products cover palm biometric authentication across module integration, fixed terminals, and mobile identity verification, helping project teams match palm recognition technology to payment-related identity authentication, access control, attendance, visitor management, and public-service identity verification needs.

Deptrum Palm Recognition Product Scope

Deptrum offers palm recognition products for organizations that need a touch-free, active authentication flow in which the user intentionally presents a palm to a device or terminal. For B2B buyers, that usually means choosing between an embedded module for a larger device or workflow, a fixed terminal for controlled entry points, or a mobile terminal for flexible field use.

Deptrum's product line includes:

• VeinShine 01 for payment-related identity authentication projects
• VeinShine 02, VeinShine 03, and VeinShine 04 for palm recognition module integration in non-payment scenarios
• HandPass 521 for fixed terminal deployments
• V6 for mobile identity verification scenarios

Across this portfolio, Deptrum supports palm biometric authentication as the core business topic. Where project design calls for a more technical discussion, Deptrum can also support palmprint and palm vein dual-modal recognition concepts, including near-infrared palm vein imaging in relevant module-based solutions. The practical point for buyers is simple: the right product depends less on a generic device category and more on where authentication happens, how users enroll, and what system the palm-recognition layer needs to connect with.

VeinShine Modules for Palm Recognition Integration

Deptrum’s VeinShine family is intended for solution teams that need to build palm recognition into a kiosk, self-service machine, industry terminal, gate, or other project-specific device.

VeinShine 01 for payment-related identity authentication

VeinShine 01 is the main Deptrum product to discuss when a project involves payment-related identity authentication. In these deployments, palm recognition acts as an identity authentication entry point within a broader workflow. That broader workflow may still depend on merchant systems, account systems, authorization logic, settlement processes owned by other platforms, and local compliance requirements.

This matters for project planning because the palm-recognition component is only one part of the full service flow. Teams often need to define:

• how the user binds identity to an account
• where authentication happens in the checkout or service journey
• how the terminal exchanges data with the surrounding business system

For integration-oriented teams, VeinShine 01 can fit projects where a palm-recognition module is being embedded into a purpose-built terminal or payment-adjacent device. VeinShine 01 is described with close-range palm presentation and a USB Type-C interface, which is useful when planning enclosure design and host-device integration.

VeinShine 02, VeinShine 03, and VeinShine 04 for non-payment integration

For non-payment palm recognition projects, Deptrum offers VeinShine 02, VeinShine 03, and VeinShine 04 as module-level options for system integration. These products are relevant when a partner is building or adapting a device for:

• self-service kiosks
• access control equipment
• attendance terminals
• industry terminals
• identity authentication touchpoints

These modules are useful when the project owner wants more control over industrial design, workflow logic, user interface, or host-system architecture.

A few practical examples:

• VeinShine 02 fits general-purpose integration into kiosks, self-service devices, and access-oriented terminals.
• VeinShine 03 fits smaller-scale or edge deployments such as single-site access control, small offices, small stores, or compact verification points.
• VeinShine 04 fits terminal integration projects that need project-specific adaptation around the palm-recognition component.

Several deployment details may also matter during evaluation. Some VeinShine models support close-range palm presentation around 5 to 12 cm, and some models use USB 2.0-based integration paths. Deptrum Palm SDK support on Windows, Linux, and Android is also relevant for teams planning secondary development, though exact software architecture should be matched to the selected model and project design.

HandPass 521 and V6 Terminal Options

When the project does not call for an embedded module, the more useful question is whether the site needs a fixed terminal or a mobile terminal.

HandPass 521 for fixed-site deployments

HandPass 521 is the fixed terminal option within Deptrum’s palm recognition portfolio. It is a practical fit for sites where the authentication point is stable and repeatable, such as:

• access control at building entrances
• attendance points
• visitor management desks
• smart building entry
• campus, library, venue, or data center access
• fixed identity verification points

For these deployments, fixed placement helps project teams standardize user interaction, lane or doorway design, registration guidance, and backend permissions. HandPass 521 is therefore relevant when a customer wants palm recognition at a known location rather than as a built-in subsystem inside another machine.

V6 for mobile identity verification

V6 is Deptrum’s mobile terminal option for teams that need palm biometric authentication away from a permanent access point. It is suited to scenarios such as:

• temporary service points
• visitor registration
• mobile counters
• events and exhibitions
• public-service field checks
• on-site identity verification in changing environments

The main value of V6 is deployment flexibility. Instead of redesigning a kiosk or installing a fixed terminal at every touchpoint, teams can bring the authentication tool to the user. That makes V6 relevant for programs that need seasonal capacity, temporary registration, roaming staff workflows, or pop-up service operations.

Matching Products to Payment, Access Control, and Identity Verification Scenarios

The easiest way to understand Deptrum products is to map them to the scenario first and the hardware form second.

A few scenario-specific notes are especially important for B2B planning.

Payment-related identity authentication

In retail, hospitality, venue, or campus service flows, Deptrum palm recognition can support the identity authentication layer around a payment-related interaction. That can include checkout counters, self-service devices, lockers, member-service points, or other service touchpoints where the user intentionally presents a palm.

The key design principle is that Deptrum’s role is the authentication entry point, not payment clearing or transaction settlement. A full deployment typically needs to work with external account systems, merchant systems, authorization logic, and other payment-related infrastructure.

Access control and attendance

For offices, campuses, libraries, venues, and controlled facilities, the palm-recognition decision is often about throughput, user convenience, and reducing dependence on cards or shared touch surfaces. HandPass 521 is the natural fit when the site wants a fixed terminal, while VeinShine modules are useful when access control needs to be embedded into a custom gate, turnstile, or integrated terminal.

Identity verification and public service

For public-service operators or field programs, the right choice often depends on whether the authentication point is permanent or mobile. V6 suits temporary counters and in-field checks, while fixed terminals or embedded modules are better when the workflow is tied to a stable location.

Evaluation Checklist for Integrators

For system integrators and solution teams, product selection should be tied to deployment logic rather than model names alone.

Start with these questions:

1. Where will authentication happen?
   Decide whether the project needs an embedded module, a fixed terminal, or a mobile terminal. This affects enclosure design, mounting position, queue flow, and service staffing.
2. How will users register?
   Enrollment design influences the whole project. Teams should define who registers users, where registration takes place, how identity is linked to accounts or permissions, and how exception handling works.
3. What systems need to connect?
   Palm recognition projects often need interfaces to access control platforms, visitor systems, attendance platforms, self-service software, merchant systems, or public-service databases. Interface planning should happen early, especially when a custom terminal or kiosk is involved.
4. What deployment model fits the project?
   Some projects prefer local processing, some use cloud-connected workflows, and some combine both. The right approach depends on site operations, network conditions, data-governance preferences, and the selected product architecture.
5. How will the terminal be maintained?
   Maintenance planning should cover device placement, field cleaning, user guidance, software updates, replacement strategy, and support ownership across the integrator and end customer.
6. What privacy review is required?
   Palm biometric authentication projects usually need a review of consent flows, access rights, template handling, data retention rules, and local legal or organizational requirements. These decisions belong in the project plan, not at the end of deployment.

This evaluation approach helps buyers narrow the real decision: not just “Which device is available?” but “Which product role fits the site, workflow, and integration path?”

How to Discuss Product Fit with Deptrum

A productive discussion with Deptrum usually starts with the scenario, not the model number. If your team is evaluating palm recognition, it helps to define:

• the primary use case
• whether the project needs module integration, a fixed terminal, or mobile verification
• how users will enroll and authenticate
• which external systems the project needs to connect with
• whether the site is a campus, workplace, venue, hospitality, retail, or public-service environment

With that information, Deptrum can help focus the conversation on the most relevant products, integration path, and deployment considerations for the project.

Contact Deptrum to discuss palm recognition and palm biometric solutions for your project.

FAQ

What are Deptrum products in the palm recognition portfolio?

Deptrum products in this palm recognition portfolio include VeinShine 01, VeinShine 02, VeinShine 03, VeinShine 04, HandPass 521, and V6. They cover module integration, fixed terminals, and mobile identity verification within Deptrum’s palm recognition portfolio.

Which Deptrum product is used for payment-related identity authentication?

VeinShine 01 is the primary Deptrum product for payment-related identity authentication. It works as part of the authentication layer in a larger payment-related workflow, alongside merchant, account, and authorization systems.

Which Deptrum products fit access control and attendance projects?

HandPass 521 fits fixed-site access control, attendance, and visitor-management style deployments. VeinShine 02, VeinShine 03, and VeinShine 04 are also relevant when access control needs to be built into a custom terminal, gate, or kiosk.

What is the difference between HandPass 521 and V6?

HandPass 521 is designed for fixed deployments such as entrances, attendance points, and visitor desks. V6 is designed for mobile identity verification, temporary service points, field checks, and other scenarios where the authentication point moves with the workflow.

Are VeinShine products modules or finished terminals?

VeinShine 01, VeinShine 02, VeinShine 03, and VeinShine 04 are module-oriented products for integration projects. HandPass 521 and V6 are the terminal-oriented options for teams that need fixed or mobile deployment forms.

Can Deptrum palm recognition be integrated into kiosks or self-service devices?

Yes. VeinShine 02, VeinShine 03, and VeinShine 04 are the most relevant Deptrum products for kiosk, self-service, and industry-terminal integration projects. The exact fit depends on the device design, user flow, host system, and deployment architecture.

Does Deptrum support palm biometric authentication with palm vein recognition?

Deptrum supports palm biometric authentication, and technical discussions can include palm vein recognition where project requirements and product fit call for it. Near-infrared palm vein imaging and Palm AE can be part of relevant palm-recognition-based solutions.

What should integrators prepare before selecting a Deptrum product?

Integrators should prepare the scenario definition, enrollment workflow, terminal placement plan, interface requirements, deployment model preference, and privacy-review considerations. That preparation makes it much easier to decide whether the project should use VeinShine modules, HandPass 521, or V6.