# Credits

> The community's booking currency. Where credits come from (the plan every month, a one-off product and grants by the team), batches and validity, the month turnover, accrual, late cancellation and no-shows, the Credits tab on the profile, My credits, the community rules and who can do what.

**Credits** are the internal currency a member spends to **book** rooms, desks and people's time ([Bookings](/espacos/reservas) and [Scheduling](/espacos/agendamento)). A credit **is not money**: it can't be withdrawn, can't be transferred and doesn't go through checkout. The community sets how many credits each room costs, and the member gets credits from the plan, from a product or from the team.

## What it's for

| Community | How it uses credits |
|---|---|
| Coworking | The **Resident** plan gives 40 credits a month; the meeting room costs 3 credits per 30 minutes |
| Study space | A one-off pack of 20 credits, valid for 90 days, for those who don't want to subscribe |
| Mentoring | The team grants courtesy credits to whoever made their first purchase |
| Association | Each member gets credits every month to use the auditorium |

## How it works

### Where credits come from

| Source | How it arrives | Shows in the statement as |
|---|---|---|
| **Plan** | Every month, for each active subscription to a plan that has **Credits per month** | Plan |
| **One-off product** | Once, when the purchase completes | Product |
| **Manual grant** | The team gives credits to a member, with a reason | Team |

**Plan.** Each **active** (or trialing) subscription to a plan with credits per month gets the month's amount, and the annual plan gets it **month by month** the same way. Plan credits are valid **until the month turnover**, at midnight in the community's time zone. Whoever switches to a plan with more credits gets **only the difference**; whoever switches to a plan with fewer doesn't lose what they already have. Canceling right away or refunding the subscription takes back what hasn't been used.

**One-off product.** A **one-time payment digital** product can grant credits on purchase, with a validity in days (empty, they don't expire). A product that is already **included in a plan** grants no credits. A refund or a dispute on the purchase takes back the credits it granted (what hasn't been used yet).

