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

# Configuring Fee Policy

> Set the default fee behavior and maximum fee amount for Bank Transfers.

The **Fee Policy** section controls how the plugin behaves when it encounters unexpected conditions around fees, and caps the maximum fee amount that can be applied to a single transfer. It acts as a safety net on top of the fee calculation performed by the [Fees Engine](/en/midaz/fees/console/fees-engine-overview).

## Accessing the section

***

<Steps>
  <Step title="Open Settings">
    In the Bank Transfer sidebar, click **Settings**.
  </Step>

  <Step title="Expand Fee Policy">
    Click the section header to expand it.
  </Step>
</Steps>

## Fields

***

### Fail Closed Default

Toggle that defines what happens when the plugin cannot compute a fee with confidence (for example, when the fee service is unreachable or returns an unexpected response):

* **On (fail closed)** — the transfer is blocked until the fee can be computed reliably. Safer but stricter.
* **Off (fail open)** — the transfer proceeds without the fee component. Looser but continues under partial failures.

<Warning>
  Prefer **Fail Closed** in production for TED Out flows. Allowing a transfer to proceed without a reliable fee calculation can lead to unbilled operations or reconciliation gaps.
</Warning>

### Max Fee Amount

The hard cap on the total fee the plugin will apply to a single transfer. Entered in regular currency units (for example, `50.00`); the plugin stores it internally in cents.

If the calculated fee exceeds this cap, the plugin trims the fee down to the configured maximum. Use this as a guardrail against misconfigured fee rules that would otherwise produce disproportionate charges.

## Saving changes

***

Click **Save** in the toolbar at the top of the page. Every change is recorded in the [Settings History](/en/rails/ted/console/bt-viewing-settings-history) tab. Monetary values are stored in cents internally; the history reflects that.

## Tips

***

* Review the Fee Policy together with your Fees Engine configuration. The cap here only protects you from *over-applying* a fee; misconfigured fee rules should still be fixed at the source.
* When updating the cap upward, notify the team operating the plugin. Larger caps allow larger per-transfer fees; you probably want that change to be explicit and reviewed, not silent.