Merchant Onboarding Capability

Identify a potential merchant and determine whether they should enter structured onboarding review.

Represent the start of an application journey without collecting or submitting live data.

Review business identity, operating model, public presence, contacts, and support posture.

Confirm that KYB/KYC evidence can be reviewed by humans before any external screening.

Review business model, restrictions, sanctions/AML readiness, and compliance ownership.

Map merchant onboarding posture against provider readiness, credentials, and approval blockers.

Confirm support, monitoring, incident, refund support, runbook, and escalation readiness.

Confirm leadership review before a merchant can move toward any controlled activation plan.

Document the future controlled activation stage while keeping activation blocked in this sprint.

Prepare future monitoring posture for support, incidents, settlement observation, refunds, and risk review.

Business name, operating model, and primary contact can be reviewed.

No business profile submission or mutation occurs.

Legal entity evidence requirements are visible for review.

No entity verification or document processing occurs.

Ownership evidence posture is tracked for human review.

No beneficial-owner verification or identity screening occurs.

Bank account evidence posture is visible for future payout readiness.

No bank account creation, verification, or payout enablement occurs.

Merchant contact, support owner, and escalation readiness are visible.

No onboarding email, SMS, or invitation is sent.

Merchant website and public business presence can be reviewed.

No external crawling or automated risk decisioning occurs.

Customer-facing support and policy readiness can be reviewed.

No policy publication, update, or legal attestation occurs.

Risk disclosure posture is visible for compliance and executive review.

No automated eligibility scoring or regulated decisioning occurs.

KYB checklist and evidence posture are visible.

No KYB execution or external verification occurs.

KYC readiness is represented for future human-reviewed workflows.

No KYC execution or identity decisioning occurs.

Sanctions and AML readiness requirements are visible.

No screening provider, OFAC API, sanctions API, or AML execution is called.

Business model review remains a compliance-owned human review.

No automated business approval or rejection occurs.

Restricted business policy posture is visible for compliance review.

No account restriction or regulated enforcement action occurs.

Document metadata requirements are visible.

No document upload, storage, parsing, or raw PII handling occurs.

Compliance owner review is required before activation planning.

No compliance decision or automated approval occurs.

Stripe controlled pilot evidence is available for review.

No Stripe API call, account creation, or payment execution occurs.

MTN, M-PESA, Orange Money, and future mobile money readiness remain visible.

No mobile money provider onboarding or execution occurs.

Bank provider readiness is tracked for future settlement and treasury planning.

No bank API calls or bank account creation occurs.

FX provider readiness is visible for future cross-border capability review.

No FX quote execution or conversion occurs.

Card processing readiness is represented through existing Stripe evidence.

No card processing, PaymentIntent, Checkout Session, or charge creation occurs.

Provider approval status remains a human-reviewed operating dependency.

No provider approval, production flag change, or credential activation occurs.

Provider blockers are visible for sequencing discussions.

No blocker resolution, external API call, or provider mutation occurs.

Support route and customer-safe guidance are available.

No support ticket creation or outbound communication occurs.

Incident response posture is documented through operations readiness.

No incident creation, paging, or alert dispatch occurs.

Monitoring and observability readiness are available for review.

No monitoring integration mutation or live alert routing occurs.

Runbook readiness supports controlled pilot preparation.

No automated runbook execution occurs.

Escalation paths can be reviewed before controlled pilot use.

No escalation ticket or notification is generated.

Internal pilot refund validation is documented for support preparation.

No refund execution or provider action occurs.

Settlement observation posture remains visible for finance review.

No settlement release, balance mutation, or treasury movement occurs.

Review the unified cross-platform operating context.

Review merchant health, revenue, support, and growth visibility.

Review activation preconditions, readiness gates, executive approval posture, AI advisory guidance, stop conditions, and safety boundaries.

Review executive controlled merchant activation posture without activating merchants.

Review post-onboarding operations readiness without execution.

Review executive readiness, risk, provider, and commercial posture.

Review existing merchant platform shell and dashboards.

Review compliance, KYB/KYC, AML, sanctions, restricted business, and evidence posture without triggering screening or decisions.

Review provider readiness and blockers without provider execution.

Review support, incident, runbook, and operations posture.

Review security, privacy, compliance, and reliability evidence.