More programs fail on economics than on compliance or technology.
The margin isn't there. Interchange is lower than projected. The BaaS take rate is higher than expected. These are not market problems. They are program design problems.
The four economic failure modes
Designing a fee structure is not benchmarking competitors. Competitor pricing reflects their cost structure, their volume economics, and their willingness to compete on price — none of which are necessarily relevant to your program. Benchmarking anchors the conversation at the market floor rather than the value ceiling.
Fee design starts by quantifying what the program eliminates or enables for the customer. An ACH transaction replacing a check — where the all-in check cost is $8–15 per payment — justifies a very different fee than one priced against the ACH rail cost. A same-day payment premium priced against the receiver's working capital benefit captures a different fraction of value than one priced against the rail cost differential.
Three fee elements missing from most programs: speed tier pricing (same-day and instant delivery priced against receiver value, not rail cost); data and reporting fees (remittance products, ERP integration feeds, and exception management charged separately from transaction execution); and exception pricing (returns, reversals, and manual exception handling priced to recover cost and incentivize cleaner payment behavior).
Full methodology: How to design a fee structure that captures real value →Ten levers that determine payments revenue
These are the specific program design decisions that determine whether your payment flow generates revenue — and how much. Each is designed as part of the architecture, not discovered after launch.
The full detail on each lever — including specific design approaches, benchmarks, and implementation guidance — is in the Payments Monetization framework.
See the full monetization framework →What the monetization design work looks like
The revenue architecture is designed before the build — or it isn't designed.
Interchange capture, float economics, and fee structure get locked in at the program design stage. The programs that capture them are the ones that design for them explicitly.