Checkout friction
Open app, scan, input, confirm and wait-especially costly at peak hours.
IDENTITY-LED COMMERCE INFRASTRUCTURE
PALM IDENTITY.
PALM IDENTITY.
FASTER PAYMENT.
MORE
VALUE
AT EVERY POINT OF SALE.
AT EVERY POINT OF SALE.
Trusted PalmPay connects Palm Vein and Palm Print identity, VNeID-assisted onboarding, Open Banking virtual-account top-up, closed-loop prepaid value, loyalty and managed palm terminals in one bank-merchant platform.
From verified identity to funded wallet and palm-authorized checkout.
< 0.7 secReference recognition benchmark
8-25 cmReference contactless capture range
VNeID-readyApproved identity integration path
Open Banking + VACustomer-specific top-up and reconciliation
Reference-device benchmark. End-to-end performance depends on device profile, network, integration, matching policy and deployment conditions.
PALM PRINTIdentity signal
PALM VEINProtected match
✓
Payment authorized< 0.7 sec reference recognition
PALM VEIN / PRINTVNeID IDENTITYOPEN BANKING + VADUAL-MODE TERMINALLOYALTY & DATA
WHY NOW
Why the market needs PalmPay now
QR and mobile apps digitized payment, but high-frequency checkout still carries friction. Trusted PalmPay turns identity into a secure transaction touchpoint and connects payment, loyalty and operational data at the moment of sale.
Bank reach
Banks need trusted off-app touchpoints that increase transaction frequency and ecosystem engagement.
Merchant throughput
Retailers need shorter queues, clearer reconciliation and loyalty activated directly at checkout.
Customer expectation
Users increasingly expect natural, contactless and device-independent experiences.
VALUE NETWORK
Four touchpoints. One value network.
PalmPay is not a standalone scanner. It is an operating platform that coordinates identity, value, loyalty and auditable transaction data.
PAYMENT
Contactless, fast and policy-controlled payment at the point of sale.
IDENTITY
Palm Print / Palm Vein linked to a verified customer profile and consent lifecycle.
LOYALTY
Points, offers, vouchers, cashback and member-tier rules at checkout.
DATA
Real transaction events and operational insight for authorized bank and merchant use.
QR / APP → TRUSTED PALMPAY
Beyond QR and app checkout
| Criteria | Current QR / app | Trusted PalmPay |
|---|---|---|
| Steps | Open app, scan, input and confirm | Present palm; authenticate and pay |
| Dependency | Phone, battery, connectivity and user actions | No phone or OTP at checkout after enrollment |
| Identity | Often separate from payment context | Biometric identity linked to the transaction |
| Loyalty | Frequently fragmented or applied later | Rules applied directly at the payment touchpoint |
| Data | Limited identity-to-transaction continuity | Authorized identity, transaction and behavior signals |
APPS / PORTALS / ONBOARDING
One ecosystem. A clear entry point for every participant.
Customers download the PalmPay Client, store teams use PalmPay Merchant, enterprise users sign in to governed portals, and new banks or merchant chains follow controlled onboarding and device activation journeys.
CUSTOMERS
PalmPay Client
Enroll, manage consent, choose merchant wallets, top up through an assigned VA, pay by palm, view receipts and use loyalty benefits.
STORE OPERATIONS
PalmPay Merchant
Monitor payment status, shifts, devices, receipts, permitted refunds, loyalty actions and store-level exceptions.
WEB-BASED PORTALS
Merchant & Admin Portal
Govern tenants, stores, users, transactions, Open Banking, devices, loyalty, approvals, reconciliation, security and audit.
GET STARTED
Business & device onboarding
Register a merchant chain, bank integration or PalmPay Device through readiness assessment, verification, configuration, UAT and go-live approval.
DISCOVER→REGISTER→VERIFY→INTEGRATE→UAT→GO LIVE→OPERATE
BUSINESS & OPERATING MODEL
A bank-merchant ecosystem, not a standalone payment gadget
Trusted PalmPay connects banking rails, merchant operations, palm identity and customer engagement in one governed operating model. Each participant keeps a clear role, measurable value and auditable responsibility.
Funding, trust and distribution
- Open Banking API and virtual-account services
- Customer funding source and account notifications
- Merchant acquiring and ecosystem expansion
- Consent-based transaction insight
TRUSTED
PALMPAYIdentity / Payment / Loyalty / Data
PALMPAYIdentity / Payment / Loyalty / Data
Checkout, prepaid value and loyalty
- Faster checkout and shorter peak-hour queues
- Closed-loop balance by chain or merchant group
- Offers, vouchers, points and cashback
- Store, terminal, shift and transaction reconciliation
Natural payment with transparent control
- Identity-assisted onboarding and consent
- Top up from the customer's own bank app
- Pay without presenting phone, card or cash
- View balance, receipts, loyalty and fallback options
What management can measure
Checkout timeQueue reductionRepeat visitsPrepaid balanceActive customersLoyalty redemptionMerchant coverageReconciliation accuracy
What architecture teams can govern
Identity assuranceDevice trustAPI securityBiometric separationLedger stateIdempotencyAudit evidenceObservability
CUSTOMER & MONEY FLOWS
Three journeys make the service deployable
Enrollment, funding and payment are deliberately separated so banks, merchants and end users understand who does what, where money moves and how consent is enforced.
Enroll & consent
- Verify the customer through the agreed identity/eKYC journey.
- Capture palm data through the approved device and quality controls.
- Create protected biometric templates and bind them to the customer profile.
- Record purpose, consent, policy version and lifecycle status.
Fund a merchant-specific wallet
- Select the wallet for Merchant Chain A.
- Assign or retrieve a customer-specific virtual account for that chain.
- The customer transfers from their bank app to the assigned VA.
- Funds settle directly into the merchant's bank account; PalmPay reconciles the event and credits the internal ledger.
Pay with the palm
- POS/ECR sends amount, merchant, terminal and order context.
- The device captures palm data and sends an encrypted request through the trusted channel.
- The platform authenticates the customer, evaluates policy and debits the internal balance.
- Result, receipt and loyalty events return to the point of sale.
CLOSED-LOOP PREPAID
Closed-loop prepaid value-with an explicit money-flow boundary
Trusted PalmPay coordinates identity, reconciliation and the merchant-specific internal ledger. In the reference model, customer funds move directly to the merchant's bank account through the assigned virtual account; PalmPay does not receive or hold customer funds. Final legal roles, licensing, safeguarding and settlement responsibilities must be confirmed for each bank-merchant deployment.
-
1
Customer
Transfers from bank app to an assigned VA
-
2
Bank / Open Banking
Posts funds to the merchant account and sends a trusted credit notification
-
3
Trusted PalmPay
Reconciles the credit and updates the customer ledger for that merchant chain
-
4
Merchant
Receives funds and accepts internal-value payment at its own points of sale
IDENTITY / VNeID / PALM ENROLLMENT
Bind a verified person to a protected palm credential
Identity proofing, consent, palm enrollment and payment activation are separated into auditable steps. VNeID may support identity verification through an approved integration and contractual access model; production scope must be agreed with the authorized service owner.
Identity initiation
Customer starts onboarding in Palm Client, bank app, merchant app or an assisted enrollment station.
VNeID-assisted verification
Verify identity attributes and transaction context through the approved VNeID/RAR integration path when applicable.
Purpose & consent
Display purposes, data categories, retention, sharing, withdrawal and fallback before palm enrollment.
Palm capture & quality
Capture Palm Print and/or Palm Vein, run quality and PAD/liveness controls supported by the approved device profile.
Protected template binding
Create a protected biometric reference and bind it to the verified customer profile without placing wallet data in the biometric domain.
Activation & lifecycle
Activate allowed use cases; support suspension, revocation, re-enrollment, device loss and consent withdrawal.
ASSURANCE CONTROLS
Enrollment is a security ceremony
Production onboarding should combine identity assurance, operator/device authorization, biometric quality, presentation-attack controls, signed evidence, policy versioning and a clear exception path.
- Identity evidenceSource, timestamp, consent and verification outcome
- Enrollment evidenceDevice, operator, quality, PAD/liveness and template status
- Lifecycle evidenceActivation, suspension, re-enrollment, revocation and deletion
- Privacy controlsPurpose limitation, minimization, retention and rights workflow
OPEN BANKING API / VIRTUAL ACCOUNT / TOP-UP
Turn a bank transfer into merchant-specific prepaid value
Open Banking connectivity and a customer-specific Virtual Account (VA) are the bridge between real money in the banking system and the internal balance used for fast palm checkout.
01CustomerChooses Merchant Chain A wallet
Bank app transfer
02Bank + VACustomer-specific VA maps the credit
Signed credit event
03Trusted PalmPayReconcile, deduplicate and credit ledger
Balance available
04MerchantFunds are already in merchant account
Virtual-account mapping
Map customer, merchant chain, bank account and reference context with controlled lifecycle and reconciliation rules.
Trusted credit notification
Receive bank webhook/event with authentication, signature validation, timestamp, replay protection and source allow-listing.
Ledger crediting
Apply idempotency, amount/reference validation, exception handling and an auditable internal ledger entry.
Reconciliation & exceptions
Expose unmatched, duplicate, reversed, delayed and manually reviewed cases to bank and merchant operations.
Money-flow boundary
In the reference closed-loop model, real funds move directly into the merchant's bank account. Trusted PalmPay receives the trusted transaction notification and manages the merchant-specific internal balance; it does not receive or hold customer funds. Licensing, safeguarding, settlement, refund and consumer-protection roles must be agreed for each deployment.
PLATFORM ARCHITECTURE
A separated, bank-grade platform architecture
The platform separates biometric trust from the prepaid ledger, applies zero-trust controls at integration boundaries and preserves a clear audit trail from device request to business outcome.
TRUSTED
PALMPAYIdentity / Value / Loyalty / Data
PALMPAYIdentity / Value / Loyalty / Data
Point of sale & edge
- Palm capture device
- POS / ECR connector
- Device certificate and channel identity
- Local quality checks and encrypted payload
Identity & biometric trust
- CheckID enrollment and identity lifecycle
- Palm Print / Palm Vein matching service
- Template protection and policy evaluation
- Consent, revocation and re-enrollment
Payment & value orchestration
- Trusted Pay transaction orchestration
- Merchant-specific balance and ledger
- Hold, debit, credit, refund and reversal
- Reconciliation, idempotency and audit
Bank & merchant ecosystem
- Open Banking adapter and virtual accounts
- Merchant POS, CRM, ERP and BI
- Loyalty and campaign integrations
- Notifications, settlement data and reporting
PALM DEVICE & EDGE
Contactless palm capture designed for real points of sale
The reference terminal combines contactless palm capture with a merchant-facing display and integration options for USB-host or direct-backend operation. Device selection, liveness/PAD controls, template strategy and retention policy are validated during the PoC.
- Reference speed
- < 0.7 sec recognition benchmark
- Capture range
- 8-25 cm reference range
- Modalities
- Palm Print and/or Palm Vein by approved configuration
- Integration
- USB host, POS/ECR connector or controlled backend API
- Data principle
- Do not retain raw palm images on the POS by design; confirm final device and server configuration
- Fallback
- Defined alternative payment and recovery path
PALM TERMINAL / DUAL MODE / DYNAMIC UI
One terminal, two control modes and multiple business applications
The palm terminal can operate as a USB-controlled peripheral for an existing POS/PC or as a directly connected managed endpoint. The same hardware can support payment, attendance, access, identity verification and approved custom workflows.
REFERENCE TERMINAL CAPABILITIES
Functional blocks at the edge
Palm Print / VeinTouch displayQR 1D/2DSpeaker / micLED statusUSB-A hostUSB-C / OTGEthernetWi-FiOptional 4G/5G24/7 powerRemote management
Actual ports, radio modules and biometric capabilities depend on the approved terminal variant and supplier specification.
PC / POS / HOSTBusiness application
USB HID / CDC / vendor protocol
PALM TERMINALUI, capture and result
- Host sends approved UI and business context through documented USB protocol.
- Device captures palm and returns identification/authentication result to the host.
- Suitable for POS environments where business logic remains on the local host.
- No backend dependency is required for the terminal command channel.
PALMPAY BACKENDOpenAPI / orchestration
MQTT 5.0 over TLS / mTLS
PALM TERMINALManaged endpoint
- Backend sends server-defined UI, commands, payment or identification requests.
- Device publishes status, events and results through authorized topics.
- Ethernet, Wi-Fi or optional cellular connectivity supports distributed estates.
- Remote configuration, logs, certificates, firmware and health are centrally governed.
Dynamic server-defined UI
Render approved screens for amount, merchant, order, check-in, identity, consent, result and notifications. The terminal never invents business values.
Palm identification command
HOST or backend initiates a 1:N identification request; device returns the result and correlation reference through the same controlled mode.
Palm authentication command
Bind the transaction to a claimed user or token for 1:1 verification, step-up authentication or high-risk confirmation.
Multi-application runtime
Support payment, attendance, access control, identity verification and custom workflows with policy-separated application contexts.
Device management
Inventory, enrollment, certificates, configuration, firmware, logs, health, alerts, remote disable and audit.
Integration contract
OpenAPI 3.1, TLS 1.3+, mTLS, MQTT 5.0, idempotency keys, correlation IDs, error model and supplier protocol deliverables.
Open the detailed terminal and communication reference
The visual is a reference requirements map. Procurement must confirm the final hardware bill of materials, protocols, security functions and supplier deliverables.
STAKEHOLDER OUTCOMES
Value for every participant
For banks
- Extend trusted transaction touchpoints beyond the mobile app
- Support prepaid funding and deeper merchant engagement
- Create consented data signals for service improvement and personalization
- Launch measurable innovation without replacing the core payment estate
For merchants
- Reduce checkout steps and peak-hour queues
- Apply offers, vouchers and points in the payment flow
- Reconcile by merchant, store, terminal, shift and transaction
- Increase repeat visits and activate prepaid value
For customers
- Pay without presenting a phone, card or cash after enrollment
- Use a natural, contactless interaction
- Manage merchant-specific balance, receipts and loyalty
- Receive transparent consent, privacy and fallback controls
BANKS / MERCHANTS / TECHNOLOGY PARTNERS
Build the ecosystem with visible integration status
A production website should show only approved partner names and logos. The structure below is ready for connected, pilot and integration-ready partners without implying participation before written approval.
CONNECTEDIN PILOTINTEGRATION-READY
Banking ecosystem
BANK LOGOConnected
BANK LOGOIn pilot
BANK LOGOOpen Banking ready
+ ADD APPROVED BANKCMS slot
Merchant ecosystem
MERCHANT LOGOConnected
MERCHANT LOGOIn pilot
MERCHANT LOGOPoC ready
+ ADD APPROVED MERCHANTCMS slot
Technology & deployment
POS / ECRIntegration partner
PALM DEVICEHardware partner
CRM / ERPBusiness integration
CHANNEL PARTNERDeployment & support
Partnership paths
Discuss partnership
Bank-led ecosystem / Merchant-chain rollout / Device/SDK partnership / POS/ECR integration / Channel deployment / Loyalty/affiliate network
ONBOARDING & ACTIVATION
Move from interest to a governed production tenant.
PalmPay onboarding combines commercial qualification, business verification, integration readiness, security review, store and device setup, UAT and go-live governance.
Register organization
Business identity, tax code, representative, project owner, locations and selected capabilities.
Verify & assess
Authority, identity path, privacy roles, systems, bank relationship, POS landscape and deployment scope.
Configure tenant
Enterprise owner, administrators, stores, roles, wallet model, loyalty, bank adapters and policies.
Register devices
Model, serial, firmware, store, terminal mode, certificate, network, POS binding and support owner.
Integrate & UAT
Open Banking events, VA mapping, POS/ECR, palm workflows, exception cases, reconciliation and reporting.
Approve go-live
Acceptance evidence, security approval, operating procedures, support model, SLA and rollback readiness.
Application statusDraft→Submitted→Business Review→Technical Assessment→Integration→UAT→Live
PALMPAY LOYALTY ENGINE
Turn every payment into a governed, programmable loyalty event.
PalmPay separates monetary balance from points, applies configurable earn and redemption rules, supports internal, cross-merchant and affiliate programs, and preserves a complete point-ledger and reconciliation trail.
Separate ledgers
Merchant wallet balance and loyalty points are independent value domains with separate states, controls and audit evidence.
Configurable rules
Earn rate, product eligibility, campaign multiplier, member tier, cap, rounding, waiting period and expiry are policy-driven.
Controlled exchange
Internal, cross-merchant and affiliate redemption use approved relationships, exchange tables, budgets and settlement rules.
Exception-safe
Refund, failed redemption, expiry, merchant suspension, suspected fraud and administrative adjustment follow explicit state transitions.
EARN FLOW
Validated payment to available points
- Payment completed
- Eligibility checked
- Earn rules evaluated
- Pending points recorded
- Transaction confirmed
- Points made available
POINT LIFECYCLE
Every point has a governed state
Pending→Available→Reserved→Redeemed
ExpiredRevokedReversedLocked
REDEMPTION
Three controlled value paths
- Internal redemption within the issuing chain
- Cross-merchant redemption under an approved agreement
- Affiliate benefits with central point-ledger control
- Reserve, confirm, redeem or release without double spending
Points Ledger
Pending, available, reserved, redeemed, expired, revoked and reversed balances.
Earn Rule Engine
Eligibility, rate, tier, campaign, cap, rounding and anti-duplication controls.
Redemption Engine
Availability check, reservation, conversion, confirmation, release and reversal.
Campaign & Tier
Audience, store, product, period, budget, member tier and maker-checker approval.
Affiliate Exchange
Merchant relationships, conversion ratios, coefficients, limits and effective dates.
Reconciliation & BI
Point liability, issue/redeem/expire/reverse totals, payables, receivables and campaign KPIs.
SECURITY / PRIVACY / COMPLIANCE
Security, privacy and compliance by architecture
Palm biometrics are sensitive data. The website describes engineering controls and deployment expectations-not a blanket compliance certification. Every production arrangement requires documented legal, security, privacy and bank-risk approval.
Biometric separation
Separate biometric services and templates from wallet/ledger data to reduce blast radius and simplify access governance.
Trusted channels
Device identity, mTLS, signed requests, nonce/replay controls, rate limiting and API gateway policy.
Template protection
Encrypted transit and storage, least privilege, key management, quality thresholds and configurable retention.
Transaction integrity
Idempotency, double-entry or equivalent ledger controls, state machines, reversals, reconciliation and immutable audit evidence.
Consent & rights
Purpose-specific notice, explicit consent where required, withdrawal, re-enrollment, retention and data-subject workflow.
Operational assurance
Monitoring, alerting, incident response, vulnerability management, penetration testing and controlled change.
Deployment review, not a blanket certification
Reference framework for deployment review in Viet Nam: regulations on non-cash payments, payment services/intermediaries, banking online-service security, cybersecurity and personal-data protection. Applicability depends on the contractual model, data flows, licensed parties and final system design.
SECURITY ASSURANCE & INTERNATIONAL REFERENCES
Translate standards into acceptance criteria
Standards are used as engineering and test references, not as unqualified certification claims. The applicable edition, scope, laboratory evidence and contractual acceptance criteria must be confirmed for the selected device and deployment.
Presentation attack detection
Reference for PAD performance testing and reporting of the selected palm capture profile.
Evidence: attack taxonomy, test plan, APCER/BPCER or applicable metrics, limitations.Biometric information protection
Reference for protected biometric references, identity binding, storage/comparison models and privacy.
Evidence: threat model, template protection, renewability/revocability, access model.Information security management
Reference for risk management, governance, operational controls and continual improvement.
Evidence: scoped ISMS, risk treatment, control ownership, audit and incident processes.API security verification
Reference for authorization, authentication, resource control, inventory and unsafe consumption risks.
Evidence: threat model, API tests, gateway policies, secure SDLC and remediation records.Trusted device communications
Secure channels, mutual identity, authorized topics, certificate lifecycle and replay-resistant messages.
Evidence: cipher policy, PKI profile, topic ACL, rotation and revocation tests.Controlled integration contract
Versioned APIs, idempotency, correlation, error semantics, event schema and traceability.
Evidence: API specification, conformance tests, audit mapping and operational runbook.Production assurance gates
- Device & biometric validationHardware, firmware, quality, PAD/liveness, environment and performance
- Identity & consent validationVNeID/eKYC path, purpose, notices, withdrawal, lifecycle and exception handling
- Payment & ledger validationVA mapping, bank events, state machine, reconciliation, reversals and audit
- Security & privacy approvalThreat model, penetration test, data protection, retention and shared responsibility
- Operational acceptanceSLA, monitoring, incident response, support, backup, recovery and rollout criteria
PRIORITY USE CASES
High-frequency environments where a controlled PoC can prove value
F&B & café
Small-ticket, repeat purchases and peak-hour queue pressure.
Convenience retail
Fast checkout, loyalty and store-level reconciliation.
Campus & canteen
Closed community, repeat users and measurable adoption.
Hospital & pharmacy
Identity, service journey and payment can be linked with strict privacy boundaries.
Corporate campus
B2B2C programs, employee benefits and controlled enrollment.
Supermarket & mall
Scale, multi-store operations and deeper POS/CRM integration.
DEPLOYMENT & INTEGRATION
Deploy where the bank and merchant need control
Private cloud
Dedicated environment with controlled tenancy, keys, networks and data residency.
On-premises
Deploy core services inside customer-controlled infrastructure and security zones.
Hybrid
Keep sensitive services and ledgers in controlled zones while integrating managed components.
Open integration
REST APIs, events and adapters for POS/ECR, mobile, CRM, ERP, BI and bank systems.
CONTROLLED ROADMAP
Controlled implementation roadmap
-
1
One-day workshop
Align use case, roles, money flow, target KPI and risk assumptions.
-
2
PoC: 30-90 days
Deploy 1-3 locations, enroll a controlled cohort and measure performance.
-
3
Pilot expansion
Standardize operations, integrate loyalty, reconciliation, support and SLA.
-
4
Chain rollout
Scale by location, merchant group and authorized ecosystem partners.
END-TO-END FUNCTIONAL MAP
One view for business, product and engineering teams
The blocks below show how customer channels, administration, palm trust, payment value, loyalty and external integrations work together.
EXPERIENCE CHANNELS
Palm ClientEnroll, consent, wallet, top-up, receipts, loyalty
Merchant PortalStores, devices, transactions, shifts, campaigns,
reconciliation
Admin PortalTenants, policies, device estate, integration, security,
audit
POS / ECR / KioskOrder context, payment request, result and receipt
CORE BUSINESS SERVICES
Customer & ConsentProfile, VNeID/eKYC result, consent version,
lifecycle
Wallet & LedgerBalance, hold, debit, credit, reversal, refund,
statement
Loyalty EngineEarn, pending, available, reserved, redeemed,
expired
Transaction OrchestrationIdempotency, policy, routing, state machine,
evidence
IDENTITY & PALM TRUST DOMAIN
Enrollment ServiceQuality, PAD/liveness, template creation, binding
Palm Identification1:N search, candidate policy, result confidence
Palm Authentication1:1 verification, step-up and transaction binding
Template VaultProtection, keys, separation, retention and
revocation
EXTERNAL ECOSYSTEM
VNeID / Identity SourceApproved identity verification and attribute sharing
path
Bank / Open BankingVA, credit notification, reconciliation and settlement
data
CRM / ERP / BICustomer, product, campaign, accounting and
analytics
Notification & SupportEmail, SMS, push, webhook, ticket and operations
identity.verifiedpalm.enrolledbank.credit.receivedwallet.creditedpayment.authorizedloyalty.earnedreconciliation.completed
COMMERCIAL MODELS
Commercial engagement models
Starter
1-3 locations; controlled users; basic payment, balance and KPI dashboard.
Pilot
5-20 locations; POS/ECR integration; loyalty basics; shift and transaction reconciliation.
Bank Ecosystem
Open Banking, virtual accounts, merchant acquiring integration, campaigns and behavioral analytics.
Enterprise
Multi-chain scale, CRM/ERP/BI integration, 24/7 operations, security assurance and SLA.
EXECUTIVE OVERVIEW
Trusted PalmPay at a glance
A high-resolution business overview is included for workshops and internal alignment. Every key point also appears as accessible HTML on this page.
Open high-resolution overview ↗
SEO & TECHNICAL RESOURCE HUB
Explore PalmPay by business and technical topic
Search-focused topic pages provide the depth that a single landing page cannot.
↗
Palm payment platform
How palm identity, wallet value and payment orchestration work together.
↗Palm terminal architecture
Dual operating modes, dynamic UI, interfaces and device management.
↗Open Banking & VA top-up
Money flow, bank events, reconciliation and closed-loop ledger controls.
↗VNeID & palm enrollment
Identity-assisted onboarding, consent, biometric binding and lifecycle.
↗Security & compliance
Biometric protection, PAD references, API security and assurance gates.
↗Banks & partners
Bank, merchant, device, POS and deployment partnership models.
↗PalmPay Loyalty Engine
Point ledger, earn/redeem rules, cross-merchant exchange and reconciliation.
↗Apps, portals & access
Entry points for customers, stores, enterprise users and partners.
↗Merchant onboarding
Business registration, verification, integration readiness, UAT and go-live.
↗Device registration
Claim, provision, bind, test, activate and operate PalmPay terminals.
FAQ
Questions procurement, security and product teams ask.
Is Trusted PalmPay only a hardware device?
No. The device is one component. Trusted PalmPay combines enrollment, palm biometrics, trusted APIs, payment orchestration, a merchant-specific internal ledger, loyalty, reconciliation and bank connectivity.
Does PalmPay hold customer money?
In the reference closed-loop model, funds move directly to the merchant bank account through an assigned virtual account. PalmPay reconciles the credit and maintains an internal ledger. The production legal and licensing model must be agreed by the bank, merchant and advisors.
Are raw palm images stored at the POS?
The recommended design avoids retaining raw palm images on the POS. The final answer depends on the selected device, SDK, matching architecture, diagnostic settings and approved retention policy.
Does payment always complete in under 0.7 seconds?
No universal guarantee is made. The figure is a reference-device recognition benchmark. End-to-end latency must be measured in the target deployment.
Can it work with an existing POS or banking platform?
Yes, subject to integration assessment. PalmPay is designed around APIs, event-driven integration and adapters for POS/ECR, Open Banking, CRM, ERP and analytics systems.
How should a bank start?
Begin with a controlled environment, define success metrics before deployment, prefer 1:1 verification first, validate privacy and security controls, then expand by measured evidence.
How does Virtual Account top-up work?
The customer transfers from their bank app to a customer-specific VA mapped to the selected merchant chain. The bank posts funds directly to the merchant account and sends a trusted credit notification. PalmPay reconciles the event and credits the merchant-specific internal ledger.
What role can VNeID play?
VNeID may support identity verification through an approved integration and contractual access path. PalmPay still needs purpose-specific notices, consent, enrollment evidence and lifecycle controls for the palm credential.
What are the two terminal operating modes?
HOST/USB mode lets an existing POS or PC control the terminal through a documented USB protocol. Direct Backend mode lets the PalmPay backend control the device through OpenAPI and MQTT over protected network channels.
Can the device support non-payment use cases?
Yes, the multi-application design can support attendance, access control, identity verification and approved custom workflows, subject to device capability, policy separation and deployment approval.
CONTACT MOBILE-ID
Design a measurable PalmPay PoC
Tell us the bank, merchant environment, target locations and systems to integrate. Mobile-ID will prepare a focused architecture and workshop plan.
info@mobile-id.vnEmail
Ho Chi Minh CityLevel 9, Thuy Loi 4 Building, 286-288 Nguyen Xi Street, Binh
Loi Trung Ward, Ho Chi Minh City