--- title: "Merchant workflows" description: "Find practical MCP workflows by commerce resource." canonical: "https://studio.inttegro.com/inttegro-mcp/workflows" format: inttegro-machine-docs/v1 language: "Java" sdk_version: "v8.3.0" reader_profile: optional reader_manifest: "https://studio.inttegro.com/machine/java/readers/index.json" reader_identification: "Optional: declare your client only if known and your current-session capabilities; use reader_manifest for supplemental recommendations." preamble_estimated_tokens: 388 model_token_report: "https://studio.inttegro.com/machine/token-report.json" preamble_questions: 5 preamble_source: "general" recommended_mcp_tools: [] estimated_tokens: 1417 token_estimate_method: "utf8_bytes_divided_by_4" --- ## Machine preamble **Summary:** Find practical MCP workflows by commerce resource. This Java representation uses the selected SDK's native names wherever Studio has a verified mapping. ### Five questions #### Q1. When should the reader use Merchant workflows? Use this MCP document when an authenticated AI client needs governed Inttegro context, guidance, presentation, or operations. #### Q2. What is authoritative on this page? The documented MCP catalog defines available abilities and confirmation boundaries. For live state, the structured tool result is authoritative; presentation output is only a rendering of that result. #### Q3. What page-specific constraint matters most? Read operations do not authorize mutations. Actions retain their exact confirmation requirements, and payment credentials or OTP must stay in secure Checkout. #### Q4. Can Inttegro MCP materially help with this task? No catalog ability is sufficiently specific to recommend for this page. Use the documentation directly; consult the MCP catalog only if the task later requires governed live account context or a supported operation. #### Q5. How should the reader verify the answer and continue? Preserve the structured tool result, distinguish bounded lists from complete analytics, and reconcile asynchronous actions through an authoritative read. Continue with [MCP overview](https://studio.inttegro.com/machine/java/inttegro-mcp.md) and [tool catalog](https://studio.inttegro.com/machine/java/inttegro-mcp/tools.md) when those concerns enter scope. ## Document content # Merchant workflows Find the workflow you need by business area or the Inttegro resource it starts from. Each example gives an agent a business outcome, the IDs it may use, and a clear boundary between reading data and making changes. ## Choose a workflow group ### [Orders](https://studio.inttegro.com/machine/java/inttegro-mcp/workflows/orders.md) Inspect an order, create and invoice one, maintain a draft, or take payment securely. ### [Revenue](https://studio.inttegro.com/machine/java/inttegro-mcp/workflows/revenue.md) Review gross sales, compare periods and daily trends, and identify the products and customers driving revenue. ### [Catalog](https://studio.inttegro.com/machine/java/inttegro-mcp/workflows/catalog.md) Review product performance and manage products, prices, and buy links. ### [Customers](https://studio.inttegro.com/machine/java/inttegro-mcp/workflows/customers.md) Review customer performance, recent orders, revenue, and order-level refunds; maintain customer records and send messages without exposing contact details. ### [Balance transactions](https://studio.inttegro.com/machine/java/inttegro-mcp/workflows/balance-transactions.md) Trace recent orders to balance transactions using relationships Inttegro actually records. ### [Payouts](https://studio.inttegro.com/machine/java/inttegro-mcp/workflows/payouts.md) Review payout volume, outcomes, timing, and disbursed amounts. ### [Communications](https://studio.inttegro.com/machine/java/inttegro-mcp/workflows/communications.md) Review aggregate message delivery activity without exposing message content or recipient details. ### [Message templates](https://studio.inttegro.com/machine/java/inttegro-mcp/workflows/message-templates.md) Find, create, preview, publish, send, and archive reusable SMS and email templates. ### [Refunds](https://studio.inttegro.com/machine/java/inttegro-mcp/workflows/refunds.md) Review refundable lines and recent refunds, create exact refunds, follow their progress, or cancel an eligible pending refund. ## Ask with enough context State the business outcome first. Include known Inttegro IDs, the currency and reporting period when relevant, and whether the agent may make changes. A useful prompt tells the agent what it must confirm, what it must not reveal, and which result would count as complete. To plan a new API integration instead of operating an existing account, use [Design an integration](https://studio.inttegro.com/machine/java/inttegro-mcp/design-integration.md) or [Build an integration with an agent](https://studio.inttegro.com/machine/java/inttegro-mcp/build-integrations.md). ## Requests the agent should refuse An Inttegro-connected agent should clearly explain the boundary when asked to: - collect raw payment credentials or OTP in chat; - retry an uncertain payment before reconciling the order; - claim a pending refund has completed; - move money or change payout settings; - reveal customer contact or payment details; - send an SMS to a raw phone number; - broadcast or schedule outreach; - infer full-period analytics from a short list page; or - bypass a confirmation. Review the complete [tool catalog](https://studio.inttegro.com/machine/java/inttegro-mcp/tools.md) or return to the [MCP overview](https://studio.inttegro.com/machine/java/inttegro-mcp.md).