# Refund Service Overview

## Overview

The Refund Service helps you track and synchronize refund statuses across payment processors using the Python SDK. While the Payment Service handles initiating refunds, this service provides dedicated operations for retrieving refund information.

**Business Use Cases:**

* **Refund status tracking** - Check the current status of pending refunds to inform customers
* **Financial reconciliation** - Synchronize refund states with your internal accounting systems
* **Webhook processing** - Handle asynchronous refund notifications from payment processors
* **Customer service** - Provide accurate refund status information to support teams

## Operations

| Operation                                                                         | Description                                                                                                                                 | Use When                                                              |
| --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| [`get`](https://docs.hyperswitch.io/integrations/prism/python/refund-service/get) | Retrieve refund status from the payment processor. Tracks refund progress through processor settlement for accurate customer communication. | Checking refund status, reconciling refund states, customer inquiries |

## SDK Setup

```python
from hyperswitch_prism import PaymentClient

payment_client = PaymentClient(
    connector='stripe',
    api_key='YOUR_API_KEY',
    environment='SANDBOX'
)
```

## Common Patterns

### Refund Status Tracking Flow

```mermaid
sequenceDiagram
    participant App as Your App
    participant CS as Prism
    participant PP as Payment Provider

    Note over App: Customer requests refund
    App->>CS: 1. refund (via PaymentService)
    CS->>PP: Initiate refund
    PP-->>CS: Return refund initiated (PENDING)
    CS-->>App: Return connector_refund_id (PENDING)
    Note over App: Customer checks status
    App->>CS: 2. get (check refund status)
    CS->>PP: Retrieve refund status
    PP-->>CS: Return status: PENDING
    CS-->>App: Return status: PENDING
    Note over App: After some time
    App->>CS: 3. get (poll for update)
    CS->>PP: Retrieve refund status
    PP-->>CS: Return status: SUCCEEDED
    CS-->>App: Return status: SUCCEEDED
```

**Flow Explanation:**

1. **Initiate refund** - First, call the Payment Service's `refund` method to initiate the refund.
2. **Check status** - Call the Refund Service's `get` method with the `connector_refund_id`.
3. **Poll for updates** - For refunds that start as PENDING, periodically call `get` to check for status updates.

## Next Steps

* [Payment Service](https://docs.hyperswitch.io/integrations/prism/python/payment-service) - Initiate refunds and process payments
* [Dispute Service](https://docs.hyperswitch.io/integrations/prism/python/dispute-service) - Handle chargebacks that may result in refunds
* [Event Service](https://docs.hyperswitch.io/integrations/prism/python/event-service) - Process asynchronous refund notifications