Why monthly minimums matter
Banks and processors price their operations against the cost to maintain a program (compliance staff, network connectivity, reconciliation tooling, exam preparation). Below a certain transaction volume, that cost is not covered by per-transaction fees. The monthly minimum is how the bank ensures it recoups its baseline cost regardless of how the program performs in any given month.
For a high-growth program, monthly minimums are invisible — actual transaction fees blow past the floor. For a slow-growth or seasonal program, they can become the dominant line item.
When monthly minimums bite
They bite hardest in: (a) launch months when volume hasn't materialized, (b) seasonal troughs in categories like tax-prep or holiday-driven merchants, (c) after a marketing pause or product pivot reduces transaction flow, or (d) under wind-down where the contract still runs but the program is being deprecated.
Common pitfalls
- Stacking minimums. A program can owe minimums to the sponsor bank, the BIN sponsor, the processor, and the BaaS platform simultaneously. Add them.
- Step-up minimums. Some contracts ratchet minimums up by year. Read the schedule.
- No volume-credit carryforward. Most contracts do not let you bank excess transaction fees in one month against a future shortfall. Negotiate this if you can.
Monthly minimums are a fixed cost dressed up as a usage fee. Model them as fixed.