A customer registers their palm successfully. Later, they scan again and the system recognises them. How does your application know which customer account, employee record or payment wallet that recognition result belongs to? The answer starts with the user ID supplied during registration. In X-Telcom’s Large Model palm vein recognition system, your platform generates and […]
Read More →
A new palm payment service has officially launched in Georgia, giving customers another way to pay at participating locations. X-Telcom, the hardware provider behind BioWavePass AirOne, is proud to see our palm vein payment terminals supporting this milestone. Seeing the devices become part of everyday transactions is a rewarding moment for everyone involved. A More […]
Read More →
When adding palm vein recognition to an existing application, one of the first architecture decisions is where to send the SDK’s requests. Should the terminal communicate directly with the Algorithm Server? Or should requests pass through your existing backend? X-Telcom’s Large Scale SDK supports both approaches. The important requirement is that the configured server exposes […]
Read More →
When integrating palm vein recognition into a payment or identity platform, developers often ask: “Does the SDK encrypt biometric data automatically, or do we need to build encryption ourselves?” For X-Telcom’s SDK and algorithm interfaces, the answer depends on the data involved. Feature data produced by the feature-value SDK is already encrypted. Palm image encryption […]
Read More →
When integrating palm vein recognition into a payment or identity platform, customers often ask how biometric images are protected between their application and the algorithm server. In X-Telcom’s current large-scale Algorithm Server API, client-side image encryption is optional. When enabled, the client encrypts the image before upload and sets is_image_encrypted to true in the request […]
Read More →
In X-Telcom’s large-scale palm vein system, your platform generates the unique user_id and supplies it during registration. The SDK and Algorithm Server do not generate this identifier. The registration process associates the user’s left and right palm data with that platform-defined ID. After successful identification, your application receives the user identifier and can use it […]
Read More →
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 […]
Read More →
When evaluating a palm vein authentication solution, customers often ask: Will the system stop working when the algorithm licence expires? For banks, fintech companies and system integrators, this question affects pilot planning, operating costs and service continuity. Understanding the difference between a permanent licence and a temporary evaluation licence helps teams plan their deployment with […]
Read More →
Deploying a palm vein terminal is only the beginning. As a project expands across merchant locations, bank branches or service points, teams need a practical way to manage devices, maintain application consistency and support terminals remotely. For banks, payment providers and fintech companies, palm vein device management should be part of the deployment plan from […]
Read More →
When developing a Palm Vein Recognition system, it is easy to focus on the feature vectors used for biometric matching. However, the original palm images captured during registration also have an important long-term role. Securely retaining both the RGB palm print image and the infrared (IR) palm vein image gives your system source data from […]
Read More →