Most payment evaluations start in the wrong place: with rates. Rates matter, but they are the easiest thing for any vendor to make look good on a slide, and they are rarely what determines whether the project succeeds.
What determines success is whether the payment system fits the way your agency already works — your business rules, your back-office system, your reconciliation routine and your staffing reality. Here is the sequence of questions that surfaces that.
1. Who pays, and how is it disclosed?
Establish whether the agency carries a cost at all. If a service fee is paid by the payer, ask to see the exact screen where it is disclosed. Fee transparency is both a compliance question and an adoption question — residents who feel surprised by a fee call your office, not the vendor's.
2. What is the contract term, and what happens at the end of it?
A multi-year lock-in shifts risk onto the agency. Ask what happens to your transaction history if you leave, and how a transition is handled. A vendor confident in the service does not need the term.
3. Does it integrate with the system you actually run?
Ask for the specific product and version, not the category. "We integrate with utility billing systems" is not the same as "we are live with your utility billing system in eleven jurisdictions."
Then ask what happens if the integration does not exist. A credible answer includes a standalone option that preserves reporting and reconciliation.
4. What does reconciliation look like on day two?
- Does the daily report carry the identifiers your staff match against, or generic transaction IDs?
- Is reporting real time, or overnight?
- Do all channels — web, phone, counter, mobile, recurring — appear in one view?
- Is the deposit the gross amount owed to the jurisdiction, or a netted figure you have to back into?
5. Who answers when a resident has a problem?
If resident support routes back to your staff, the project has not reduced your workload — it has moved it. Ask specifically whether support is in-house, what the hours are, and whether the vendor's team talks to residents directly.
6. What is the security posture, in writing?
- PCI compliance for cardholder data handling
- Whether agency systems ever store card data (the answer should be no)
- Hosting environment, backup and recovery approach
- Uptime commitment and how peak capacity is handled
- Role-based access control and audit trails for staff actions
7. How long until we are live?
Implementation timelines are a proxy for how much of the work the vendor has already done. A provider with a mature integration library goes live in days or weeks. A provider building from scratch quotes months and delivers later.
8. Will residents actually use it?
Ask for adoption data from comparable jurisdictions, and ask what the vendor does to drive it — reminders, eBilling, autopay, portal accounts, promotion on bills. Adoption is a program, not a launch event.
The short version
A payment processor moves money. A government payments partner understands that a court clerk reconciles against ticket numbers, that a tax office's whole year lands in three weeks, and that a utility billing office measures success in calls not received.
Evaluate for the second thing.