Merchant Pilot Home

Guided merchant onboarding readiness for company profile, organization profile, business verification, KYB readiness, contacts, team invitations, and pilot enrollment.

Merchant dashboard shell covering payments, transactions, refunds, settlements, wallet, reports, customers, invoices, developers, support, settings, production readiness, and pilot readiness.

Organization management readiness for business profile, locations, contacts, departments, teams, users, roles, permissions, and invitation readiness.

Team management readiness for members, invitations, pending invitations, role summaries, permission visibility, activity, and access summaries without sending invites.

Developer Platform readiness for API keys, webhook configuration, sandbox readiness, SDKs, documentation, quick starts, sample integrations, and rate limits without key generation.

Display-only financial views for payments, transactions, refunds, wallet, settlement, treasury, reports, execution state, blocked actions, and backend readiness.

Payment readiness view for payment lifecycle visibility, provider state, failed payment readiness, reconciliation dependency, and blocked payment actions.

Transaction visibility surface for metadata-only payment events, lifecycle state, provider traceability, reconciliation dependency, and settlement dependency.

Refund readiness surface covering refund lifecycle, provider dependency, ledger dry-run dependency, settlement adjustment dependency, audit requirements, and disabled refund controls.

Settlement readiness view for queue readiness, settlement history readiness, payout readiness, treasury dependency, reconciliation dependency, and blocked settlement controls.

Wallet read-model surface for ledger-derived balance explanation, reserve summary, treasury dependency, blocked wallet actions, and balance mutation blockers.

Analytics readiness for daily volume, monthly volume, revenue, payment trends, refund trends, settlement trends, customer growth, provider mix, pilot metrics, and executive summaries.

Customer readiness surface for customer list, profile shell, activity readiness, production blockers, support context, and future roadmap without customer mutation.

Invoice readiness surface for invoice list, invoice detail shell, invoice status readiness, payment link readiness, blocked production capabilities, and future roadmap.

Merchant readiness scorecard for identity, business, provider, developer, financial, production, pilot, and go-live blocker visibility.

Non-sending notification readiness for verification, provider approval, pilot readiness, missing evidence, blocked execution, workflow reminders, and support notices.

Read-only timeline for organization, workflow, readiness, developer, financial, support, audit, and production readiness activity.

Merchant help center for documentation, getting started, API guides, pilot guides, support, FAQ, troubleshooting, and release notes.

Merchant settings readiness for organization, users, notifications, security, developer, branding, compliance, billing readiness, execution settings, and blocked production settings.

Overview is represented with demo-safe, metadata-only readiness information.

Use this section for pilot review and operational planning.

Payments is visible for readiness review, but execution remains blocked.

Review blockers before any future backend-owned execution program.

Transactions is represented with demo-safe, metadata-only readiness information.

Use this section for pilot review and operational planning.

Refunds is visible for readiness review, but execution remains blocked.

Review blockers before any future backend-owned execution program.

Settlements is visible for readiness review, but execution remains blocked.

Review blockers before any future backend-owned execution program.

Wallet is visible for readiness review, but execution remains blocked.

Review blockers before any future backend-owned execution program.

Reports is represented with demo-safe, metadata-only readiness information.

Use this section for pilot review and operational planning.

Customers is represented with demo-safe, metadata-only readiness information.

Use this section for pilot review and operational planning.

Invoices is represented with demo-safe, metadata-only readiness information.

Use this section for pilot review and operational planning.

Developers is represented with demo-safe, metadata-only readiness information.

Use this section for pilot review and operational planning.

Support is represented with demo-safe, metadata-only readiness information.

Use this section for pilot review and operational planning.

Settings is represented with demo-safe, metadata-only readiness information.

Use this section for pilot review and operational planning.

Production readiness is visible for readiness review, but execution remains blocked.

Review blockers before any future backend-owned execution program.

Pilot readiness is represented with demo-safe, metadata-only readiness information.

Use this section for pilot review and operational planning.

