Palm payments under your name, on your rails.
HathPay is infrastructure. It never holds funds, never owns the customer and never approves a payment on its own. You decide, you settle, and you keep the relationship.
Platform licence
The biometric service, APIs, operations console and platform availability.
Terminal as a service
Enrolment and merchant terminals supplied, managed and replaced for a monthly fee.
Integration
Adapter build, certification in your test environment, staff training and rollout.
Usage component
A share of eligible palm-payment volume, where your acquiring arrangements allow it.
Terms are agreed with each bank. The model is built so it never depends on a per-transaction fee that regulation or competition could remove.
One bank. One site. Real people.
Start where enrolment is easy and merchants are close: a campus or a large employer whose staff bank with you. Nothing expands until the numbers are good enough for you.
Scope
Agree the site, the merchants, the success measures and the hosting model with your technology and compliance teams.
Integrate
Build the two adapter endpoints and the event receiver in your test environment, against our reference bank first.
Enrol and run
An enrolment desk on site, terminals at a handful of on-us merchants, and support from our team throughout.
Measure
A fixed measurement period, then a joint decision on whether to widen, change or stop.
Terminals, platform and people.
Enrolment and merchant terminals, the HathPay platform hosted as you require, the embedded module for your app, and our team on site during enrolment.
You bring the customers, the accounts and the decision on every payment.
What you will see from the pilot
- Enrolment completionstarted vs finished
- First-attempt matchgenuine palms
- False accept and false rejectpilot population
- Time at checkoutpalm to approval
- Support contactsper 100 payments
- Repeat useactive vs enrolled
Palm payment works when it lives inside an existing relationship.
The two best-known palm payment services took opposite routes, and the results are public.
Weixin Pay
Tencent registers palms inside the Weixin Pay app people already use, and reads both the lines on the palm and the veins beneath them.
Source: Tencent ↗Amazon One
Amazon is removing its palm readers from retail by 3 June 2026, citing limited customer adoption.
Source: Payments Dive ↗HathPay
Customers switch it on in the banking app they already trust, enrol at a branch with identity checked by the bank, and pay from their existing account.
The short answers.
Anything not here is a good question for the briefing.
Does HathPay hold customer funds?
No. HathPay is not a wallet and never holds money. It identifies the customer and asks the bank to authorise the debit. The bank moves the funds on its own rails and keeps the ledger.
What is stored about a customer's palm?
An encrypted template, a numeric description of the palm's pattern, not a photograph. Captures are deleted once the template is built, and removing HathPay deletes the templates.
Where would the system run?
For a pilot, onshore or inside the bank's own environment, as agreed with your technology and compliance teams and consistent with State Bank of Pakistan requirements for outsourcing and cloud use.
What if a customer injures their hand?
Customers can enrol both hands and either one pays. The merchant can always fall back to the bank's usual payment methods.
Can one person open two accounts with two hands?
No palm system can tell that two different palms belong to one person; that is the job of the bank's identity checks. HathPay closes the practical gap by enrolling both hands, so a second registration with either hand is refused as a duplicate.
How accurate is the matching?
We will publish false-accept and false-reject rates measured on the pilot population with the production sensor. Lab or synthetic figures would not tell a bank anything useful, so we do not quote them.
What happens if HathPay is unavailable?
Palm payments stop and nothing else does. Your accounts, cards and other channels are untouched, and no payment is ever approved without your own authorisation.
How much work is the integration?
Two adapter endpoints, an event receiver, and either one call to open the embedded module or your own screens on the partner API. A reference bank implementation is included to test against.
See it working, end to end, in thirty minutes.
Activation in a bank app, enrolment at a branch terminal and a palm payment settled through a simulated bank. Then the architecture and the pilot plan.