AB 1951 authorizes courts, cities, counties, city-and-county governments, and other public agencies to accept credit cards, debit cards, and electronic funds transfers for a specified list of payments (including filing fees, certain bail deposits, towage/storage, child and spousal support, sheriff levies, and donations). The bill conditions that authority on local or Judicial Council approval, allows contracts or master agreements with card issuers and processors, and sets rules for how fees and discounts are accounted for.
The bill matters because it reshapes who bears transaction costs and how payment risk is allocated. It establishes a capped fee regime tied to actual costs, creates agent status and reporting requirements for electronic filing service providers (EFSPs), sets rules for refunds (refunds go to the most recent payer and must be tracked by transaction ID), and makes payments subject to voiding if a chargeback or transfer failure occurs — leaving the underlying debt intact.
At a Glance
What It Does
Permits public agencies, with appropriate approval, to accept credit/debit cards and electronic funds transfers for enumerated government payments; authorizes contracts or master agreements with processors and card issuers and allows recovery of reasonable processing fees up to actual costs. The bill treats an honored card or completed transfer as payment but voids that payment if the transaction is charged back or fails.
Who It Affects
Trial courts and their electronic filing service providers, municipal and county finance offices, payment processors and card issuers, litigants and individuals paying fines, filings, support, tow fees, and parties subject to sheriff levies. Electronic filing managers and EFSPs are explicitly pulled into the agent framework.
Why It Matters
It shifts the operational and financial mechanics of public payments: agencies gain electronic payment options and a legal framework to allocate processing costs, while vendors and EFSPs face new reporting, contract, and refund responsibilities. The chargeback and refund rules also create legal and cash-flow risks for agencies and payers.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
AB 1951 is a practical rewrite of how California public bodies may take electronic payments. It lists specific allowable payments — filing fees, nonfelony bail deposits, towage and storage, support payments, sheriff levy receipts, donations, and other public charges — and then authorizes courts and agencies to accept credit and debit cards or electronic funds transfers for those items, provided the Judicial Council or the relevant governing body first approves.
That initial approval step centralizes oversight while leaving implementation to local entities.
Once approval is in place, a court or agency may enter contracts with card issuers, processing firms, or draft purchasers. The bill requires contracts to address presentment, acceptability, settlement mechanisms, and a “reasonable” fee or discount paid to the processor.
It also allows the Judicial Council to negotiate master agreements that local courts may join, reducing duplication but also concentrating bargaining power and standard terms at the state level.On the mechanics of payment, the bill says that when a card or transfer is honored and paid, that counts as payment as of the date processed. But it makes clear that if the card draft or transfer is later unpaid or charged back, the court or agency’s record of payment is voided and the underlying obligation remains.
Agencies may add a charge-back recovery fee not to exceed their actual costs, except they cannot tack that fee onto obligations that are liens on real property. The statute also places several procedural requirements on EFSPs and agents of the court: EFSPs are deemed agents for limited payment-collection purposes, cannot charge fee-exempt parties for completing an e-filing payment, must report costs under Judicial Council guidelines, and must keep records for a minimum of four years to support possible verification and audits.Finally, the bill addresses refunds and payment methods.
In case of duplicate payments or overpayments, courts must refund the most recent payer and annotate the refund with the transaction ID. Courts and contracted electronic filing managers must accept multiple payment methods from EFSPs – including cards, ACH, and other low-cost networks – and the Judicial Council can inspect agent records to verify compliance.
The Five Things You Need to Know
The bill requires Judicial Council approval before any court may authorize card or electronic payments; cities and other agencies must get approval from their own governing fiscal bodies.
A court or agency may impose a fee for card or electronic payments, but the fee cannot exceed the actual costs the agency incurs in providing the payment option and, for courts, the fee must be approved by the Judicial Council.
Payment by card or electronic transfer counts as payment when honored, but if the draft is unpaid or charged back the payment record and receipt are void and the original obligation remains outstanding.
In cases of duplicate or overpayment, the court must refund the most recent payer and record the transaction ID on the refund; courts must also note transaction IDs when issuing refunds electronically or by check.
Electronic filing service providers are expressly deemed agents of the court for collecting and remitting filing payments, may not charge fee-exempt parties to complete a filing payment, and must retain fee-and-cost records for at least four years for Judicial Council review.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Definitions that frame scope and actors
This section defines key terms — credit card, debit card, card issuer, cardholder, draft purchaser, and electronic funds transfer — anchoring which payment instruments and actors the rest of the statute reaches. Practically, those definitions bring EFSPs and processors into scope as service providers and distinguish cardholder obligations from agency records obligations.
Enumerated payments a public agency may accept electronically
Lists the exact categories of payments that may be accepted by card or electronic transfer: certain bail deposits (nonfelonies), filing and other court fees, towage/storage for removed vehicles, child/family/spousal support (with cardholder authorization), public service fees, taxes/charges due public agencies, sheriff levy payments, and certain county donations. That enumeration limits eligibility — agencies cannot use the statute as a blank check to accept cards for unrelated revenues without additional authority.
Approval gatekeeping for local implementation
Requires courts to obtain Judicial Council approval before authorizing card acceptance and requires cities and other public agencies to obtain approval from their governing fiscal body. The approval step gives centralized oversight for courts while preserving local control for other agencies, and it becomes the procedural trigger for entering contracts with processors.
Mandatory contract terms with processors and card issuers
Permits contracts or master agreements and requires them to cover presentment and settlement mechanics, fee/discount arrangements, and methods to facilitate payment settlement. For compliance officers this means negotiated terms must explicitly allocate settlement timing, chargeback procedures, and fee responsibilities; the statute contemplates both local contracts and Judicial Council master agreements.
Payment finality, chargebacks, and recovery of agency costs
Sets the legal effect: an honored card or completed transfer constitutes payment at the date processed, but if the draft isn’t paid or is charged back the agency’s receipt is void and the payer’s obligation persists. Agencies may impose a charge-back recovery fee not to exceed actual costs, and that recovery can be added to the underlying obligation except where the obligation is a lien on real property. This provision allocates financial risk for returned items and permits limited recovery of administrative costs.
Fee caps, agent status, reporting, audits, and record retention
Allows agencies (and courts with Judicial Council approval) to impose a fee for card or electronic payments capped at the agency’s incurred costs; courts must obtain Judicial Council approval for such fees. The subdivision deems EFSPs agents of the court for payment collection, bars EFSPs from charging exempt filers, requires agents to report costs under Judicial Council guidelines, grants the Judicial Council audit and on-site inspection rights, and requires agents to retain records for at least four years.
Accounting for processor discounts, master agreements, refunds, and payment-method flexibility
Directs that processor fees/discounts be accounted for before statutory distributions, authorizes the Judicial Council to sign statewide master agreements that local courts may join, mandates refunds to the most recent payer in duplicate-payment scenarios with transaction-ID tracking, and requires courts/electronic filing managers to accept multiple payment types (cards, ACH, other low-cost networks) from EFSPs. Together these provisions govern money flow, reconciliation, and practical payment options.
This bill is one of many.
Codify tracks hundreds of bills on Government across all five countries.
Explore Government in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- State and local courts — Gain a statutory pathway to accept modern payments, join Judicial Council master agreements to reduce friction, and recover processing costs under a capped regime.
- Municipal finance offices and counties — Can offer more payment options for taxes, fees, and service charges, improving collections and convenience for residents.
- Electronic filing service providers and payment processors — Get clearer legal status (EFSPs as agents for payment collection) and a structured marketplace for contracts and master agreements.
- Paying public — Individuals and businesses that prefer cards or ACH gain choice and convenience for a narrow set of government payments, including filings and support.
Who Bears the Cost
- Cardholders and accountholders — May face administrative or convenience fees passed through to cover processing costs, and risk having a payment voided if a chargeback occurs, leaving the obligation unpaid.
- Public agencies and courts — Must implement contract, reporting, reconciliation, and refund processes, bear audit and recordkeeping burdens, and may initially shoulder chargeback losses until recovery mechanisms take effect.
- Electronic filing service providers and contractors — Must comply with agent reporting, retain records for four years, cannot charge fee-exempt filers for payment completion, and may face on-site audits by the Judicial Council.
- Small jurisdictions and under-resourced agencies — Face upfront implementation costs and contracting complexity that may outweigh the modest processing-fee recoveries, at least initially.
Key Issues
The Core Tension
The central tension is between expanding convenient, modern payment options (and allowing agencies to recover processing costs) versus protecting payers and agencies from the financial and administrative risks of returned transactions and variable processor fees; the statute tries to allocate costs and oversight, but doing so inevitably shifts risk either onto individual payers or onto public agencies and their contractors.
The bill balances convenience against several operational and equity concerns but leaves key implementation choices unresolved. It allows agencies to recover only their actual costs, yet it does not define a clear methodology for calculating those costs or resolving disputes when processors’ fees and discounts vary by contract.
That leaves room for divergent treatment across counties and courts, potential inconsistencies in what is deemed a recoverable ‘cost,’ and compliance challenges for auditors.
The statute assigns payment finality but preserves agency exposure to chargebacks: a payment that was “honored” can later be voided and the payer’s obligation revived. That creates cash-flow volatility for agencies that rely on processed receipts and incentivizes conservative settlement timing or holding periods, which counteracts the convenience the bill intends to create.
The refund rule that returns duplicate payments to the most recent payer is administratively sensible but creates potential gaming and reconciliation complexity for multi-party transactions (for example, an EFSP paying on behalf of a filer versus the filer paying directly). Finally, the Judicial Council’s right to inspect agent premises and records raises privacy and contract-security questions that the bill does not explicitly address, including how to handle sensitive payment data and who bears the cost of compliance with audit demands.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.