# Giving Tiers & Impact Receipt

## Giving Tiers & Impact Receipt

**File:** `src/content/donate/<language>/-index.md` · **Skill level:** Beginner

Donors give more readily when they can see what an amount pays for. Givo turns each amount into an outcome ("$50 pays for a hygiene kit for a family after a disaster") and shows it on a receipt beside the form. Monthly donors can also pick from named tiers. Both come from the same donate file as the form, so a number changes in one place.

### The Impact List
```yaml
# src/content/donate/english/-index.md
impactMap:
  - amount: 10
    label: "five hot meals at the community kitchen"
  - amount: 25
    label: "school supplies for one child"
  - amount: 50
    label: "a hygiene kit for a family after a disaster"
  - amount: 100
    label: "a food parcel for a family of four"
```

For any amount, the theme uses the line with the **closest amount at or below it**. With the list above:

| The donor gives | The outcome shown |
| --- | --- |
| $25 | school supplies for one child |
| $40 | school supplies for one child (the $25 line) |
| $100 | a food parcel for a family of four |
| $5 | No line is lower, so the receipt names the cause instead ("Where it is needed most") |

- Write each `label` so it reads after "pays for": "a food parcel for a family of four", not "Buys a food parcel".
- The order of the list doesn't matter; the theme sorts it.
- Give one line per preset amount, so every button has its own outcome.
- The costs in the sample are not real: replace them with what your programs actually cost. If you can't stand behind a figure, remove the line.

The impact list is used in three places:

- The **donation form** on `/donate/` and `/tribute/`: the line under the amount and the receipt.
- The **donation widget** in the `photo` hero on the homepage: the outcome line under the amount buttons. The widget shows the first four preset amounts of each frequency.
- The **donate section** in its `quick` layout (see below).

Cause pages use the cause's own `impact` lines in their donation box instead, so the outcome speaks about that cause. See [Causes & Campaign Progress](/givo/customization/causes-campaigns/).

### The Receipt
On `/donate/`, a paper receipt beside the form (inside the form on phones) follows the donor's choices: the amount, the outcome, the card fees if they cover them, the cause, and the total. For a monthly gift it adds a line with the total over a year.

Its words are under `form:` in `src/content/sections/<language>/donate-section.md`:

```yaml
form:
  receiptTitle: "Your gift"
  feesLine: "card fees, covered by you"
  causeLine: "Going to:" # receipt note before the chosen cause
  yearNote: "Over a year, that is {total}." # monthly only
  stamp: "100% to programs" # sample; only if true for your charity
```

The tilted stamp is a claim about your charity. Keep it only if it is true, change it, or set it to `""` to remove it.

### Monthly Tiers
```yaml
tiers:
  - name: "Friend"
    amount: 10
    description: "Five hot meals every month at the community kitchen."
    features:
      - "A short update from the field every quarter"
      - "Cancel or change at any time"
  - name: "Supporter"
    amount: 20
    description: "A new backpack of school supplies almost every month."
    features:
      - "Quarterly updates"
      - "Your name on the supporters' wall (optional)"
```

Each tier has a `name`, a monthly `amount`, a `description` (what it pays for), and `features` (what the donor receives). The plans section on `/donate/` shows them as cards. Each tier's button opens the form with monthly and that amount selected (`?frequency=monthly&amount=20`).

- Add, remove, or reorder tiers in every language, with the same amounts.
- The features in the sample ("An invitation to the annual open day", "A call each year with a program director") are examples. List only what you really offer.
- A tier amount does not have to be one of the preset buttons: the form puts it in the custom amount field.

The heading, button label, and layout of the tiers are in the `plansSection` block of the donate file:

```yaml
plansSection:
  title: "Monthly giving"
  perLabel: "/ month"
  button:
    label: "Give monthly"
    url: "/donate/#give" # each tier adds ?frequency=monthly&amount=<amount> before the #
  options:
    layout: "default" # default | compact
```

`default` shows one card per tier. `compact` shows the tiers as rows in one card.

The plans section can also appear on other pages (`/home-community/` uses it). With an empty `plans: []` in `src/content/sections/<language>/plans-section.md`, it reads the tiers from the donate file. A page can list its own `plans` instead, with `name`, `amount`, `description`, `badge`, `featured`, `customPrice`, `features`, and `button`.

### The Quick Donate Section
`src/content/sections/<language>/donate-section.md` has two layouts:

- `default`: the full donation form, used on `/donate/` and `/tribute/`.
- `quick`: a short panel with the one-time/monthly switch, the amount buttons, and the receipt for the chosen amount. Its button opens `/donate/` with the amount and frequency filled in. It is not on the shipped homepages, but you can preview it at `/elements/` and add it to a page. See [Section Layouts](/givo/customization/section-layouts/).

The `receipt` block at the top of that file is the `quick` layout's receipt:

```yaml
receipt:
  title: "What {amount} does" # {amount} = the chosen amount
  stamp: "Tax-deductible" # sample; check the rules where you are registered
  yearNote: "Over a year, that is {total}." # monthly only
```

<Aside type="caution" title="Tax-deductible is a legal claim">
  The sample `stamp: "Tax-deductible"` and the tax note under the form are
  true only where your organization is registered for it. Check the rules in
  your country before you keep them. `taxNote = false` in `[organization]` of
  `config.toml` hides the tax note.
</Aside>

### Keep The Numbers Equal
Every language has its own donate file. The words are translated, but the numbers must match: `amounts`, `default`, `minimum`, `coverFeesPercent`, the impact amounts, and the tier amounts. `npm run build` compares them with the default language and prints a `[donate]` warning that names each number that differs, for example `tiers.2.amount`.

### Do It With AI
```text
Rewrite my impact list in src/content/donate/<language>/-index.md, in every language, from these
real costs: [AMOUNT: WHAT IT PAYS FOR]. Write each label so it reads after "pays for". Keep one
line for each preset amount, and keep the numbers identical in every language. Then run
npm run build and tell me if a [donate] warning is left.
```

```text
Replace my monthly tiers with these: [NAME, AMOUNT, WHAT IT PAYS FOR, WHAT THE DONOR GETS].
Edit tiers in src/content/donate/ in every language folder, translate the text, keep the amounts
identical, and don't promise anything I haven't listed.
```