Fines.
Government-imposed fines and penalties.
- MCC
- 9222
- Category
- Government Services
- Cardflo support
- Yes
What MCC 9222 covers
Merchant Category Code 9222 is the ISO 18245 identifier used by the card networks for fines. Acquirers, issuers and regulators use this code to set interchange, scheme fees, fraud rules and reporting categories for every transaction your business processes.
Government-imposed fines and penalties. Choosing the right MCC is critical: an incorrect code can lead to higher interchange, surcharges, or, in regulated categories, declined transactions and account holds.
MCC 9222 is for fines, typically issued by government bodies or associated agencies (e. g. , parking fines, traffic penalties, library fines). These are one-off, non-negotiable payments.
Ticket sizes are generally low to medium. Payments are almost exclusively card-not-present, usually made online or by phone.
Chargebacks are rare for legitimate fines but can occur due to 'not as described' (e. g. , disputing the validity of the fine) or 'unauthorised transaction' (card fraud).
Because they are mandated payments, genuine disputes are usually settled directly with the issuing authority rather than via chargeback. Schemes monitor this MCC for high fraud rates.
Cardflo provides governmental entities with secure payment processing for fines, offering compliant solutions that prioritise fraud prevention while simplifying payment collection for citizens.
Organisations accepting fine payments should prioritise simplicity and security for their CNP channels. Implement 3DS2 as the default for all online transactions to combat fraud effectively, given the prevalence of 'unauthorised transaction' disputes.
As ticket sizes are generally low to medium, focus on optimising the payment flow for quick completion and ensuring clear payment confirmation.
Given the 'take it or leave it' nature of fines, genuine disputes are rare but can arise from incorrect fine details; ensure transaction data includes the fine reference number for easy reconciliation. Multi-acquirer routing helps prevent declines.
Acquirer and acquirer assessment stance.
Low-risk standard board. These are governmental or quasi-governmental payments with infrequent genuine chargebacks.
Fraud prevention is key. No typical reserve requirements.
Dispute and chargeback profile.
The most common dispute reason for fines is "4837 / 10.4 (fraud, card absent environment)", where an unauthorised individual pays a fine using stolen card details.
Less frequently, "4853 / 13.1 (services not as described)" may occur if a cardholder disputes the validity of the fine itself. To counter fraud, robust 3DS authentication data and IP address information are key.
For 'services not as described', evidence of the fine type, issuing authority, and the unique fine reference number, alongside any legal documentation justifying the charge, typically defeats the dispute.
See also: chargeback management · payment response codes · Compelling Evidence 3.0.
Book a scoping call to see how Cardflo would set you up.
How Cardflo handles MCC 9222
- Placement with acquirers that actively board MCC 9222 businesses in your region.
- Surcharge and convenience-fee handling compliant with government-sector rules.
- ACH/eCheck alongside card acceptance for taxpayer and citizen payments.
- Reporting and reconciliation suitable for public-sector audit requirements.
- Settlement timing options that fit treasury and public-finance cycles.
- Dedicated onboarding manager familiar with public-sector procurement and compliance.
Payment methods typically enabled.
Onboarding checklist.
What acquirers typically ask to see when boarding MCC 9222. Cardflo collects this once and reuses it across every acquirer we route you through.
- Public-body registration, department reference or equivalent.
- Authorisation letter confirming the entity may charge the fee in question.
- Refund, appeal and cancellation policy aligned with statutory rules.
- Descriptor and reference-number specification so cardholders can identify charges.
- Six months of processing statements or ledger extract demonstrating volume.
- Business registration and beneficial-owner documentation (KYB, UBO).
See also: Know Your Customer (KYC) · high-risk merchant · smart routing.
Talk to an acquiring specialist about your MID setup.
Common questions
What security measures are most effective for processing fines online?
For processing fines online, strong security measures are essential to combat card-not-present fraud. This includes mandatory 3D Secure authentication, robust fraud screening tools that check IP addresses and cardholder data against fraud databases, and ensuring the payment portal is PCI DSS compliant.
Cardflo's fraud tooling helps mitigate these risks.
If a cardholder disputes a fine, will it lead to a chargeback in MCC 9222?
Disputes over the legitimacy of a fine itself (e. g. , arguing a parking ticket is unjust) are typically administrative and handled directly with the issuing authority.
A direct chargeback in this MCC is more likely to be an 'unauthorised transaction' (fraud) rather than a 'services not received' or 'not as described' dispute related to the fine itself.
The fine issuer needs to provide strong evidence of the fine's validity if a chargeback does occur.
Are there specific billing descriptor requirements for fines?
Yes, clear and concise billing descriptors are crucial. They should include the name of the issuing authority and potentially a reference number for the fine (e. g. , 'CITY COUNCIL FINE #12345').
This helps cardholders recognise the transaction and reduces unnecessary disputes or queries to their bank, improving customer service and reducing operational overhead.
How can we prevent fraudulent payments when individuals pay fines on behalf of others?
When individuals pay fines on behalf of others, implement mandatory 3DS2 authentication for all online payments. This verifies the cardholder's identity, even if it's not the individual named on the fine.
Capture the IP address of the transaction and, if possible, details of the person making the payment (if different from the cardholder) versus the person the fine relates to. Ensure transaction receipts clearly link the payment to the specific fine reference number.
This comprehensive data set provides strong evidence against 'unauthorised transaction' chargebacks.
What information should be included on payment receipts for fines to best defend against disputes?
Payment receipts for fines should conspicuously display the issuing authority, the specific fine reference number, the date and time of the payment, and the amount paid.
Crucially, include a clear statement that payment of the fine does not constitute an admission of guilt but rather settles the obligation. Providing a direct contact method for disputing the fine's validity (distinct from repayment issues) channels appropriate queries.
This level of detail helps to distinguish legitimate payments from fraud and clarifies the service rendered, assisting in dispute resolution.
Other MCCs in Government Services
Related industries.
Related features.
Related guides.
Ready to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.