---
title: "Check a refund status"
description: "Reconcile one refund by ID and explain whether it completed, remains in progress, or did not complete."
canonical: "https://studio.inttegro.com/inttegro-mcp/workflows/refunds/check-refund-status"
format: inttegro-machine-docs/v1
language: "PHP"
sdk_version: "v12.0.0"
reader_profile: optional
reader_manifest: "https://studio.inttegro.com/machine/php/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: 478
model_token_report: "https://studio.inttegro.com/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: ["get_refund"]
estimated_tokens: 1011
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Reconcile one refund by ID and explain whether it completed, remains in progress, or did not complete. This PHP representation uses the selected SDK's native names wherever Studio has a verified mapping.

### Five questions

#### Q1. When should the reader use Check a refund status?

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_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/php/inttegro-mcp/tools.md#get_refund) when those concerns enter scope.

### Recommended MCP assistance

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

- [`get_refund`](https://studio.inttegro.com/machine/php/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

# Check a refund status

Use the refund itself as the source of truth after creation or cancellation. Do not infer completion from an earlier response or from elapsed time.

### Prompt

> **Copyable prompt:**
>
> Check refund `<REFUND_ID>`. Show its order, amount, line allocations, reason,
> current status, and the relevant lifecycle time. Tell me plainly whether it
> completed, is still in progress, or did not complete.

The agent calls [`get_refund`](https://studio.inttegro.com/machine/php/inttegro-mcp/tools.md#get_refund). Only `succeeded` means the refund completed. `pending` and `processing` remain in progress; `failed` and `canceled` did not complete.

## Sample response: Refund is still processing

Inttegro has started the refund, but customer receipt is not yet confirmed.

- **Refund**: rf\_example\_401
- **Order**: ord\_example\_2088
- **Amount**: GHS 145.00
- **Status**: Processing — Still in progress

* **Row 1**: Order line: Canvas bag × 1; Refund amount: GHS 75.00; Reason: Requested by customer
* **Row 2**: Order line: Delivery × 1; Refund amount: GHS 70.00; Reason: Requested by customer

Processing began today at 10:43. Check the same refund again before reporting
completion or attempting another refund for these lines.