**Manual grant.** The team opens a new batch for the member, with a **required reason** and an optional validity (see [Who can do what](#who-can-do-what)).

### Batches and validity

Each grant opens a **batch**, with its own validity. The **balance** is the sum of the batches that **haven't expired yet**. When the member books, the cost comes **first from the batch that expires soonest**, and a refund goes back to the same batch (if it has already expired, it goes back in a new batch, valid for 30 days). The statement is never deleted or edited: a mistake is fixed with a new entry.

The statement shows each entry with its type:

| Type | What it is |
|---|---|
| **Grant** | A new batch (plan, product or team) |
| **Used on a booking** | The cost of a booking |
| **Refund** | Credits given back for a cancellation, a reschedule or a block |
| **Adjustment** | A correction made by the team, with the reason |
| **Expiration** | What expired unused |
| **Revocation** | Credits taken back (a refund, for example) |

### The month turnover

Plan credits expire at **00:00 on the 1st**, in the **community's time zone** (not the viewer's). By default there is **no accrual**: what is left of the plan expires at the turnover and the next month starts with the new allowance.

With **accrual** on, what is left moves to the next month, within:

- the **cap** on what can carry over from one month to the next (empty, no cap);
- the **months an accumulated credit lives**, from 1 to 12.

The change applies **from the next month turnover on** and never changes a batch that already exists.

### Late cancellation and no-shows

Each booking has a **cancellation window**, **24 hours** by default (from 0 to 720; a room can have its own). Whoever cancels or reschedules **within the window** (24 h or more in advance) gets everything back.

| Situation | By default |
|---|---|
| Cancellation **after** the window (late) | The member **loses** the credits |
| **No-show**, marked by the team or by the host | The member **loses** the credits |
| Cancellation by the **team** or by the host | Always refunds in full |
| Room deleted or time blocked with bookings | Always refunds in full |

Each loss rule is a switch in the [community rules](#the-community-rules): turned off, the credit comes back even on a late cancellation or a no-show.

### Paused or past-due subscription

A **paused** or **past-due** subscription **doesn't get the new month** of credits. As for the balance the person already has, **by default they keep using it**, including for booking. This is a platform rule, not a community option: it doesn't show in the settings. When the subscription is active again, the person gets the current month's credits.

## Where to see it

### The Credits tab on the profile

On a member's profile, the **Credits** tab shows:

- the **balance** and what **expires soon**;
- the **batches**, with the source, how much is left in each and the validity (or "does not expire");
- the **statement**, newest first, with who made each entry and the reason.

The member sees **only their own tab**; the team (owner, admin, moderator and finance) sees **any member's**. The moderator only sees: the **Grant credits** and **Adjust balance** buttons appear to the owner, the admin and finance.

### My credits

The member opens **My account › Credits** (**My credits**) and sees the same panel: balance, batches and statement. With no credits, the screen explains where they come from (plan, products or a grant by the team).

### The community rules

**Settings › Credits** gathers the rules (only the owner and the admin change them):

| Field | What it does | Default |
|---|---|---|
| **Carry plan credits over to the next month** | Turns accrual on | Off |
| **Cap on what carries over** | The most that can accumulate | No cap |
| **Months an accumulated credit lives** | For how many months an accumulated credit is still valid (1 to 12) | 1 |
| **In the first month, grant the share for the days left** | Whoever subscribes mid-month gets only the remaining days | Off |
| **Window to cancel or change (hours)** | How far ahead you can cancel without losing (0 to 720) | 24 |
| **Late cancellation loses the credit** | Canceling inside the window gives nothing back | On |
| **No-show loses the credit** | Whoever doesn't show up gets nothing back | On |

## Step by step

### Give monthly credits to a plan

1. Open **Monetization › Plans** and create or edit the plan.
2. In the **Credits per month** field, enter the amount. **0** means the plan grants no credits.
3. Save. Each active subscription starts getting the allowance every month, until the month turnover in the community's time zone.

### Give credits on a product purchase

1. Open the product (digital, one-time payment).
2. In **Credits granted on purchase**, enter the amount (0 = grants none).
3. In **Credits validity (days)**, enter the days, counted from the purchase. Empty, the credits **don't expire**.

> [!NOTE]
> Credits only work in a community that has a **Bookings** or **Scheduling** space. Without one, the app warns under the field: *"Credits only work in a community with a Bookings or Scheduling space. Create one first, then set the credits."* Create the space and go back to the plan or the product.

### Grant or adjust a member's credits

1. Open the member's profile and the **Credits** tab.
2. **Grant credits** opens a new batch: enter the **amount**, the **reason** (required, it shows in the statement) and, if you want, the **validity** (the last day counts until 11:59 PM in the community's time zone).
3. **Adjust balance** corrects the balance: pick **Add** or **Remove**, the amount and the reason. Removing asks for a second confirmation, uses the batches that expire first and **can't go beyond the usable balance**.

## Who can do what

| Action | Owner | Admin | Finance | Moderator | Member |
|---|---|---|---|---|---|
| See their own balance and statement | ✔ | ✔ | ✔ | ✔ | ✔ |
| See any member's balance and statement | ✔ | ✔ | ✔ | ✔ | — |
| Grant credits and adjust the balance | ✔ | ✔ | ✔ | — | — |
| See the community rules | ✔ | ✔ | ✔ | ✔ | — |
| Change the community rules | ✔ | ✔ | — | — | — |
| Book as a **courtesy** (no debit) | ✔ | ✔ | — | — | — |

A **courtesy** is a booking that debits nothing, always with a reason; only the owner and the admin use it (see [Bookings](/espacos/reservas#booking-for-someone-else)).

## Common errors and how to fix them

| Situation | What to do |
|---|---|
| The plan's or product's credits field shows the space notice | Create a Bookings or Scheduling space first |
| *"You are N credits short for this booking"* | The member needs more credits: the team grants them, or they pick a cheaper time |
| I can't remove credits | The usable balance is lower than the request; remove at most the balance |
| I changed accrual and nothing changed in the current batch | The rule applies from the next month turnover and doesn't change existing batches |
| The product grants no credits | Only a **one-time payment digital** product grants them, and not when it is included in a plan |

## Frequently asked questions

**Is a credit money?** No. It only pays for bookings inside the community; it can't be withdrawn or transferred.

**Does the member see when credits expire?** Yes: the balance shows what expires soon and each batch shows the date.

**What happens to the credits if the subscription is canceled?** Immediate cancellation and a refund take back what hasn't been used.

**Can I change a room's cost later?** Yes. Bookings already made keep the cost they had.

## In the API and MCP

The routes live under `/api/credits` (balance, statement, grants, adjustments and rules), documented in the [API reference](/api/referencia). The assistant does all of this in conversation: see [Tools · Credits](/mcp/ferramentas-creditos).

## Related

- [Bookings](/espacos/reservas)
- [Scheduling](/espacos/agendamento)
- [Plans](/monetizacao/planos)
- [Products](/monetizacao/produtos)
- [Roles and permissions](/conceitos/papeis-e-permissoes)