> 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/recurring-payment-service/revoke.md).

# Revoke

## Overview

The `revoke` method cancels an existing recurring payment mandate. Once revoked, no future automatic charges can be made using this mandate. Use this when customers cancel their subscriptions or recurring services.

**Business Use Case:** A customer cancels their SaaS subscription. You call `revoke` to stop all future billing and comply with their cancellation request.

## Purpose

**Why revoke mandates?**

| Scenario                      | Benefit                                              |
| ----------------------------- | ---------------------------------------------------- |
| **Subscription cancellation** | Honor customer cancellation requests                 |
| **Compliance**                | Meet regulatory requirements for recurring billing   |
| **Customer retention**        | Clean revocation improves re-subscription likelihood |
| **Billing hygiene**           | Remove inactive mandates to reduce system clutter    |

**Key outcomes:**

* Future automatic charges are blocked
* Customer billing stops immediately
* Compliance with cancellation regulations

## Request Fields

| Field        | Type   | Required | Description                                      |
| ------------ | ------ | -------- | ------------------------------------------------ |
| `mandate_id` | string | Yes      | The mandate ID to revoke                         |
| `reason`     | string | No       | Reason for revocation (customer\_canceled, etc.) |

## Response Fields

| Field         | Type          | Description                             |
| ------------- | ------------- | --------------------------------------- |
| `mandate_id`  | string        | The revoked mandate ID                  |
| `status`      | MandateStatus | New status: REVOKED                     |
| `revoked_at`  | string        | ISO 8601 timestamp of revocation        |
| `status_code` | int           | HTTP-style status code (200, 404, etc.) |

## Example

### SDK Setup

```python
from hyperswitch_prism import RecurringPaymentClient

recurring_client = RecurringPaymentClient(
    connector='stripe',
    api_key='YOUR_API_KEY',
    environment='SANDBOX'
)
```

### Request

```python
request = {
    "mandate_id": "mandate_xxx",
    "reason": "customer_canceled"
}

response = await recurring_client.revoke(request)
```

### Response

```python
{
    "mandate_id": "mandate_xxx",
    "status": "REVOKED",
    "revoked_at": "2024-01-15T10:30:00Z",
    "status_code": 200
}
```

## Important Notes

* **Immediate effect** - Revocation takes effect immediately
* **No refunds** - Revoking doesn't refund past charges
* **Idempotent** - Calling revoke multiple times returns same result
* **No undo** - A revoked mandate cannot be reactivated; setup a new one instead

## Error Handling

| Error Code | Meaning           | Action                       |
| ---------- | ----------------- | ---------------------------- |
| `404`      | Mandate not found | Check mandate\_id is correct |
| `410`      | Already revoked   | Mandate was already revoked  |

## Best Practices

* Always revoke when customer cancels subscription
* Keep record of revocation reason for support
* Confirm successful revocation before updating subscription status
* Notify customer that cancellation is complete

## Next Steps

* [charge](/integrations/prism/python/recurring-payment-service/charge.md) - Process recurring payments before revocation
* [setup\_recurring](/integrations/prism/python/payment-service/setup-recurring.md) - Create new mandate if customer resubscribes


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hyperswitch.io/integrations/prism/python/recurring-payment-service/revoke.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.