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

# Setup Recurring

## Overview

The `setup_recurring` method establishes a payment mandate for future recurring charges. This enables subscription billing without requiring customer presence for each transaction.

**Business Use Case:** A customer signs up for your SaaS monthly plan. Setup a recurring mandate so you can charge their card automatically each month.

## Purpose

| Scenario           | Benefit                   |
| ------------------ | ------------------------- |
| SaaS subscriptions | Automate monthly billing  |
| Utility bills      | Enable automatic payments |
| Membership dues    | Automate renewals         |

## Request Fields

| Field                           | Type           | Required | Description                    |
| ------------------------------- | -------------- | -------- | ------------------------------ |
| `merchant_recurring_payment_id` | str            | Yes      | Your unique recurring setup ID |
| `amount`                        | Money          | Yes      | Initial amount for validation  |
| `payment_method`                | PaymentMethod  | Yes      | Card or payment method         |
| `address`                       | PaymentAddress | Yes      | Billing address                |
| `auth_type`                     | str            | Yes      | THREE\_DS or NO\_THREE\_DS     |
| `setup_future_usage`            | str            | No       | ON\_SESSION or OFF\_SESSION    |

## Response Fields

| Field                            | Type          | Description            |
| -------------------------------- | ------------- | ---------------------- |
| `merchant_recurring_payment_id`  | str           | Your reference         |
| `connector_recurring_payment_id` | str           | Connector's mandate ID |
| `status`                         | PaymentStatus | ACTIVE, FAILED         |
| `mandate_reference`              | dict          | Mandate ID and status  |
| `status_code`                    | int           | HTTP status code       |

## Example

### SDK Setup

```python
from hyperswitch_prism import PaymentClient

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

### Request

```python
request = {
    "merchant_recurring_payment_id": "recurring_001",
    "amount": {
        "minor_amount": 2900,
        "currency": "USD"
    },
    "payment_method": {
        "card": {
            "card_number": {"value": "4242424242424242"},
            "card_exp_month": {"value": "12"},
            "card_exp_year": {"value": "2027"},
            "card_cvc": {"value": "123"}
        }
    },
    "address": {
        "billing": {
            "line1": "123 Main St",
            "city": "San Francisco",
            "state": "CA",
            "zip": "94102",
            "country": "US"
        }
    },
    "auth_type": "NO_THREE_DS",
    "setup_future_usage": "OFF_SESSION"
}

response = await payment_client.setup_recurring(request)
```

### Response

```python
{
    "merchant_recurring_payment_id": "recurring_001",
    "connector_recurring_payment_id": "seti_3Oxxx...",
    "status": "ACTIVE",
    "mandate_reference": {
        "mandate_id": "pm_3Oxxx...",
        "mandate_status": "ACTIVE"
    },
    "status_code": 200
}
```

## Next Steps

* [RecurringPaymentService.charge](/integrations/prism/python/recurring-payment-service/charge.md) - Use mandate for charges
* [RecurringPaymentService.revoke](/integrations/prism/python/recurring-payment-service/revoke.md) - Cancel the mandate


---

# 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/payment-service/setup-recurring.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.