A payment review can become a sales pitch if the provider starts with a promised rate instead of the business, data, agreement, and workflow. Better questions create a more useful result.
What to understand
The review should explain the current state, the assumptions behind each option, and the changes required to implement it. Costs controlled by the processor should be distinguished from pass-through network costs. Hardware, software, integrations, funding, risk, support, and contract terms belong in the same decision record as percentage and per-transaction pricing.
Practical checklist
- What monthly volume, ticket size, card mix, channels, and seasonality were modeled?
- Which fees are pass-through and which are provider-controlled?
- What recurring, gateway, software, PCI, equipment, and support fees apply?
- How do funding, reserves, disputes, refunds, and chargebacks work?
- What contract term, termination, renewal, and equipment conditions apply?
- Which integrations and workflow changes are included?
- Who owns implementation, training, support, and escalation?
- How are approvals, downtime, and exceptions measured?
- What assumptions could materially change the estimate?
- What data can the merchant export and keep?
- What compliance or legal review is still required?
- How will actual results be compared with the proposal?
Bottom line
A trustworthy review welcomes these questions and answers them in writing. If a key cost or operational dependency cannot be explained, it is not ready for a decision.
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