Skip to main content
The Fee Policy section controls how the plugin behaves when it cannot compute a fee. It also caps the maximum fee the plugin applies to a single transfer. This policy guards the fee calculation that the Fees Engine runs.

​
Accessing the section

1

Open Settings

In the Bank Transfer sidebar, click Settings.
2

Expand Fee Policy

Click the section header to expand it.

​
Fields

​
Fail Closed Default

This toggle sets the plugin behavior when the fee service is unavailable. It applies to a timeout, a connection failure, or a server error from the fee service:
  • On (fail closed) — the plugin blocks the transfer until it computes the fee reliably. This option is safer but stricter.
  • Off (fail open) — the plugin lets the transfer proceed without the fee. This option is looser but allows transfers during a partial failure.
Prefer Fail Closed in production for TED Out flows. A transfer that proceeds without a reliable fee can create unbilled operations or reconciliation gaps.

​
Max Fee Amount

This field sets the hard cap on the total fee for a single transfer. You enter it in currency units, for example 50.00. The plugin stores the cap in cents. If the calculated fee exceeds this cap, the plugin rejects the transfer. The plugin does not trim the fee to the cap. Use the cap as a guardrail against misconfigured fee rules that produce oversized charges.

​
Saving changes

Click Save in the toolbar at the top of the page. The Settings History tab records every change. The history shows the maximum fee in cents, because the plugin stores that value in cents.

​
Tips

  • Review the Fee Policy together with your Fees Engine configuration. The cap blocks a transfer whose fee exceeds the limit. Still fix misconfigured fee rules at the source.
  • Raise the cap only when you must. A higher cap allows a larger fee per transfer. Tell the team that operates the plugin first, so the team can review the change.