Processor proposals often use different rate formats, included services, card-mix assumptions, and definitions. Comparing only the largest printed percentage rewards the least complete proposal.
What to understand
Normalize both options against the same recent transaction data. Separate pass-through costs from processor markup and list every recurring or conditional fee. Then compare operational terms: funding, reserves, refunds, disputes, gateway, integrations, hardware ownership, software subscriptions, support, migration, and contract conditions. Any promised savings should be traceable to documented assumptions.
Practical checklist
- Use the same months, volume, transactions, ticket size, and card mix
- Build an all-in monthly and annual cost model
- List one-time, recurring, conditional, hardware, software, and support costs
- Compare funding, risk, refund, chargeback, and reserve policies
- Document implementation, training, data export, support, term, renewal, and exit conditions
Bottom line
The best proposal is the one the business can understand, implement, operate, and verify. Put every material assumption in the decision record before signing.
Next step: Bring a recent processing statement and your current payment workflow to a review. Apex Pay can help map the economics, operating requirements, and questions that deserve an answer before you change anything.
See what these signals mean for your payment stack.
Apex Pay can map the fee architecture, routing, approvals, risk, technology, and service requirements behind the business.
Book a Payment Review