01
You describe the site
Sector, track, and how many terminals the site would need. The more concrete the environment (gate, counter, branch, platform), the more accurate the scope that comes back.
Book a pilot
Tell us where PalmPay should be tested first.
One form starts the pilot conversation across retail payments, SecureAccess, banking and transit. Describe the site and the volume, and we come back with a scoped six-month deployment: terminal count, enrolment plan and the success metrics we will both be measured on.
- Pilot term
- 6 months
- Terminals per site
- 1-25+
- Tracks
- SecureAccess / FinTech
- Base
- Gujarat, India
After you submit
02
We come back with a scope
Terminal count and placement, an enrolment plan for the user population, the integration surface (access controller, UPI switch or AePS), and the success metrics the pilot will be judged against.
03
The pilot runs against those metrics
A six-month deployment on live sites, measured on the numbers agreed before installation rather than on numbers chosen afterwards. Raw frames are purged at the edge throughout; no biometric images leave the terminal.
On site
The scope becomes a terminal on your counter or gate.
Once the scope is agreed, installation runs against your existing layout — a reader at the counter, a gate controller, or a branch teller line — rather than a parallel system alongside what you already operate.
- Terminal count and placement fixed against the agreed scope
- Enrolment run against the user population you specified
- Integration surface: access controller, UPI switch or AePS
- Raw frames purged at the edge from the first terminal to the last
Pilot intake
Deploy PalmPay at your facility.
A pilot is scoped as a six-month deployment with a defined terminal count, an enrolment plan and agreed success metrics. Tell us the shape of the site and we will come back with a scope.
6months
standard pilot term
1-25+
terminals per site