> ## Documentation Index
> Fetch the complete documentation index at: https://mam-api.exuratech.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Performance fees

> Calendar schedule and endpoints for reconciling credits and individual payments.

## Supported periods

The leader's `performance_fee_period` uses UTC calendar boundaries.

| Period | Closed period | Current scheduled eligibility |
| - | - | - |
| `OFF` | None | Disabled, including withdrawal and unsubscription collection. |
| `MINUTELY` | Previous calendar minute | Five minutes after each minute boundary. |
| `HOURLY` | Previous clock hour | Five minutes after the top of the hour. |
| `DAILY` | Previous UTC day | Daily at `00:05 UTC`. |
| `WEEKLY` | Previous Sunday-to-Sunday interval | Sunday at `00:05 UTC`. |
| `SEMIMONTHLY` | Day 1–16 or day 16–next month | Day 1 and day 16 at `00:05 UTC`. |
| `MONTHLY` | Previous calendar month | First day of the month at `00:05 UTC`. |

The five-minute eligibility delay allows the closing boundary to settle before crystallization. The resulting MT5 debit and PAYMENT credit remain asynchronous.

In addition to the schedule, pending fees are processed before a follower withdrawal and during allocation unsubscription. Those lifecycle operations do not wait for the next calendar boundary.

If the credited leader is a downstream master with an active cascade-fee agreement, that confirmed credit can create a separate cascade-fee charge. See the [cascade-fee reference](https://mam-api.exuratech.com/reference/cascade-fees.md).

## Reconciliation endpoints

| Method | Path | Purpose |
| - | - | - |
| `GET` | `/api/v1/perf-fee/transactions` | Lists performance-fee credits received by a master. |
| `GET` | `/api/v1/perf-fee/master/{master_login}/investor-payments` | Breaks down individual payments by follower. |
| `GET` | `/api/v1/mam/leaders/{master_login}/payment-account/balance` | Retrieves the MT5 amount, reserved cascade fee, and effective withdrawable amount. |
| `POST` | `/api/v1/mam/leaders/{master_login}/payment-account/withdraw` | Withdraws credited funds. |

## Transaction filters

* `master_login`: required operational leader login.
* `from_at`: inclusive start in ISO 8601.
* `to_at`: exclusive end in ISO 8601.
* `limit`: from `1` to `100`; default `5`.
* `cursor`: continues with IDs earlier than the returned cursor.

```json theme={"theme":{"light":"github-light","dark":"github-dark"}}
{
  "payment_account_login": "139683",
  "items": [
    {
      "id": 984,
      "run_id": 73,
      "kind": "PF_CREDIT",
      "amount": 206.55,
      "currency": "USD",
      "executed_at": "2026-08-16T00:00:10Z"
    }
  ],
  "next_cursor": null,
  "has_more": false
}
```

## Individual payment filters

* `run_id`: limits the query to one consolidated credit.
* `from_at` and `to_at`: interval when a specific run is not requested.
* `limit`: from `1` to `500`; default `100`.
* `cursor`: continuation value returned by the API.

```json theme={"theme":{"light":"github-light","dark":"github-dark"}}
{
  "master_login": "139682",
  "payment_account_login": "139683",
  "items": [
    {
      "run_id": 73,
      "investor_mt5_login": "146537",
      "amount": 95.47,
      "currency": "USD",
      "status": "EXECUTED",
      "executed_at": "2026-08-16T00:00:08Z"
    }
  ],
  "next_cursor": null,
  "has_more": false
}
```

> [!TIP]
>
> Use the consolidated credit's `run_id` to prove which follower payments compose it. Deduplicate individual records before distributing commissions to sponsors or an IB network.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.