Convenience fees and surcharges on online government payments

Reference article · 6 min read

Every online payment an agency accepts carries a processing cost. The question is not whether that cost exists but who pays it: the agency out of its own budget, the payer as a separate line on the transaction, or a third party that collects the fee and never routes it through the agency's bank account. That single decision shapes the disclosure language on the payment page, the refund policy, the deposit pattern, and the journal entries finance posts every morning.

The answer is rarely purely a policy preference. Card brand operating rules limit what kind of fee may be charged, on which card types, and how it must be disclosed. State statutes and local ordinances determine whether the agency has authority to impose a fee at all and whether it may keep any portion of it. Both change over time, so treat what follows as a framework for asking the right questions rather than a substitute for current rules or the advice of your counsel.

Four ways to cover the cost

• Absorb the cost. The agency pays merchant discount and per-transaction fees from an appropriation. The payer sees one amount. This is the simplest experience and the simplest accounting, but it puts a variable, volume-driven expense into a fixed budget line.
• Flat convenience fee. A fixed amount added for using an alternative channel, applied the same way regardless of payment amount. Predictable for payers of small bills, regressive for large ones.
• Percentage service fee. A rate applied to the transaction, usually structured so that it tracks the underlying processing cost. Works better for widely varying amounts such as property tax or utility bills.
• Third-party collected fee. A processor contracts to collect and retain the fee directly from the payer. The agency receives the full billed amount and records no fee revenue and no processing expense. Vendors often describe this as costing the agency nothing, which is accurate only in the narrow sense that the payer bears the cost.

What the card brand rules allow

Card network rules distinguish among several fee types, and the labels carry real obligations.

A convenience fee is generally permitted only for a genuine alternative payment channel, must be a flat amount rather than a percentage, and must apply to all payment brands and card types in that channel. A surcharge applies to credit transactions only; network rules and several state laws restrict it, it generally may not exceed the agency's cost of acceptance, and it typically requires advance notice to the acquirer and networks plus disclosure at entry and on the receipt. Debit and prepaid transactions are broadly off limits for surcharging, which matters because many residents pay with debit.

Separately, the major networks maintain programs that let registered government and education merchants charge a service fee, including on debit, under defined merchant category codes. Eligibility, registration, and fee structure are set by the networks and change periodically, so confirm current terms with your acquirer before designing the payment page.

Across every model, the fee must be disclosed clearly before the payer commits, shown as a separate amount from the base obligation, and the payer must be able to cancel without paying it.

ACH and cards price differently

ACH debits are priced per item rather than as a percentage, so the cost of a large payment is far lower than on a card. Many agencies charge no fee, or a small flat fee, for ACH and reserve fees for cards. The tradeoffs are operational: returns for insufficient funds or closed accounts arrive days after the payment appears successful, which means posting rules, return handling, and any late penalty relief need to be designed in advance. NACHA rules also impose account validation expectations for internet-initiated debits, so confirm how your provider satisfies that.

Refunds, chargebacks, and partial payments

Decide the refund rule before go-live and publish it. When a third party collected and retained the fee, the agency usually cannot refund it, and staff need a clear explanation for the counter and the call center. When the agency collected the fee itself, card rules generally require that any surcharge be refunded in proportion to the refunded amount. Chargebacks add a second path: the disputed amount may include the fee, and the agency may absorb it even if it never received it. Partial refunds, overpayments, and reversed utility payments each need a documented treatment.

Deposits, reconciliation, and the general ledger

The fee model determines the shape of the daily deposit. Fees collected by a third party never touch agency accounts, so the deposit equals the billed amount and the only reconciliation is gross settlement against the receivable. Fees the agency collects arrive as part of the deposit and must be split between the receivable and a fee revenue account, with processing costs posted as expense, often against a specific appropriation. Settlement is frequently net of processor fees or lands in separate batches for principal and fee, which means the bank deposit will not match any single system total.

Practical safeguards:

• Use a clearing or suspense account so items in transit do not distort revenue.
• Reconcile daily against the processor settlement report, not only the bank statement.
• Confirm fund distribution rules early when one payment splits across funds or agencies.
• Check whether fee revenue and processing expense need budget authority before the season starts.

What to ask vendors and require in the contract

1. Which fee model, by card type and channel, and which network program the arrangement relies on.
2. Who registers with the networks and who bears the risk if rules change mid-term.
3. Exact disclosure text and screen sequence, with cancel-before-charge behavior.
4. Settlement timing, gross or net, and the format and retention of reconciliation files.
5. Refund, chargeback, and ACH return handling, including who funds losses.
6. Current PCI attestation and how the design keeps cardholder data out of agency systems.
7. Rate change notice, termination assistance, and export of payment history.

HQT works with state and local agencies on payment integrations, reconciliation interfaces, and the systems that post transactions to the general ledger.

Frequently asked questions