Organization
Legal name, tax code, sector, branches, stores and authorized representative.
MERCHANT ONBOARDING
Register, integrate and activate a PalmPay merchant.
A controlled pathway from business application to verified tenant, integrated stores and production acceptance.
Merchant onboarding lifecycle
Draft↗Submitted↗Verification↗Assessment↗Contracting↗Integration↗UAT↗Live
BUSINESS APPLICATION
Register your merchant chain
Provide high-level project context only. Do not submit credentials, biometric samples, payment data or restricted documents through this public form.
01
Business registration
Establish who is applying and what will be deployed.
Project ownership
Business sponsor, product owner, finance, IT, security, operations and support contacts.
Requested scope
Palm payment, identity, attendance, prepaid wallet, loyalty, Open Banking, POS/ECR and analytics.
02
Verification and readiness
Confirm authority and the target operating model.
Authority and identity
Representative verification, invitation model and approved VNeID/identity-assisted path where applicable.
Existing systems
POS/ECR, CRM, ERP, loyalty, mobile app, bank accounts, API gateway and reporting.
Privacy and security
Data roles, consent, biometric processing, retention, incident, access and audit expectations.
03
Tenant and integration
Configure the enterprise foundation.
Roles
Enterprise Owner, Business Administrator, Store Manager, Finance, Loyalty and Operator.
Bank and VA
Merchant receiving account, VA mapping, event authentication, idempotency and reconciliation.
Stores and terminals
Location, POS identity, device mode, network, certificate, support owner and acceptance status.
04
UAT and go-live
Prove the full journey and the exception paths.
Business cases
Enroll, top up, pay, refund, loyalty earn/redeem, receipt and customer support.
Technical cases
Offline, duplicate, timeout, reversal, low-confidence palm, device degraded and bank-event delay.
Acceptance
KPI, security evidence, operating procedures, SLA, support, rollback and executive approval.
Onboarding produces an operating model, not only a tenant record
Commercial evidence
The merchant confirms business scope, locations, target transaction volume, customer segment, selected packages, device quantity, bank relationship, support hours and rollout plan. Commercial approval should not bypass technical or privacy acceptance.
Data responsibility
Parties document controller/processor or equivalent roles, customer notices, consent, biometric purpose, retention, data access, subprocessors, incident notification, customer requests and deletion or re-enrollment workflow.
Operational responsibility
The merchant owns store readiness, staff training, physical placement, customer assistance and cash-register procedure. Mobile-ID owns agreed platform operation; banks and licensed parties own their contracted payment and account functions.
Go-live evidence
Acceptance should include signed UAT, device inventory, certificate status, Open Banking contract tests, reconciliation results, exception tests, support contacts, monitoring, backup/restore, rollback, risk acceptance and launch authorization.
How long does onboarding take?
A simple controlled PoC can be prepared in weeks, while production timing depends on contracts, identity access, bank integration, POS changes, device supply, security review and UAT.
Can one enterprise operate multiple chains?
Yes, with a designed tenant and merchant hierarchy. Wallets, points, bank accounts, policies and data access can remain separated by chain.
Who creates the first account?
The verified enterprise representative nominates the Enterprise Owner. Additional users are invited, verified and assigned tenant-scoped roles.
MOBILE-ID / TRUSTED PALMPAY
Start merchant onboardingStart merchant onboarding
Mobile-ID will review the business case, integration landscape, bank relationship, device plan and acceptance goals.