Pilot scope, blocked production settings, and support expectations are visible.

Blocker: No live merchant activation occurs from the welcome flow.

Review pilot boundaries before onboarding review.

Company name, industry, website, operating country, and support contact are represented as metadata.

Blocker: No legal, tax, bank, or ownership documents are collected.

Prepare production KYB intake outside this non-executing UI.

Organization summary, locations, contacts, departments, teams, and user roles are visible.

Blocker: Organization mutation and activation remain backend-governed.

Review organization metadata before RBAC enforcement.

Verification status and missing evidence are visible without KYB submission.

Blocker: Real KYB, KYC, AML, and OFAC execution are disabled.

Complete compliance review in a future governed workflow.

Invite roles, pending invitations, and invitation lifecycle are visible.

Blocker: Real invitation sending and email delivery are disabled.

Keep invites in preview until identity/RBAC approval.

Pilot enrollment status, cohort review, and next recommended action are visible.

Blocker: Pilot enrollment does not activate merchants or providers.

Route the merchant to human pilot steering review.

Organization information is shown as governed metadata for merchant review without account mutation.

Confirm the owner and evidence source before enabling durable organization changes.

Organization information is shown as governed metadata for merchant review without account mutation.

Confirm the owner and evidence source before enabling durable organization changes.

Organization information is shown as governed metadata for merchant review without account mutation.

Confirm the owner and evidence source before enabling durable organization changes.

Organization information is shown as governed metadata for merchant review without account mutation.

Confirm the owner and evidence source before enabling durable organization changes.

Organization information is shown as governed metadata for merchant review without account mutation.

Confirm the owner and evidence source before enabling durable organization changes.

Organization information is shown as governed metadata for merchant review without account mutation.

Confirm the owner and evidence source before enabling durable organization changes.

Organization information is shown as governed metadata for merchant review without account mutation.

Confirm the owner and evidence source before enabling durable organization changes.

Organization information is shown as governed metadata for merchant review without account mutation.

Confirm the owner and evidence source before enabling durable organization changes.

Organization information is shown as governed metadata for merchant review without account mutation.

Confirm the owner and evidence source before enabling durable organization changes.

Organization information is shown as governed metadata for merchant review without account mutation.

Confirm the owner and evidence source before enabling durable organization changes.

Team management is display-only; it does not grant roles, send invitations, or change permissions.

Review access summaries before backend-owned RBAC enforcement is enabled.

Team management is display-only; it does not grant roles, send invitations, or change permissions.

Review access summaries before backend-owned RBAC enforcement is enabled.

Team management is display-only; it does not grant roles, send invitations, or change permissions.

Review access summaries before backend-owned RBAC enforcement is enabled.

Team management is display-only; it does not grant roles, send invitations, or change permissions.

Review access summaries before backend-owned RBAC enforcement is enabled.

Team management is display-only; it does not grant roles, send invitations, or change permissions.

Review access summaries before backend-owned RBAC enforcement is enabled.

Team management is display-only; it does not grant roles, send invitations, or change permissions.

Review access summaries before backend-owned RBAC enforcement is enabled.

Team management is display-only; it does not grant roles, send invitations, or change permissions.

Review access summaries before backend-owned RBAC enforcement is enabled.

API key generation is not available from the merchant portal.

Keep credentials server-side and route key requests through future approval workflow.

Webhook configuration is available as reference-only developer readiness content.

Keep credentials server-side and route key requests through future approval workflow.

Sandbox readiness is available as reference-only developer readiness content.

Keep credentials server-side and route key requests through future approval workflow.

SDK readiness is available as reference-only developer readiness content.

Keep credentials server-side and route key requests through future approval workflow.

API Documentation is available as reference-only developer readiness content.

Keep credentials server-side and route key requests through future approval workflow.

Quick Starts is available as reference-only developer readiness content.

Keep credentials server-side and route key requests through future approval workflow.

