> For the complete documentation index, see [llms.txt](https://jframework.gitbook.io/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jframework.gitbook.io/help/services/billing.md).

# Billing

### Billing Notifications

Our platform uses a structured billing notification system to ensure customers are informed about upcoming subscription expirations, invoice creation, payment due dates, and overdue invoices. This system provides multiple reminders before and after subscription expiry to give customers ample opportunity to renew and avoid service disruption.

### Lifecycle Diagram

<figure><img src="/files/oT9fXzVzSAfTqrQkuPoY" alt=""><figcaption></figcaption></figure>

***

#### Subscription Renewal & Expiry Notifications

Customers are notified in multiple stages before and on the day their subscription expires:

* **3 days before expiry**\
  An email reminder is sent to inform the customer that their subscription will expire soon.
* **1 day before expiry**\
  A second reminder is sent, highlighting the urgency of renewing to avoid service interruption.
* **On expiry date**
  * The system automatically generates a **renewal invoice** with a status of **Unpaid**.
  * The invoice includes all relevant line items for the new billing cycle.
  * A **Due Date of 7 days** is applied, providing time to complete payment.
  * If payment is made within the due date, the invoice is updated to **Paid** and the subscription is reactivated.

***

#### Unpaid Invoice Follow-Up Cycle

If the invoice remains unpaid after the due date, the system will automatically send reminder notifications according to the following schedule:

#### Days 3–30 after due date

* Reminder emails are sent **every 3 days** (e.g., Day 3, 6, 9, 12, … 30).
* These notifications remind the customer of the outstanding invoice and encourage immediate payment.

#### Days 31–75 after due date

* Reminder emails are sent **every 14 days** (e.g., Day 33, 47, 61, 75).
* Each notification includes a **“suspend soon”** warning with a defined suspension date.

#### Day 90 after due date

* If the invoice is still unpaid, the account is **suspended**.
* A final notification email is sent with the subject *“Account Suspended – Payment Required”*, informing the customer that services have been halted until payment is completed.

### Payment Method

Currently, our platform supports payments exclusively through **PayPal**.

* Customers can complete invoice payments securely via PayPal.
* Once PayPal confirms the transaction, the invoice status is updated to **Paid**, and services are restored immediately.
* Future enhancements may include additional payment methods.


---

# 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:

```
GET https://jframework.gitbook.io/help/services/billing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.