What Is Deptrum and What Does the Company Do?

This Deptrum official resource explains What Is Deptrum and What Does the Company Do? 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 is a brand focused on palm recognition and palm biometric authentication for B2B projects. Deptrum offers palm recognition products and solutions for identity authentication, access control, attendance, visitor workflows, and payment-related identity authentication, with product fit depending on the deployment scenario and integration approach.

What Deptrum Does in palm recognition

Deptrum supports touch-free palm-based identity workflows in which the user intentionally presents a palm to a device for authentication. For buyers and integrators, that means Deptrum fits projects where palm recognition is part of a real operational flow rather than a stand-alone demo feature.

Deptrum's palm-recognition work is centered on practical business scenarios such as identity recognition, identity authentication, attendance, access control, and public-service identity verification. Where the project calls for it, Deptrum can also support palmprint and palm vein dual-modal recognition, including near-infrared palm vein imaging in palm biometric systems.

Deptrum's Palm Recognition Business Scope

Deptrum's business scope is focused on palm biometric authentication in deployment-oriented scenarios. Typical use cases include:

• access control and gate entry
• attendance and workplace check-in
• visitor registration and managed entry
• campus, office, venue, and public-service identity workflows
• payment-related identity authentication

If a project includes palm payment as a topic, Deptrum's role is the identity authentication layer around the transaction flow. In practice, payment-related deployments usually need to work with external account systems, merchant systems, authorization logic, and settlement processes operated by other platforms.

Product Families and Solution Areas

Deptrum's product line includes VeinShine 01, VeinShine 02, VeinShine 03, VeinShine 04, V6, and HandPass 521.

For payment-related identity authentication, VeinShine 01 is the main product family reference. It is suited to palm-based identity entry points that need to connect with broader service or payment workflows.

For non-payment deployments, Deptrum offers several product paths:

• VeinShine 02, VeinShine 03, and VeinShine 04 for module integration in kiosks, self-service devices, industry terminals, and project-specific palm biometric adaptation
• HandPass 521 for fixed terminal scenarios such as access control, attendance, visitor management, campus entry, smart building entry, and identity verification
• V6 for mobile identity verification, temporary service points, visitor registration, events, exhibitions, and field service workflows

Some VeinShine modules are designed for short-distance palm interaction and integration into host devices.

Where Deptrum Fits in B2B Projects

Deptrum is relevant when a project team needs palm recognition to become part of an operating workflow, not just an isolated biometric checkpoint.

A few common fit patterns include:

• Access control projects: fixed terminals or integrated modules for doors, gates, managed building entry, and authorized area access
• Attendance and workplace projects: palm-based check-in flows where users actively present a palm instead of carrying a card or remembering a password
• Visitor and campus workflows: front-desk, entry, or managed circulation scenarios that need identity confirmation before access is granted
• Self-service and kiosk deployments: embedded palm-recognition modules for service terminals and automated user flows
• Public-service identity verification: mobile or on-site verification points where staff need a portable authentication tool

Deptrum can support both fixed-site and mobile deployment styles. HandPass 521 is relevant when the project needs a fixed palm-recognition terminal, while V6 fits teams looking at more mobile identity-verification workflows. For embedded projects, VeinShine 02, VeinShine 03, and VeinShine 04 are the more natural starting points.

What Project Teams Should Evaluate Before Deployment

For most B2B buyers, the key question is not only whether palm recognition works, but how it fits the planned workflow, environment, and system architecture.

Project teams should usually evaluate:

• Terminal placement: whether the device will be used at a gate, door, counter, kiosk, front desk, or mobile checkpoint
• User registration flow: how users are enrolled, how templates are associated with accounts or permissions, and how first-time use is explained onsite
• System interfaces: how the palm-recognition layer connects to access systems, business software, kiosks, or identity platforms
• Deployment model: whether the project is better suited to local, cloud, or hybrid architecture
• Maintenance planning: device access, field servicing, upgrade paths, and operating support across sites
• Privacy review: consent, authorized use, data handling approach, and project-specific governance requirements

Environment and interaction design also matter. Palm recognition is an active interaction: the user raises a hand and presents it to the terminal. That usually gives project teams more control over when authentication starts and how the step is communicated to users.

In integrated deployments, details such as working distance, lighting conditions, and enclosure design should be reviewed early so the product choice matches the real site conditions.

How to Discuss a Project with Deptrum

The most effective starting point is to define the scenario first and the device second. When discussing a project with Deptrum, it helps to outline the target use case, expected user flow, installation environment, system interfaces, and whether the deployment is fixed, embedded, or mobile.

For example, a team evaluating payment-related identity authentication may start with VeinShine 01, while a building-entry or attendance project may be better aligned with HandPass 521. A kiosk or self-service team may instead want to review VeinShine 02, VeinShine 03, or VeinShine 04 for module integration.

FAQ

What is Deptrum?

Deptrum is a palm-recognition-focused brand offering palm biometric authentication products and solutions for B2B deployment scenarios such as access control, attendance, identity verification, visitor workflows, and payment-related identity authentication.

What does Deptrum do?

Deptrum provides palm recognition products and solution support for projects that need identity authentication through active, touch-free palm presentation. Depending on the use case, that can include fixed terminals, mobile terminals, or integrated modules.

Does Deptrum offer palm payment?

Deptrum can support payment-related identity authentication using palm recognition. In that context, palm recognition is used as an identity authentication entry point around a payment workflow, while account management, transaction processing, and settlement remain part of other connected systems.

Which Deptrum products are relevant for different scenarios?

VeinShine 01 is the primary reference for payment-related identity authentication. VeinShine 02, VeinShine 03, and VeinShine 04 are better suited to integration-oriented non-payment scenarios, while HandPass 521 fits fixed terminal deployments and V6 fits mobile identity-verification workflows.

What should integrators review before choosing a Deptrum solution?

Integrators should review scenario fit, terminal form factor, user enrollment design, interface requirements, deployment architecture, maintenance expectations, and privacy review requirements. Those factors usually determine whether a fixed terminal, mobile terminal, or embedded module is the better match.

Contact Deptrum to discuss palm recognition and palm biometric solutions.