Sample integrations is available as reference-only developer readiness content.

Keep credentials server-side and route key requests through future approval workflow.

Rate limits is available as reference-only developer readiness content.

Keep credentials server-side and route key requests through future approval workflow.

Financial data is presented as visibility metadata only. No payment, ledger, wallet, settlement, or treasury mutation is exposed.

Review backend readiness and approval gates before any future execution work.

Financial data is presented as visibility metadata only. No payment, ledger, wallet, settlement, or treasury mutation is exposed.

Review backend readiness and approval gates before any future execution work.

Financial data is presented as visibility metadata only. No payment, ledger, wallet, settlement, or treasury mutation is exposed.

Review backend readiness and approval gates before any future execution work.

Financial data is presented as visibility metadata only. No payment, ledger, wallet, settlement, or treasury mutation is exposed.

Review backend readiness and approval gates before any future execution work.

Financial data is presented as visibility metadata only. No payment, ledger, wallet, settlement, or treasury mutation is exposed.

Review backend readiness and approval gates before any future execution work.

Financial data is presented as visibility metadata only. No payment, ledger, wallet, settlement, or treasury mutation is exposed.

Review backend readiness and approval gates before any future execution work.

Financial data is presented as visibility metadata only. No payment, ledger, wallet, settlement, or treasury mutation is exposed.

Review backend readiness and approval gates before any future execution work.

Financial data is presented as visibility metadata only. No payment, ledger, wallet, settlement, or treasury mutation is exposed.

Review backend readiness and approval gates before any future execution work.

Financial data is presented as visibility metadata only. No payment, ledger, wallet, settlement, or treasury mutation is exposed.

Review backend readiness and approval gates before any future execution work.

Financial data is presented as visibility metadata only. No payment, ledger, wallet, settlement, or treasury mutation is exposed.

Review backend readiness and approval gates before any future execution work.

Payment visibility is advisory-only and does not create, capture, charge, retry, or refund payments.

Use the view for lifecycle understanding while backend execution gates remain closed.

Payment visibility is advisory-only and does not create, capture, charge, retry, or refund payments.

Use the view for lifecycle understanding while backend execution gates remain closed.

Payment visibility is advisory-only and does not create, capture, charge, retry, or refund payments.

Use the view for lifecycle understanding while backend execution gates remain closed.

Payment visibility is advisory-only and does not create, capture, charge, retry, or refund payments.

Use the view for lifecycle understanding while backend execution gates remain closed.

Payment visibility is advisory-only and does not create, capture, charge, retry, or refund payments.

Use the view for lifecycle understanding while backend execution gates remain closed.

Payment visibility is advisory-only and does not create, capture, charge, retry, or refund payments.

Use the view for lifecycle understanding while backend execution gates remain closed.

Payment visibility is advisory-only and does not create, capture, charge, retry, or refund payments.

Use the view for lifecycle understanding while backend execution gates remain closed.

Payment visibility is advisory-only and does not create, capture, charge, retry, or refund payments.

Use the view for lifecycle understanding while backend execution gates remain closed.

Transaction data is represented as approved metadata and read-model readiness, not financial records or ledger entries.

Keep transaction visibility tied to approved webhook and financial persistence evidence.

Transaction data is represented as approved metadata and read-model readiness, not financial records or ledger entries.

Keep transaction visibility tied to approved webhook and financial persistence evidence.

Transaction data is represented as approved metadata and read-model readiness, not financial records or ledger entries.

Keep transaction visibility tied to approved webhook and financial persistence evidence.

Transaction data is represented as approved metadata and read-model readiness, not financial records or ledger entries.

Keep transaction visibility tied to approved webhook and financial persistence evidence.

Transaction data is represented as approved metadata and read-model readiness, not financial records or ledger entries.

Keep transaction visibility tied to approved webhook and financial persistence evidence.

Transaction data is represented as approved metadata and read-model readiness, not financial records or ledger entries.

