> For the complete documentation index, see [llms.txt](https://developer.paywall.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.paywall.one/payment-orchestration-integration-document/system-data/recurring-payment.md).

# Recurring Payment

**Subscription Type (SubscriptionType)**

<table><thead><tr><th width="200">Type</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>"Unlimited" type continues charging at defined intervals until you cancel the subscription</td></tr><tr><td>2</td><td>"Quantity Based" type charges for the amount defined at subscription creation Once the quantity is completed the payment stops automatically For example if a monthly subscription is created with quantity 10 it charges once per month for 10 months</td></tr></tbody></table>

**Recurring Period Type (RecurringPeriodType)**

<table><thead><tr><th width="200">Type</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>Daily</td></tr><tr><td>2</td><td>Weekly</td></tr><tr><td>3</td><td>Bi-Weekly</td></tr><tr><td>4</td><td>Monthly</td></tr><tr><td>5</td><td>3 Months</td></tr><tr><td>6</td><td>6 Months</td></tr><tr><td>7</td><td>9 Months</td></tr><tr><td>8</td><td>Yearly</td></tr></tbody></table>

**Item Type (ItemsType)**

<table><thead><tr><th width="200">Type</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>Subscription Account</td></tr><tr><td>2</td><td>Product</td></tr><tr><td>3</td><td>Service</td></tr></tbody></table>

**Channel Type (ChannelType)**

<table><thead><tr><th width="200">Type</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>API</td></tr><tr><td>2</td><td>Web</td></tr></tbody></table>

**Callback Content**

<table><thead><tr><th width="269">Parameter</th><th width="190">Type</th><th>Description</th></tr></thead><tbody><tr><td>SubscriptionId</td><td>int</td><td>Recurring payment identifier returned by Paywall at creation</td></tr><tr><td>SubscriptionType</td><td>int</td><td>Recurring payment type</td></tr><tr><td>SubscriptionCode</td><td>string</td><td>Unique code assigned by Paywall to the subscription</td></tr><tr><td>SubscriptionMerchantCode</td><td>string</td><td>Unique code assigned by you to the subscription</td></tr><tr><td>Amount</td><td>decimal</td><td>Recurring payment amount</td></tr><tr><td>Success</td><td>bool</td><td>Payment success or failure status</td></tr><tr><td>FailReason</td><td>string</td><td>Failure reason if the payment is unsuccessful</td></tr><tr><td>PaymentId</td><td>int? - nullable</td><td>Payment identifier</td></tr><tr><td>Attempt</td><td>int</td><td>Number of payment attempts</td></tr><tr><td>AttemptFinished</td><td>bool</td><td>Indicates whether the attempt is completed</td></tr></tbody></table>


---

# 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://developer.paywall.one/payment-orchestration-integration-document/system-data/recurring-payment.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.