> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integrations/prism/python/event-service/handle.md).

# Handle

## Overview

The `handle` method processes raw webhook payloads from payment processors. It verifies webhook signatures and returns a normalized response.

**Business Use Case:** When Stripe sends a webhook that a payment succeeded, verify it's authentic and update your order status.

## Purpose

| Challenge              | Solution               |
| ---------------------- | ---------------------- |
| Signature verification | Automatic verification |
| Multiple formats       | Normalized responses   |
| Security               | Validates secrets      |

## Request Fields

| Field               | Type     | Required | Description                 |
| ------------------- | -------- | -------- | --------------------------- |
| `merchant_event_id` | str      | Yes      | Your unique event reference |
| `payload`           | str/dict | Yes      | Raw webhook body            |
| `headers`           | dict     | Yes      | HTTP headers                |
| `webhook_secret`    | str      | Yes      | Webhook signing secret      |

## Response Fields

| Field             | Type | Description                                    |
| ----------------- | ---- | ---------------------------------------------- |
| `event_type`      | str  | Type: payment.captured, refund.succeeded, etc. |
| `event_response`  | dict | Payment/refund/dispute details                 |
| `source_verified` | bool | Whether signature verified                     |
| `event_status`    | str  | COMPLETE, INCOMPLETE                           |

## Example

### SDK Setup

```python
from hyperswitch_prism import EventClient

event_client = EventClient(
    connector='stripe',
    api_key='YOUR_API_KEY'
)
```

### Flask Webhook Handler

```python
from flask import Flask, request

@app.route('/webhooks/stripe', methods=['POST'])
async def handle_webhook():
    request_data = {
        "merchant_event_id": f"evt_{int(time.time())}",
        "payload": request.get_data().decode(),
        "headers": dict(request.headers),
        "webhook_secret": os.environ['STRIPE_WEBHOOK_SECRET']
    }

    try:
        response = await event_client.handle(request_data)

        if response["event_type"] == "payment.captured":
            await fulfill_order(
                response["event_response"]["payments_response"]["merchant_transaction_id"]
            )

        return "OK", 200
    except Exception as e:
        return str(e), 400
```

### Response

```python
{
    "event_type": "payment.captured",
    "event_response": {
        "payments_response": {
            "merchant_transaction_id": "txn_order_001",
            "connector_transaction_id": "pi_3Oxxx...",
            "status": "CAPTURED"
        }
    },
    "source_verified": True,
    "event_status": "COMPLETE"
}
```

## Event Types

| Event Type           | Description        |
| -------------------- | ------------------ |
| `payment.authorized` | Payment authorized |
| `payment.captured`   | Payment completed  |
| `payment.failed`     | Payment declined   |
| `refund.succeeded`   | Refund processed   |
| `dispute.created`    | New chargeback     |

## Next Steps

* [Payment Service](/integrations/prism/python/payment-service.md) - Process payment events
* [Refund Service](/integrations/prism/python/refund-service.md) - Process refund events


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hyperswitch.io/integrations/prism/python/event-service/handle.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.