# RevCent MCP Guide: `RenewSubscription`

Brief AI/MCP-focused guide for manually renewing a RevCent Subscription.

Reference overview:

```text
https://revcent.com/documentation/markdown/mcp/operation/OverviewSubscription.md
```

---

## Operation Summary

Operation:

```text
RenewSubscription
```

Purpose:

```text
Manually renew a subscription using the subscription ID.
```

Critical note:

```text
RevCent automatically processes subscription renewals internally.
```

Use `RenewSubscription` only when the user explicitly wants to charge the customer immediately.

---

## When to Run

Run `RenewSubscription` only with explicit purpose.

Valid examples:

- customer requests immediate renewal,
- support needs to process an early refill,
- customer authorizes an immediate charge,
- a failed/overdue subscription has been reviewed and manual recovery is approved,
- an approved recovery workflow intentionally charges now,
- the business wants to renew immediately rather than wait for the automatic schedule.

Do not use this operation just because a subscription is due soon.

RevCent already handles scheduled renewals.

---

## Important Billing Warning

Manual renewal charges the customer immediately.

It can also affect the next renewal date.

The operation behavior notes:

```text
Manually renewing a subscription will set the next renewal date according to the Subscription Profile duration setting in combination with the date of the manual renewal.
```

So manual renewal can shift the future renewal schedule.

---

## Input Schema

Required:

| Field | Type | Description |
|---|---|---|
| `subscription_id` | string | 20-character Subscription ID. |

Example:

```json
{
  "subscription_id": "SSSSSSSSSSSSSSSSSSSS"
}
```

---

## Output

Successful output can include:

| Field | Description |
|---|---|
| `api_call_id` | 20-character API call ID. |
| `api_call_unix` | Unix timestamp of API call initiation. |
| `code` | Response code. `1` indicates success. |
| `subscription_id` | 20-character Subscription ID. |
| `result` | Result message. |

---

## Best Practices

- Retrieve the subscription first with `GetSubscription`.
- Confirm the customer/business wants an immediate charge.
- Confirm payment recovery context if the subscription is overdue.
- Do not manually renew for reporting, lookup, status checks, or testing.
- Do not blindly retry failed renewals.
- Review decline reason and salvage/recovery context before manual recovery.
- Explain that RevCent normally renews subscriptions automatically.
- Explain that manual renewal can change the next renewal date.

---

## AI / Voice / Recovery Guidance

If used inside an AI Assistant, AI Voice Agent, or external recovery workflow:

- confirm the customer authorized an immediate charge,
- confirm the subscription is still recoverable,
- check hard-decline/fraud/invalid-card reasons before retrying,
- consider using salvage transaction recovery workflows when applicable,
- create a note or metadata outcome after the attempt.

---

## Final AI/MCP Instruction

Use `RenewSubscription` only when there is an explicit reason to charge the customer immediately. RevCent automatically processes scheduled renewals internally, so manual renewal should not replace normal automatic renewal processing.


---
Document Parent Directory
* [Operations](https://revcent.com/documentation/markdown/mcp/operation/index.md) - AI/MCP details and overviews for operations available within the RevCent MCP.