A palm vein payment project may work well in a development environment, yet face a different challenge when it reaches the customer’s infrastructure: the production servers cannot freely access the internet.
Banks, fintech companies and enterprise IT teams may restrict external downloads or require all software packages to pass an internal review before deployment.
X-Telcom’s large-model palm vein algorithm supports private-server deployment, with offline deployment documentation available for environments with limited connectivity. Preparing the required resources in advance helps teams deploy within their own infrastructure policies.
The Pain Point: Deployment Depends on External Downloads
In a restricted environment, downloading container images or installation packages during deployment may be impractical.
The customer’s technical team may need to:
- Review the required software resources before installation.
- Download packages through an approved network.
- Transfer container images to a private registry.
- Prepare the production environment without direct access to public repositories.
For a palm vein authentication project, these requirements should be discussed before scheduling deployment.
Private Deployment Keeps the Algorithm on Your Infrastructure
With X-Telcom’s large-model deployment package, the palm vein algorithm service runs on the customer’s own infrastructure.
Your application and backend communicate with that service as part of your identity verification or palm vein payment workflow. The algorithm deployment does not depend on X-Telcom hosting the matching service in its own cloud.
This gives your team responsibility for operating the server environment, controlling access and maintaining the deployed system.
How Offline Deployment Is Prepared
After a customer officially purchases the large-model palm vein algorithm licence deployment package, X-Telcom provides the resource configuration list.
The customer’s technical team can use this list to prepare the required chart packages and container images in advance, then transfer them to an approved private repository or deployment environment.
The preparation process generally follows these stages:
| Stage | What Needs to Be Prepared |
|---|---|
| Confirm the environment | Server resources, deployment architecture and network restrictions |
| Review the resource list | Required packages, images and configuration resources |
| Download approved resources | Obtain the required resources through an authorised connection |
| Transfer resources internally | Place images and packages in the customer’s private environment |
| Deploy and validate | Configure the services and test the application-to-algorithm workflow |
Offline deployment documentation supports this process. The exact preparation should be agreed with the customer’s infrastructure team.
Offline Deployment Does Not Mean Every Terminal Works Without a Network
It is important to distinguish offline server deployment from local matching on a palm vein device.
Offline deployment means the server environment can be prepared without downloading resources directly from external repositories during installation.
In a server-side palm vein recognition architecture, terminals still need a working connection to the customer’s backend and algorithm service. That connection may use a private network or another approved network path.
If a project requires palm matching directly on the terminal without contacting a server, that is a different architecture and should be discussed separately.
What About Access After Deployment?
X-Telcom can provide free remote support for the large-model deployment. However, remote assistance requires an access method approved by the customer. For a fully isolated environment, the deployment procedure and support arrangements need to be coordinated in advance.
After deployment is completed, X-Telcom does not require continued remote access to the customer’s server environment. The algorithm deployment has no external connections.
If a technical case needs investigation later, the customer can provide the relevant case images and error information for analysis.
Define the Whole Palm Vein Payment Workflow
Deploying the biometric algorithm privately addresses one part of the system.
A complete palm vein payment solution may also involve:
- Terminal applications and SDK integration.
- User registration and account binding.
- Customer middleware and backend services.
- Payment gateways or wallet platforms.
- Monitoring, backups and operational support.
Your team should identify the network requirements of each component. A privately deployed palm vein matching service does not automatically make every connected business service independent of external networks.
To help X-Telcom assess your large-model deployment requirements, please provide:
- Your expected registered user population.
- The proposed server configuration and operating environment.
- Whether external internet access is restricted or unavailable.
- Whether you operate a private container registry.
- Your preferred deployment and technical support arrangements.
If your organisation requires additional delivery materials, such as an SBOM, checksums or image signatures, please identify these during the technical review so their availability and scope can be confirmed.
Prepare the Infrastructure Before Expanding the Pilot
A successful palm vein authentication rollout depends on both the biometric technology and the environment in which it operates.
By preparing deployment resources in advance, your team can evaluate the large-model architecture within its own network and server policies, while retaining control of ongoing operations.
