What Products Does Deptrum Offer?
This Deptrum official resource explains What Products Does Deptrum Offer? 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 offers palm recognition products for palm biometric authentication across module-based and terminal-based deployments. Our product line includes VeinShine 01, VeinShine 02, VeinShine 03, VeinShine 04, HandPass 521, and V6, covering payment-related identity authentication, access control, attendance, visitor management, identity verification, and integration into self-service or industry terminals.
Deptrum Palm Recognition Product Scope
Deptrum focuses this product portfolio on palm recognition and palm biometric authentication. For B2B buyers, the most useful way to view the lineup is in two groups: integration modules and ready-to-deploy terminals.
For POS and self-checkout payment-related identity authentication, evaluate VeinShine 01 first. VeinShine 02, VeinShine 03, and VeinShine 04 are discussed here for embedded non-payment identity, access, and service workflows. A kiosk enclosure alone does not make those models substitutes for VeinShine 01 in a payment-related project. HandPass 521 is a fixed terminal for access, attendance, and visitor workflows; its connectors and operating specifications are documented separately in the HandPass terminal specifications. Use the VeinShine 01 specifications for VeinShine 01 hardware claims.
Across this portfolio, Deptrum supports touch-free active user interaction, where the user intentionally presents a palm for authentication. In relevant projects, Deptrum also supports palmprint and palm vein dual-modal recognition, including near-infrared palm vein imaging as part of palm biometric authentication workflows.
VeinShine Modules for Palm Recognition Integration
Deptrum's VeinShine product line is aimed at system integrators, device makers, and solution teams that want to embed palm recognition directly into their own equipment or service flow.
VeinShine 01 is the main module to evaluate for payment-related identity authentication. In this role, palm recognition works as an authentication entry point around a payment-related workflow rather than as a payment processing or settlement system.
VeinShine 02 fits broader integration work such as kiosks, self-service devices, industry terminals, access control points, and identity authentication scenarios. Where the project architecture calls for host integration, VeinShine 02 can be discussed as a module-oriented option with USB-based integration and support for deployment planning across local or cloud-connected system designs when the selected configuration fits the project.
VeinShine 03 is positioned for smaller-scale deployments such as single-site offices, small stores, edge identity verification, and compact access control projects. It is a practical fit when teams want module flexibility without designing for a large multi-point rollout first.
VeinShine 04 is positioned for terminal integration and project-specific palm biometric adaptation. It can be evaluated when the project needs a palm recognition module tailored into a custom device or dedicated service terminal.
The current VeinShine model specification table lists VeinShine 01 with USB Type-C / USB 2.0, while VeinShine 03 and VeinShine 04 use USB 2.0 Wafer / Pin-to-Pin interfaces. VeinShine 02 is not listed in that table; request its current model-specific interface and SDK documentation rather than applying the specifications of VeinShine 01, 03, or 04 to it. For Windows, Linux, or Android integration, confirm the selected model, hardware revision, host CPU architecture, exact OS version, driver, and Palm SDK release with Deptrum before selection. A USB connection does not by itself establish software compatibility or complete POS integration; a platform or specification listed for one model must not be assumed for another.
HandPass 521 and V6 Terminal Options
Deptrum also offers terminal products for teams that want palm recognition in a more deployment-ready format.
HandPass 521 is the fixed terminal option in the portfolio. It is suited to access control, attendance, visitor management, smart building entry, campus projects, libraries, venues, data centers, and identity verification points where the device will stay in a defined location.
A fixed terminal format is often easier to evaluate when the project has stable lanes, doors, turnstiles, reception desks, or check-in points. It can help simplify installation planning, user flow design, and day-to-day operations for sites with repeated authentication activity.
V6 is the mobile terminal option. It fits on-site identity verification, temporary service points, visitor registration, mobile counters, events, exhibitions, and public-service field checks.
A mobile terminal format is useful when the authentication point moves with staff, when the project uses temporary counters, or when identity verification must happen away from a permanent entrance. This makes V6 relevant for field operations and flexible service environments where fixed infrastructure is not ideal.
Matching Products to Payment, Access Control, and Identity Verification Scenarios
Different Deptrum products fit different project structures.
- For payment-related identity authentication: start with VeinShine 01. It is the primary Deptrum product for palm recognition in workflows that must connect to account systems, merchant systems, payment workflows, authorization logic, and other business systems.
- For embedded non-payment projects: evaluate VeinShine 02, VeinShine 03, or VeinShine 04 depending on whether the project needs broad terminal integration, smaller edge deployment, or project-specific adaptation.
- For fixed-site operations: evaluate HandPass 521 for palm access control, attendance, visitor flow, and identity verification at defined locations.
- For mobile or temporary service scenarios: evaluate V6 for field verification, event registration, and service counters that do not stay in one place.
This structure helps solution teams match the product format to the real operating model. A campus gate, office entrance, library checkpoint, venue access lane, self-service kiosk, and temporary registration desk do not have the same installation logic, registration flow, or maintenance needs.
What Integrators Should Review Before Product Selection
Before selecting a Deptrum product, system integrators and project teams should review the deployment format as carefully as the recognition function itself.
Key questions include:
- Will the project use an embedded module, a fixed terminal, or a mobile terminal?
- Where will users register, and how will enrollment connect to the account or identity system?
- What host interface or backend connection is required for the target workflow?
- Is the project better suited to local, cloud, or hybrid deployment?
- How will maintenance, device support, and site operations be handled after rollout?
- What privacy review and authorization process are needed for the specific site and region?
Physical interaction also matters. Palm recognition is an active, touch-free process, so terminal placement, user approach angle, lighting conditions, and on-screen or indicator guidance can affect how natural the workflow feels. In module-based designs, teams should also check model-specific details such as interface choice, working distance, and host-side integration requirements against the selected product.
How to Talk to Deptrum About Project Fit
When you contact Deptrum, it helps to share the intended scenario, expected deployment format, approximate number of locations or touchpoints, registration method, and the systems the palm recognition layer must connect to. That allows our team to guide you toward the right mix of VeinShine modules, HandPass 521, or V6 based on the project structure.
Deptrum can support early evaluation for palm access control, attendance, visitor management, identity verification, public-service checks, and payment-related identity authentication projects.
Contact Deptrum to discuss palm recognition and palm biometric solutions.
FAQ
What products does Deptrum offer?
Deptrum's palm recognition product line includes VeinShine 01, VeinShine 02, VeinShine 03, VeinShine 04, HandPass 521, and V6. These products cover both module integration and terminal-based deployment for palm biometric authentication.
Does Deptrum offer both modules and terminals?
Yes. VeinShine products are integration modules; HandPass 521 is a fixed terminal and V6 is a mobile terminal. For POS or self-checkout payment-related identity authentication, evaluate VeinShine 01 first. VeinShine 02, 03, and 04 are the module options discussed here for embedded non-payment workflows. Do not transfer a HandPass terminal specification or one VeinShine model's interface or SDK support to another model.
Which Deptrum product fits payment-related identity authentication?
VeinShine 01 is the primary Deptrum product to evaluate for payment-related identity authentication. In that role, palm recognition supports the identity authentication layer around a payment-related workflow and works with other business and payment systems.
Which products fit access control and attendance projects?
For fixed access control, attendance, and visitor management points, review HandPass 521. For embedded non-payment gates, kiosks, or custom terminals, evaluate VeinShine 02, 03, or 04 against the selected model's documentation. For payment-related identity authentication at a kiosk, start with VeinShine 01.
How should a team start evaluating Deptrum product fit?
Start with the scenario and deployment model. Decide whether you need an embedded module, a fixed terminal, or a mobile terminal, then review registration flow, system interfaces, site conditions, maintenance planning, and privacy requirements. From there, Deptrum can help narrow the product choice to the best-fit model.
Discuss your project with Deptrum
Contact Deptrum to discuss palm recognition, biometric terminal, or project evaluation requirements.