Merchant Operations Capability
A governed operating command center for post-onboarding and pre/full controlled merchant operations. It centralizes readiness and visibility while keeping every payment, refund, provider, settlement, treasury, ticket, notification, and workflow mutation path blocked.
Operations Overview
Merchant Operations Capability
Route: /merchant-operations
Purpose: A governed, read-only operating command center for post-onboarding and pre/full controlled merchant operations across payments visibility, refunds visibility, settlement observation, treasury observation, support, incidents, monitoring, runbooks, escalations, evidence, risk, SLA, and communications readiness.
Current status: visible. Operations health: ready with watch items.
Current recommendation: Continue controlled operations preparation with human-reviewed support, incident, treasury, and executive evidence before any future execution path is considered.
Merchant Operations Status
visibleRead-only command center
The capability centralizes merchant operations readiness and visibility without activating operational workflows.
Operations Health
watchReady with watch items
Support, monitoring, incident, runbook, and evidence posture are visible while settlement and treasury observation remain watch items.
Readiness Score
readiness only86
The readiness score is advisory and does not approve operations or execute merchant activity.
Current Recommendation
human review requiredPrepare controlled operations
Continue controlled operations preparation with human-reviewed support, incident, treasury, and executive evidence before any future execution path is considered.
Execution Boundary
blockedBlocked
No payment, refund, provider, ledger, settlement, treasury, ticket, workflow, notification, merchant, customer, or autonomous AI execution is enabled.
Execution Boundary
Merchant Operations is read-only. It does not execute payments, refunds, provider actions, ledger entries, settlements, treasury movement, ticket creation, workflow mutation, notifications, merchant mutation, customer mutation, or autonomous AI decisions.
Merchant operations posture is visible across support, incidents, payments, refunds, settlement, treasury, evidence, and communications.
Every area is governed and display-only. The surface helps teams prepare controlled merchant operations without creating tickets, workflows, notifications, payment actions, provider calls, ledger entries, settlement releases, treasury movement, or account mutations.
Payment operations visibility
readyPayment operations context can be reviewed from existing transaction visibility and Stripe evidence surfaces.
No payment, Checkout Session, PaymentIntent, provider call, or payment retry is created.
Refund operations visibility
readyRefund observation and support readiness are visible as operational evidence inputs.
No refund is created, approved, retried, or submitted to a provider.
Settlement observation
watchSettlement posture is visible for CFO and operations review while settlement execution remains governed.
No settlement is executed, released, accelerated, or posted.
Treasury observation
watchTreasury visibility connects to treasury readiness and financial intelligence for liquidity, reserve, and exposure context.
No treasury movement, payout, bank transfer, reserve account, or balance mutation occurs.
Support operations
readySupport posture is available for merchant and customer support preparation.
No support ticket, internal note, assignment, escalation, or customer communication is created.
Incident readiness
readyIncident roles, response paths, and readiness posture are visible for operational review.
No incident workflow, status page update, alert, or paging action is triggered.
Monitoring readiness
readyMonitoring readiness is visible for production observation and operational handoff.
No monitoring configuration, alert rule, or external observability API is changed.
Runbook readiness
readyRunbook readiness is displayed for human review across payment, refund, support, incident, and settlement observation paths.
No runbook task, workflow state, or operational checklist is mutated.
Escalation readiness
readyEscalation ownership and review posture are visible for support and executive operations.
No escalation record, notification, assignment, or approval workflow is created.
Evidence capture readiness
readyEvidence capture posture aligns with durable evidence, audit storage readiness, and operational review requirements.
No raw provider payloads, raw card data, secrets, credentials, or sensitive private merchant data are stored or exposed.
Operational risk posture
human review requiredOperational risk posture summarizes watch items, stop conditions, and human-reviewed readiness requirements.
No risk acceptance, regulated decision, or autonomous approval is made.
SLA or support posture
watchSupport posture and future SLA expectations are visible as readiness context.
No SLA commitment, support policy, or customer-facing service promise is activated.
Customer communication readiness
human review requiredCustomer communication readiness is visible for future receipt, refund, incident, and support messaging review.
No email, SMS, push notification, webhook, or customer message is sent.
Merchant communication readiness
human review requiredMerchant communication readiness is visible for future operational updates, escalation paths, and controlled pilot guidance.
No merchant notification, portal message, ticket update, or workflow mutation is performed.
Explainable guidance for human-reviewed merchant operations.
The advisor summarizes operating posture but cannot approve operations, execute workflows, create tickets, notify customers, call providers, move funds, write ledgers, release settlements, mutate merchants, or make regulated decisions.
No backend operations AI endpoint is used by this surface. The advisor renders safe static, demo-safe operating guidance until an approved backend AI operations capability exists.
Merchant operations are prepared for read-only command review.
Payment and refund evidence should remain observable before any future operational escalation.
Settlement and treasury items remain watch items for CFO and operations review.
Support, runbook, incident, and monitoring readiness are available for human review.
Executive signoff is required before any future controlled operations expansion.
The AI Operations Advisor cannot approve operations, execute workflows, create tickets, notify customers, call providers, move funds, write ledgers, release settlements, mutate merchants, or make regulated decisions.
Read-only operating memory for merchant operations readiness.
The timeline reflects operations readiness, support preparation, monitoring readiness, incident readiness, refund support readiness, settlement observation, executive review, and future controlled operations blockers.
Milestone 16
Merchant operations readiness established
The Merchant Operations command center is available for read-only operating review.
Support
Support preparation visible
Support posture is visible for merchant and customer operating readiness without ticket creation.
Monitoring
Monitoring readiness visible
Monitoring posture is visible without changing observability configuration.
Incident
Incident readiness visible
Incident readiness is available for operational review without creating incidents or alerts.
Refund Support
Refund support readiness visible
Refund support readiness is displayed without creating, approving, or submitting refunds.
Settlement
Settlement observation remains watch item
Settlement observation remains visible and human-reviewed before future operational expansion.
Executive
Executive review required
Executive review remains required before controlled operational changes can be considered.
Blocked
Future controlled operations not executed
This capability does not execute controlled operations and keeps all mutations blocked.
Merchant Operations connects the existing enterprise surfaces without triggering work.
These links are navigation only across Ecosystem, Merchant Success, Merchant Onboarding, Merchant Account, Merchant Activation, Customer Experience, Executive Operations, Financial Intelligence, Trust Center, Provider Platform, Treasury Platform, and Operations Platform.
Merchant Activation
human review requiredReview activation readiness before future controlled operations.
OpenControlled Activation Control
human review requiredReview the executive activation control center without executing operations or activating merchants.
OpenFinancial Intelligence
advisory onlyReview advisory financial intelligence without autonomous decisions.
OpenTreasury Operations
watchReview settlement, liquidity, reconciliation, financial operations, and treasury risk posture.
OpenCompliance Operations
human review requiredReview compliance operations posture without KYB/KYC, AML, sanctions, approval, case, or workflow execution.
OpenMerchant Operations remains read-only and execution blocked.
This capability shows operating readiness only. It does not execute payments, refunds, provider actions, ledger entries, settlements, treasury movement, merchant updates, customer updates, ticket creation, workflow mutation, notification sending, or autonomous AI decisioning.
Payment execution
false
Refund execution
false
Provider execution
false
Ledger execution
false
Settlement execution
false
Treasury movement
false
Merchant mutation
false
Customer mutation
false
Ticket creation
false
Workflow mutation
false
Notification sending
false
Autonomous AI decisioning
false
Credentials exposed
false
API keys exposed
false
Private endpoints exposed
false
Raw card data exposed
false
Secrets exposed
false