Keep transaction visibility tied to approved webhook and financial persistence evidence.

Transaction data is represented as approved metadata and read-model readiness, not financial records or ledger entries.

Keep transaction visibility tied to approved webhook and financial persistence evidence.

Transaction data is represented as approved metadata and read-model readiness, not financial records or ledger entries.

Keep transaction visibility tied to approved webhook and financial persistence evidence.

Refund controls are disabled and no provider refund, ledger posting, settlement adjustment, or treasury update can occur.

Document refund requirements before a future governed refund execution program.

Refund controls are disabled and no provider refund, ledger posting, settlement adjustment, or treasury update can occur.

Document refund requirements before a future governed refund execution program.

Refund controls are disabled and no provider refund, ledger posting, settlement adjustment, or treasury update can occur.

Document refund requirements before a future governed refund execution program.

Refund controls are disabled and no provider refund, ledger posting, settlement adjustment, or treasury update can occur.

Document refund requirements before a future governed refund execution program.

Refund controls are disabled and no provider refund, ledger posting, settlement adjustment, or treasury update can occur.

Document refund requirements before a future governed refund execution program.

Refund controls are disabled and no provider refund, ledger posting, settlement adjustment, or treasury update can occur.

Document refund requirements before a future governed refund execution program.

Refund controls are disabled and no provider refund, ledger posting, settlement adjustment, or treasury update can occur.

Document refund requirements before a future governed refund execution program.

Refund controls are disabled and no provider refund, ledger posting, settlement adjustment, or treasury update can occur.

Document refund requirements before a future governed refund execution program.

Settlement and payout views explain readiness only; they cannot release settlements or execute payouts.

Keep settlement readiness dependent on treasury, reconciliation, ledger, and executive approval evidence.

Settlement and payout views explain readiness only; they cannot release settlements or execute payouts.

Keep settlement readiness dependent on treasury, reconciliation, ledger, and executive approval evidence.

Settlement and payout views explain readiness only; they cannot release settlements or execute payouts.

Keep settlement readiness dependent on treasury, reconciliation, ledger, and executive approval evidence.

Settlement and payout views explain readiness only; they cannot release settlements or execute payouts.

Keep settlement readiness dependent on treasury, reconciliation, ledger, and executive approval evidence.

Settlement and payout views explain readiness only; they cannot release settlements or execute payouts.

Keep settlement readiness dependent on treasury, reconciliation, ledger, and executive approval evidence.

Settlement and payout views explain readiness only; they cannot release settlements or execute payouts.

Keep settlement readiness dependent on treasury, reconciliation, ledger, and executive approval evidence.

Settlement and payout views explain readiness only; they cannot release settlements or execute payouts.

Keep settlement readiness dependent on treasury, reconciliation, ledger, and executive approval evidence.

Settlement and payout views explain readiness only; they cannot release settlements or execute payouts.

Keep settlement readiness dependent on treasury, reconciliation, ledger, and executive approval evidence.

Wallet and balance information is an explanatory read model only and cannot mutate balances or move funds.

Use wallet readiness for merchant education until ledger, treasury, and settlement gates are approved.

Wallet and balance information is an explanatory read model only and cannot mutate balances or move funds.

Use wallet readiness for merchant education until ledger, treasury, and settlement gates are approved.

Wallet and balance information is an explanatory read model only and cannot mutate balances or move funds.

Use wallet readiness for merchant education until ledger, treasury, and settlement gates are approved.

Wallet and balance information is an explanatory read model only and cannot mutate balances or move funds.

Use wallet readiness for merchant education until ledger, treasury, and settlement gates are approved.

Wallet and balance information is an explanatory read model only and cannot mutate balances or move funds.

Use wallet readiness for merchant education until ledger, treasury, and settlement gates are approved.

Wallet and balance information is an explanatory read model only and cannot mutate balances or move funds.

Use wallet readiness for merchant education until ledger, treasury, and settlement gates are approved.

