How Does Palm Vein Payment Technology Migration from Small Model to Large Scale Model Work?

June 3, 2026
8 min. de leitura

As fintech platforms, digital wallets, and banking projects grow, one question frequently arises:

"If we start with the free Small Model and later upgrade to the Large Scale Model, will all existing users need to register again?"

The answer is:

No.

A properly designed palm vein payment architecture should allow future expansion without forcing users to repeat the enrollment process.


Understanding the Difference Between Small Model and Large Scale Model

BioWavePass provides two algorithm deployment options.

Small Model

The Small Model is designed for:

  • MVP testing
  • Pilot projects
  • Early-stage fintech deployments

It supports:

✅ Up to 10,000 Free User IDs

The Small Model primarily uses:

  • End-side Palm Print Feature (RGB)
  • End-side Palm Vein Feature (IR)

Only extracted biometric features are used for verification.


Large Scale Model

The Large Scale Model is designed for:

  • Commercial deployments
  • Banking platforms
  • National-scale projects
  • Million-level biometric databases

Unlike the Small Model, the Large Scale Model introduces additional server-side verification capabilities.

The algorithm uses:

  • Palm Print Image (RGB)
  • Palm Vein Image (IR)

to build and maintain large-scale biometric databases.


Does Migration Mean Users Must Register Again?

This is where many customers misunderstand the process.

The answer depends on whose perspective we are discussing.

From the Algorithm Perspective

Yes.

The Large Scale Model requires users to be registered into the new Large Model database.

Because the Large Scale Model uses original RGB and IR registration images, the algorithm must create a new biometric record within the Large Model architecture.


From the User Perspective

No.

Users do not need to:

  • Register again
  • Scan their palm again
  • Visit a registration center
  • Repeat the onboarding process

The migration is completely transparent to them.


How Is Migration Achieved?

When users are first enrolled in the Small Model system, BioWavePass strongly recommends storing:

  • RGB Palm Print Images
  • IR Palm Vein Images

along with the extracted biometric features.

These registration images become valuable assets for future expansion.

When upgrading to the Large Scale Model, the application simply calls the Large Model registration interface and submits the previously stored RGB and IR registration images.

The entire process can be completed programmatically.


What Happens During Migration?

From the application perspective:

✅ A new registration is performed for the Large Scale Model algorithm service.

Because the original registration images already exist, the system can automatically use them to complete registration into the new database.

No manual user action is required.


Why Is Image Storage Important?

Image storage is one of the most important considerations when designing a scalable palm vein payment platform.

Even if a project initially uses the free Small Model, storing:

  • Palm Print Images (RGB)
  • Palm Vein Images (IR)

creates a seamless migration path for future growth.

Without these images, upgrading to the Large Scale Model may require collecting registration images again.


What Does the User Experience?

From the user’s perspective:

✅ No new registration
✅ No additional palm scan
✅ No interruption to service
✅ No change to the user experience

Users continue using the platform exactly as before.

The migration occurs entirely in the background.


Developer Benefits

For development teams, migration is straightforward.

BioWavePass provides:

✅ Small Model Test Server
✅ Large Scale Model Test Server
✅ Android Java SDK
✅ Android Flutter SDK
✅ RESTful API Support
✅ Migration Testing Support

Only the device-server communication interfaces and server APIs need to be updated according to the Large Scale Model specifications.

No major application redesign is required.


Final Thought

A scalable palm vein payment platform should grow with your business.

With BioWavePass, migration to the Large Scale Model is a new registration process for the algorithm, but not for the user.

From the system’s perspective, users are registered into a new Large Scale Model database. From the user’s perspective, nothing changes because their original RGB and IR registration images already make the migration possible.


Learn More

https://biowavepass.com/

PalmVeinPayment #PalmPaymentTechnology #PalmVeinRecognition #BiometricPayment #Fintech #DigitalWallet #BankingTechnology #BiometricAuthentication #PalmPayment #BioWavePass

Também pode gostar

Can a Palm Vein SDK Capture Data Without an Algorithm Server?

“We already have our own backend. Can the terminal simply scan a palm and return the biometric data for us to process?” This is a practical question for teams building

Palm Vein Image Encryption: Why AES-256-GCM Alone Does Not Guarantee Compatibility

Your development team has implemented AES-256-GCM encryption. The algorithm server also uses AES-256-GCM. Yet an encrypted palm image still fails to process. Why? Using the same encryption algorithm does not

Large-Scale Palm Vein Recognition: How to Test the SDK and Plan for Growth

Before investing in a large-scale palm vein recognition system, product and development teams need to answer a practical question: How can we test the technology before purchasing an algorithm licence?

Palm Vein Payment SDK: Direct Algorithm Server Integration or Your Own Backend?

BioWavePass’s large-scale palm vein SDK supports two integration routes: connecting directly to the Algorithm Server, or connecting through your own backend. Both require a valid server URL and the response

Palm Vein Deployment Support: Who Can Access Your Servers?

Before introducing palm vein authentication into a production environment, IT teams need to know who will access their servers, what permissions are required and whether that access will continue after

Scaling Palm Vein Payment: Single Server or Kubernetes Cluster?

A palm vein payment pilot may begin with a few terminals and a limited group of users. As the project grows, one infrastructure question becomes increasingly important: Should your palm

Before You Scale Palm Vein POS: A Terminal Management Checklist

Your pilot has demonstrated the user experience. The next question is how to operate the terminals across multiple locations. Who will prepare new devices? How will applications be distributed? What

Why Saving Original Palm Images Matters for Biometric Recovery and Future Upgrades By BioWavePass

A successful Palm Vein Recognition deployment needs to support more than today’s matching requirements. It should also be prepared for server failures, lost biometric feature data and future algorithm upgrades.

Optimizing Palm Payment Performance: AirOne Palm Module Firmware v2.4.4

In a palm payment system, recognition accuracy is important, but the overall user experience also depends on how efficiently the biometric technology works together with the payment application. BioWavePass has

Bringing Palm Vein Scanning into a Web Workflow

Web applications are effective at managing users and business workflows. Connecting one to a USB palm vein scanner requires an additional software layer, because BioWavePass does not currently provide a