---
title: "Review payout performance"
description: "Review payout volume, outcomes, timing, and disbursed amounts for a selected period and currency."
canonical: "https://studio.inttegro.com/inttegro-mcp/workflows/payouts/review-payout-performance"
format: inttegro-machine-docs/v1
language: "Ruby"
sdk_version: "v10.0.0"
reader_profile: optional
reader_manifest: "https://studio.inttegro.com/machine/ruby/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: 563
model_token_report: "https://studio.inttegro.com/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: ["get_payout","get_payout_analytics"]
estimated_tokens: 1211
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Review payout volume, outcomes, timing, and disbursed amounts for a selected period and currency. This Ruby representation uses the selected SDK's native names wherever Studio has a verified mapping.

### Five questions

#### Q1. When should the reader use Review payout performance?

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 `get_payout`, `get_payout_analytics`; 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 [get_payout_analytics](https://studio.inttegro.com/machine/ruby/inttegro-mcp/tools.md#get_payout_analytics) when those concerns enter scope.

### Recommended MCP assistance

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

- [`get_payout`](https://studio.inttegro.com/machine/ruby/inttegro-mcp/tools.md#get_payout) — read; no mutation confirmation. Gets one payout by ID with status, amount, timing, and minimized reconciliation detail. This tool cannot move funds.
- [`get_payout_analytics`](https://studio.inttegro.com/machine/ruby/inttegro-mcp/tools.md#get_payout_analytics) — analytics read; no mutation confirmation. Compares payout starts, successes, failures, cancellations, lateness, and exact requested, disbursed, and failed amounts.

## Document content

# Review payout performance

Choose a period and currency explicitly. Payout analytics supports `7d`, `30d`, and `90d` periods.

### Prompt

> **Copyable prompt:**
>
> Show payout performance for the last 30 days in GHS, including exact started,
> succeeded, failed, late, and disbursed figures. Include the Flint chart and do
> not estimate missing data.

The agent uses [`get_payout_analytics`](https://studio.inttegro.com/machine/ruby/inttegro-mcp/tools.md#get_payout_analytics). Amounts are presented as exact major-unit decimals with the selected currency; supplemental minor-unit integers remain available for machine consumers.

## Sample response: Payout performance for the last 30 days

The trend is visual, while the summary retains exact lifecycle counts and currency amounts.

- **Started**: 18 — Previous period: 16
- **Succeeded**: 16 — Previous period: 14
- **Failed**: 1 — Previous period: 1
- **Late**: 1 — Previous period: 2
- **Disbursed**: GHS 48,750.00 — Exact major-unit amount

Exact amount summary

- **Row 1**: Amount: Requested; Current period: GHS 51,200.00; Previous period: GHS 44,900.00
- **Row 2**: Amount: Disbursed; Current period: GHS 48,750.00; Previous period: GHS 41,600.00
- **Row 3**: Amount: Failed; Current period: GHS 1,250.00; Previous period: GHS 1,100.00

### Daily disbursed amount

- **Aug 2**: GHS 4,200.00
- **Aug 7**: GHS 7,350.00
- **Aug 12**: GHS 5,100.00
- **Aug 17**: GHS 9,400.00
- **Aug 22**: GHS 6,850.00
- **Aug 27**: GHS 11,200.00
- **Aug 31**: GHS 4,650.00

Use payout analytics for period totals and trends. A bounded payout list is useful for operational inspection, but it is not a complete performance report.