Wallet and balance information is an explanatory read model only and cannot mutate balances or move funds.

Use wallet readiness for merchant education until ledger, treasury, and settlement gates are approved.

Wallet and balance information is an explanatory read model only and cannot mutate balances or move funds.

Use wallet readiness for merchant education until ledger, treasury, and settlement gates are approved.

Customer surfaces are shells for future merchant operations and cannot create, edit, import, or expose customer PII.

Keep customer workflows behind future authenticated, audited, and privacy-reviewed backend services.

Customer surfaces are shells for future merchant operations and cannot create, edit, import, or expose customer PII.

Keep customer workflows behind future authenticated, audited, and privacy-reviewed backend services.

Customer surfaces are shells for future merchant operations and cannot create, edit, import, or expose customer PII.

Keep customer workflows behind future authenticated, audited, and privacy-reviewed backend services.

Customer surfaces are shells for future merchant operations and cannot create, edit, import, or expose customer PII.

Keep customer workflows behind future authenticated, audited, and privacy-reviewed backend services.

Customer surfaces are shells for future merchant operations and cannot create, edit, import, or expose customer PII.

Keep customer workflows behind future authenticated, audited, and privacy-reviewed backend services.

Customer surfaces are shells for future merchant operations and cannot create, edit, import, or expose customer PII.

Keep customer workflows behind future authenticated, audited, and privacy-reviewed backend services.

Invoice views are product-readiness previews only. No invoice creation, payment link generation, or customer billing is enabled.

Use invoice readiness for roadmap planning until billing and payment execution are approved.

Invoice views are product-readiness previews only. No invoice creation, payment link generation, or customer billing is enabled.

Use invoice readiness for roadmap planning until billing and payment execution are approved.

Invoice views are product-readiness previews only. No invoice creation, payment link generation, or customer billing is enabled.

Use invoice readiness for roadmap planning until billing and payment execution are approved.

Invoice views are product-readiness previews only. No invoice creation, payment link generation, or customer billing is enabled.

Use invoice readiness for roadmap planning until billing and payment execution are approved.

Invoice views are product-readiness previews only. No invoice creation, payment link generation, or customer billing is enabled.

Use invoice readiness for roadmap planning until billing and payment execution are approved.

Invoice views are product-readiness previews only. No invoice creation, payment link generation, or customer billing is enabled.

Use invoice readiness for roadmap planning until billing and payment execution are approved.

Readiness is scored from backend and static advisory metadata. It does not approve production operation.

Resolve human approval, provider, compliance, financial, and operations blockers.

Readiness is scored from backend and static advisory metadata. It does not approve production operation.

Resolve human approval, provider, compliance, financial, and operations blockers.

Readiness is scored from backend and static advisory metadata. It does not approve production operation.

Resolve human approval, provider, compliance, financial, and operations blockers.

Readiness is scored from backend and static advisory metadata. It does not approve production operation.

Resolve human approval, provider, compliance, financial, and operations blockers.

Readiness is scored from backend and static advisory metadata. It does not approve production operation.

Resolve human approval, provider, compliance, financial, and operations blockers.

Readiness is scored from backend and static advisory metadata. It does not approve production operation.

Resolve human approval, provider, compliance, financial, and operations blockers.

Readiness is scored from backend and static advisory metadata. It does not approve production operation.

Resolve human approval, provider, compliance, financial, and operations blockers.

Readiness is scored from backend and static advisory metadata. It does not approve production operation.

Resolve human approval, provider, compliance, financial, and operations blockers.

Notification cards are visible reminders only. No delivery provider, email, SMS, push, or webhook notification is called.

Use these reminders for pilot review until notification governance is approved.

Notification cards are visible reminders only. No delivery provider, email, SMS, push, or webhook notification is called.

Use these reminders for pilot review until notification governance is approved.

Notification cards are visible reminders only. No delivery provider, email, SMS, push, or webhook notification is called.

Use these reminders for pilot review until notification governance is approved.

