> For the complete documentation index, see [llms.txt](https://digitals-private-organization.gitbook.io/rizones45678.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://digitals-private-organization.gitbook.io/rizones45678.org/mobile-app-guide/payments.md).

# Payments

Email and WhatsApp credits, Club Dues collection, and your club website.

This section shows your club's credits and money features. The green tags on screen show the current status, for example "487 left", "Active" or "Live".

## Email (credits)

Your club's Email credits, used whenever you send by email, such as from **Announcements** or **Mass Email**.

**Use it:** tap **Email** to see how many credits are left and your usage. Tap **Buy** or **Top-up** to purchase more, then pay online.

The balance also shows on the tile, for example "487 left".

## WhatsApp (credits)

Your club's WhatsApp credits, used whenever a feature sends by WhatsApp.

**Use it:** tap **WhatsApp** to see how many are left. Tap **Buy** or **Top-up** to purchase more.

The balance shows on the tile, for example "480 left".

{% hint style="warning" %}
If your email or WhatsApp sends are not going out, check the balance here first. At zero credits, nothing sends.
{% endhint %}

## Club Dues (Membership Dues)

Set up member fees, collect payments online or offline, approve them and issue receipts.

Reminders and receipts are built in. Collection figures and the paid and unpaid lists update automatically, and honorary members are excluded.

## Website

Buy or renew your club's public website and see its status.

**Use it:** tap **Website**, then **Buy** the first time or **Renew** after that, and pay online.

The tag shows the current state, for example "Live". Renewal opens in the last 30 days.

{% hint style="info" %}
The website's **content** is edited under **Website Data** in E-Governance & Reporting, not here.
{% endhint %}


---

# 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://digitals-private-organization.gitbook.io/rizones45678.org/mobile-app-guide/payments.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.