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

# Financial safety

> Operate without blind retries and keep the CRM ledger aligned with PAMM and MT5.

Deposit and withdrawal endpoints do not accept a CRM idempotency key. Your CRM must prevent duplicate requests and reconcile uncertain results before retrying.

## Safe withdrawal sequence

<Steps>
  <Step title="Create a durable operation">
    Generate a unique CRM reference and store the withdrawal as `PENDING` before sending the request.
  </Step>

  <Step title="Send the request once">
    Call `/investor/withdraw` with the CRM reference in `comment`.
  </Step>

  <Step title="Persist the full outcome">
    Store requested and effective amounts, pending fee, available balance, and `mt5_deal_id`.
  </Step>

  <Step title="Reconcile uncertainty">
    If the HTTP outcome is unknown, inspect the MT5 balance and fee records before considering another request.
  </Step>

  <Step title="Complete locally">
    Mark the CRM operation `COMPLETED` only after the executed result is known.
  </Step>
</Steps>

## Safe unassignment sequence

1. Resolve the active relationship with `/info/investor/{login}/master`.
2. Send `/subscriptions/unassign` once.
3. If the response is `PAUSED`, poll `/info/subscriptions`; do not repeat the command.
4. Complete the CRM workflow only when the subscription is `CANCELLED` and `ended_at` is populated.

## Critical rules

| Rule            | Required behavior                                                             |
| --------------- | ----------------------------------------------------------------------------- |
| Investor funds  | Use only `/investor/deposit` and `/investor/withdraw`.                        |
| Master funds    | Never send direct external deposits.                                          |
| Payment account | Receive fees only; do not treat it as Investor capital.                       |
| Fee rate        | Validate a decimal from `0` to `1` in both backend and UI.                    |
| Open positions  | Expect assignment, withdrawal, or unassignment to be blocked when applicable. |
| Credentials     | Keep API keys and MT5 passwords out of frontend clients and logs.             |
| Compatibility   | Ignore unknown response properties and depend only on documented fields.      |

<CardGroup cols={2}>
  <Card title="Previous: Asynchronous operations" icon="arrow-left" href="/reliability/async-operations">
    Review polling and completion conditions.
  </Card>

  <Card title="Next: Errors" icon="arrow-right" href="/reliability/errors">
    Handle HTTP failures without creating inconsistent state.
  </Card>
</CardGroup>