> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paylead.fr/llms.txt
> Use this file to discover all available pages before exploring further.

# Pool & payout

> How Paylead fills the Consumer pool, triggers the payout against the Program Manager's thresholds, and settles the Program's commission.

[Ventilation](/glossary#ventilation) is how the value of each matched [Offer](/glossary#offer) is distributed: the [Consumer](/glossary#consumer)'s [Cashback](/glossary#cashback) into their [pool](/glossary#pool) (the cagnotte), and the [Program Manager](/glossary#program-manager)'s commission back to the Program. Paylead manages the pool, runs the Consumer payout, and settles the Program Manager's commission. The Cashback is owed by the Program Manager to its Consumers; Paylead distributes it on the Program Manager's behalf.

## Set up a Consumer for payout

Before Paylead can pay a Consumer, two pieces of information must be registered for that Consumer.

<Steps>
  <Step title="Basic KYC">
    Identity data Paylead forwards to its payment provider to register the Consumer's payout account. Only `first_name`, `last_name`, and `email` are required. Register it with [Create or update a consumer's KYC](/program/api/perks/kyc/create-or-update-a-consumers-kyc-mangopay-natural-user).
  </Step>

  <Step title="Payment account">
    The bank account where the Consumer wants to be paid out, set through `target_account`. Designate it with [Designate the bank account where a consumer wants to be paid out](/program/api/perks/upm/designate-the-bank-account-where-a-consumer-wants-to-be-paid-out). You can also [read](/program/api/perks/upm/read-the-payment-account-currently-designated-for-a-consumer) or [revoke](/program/api/perks/upm/revoke-the-consumers-currently-designated-payment-account) it.
  </Step>
</Steps>

<Warning>
  KYC is **personal data**. Handle it under GDPR and send only what the payout requires.
</Warning>

## How Ventilation works

Every pooled [Reward](/glossary#reward) feeds the Consumer's cagnotte. Paylead sums the Reward amounts and triggers the payout against two thresholds, both set by the Program Manager.

```mermaid theme={null}
flowchart TD
  R[Pooled Rewards] --> POOL[Consumer cagnotte]
  POOL --> S{Sum of Reward amounts}
  S -->|Reaches the manual threshold| MAN[Consumer can trigger the payout]
  S -->|Reaches the auto threshold| AUTO[Paylead triggers the payout automatically]
  MAN --> PAY[Cashback paid to the Consumer]
  AUTO --> PAY

  classDef neutral fill:#f1efe8,stroke:#888780,color:#2c2c2a
  classDef decision fill:#ffffff,stroke:#888780,color:#2c2c2a
  classDef primary fill:#e6f1fb,stroke:#0465ff,color:#042c53
  classDef success fill:#eaf3de,stroke:#3b6d11,color:#173404

  class R,MAN,AUTO neutral
  class POOL primary
  class S decision
  class PAY success
```

## When a Reward enters the pool

A Reward feeds the cagnotte once it reaches the Consumer-facing `Pool` status. **When** that happens depends on a Program-level model the Program Manager chooses.

| Model               | A Reward is pooled when                              | How it is funded                                                                                                                                      |
| ------------------- | ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Best experience** | It is technically `VALIDATED`.                       | Paylead advances the funds from a working capital line, so the Cashback is available to the Consumer immediately after the validation delay.          |
| **On receipt**      | The funds are available, technical status `PAID_IN`. | No advance: Paylead transfers the funds per the contractual payment term, 3 months after the last day of the month in which the Reward was validated. |

<Note>
  Every `VALIDATED` Reward is guaranteed to be paid by Paylead. The **Best experience** model relies on that guarantee to front the Cashback to the Consumer at validation, instead of waiting for `PAID_IN`.
</Note>

For the full list of both status tracks and what each value means, see the canonical [Reward status flow](/program/user-journey/guides/reward-lifecycle#the-reward-status-flow).

## Triggering the payout

The Program Manager defines two thresholds on the pooled amount:

* **Manual threshold**: once the sum of pooled Reward amounts reaches it, the Consumer can [trigger the payout](/program/api/perks/upm/trigger-a-payout-of-the-consumers-pool) from the app.
* **Auto threshold**: once the sum reaches it, Paylead pays out the cagnotte automatically.

<Tip>
  Letting the pool grow before payout keeps transfers meaningful, reduces transfer overhead, and turns the visible cagnotte into a marketing lever. The manual threshold lets motivated Consumers cash out sooner; the auto threshold guarantees nobody is left waiting indefinitely.
</Tip>

## Program commission settlement

The Program Manager's commission (its share of the Offer value) is settled separately from the Consumer payout, through a **debit note**.

| Moment        | Event                                                                                          |
| ------------- | ---------------------------------------------------------------------------------------------- |
| Month M       | Rewards reach `VALIDATED`.                                                                     |
| 01 / M+2      | Paylead issues the debit note for those commissions, by email and on [Shift](/glossary#shift). |
| 01 / M+2      | The Program Manager issues an invoice from the debit note.                                     |
| 60 days later | Paylead settles the invoice.                                                                   |

<Info>
  Under European regulation, Paylead pays an invoice **60 days after it is issued**. Example: Rewards validated in March produce a debit note on 1 May; if the Program Manager invoices the same day, Paylead settles around 30 June.
</Info>

## Check a Consumer's pool

A Program Manager can read a Consumer's aggregated pool status (pooled amount and Reward counts) with [Get a consumer's aggregated reward information](/program/api/thub/rewards/get-a-consumers-aggregated-reward-information).

## Reconciliation and reporting

The Program Manager does not pull a distribution file. Paylead runs the Consumer-level payout. For accounting and reconciliation, use the [Reporting](/program/user-journey/guides/reporting) exports via the [Paylead API](/program/user-journey/quickstart).

## Edge cases

<AccordionGroup>
  <Accordion title="The Consumer leaves the Program before payout">
    A Consumer may unsubscribe between Reward validation and payout. Paylead stops the payout because the account link is no longer authoritative. Pending pool balance handling is documented in the Program's terms and conditions.
  </Accordion>

  <Accordion title="The transaction is refunded before the Reward is validated">
    Paylead reconciles the refund against the original transaction and cancels the Reward during the refund window, before it reaches `VALIDATED`. Refunds that land after validation are handled according to the Program's terms and conditions.
  </Accordion>

  <Accordion title="Multiple Rewards on one Consumer">
    A Consumer's pool aggregates every pooled Reward. Paylead pays out the accumulated balance.
  </Accordion>

  <Accordion title="Currency">
    All amounts are denominated in **EUR**. Paylead does not support multi-currency Programs.
  </Accordion>
</AccordionGroup>

## What's next

<CardGroup cols={2}>
  <Card title="Loyalty journey" icon="medal" href="/program/user-journey/loyalty-journey">
    The loyalty wallet Consumers build alongside their Rewards.
  </Card>

  <Card title="Webhooks" icon="zap" href="/program/user-journey/concepts/webhooks">
    Get notified when a payout succeeds or fails.
  </Card>
</CardGroup>