Thyris Merchant Services as an Agentic Commerce Operations Platform
Thyris Merchant Services is the operational control platform for connecting agents to merchant capabilities. Platform teams install agents and MCP servers, define ARP boundaries, route requests, attach payment providers, and compose approved resources in Commerce Flow Studio.
When to use this scenario
Use this model when an organization needs to:
- Operate multiple store-scoped agent instances.
- Provide controlled catalog or procurement tools through MCP.
- Route different agent capabilities through separate policies or endpoints.
- Compose an agentic commerce flow from approved resources.
- Connect a payment provider to an intended flow.
- Separate pilot and production configurations.
- Disable or reroute a capability during an incident.
Platform composition
| Capability | Merchant Services role |
|---|---|
| Agents | Installs and manages store-specific agent instances. |
| MCP servers | Defines agent-accessible tool endpoints and configuration. |
| ARP | Applies endpoint, rule, rule-set, and file-based agent boundaries. |
| Router | Sends traffic to approved ARP destinations and rule sets. |
| ACP configuration | Stores the store's Agentic Commerce Protocol settings. |
| Commerce Flow Studio | Connects MCP, payment, ARP, and Router resources visually. |
| Agentic Payment | Registers provider instances and store-scoped wallets. |
| Marketplace | Installs reusable agent, MCP, payment, and extension templates. |
Control flow
Implementation journey
1. Define the agent contract
List the intended user, store, supported tasks, allowed tools, prohibited actions, approval requirements, data fields, expected failure behavior, and accountable owners.
2. Install resources in a pilot store
Use Marketplace or direct configuration to install the required agent and MCP resources. Review dependencies, endpoint ownership, credentials, and upgrade behavior before activation.
3. Apply policy and routing
Create restrictive ARP rules and attach the correct Router rule set. Avoid a single broad route that gives every agent access to every merchant operation.
4. Compose the flow
Use Commerce Flow Studio to connect the approved MCP server, ARP endpoint, Router, and payment provider when required. Record the owner and version of the active flow.
5. Test authorization and failure behavior
Validate tool discovery, permitted calls, denied calls, malformed input, unavailable endpoints, timeout, duplicate actions, partial failure, and approval cancellation.
6. Release in stages
Begin with a controlled audience and read-only capabilities. Add write operations only after audit, recovery, and approval paths are proven.
7. Operate and recover
Monitor request failures, policy denials, MCP health, agent state, and payment exceptions. During an incident, disable the affected agent or MCP server, block or reroute traffic, rotate credentials, test the correction, and restore gradually.
Success measures
- Successful approved tool execution rate
- Denied request rate by rule and agent
- MCP endpoint availability and latency
- Agent journey completion rate
- Time to disable or reroute an affected capability
- Unauthorized or out-of-scope action count
- Rollback success for flow and policy changes
Production controls
- Keep every resource scoped to its intended merchant and store.
- Store secrets outside flow metadata and agent instructions.
- Require approval before irreversible or financial operations.
- Version rules, routes, and active flow configuration.
- Test payment decline, timeout, and reconciliation separately.
- Maintain a last known-good configuration and documented rollback path.