Pilot readiness stays safety-first and non-executing.
Readiness reviews business profile, support escalation, demo onboarding, settlement disablement, provider disablement, blockers, and human recommendations.
Business profile readiness
Prepare high-level merchant profile metadata for review without collecting sensitive business, tax, banking, or identity documents.
Settlement disabled
Settlement execution remains off. Readiness does not create settlement instructions, bank accounts, balances, or ledger entries.
Provider disabled
Provider activation remains blocked until separate production readiness, credential governance, and human approval processes are complete.
Pilot participation follows a human review path.
The merchant pilot program organizes readiness evidence and cohort planning only. It does not create registrations, merchant accounts, settlements, provider access, or production financial services.
Step 1
Prepare business profile metadata
Step 2
Assign support escalation owner
Step 3
Review demo onboarding path
Step 4
Confirm settlement execution remains disabled
Step 5
Confirm provider activation remains disabled
Enrollment remains static and non-executing.
The public merchant pilot pages are publication-safe planning surfaces. They do not collect sensitive data, persist submissions, or enable financial activity.
Readiness outputs are advisory and static/demo only.
No ledger writes, balance writes, settlement execution, provider execution, or money movement.
Human review is required before any future activation workflow.