Notification cards are visible reminders only. No delivery provider, email, SMS, push, or webhook notification is called.

Use these reminders for pilot review until notification governance is approved.

Notification cards are visible reminders only. No delivery provider, email, SMS, push, or webhook notification is called.

Use these reminders for pilot review until notification governance is approved.

Notification cards are visible reminders only. No delivery provider, email, SMS, push, or webhook notification is called.

Use these reminders for pilot review until notification governance is approved.

Notification cards are visible reminders only. No delivery provider, email, SMS, push, or webhook notification is called.

Use these reminders for pilot review until notification governance is approved.

Help content is visible for pilot preparation and does not expose secrets or production credentials.

Use support for readiness questions before production review.

Help content is visible for pilot preparation and does not expose secrets or production credentials.

Use support for readiness questions before production review.

Help content is visible for pilot preparation and does not expose secrets or production credentials.

Use support for readiness questions before production review.

Help content is visible for pilot preparation and does not expose secrets or production credentials.

Use support for readiness questions before production review.

Help content is visible for pilot preparation and does not expose secrets or production credentials.

Use support for readiness questions before production review.

Help content is visible for pilot preparation and does not expose secrets or production credentials.

Use support for readiness questions before production review.

Help content is visible for pilot preparation and does not expose secrets or production credentials.

Use support for readiness questions before production review.

Help content is visible for pilot preparation and does not expose secrets or production credentials.

Use support for readiness questions before production review.

Settings are visible as readiness metadata. Production, billing, and execution switches cannot be enabled here.

Route settings changes through future authenticated and audited backend workflows.

Settings are visible as readiness metadata. Production, billing, and execution switches cannot be enabled here.

Route settings changes through future authenticated and audited backend workflows.

Settings are visible as readiness metadata. Production, billing, and execution switches cannot be enabled here.

Route settings changes through future authenticated and audited backend workflows.

Settings are visible as readiness metadata. Production, billing, and execution switches cannot be enabled here.

Route settings changes through future authenticated and audited backend workflows.

Settings are visible as readiness metadata. Production, billing, and execution switches cannot be enabled here.

Route settings changes through future authenticated and audited backend workflows.

Settings are visible as readiness metadata. Production, billing, and execution switches cannot be enabled here.

Route settings changes through future authenticated and audited backend workflows.

Settings are visible as readiness metadata. Production, billing, and execution switches cannot be enabled here.

Route settings changes through future authenticated and audited backend workflows.

Settings are visible as readiness metadata. Production, billing, and execution switches cannot be enabled here.

Route settings changes through future authenticated and audited backend workflows.

Settings are visible as readiness metadata. Production, billing, and execution switches cannot be enabled here.

Route settings changes through future authenticated and audited backend workflows.

Settings are visible as readiness metadata. Production, billing, and execution switches cannot be enabled here.

Route settings changes through future authenticated and audited backend workflows.

Role awareness is displayed for portal planning only. No permission enforcement change is made by the website.

Preserve backend RBAC ownership for future production authorization.

Role awareness is displayed for portal planning only. No permission enforcement change is made by the website.

Preserve backend RBAC ownership for future production authorization.

Role awareness is displayed for portal planning only. No permission enforcement change is made by the website.

Preserve backend RBAC ownership for future production authorization.

Role awareness is displayed for portal planning only. No permission enforcement change is made by the website.

Preserve backend RBAC ownership for future production authorization.

Role awareness is displayed for portal planning only. No permission enforcement change is made by the website.

Preserve backend RBAC ownership for future production authorization.

Role awareness is displayed for portal planning only. No permission enforcement change is made by the website.

Preserve backend RBAC ownership for future production authorization.

Role awareness is displayed for portal planning only. No permission enforcement change is made by the website.

Preserve backend RBAC ownership for future production authorization.

Role awareness is displayed for portal planning only. No permission enforcement change is made by the website.

Preserve backend RBAC ownership for future production authorization.