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 refuses an outgoing transfer. For an incoming TED, it refuses the credit and returns the money to the sender (STR0010). Before it turns the toggle on, the Console asks you to confirm with Yes, fail closed.
  • Off (fail open): the transfer proceeds with no fee charged. This is the default.
The toggle applies to incoming and outgoing transfers together. With Fail Closed, every incoming TED that arrives while the fee service is down goes back to its sender, and you cannot undo that return.

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 an outgoing transfer. The plugin does not trim the fee to the cap. An incoming TED whose fee exceeds the cap is credited with no fee, or returned to the sender when Fail Closed Default is on. If you clear the field, the plugin applies the deployment default. 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.

Tips


  • Review the Fee Policy together with your Fees Engine configuration. The cap blocks an outgoing 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.