Customer readiness stays safety-first and non-executing.
Readiness reviews demo profile preparation, mobile beta path, support escalation, wallet disablement, money movement disablement, blockers, and human recommendations.
Demo profile readiness
Prepare high-level synthetic pilot metadata for review without collecting sensitive personal, identity, banking, card, or KYC data.
Wallet creation disabled
Wallet creation remains off. Readiness does not create wallet records, balances, accounts, ledger entries, or stored profiles.
Money movement disabled
Payments, transfers, provider execution, and money movement remain blocked until separate future activation work is approved.
Customer participation follows a human review path.
The customer pilot program organizes readiness evidence and cohort planning only. It does not create registrations, customer accounts, wallets, KYC records, provider access, or production financial services.
Step 1
Prepare demo profile metadata
Step 2
Review mobile beta path
Step 3
Confirm support escalation path
Step 4
Confirm wallet creation remains disabled
Step 5
Confirm money movement remains disabled
Enrollment remains static and non-executing.
The public customer pilot pages are publication-safe planning surfaces. They do not collect sensitive data, persist submissions, create wallets, or enable financial activity.
Readiness outputs are advisory and static/demo only.
No account creation, wallet creation, ledger writes, balance writes, provider execution, or money movement.
Human review is required before any future activation workflow.