---
title: "Trace recent operations"
description: "Match recent orders to balance transactions using only explicit recorded references."
canonical: "https://studio.inttegro.com/inttegro-mcp/workflows/balance-transactions/trace-recent-operations"
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: 595
model_token_report: "https://studio.inttegro.com/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: ["list_orders","list_balance_transactions"]
estimated_tokens: 1186
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Match recent orders to balance transactions using only explicit recorded references. This Java representation uses the selected SDK's native names wherever Studio has a verified mapping.

### Five questions

#### Q1. When should the reader use Trace recent operations?

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?

Yes, when the reader has an authenticated MCP connection and the task needs live context, guided planning, or a supported operation. The strongest matches are `list_orders`, `list_balance_transactions`; their exact roles and boundaries are listed below.

#### 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 [list_balance_transactions](https://studio.inttegro.com/machine/java/inttegro-mcp/tools.md#list_balance_transactions) and [list_orders](https://studio.inttegro.com/machine/java/inttegro-mcp/tools.md#list_orders) when those concerns enter scope.

### Recommended MCP assistance

Use these through an authenticated Inttegro MCP connection. This document remains the contract source.

- [`list_orders`](https://studio.inttegro.com/machine/java/inttegro-mcp/tools.md#list_orders) — read; no mutation confirmation. Lists a bounded page of recent orders with totals and status, excluding customer contact and address data.
- [`list_balance_transactions`](https://studio.inttegro.com/machine/java/inttegro-mcp/tools.md#list_balance_transactions) — read; no mutation confirmation. Lists a bounded page of balance activity with related order and payment IDs, all current refund and payout allocations, and exact familiar-unit amount summaries.

## Document content

# Trace recent operations

Use this workflow for a bounded operational trace, not for totals or an all-time sales report.

### Prompt

> **Copyable prompt:**
>
> Review the five most recent orders and five most recent balance transactions.
> Identify only the transaction IDs that explicitly refer to those orders.
> Summarize the supported relationships and do not infer customer details or
> call this a complete sales report.

The agent uses [`list_orders`](https://studio.inttegro.com/machine/java/inttegro-mcp/tools.md#list_orders) and [`list_balance_transactions`](https://studio.inttegro.com/machine/java/inttegro-mcp/tools.md#list_balance_transactions). It reports only relationships present in the returned records.

## Sample response: Explicitly matched records

Only balance transactions whose returned order\_id matches one of the returned orders appear here.

- **Orders reviewed**: 5
- **Transactions reviewed**: 5
- **Explicit matches**: 3

* **Row 1**: Balance transaction: btxn\_example\_01; Order: ord\_example\_1042; Amount: GHS 350.00; Available at: 6 Sep 2026
* **Row 2**: Balance transaction: btxn\_example\_02; Order: ord\_example\_1041; Amount: GHS 125.00; Available at: 6 Sep 2026
* **Row 3**: Balance transaction: btxn\_example\_04; Order: ord\_example\_1039; Amount: GHS 480.00; Available at: 5 Sep 2026

Ask for another page explicitly when needed. One result page must never be treated as a complete period or account history.