---
title: "Review recent refunds"
description: "Browse a bounded page of recent refunds and distinguish completed, in-progress, failed, and canceled outcomes."
canonical: "https://studio.inttegro.com/inttegro-mcp/workflows/refunds/review-recent-refunds"
format: inttegro-machine-docs/v1
language: "Go"
sdk_version: "v11.0.1"
reader_profile: optional
reader_manifest: "https://studio.inttegro.com/machine/go/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: 565
model_token_report: "https://studio.inttegro.com/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: ["list_refunds","get_refund"]
estimated_tokens: 1156
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Browse a bounded page of recent refunds and distinguish completed, in-progress, failed, and canceled outcomes. This Go representation uses the selected SDK's native names wherever Studio has a verified mapping.

### Five questions

#### Q1. When should the reader use Review recent refunds?

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_refunds`, `get_refund`; 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_refund](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#get_refund) and [list_refunds](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#list_refunds) when those concerns enter scope.

### Recommended MCP assistance

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

- [`list_refunds`](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#list_refunds) — read; no mutation confirmation. Lists a bounded page of refunds with per-line allocations, reasons, timestamps, and lifecycle status.
- [`get_refund`](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#get_refund) — read; no mutation confirmation. Gets one refund for authoritative lifecycle reconciliation. Only succeeded means the refund completed.

## Document content

# Review recent refunds

Use the refund list to find recent activity or locate a refund for follow-up. The result is a bounded operational page, not a full-period refund report.

### Prompt

> **Copyable prompt:**
>
> Show the 25 most recent refunds. Include the refund ID, order ID, amount,
> status, reason, and creation time. Group the result into completed, in
> progress, failed, and canceled outcomes without estimating totals beyond this
> page.

The agent uses [`list_refunds`](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#list_refunds). A full page may have more results, so the response should keep the page boundary visible.

## Sample response: Recent refunds

This is page 1 of recent refund activity; more results may be available.

- **Shown**: 25 refunds — Page 1
- **Succeeded**: 18
- **In progress**: 4 — Pending or processing
- **Failed or canceled**: 3

* **Row 1**: Refund: rf\_example\_401; Order: ord\_example\_2088; Amount: GHS 145.00; Status: Processing; Created: Today, 10:42
* **Row 2**: Refund: rf\_example\_400; Order: ord\_example\_2081; Amount: GHS 50.00; Status: Succeeded; Created: Today, 09:18
* **Row 3**: Refund: rf\_example\_399; Order: ord\_example\_2074; Amount: GHS 25.00; Status: Canceled; Created: Yesterday, 16:05

The counts summarize only the returned page. Use [`get_refund`](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#get_refund) when one refund needs authoritative reconciliation.