U.S. Federal Government Agencies or Departments.
Payments to US federal agencies.
- MCC
- 9405
- Category
- Government Services
- Cardflo support
- Yes
What MCC 9405 covers
Merchant Category Code 9405 is the ISO 18245 identifier used by the card networks for u.s. federal government agencies or departments. Acquirers, issuers and regulators use this code to set interchange, scheme fees, fraud rules and reporting categories for every transaction your business processes.
Payments to US federal agencies. 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 9405 is designated for operations involving payments to U. S.
Federal Government Agencies or Departments. This covers a broad spectrum of payments, including permit fees, application fees, fines, payments for specific government-provided goods or services, and sometimes certain federal taxes or charges.
Payments are made by individuals or businesses to meet legal or administrative requirements.
Ticket sizes range widely, from small administrative fees to significant payments. Payment frequency varies based on the specific agency and service, often being infrequent for individual payments but consistent across the population.
Chargebacks are generally very low due to the authoritative nature of the collecting entity and clear regulatory context. Schemes consider these low-risk transactions.
Cardflo's compliant and robust platform provides these federal entities with a secure and efficient means to collect essential payments.
Merchants in this category should prioritise acceptance of card payments to facilitate citizen interaction and government efficiency. Given the low ticket sizes for many administrative fees and fines, enable robust online payment portals with clear transaction descriptions.
For higher-value transactions, ensure that payment processors can handle larger sums securely. The extremely low dispute rates mean that aggressive fraud prevention, such as 3DS, is less critical than for other sectors.
Focus on clear payment confirmations and transparent refund policies, although refunds are rare. Payment flexibility, including APMs where relevant, can enhance user engagement and compliance.
Acquirer and acquirer assessment stance.
Low-risk standard board. Federal government entities are inherently stable, with low fraud and chargeback risk.
Generally, no reserves are required.
Dispute and chargeback profile.
The most likely chargebacks are 13.1 / 4853 (merchandise not received/services not rendered) or 13.3 / 4855 (non-receipt of merchandise). These typically occur if a payment is made but the corresponding permit, licence, or service is delayed or perceived as not delivered.
To combat these, provide detailed transaction receipts, clear service descriptions, and evidence of application submission dates or service provision. For fines, proof of the violation and payment application is crucial.
Keeping records of communication and delivery of any digital or physical entitlements will also help.
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 9405
- Placement with acquirers that actively board MCC 9405 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 9405. 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
Are there specific U.S. Federal Government regulations that impact payment processing for MCC 9405?
Yes, U. S. federal agencies must adhere to specific regulations, including the Digital Government Strategy and various OMB (Office of Management and Budget) circulars, promoting electronic payments and efficient financial management.
They also need to comply with PCI DSS for card data security. Treasury Financial Manual (TFM) guidance also outlines requirements for federal agency collections, which acquirers must support.
What is the typical timeframe for dispute resolution for payments to U.S. Federal Government Agencies?
While chargebacks are rare, if one occurs, the standard scheme rules for dispute resolution apply, typically allowing cardholders 120-180 days from the transaction date or service date to dispute a charge.
Federal agencies, through their acquirer, would then have 30-45 days to respond with compelling evidence, such as proof of service, payment authorisation, or detailed transactional records. Due to their nature, such disputes are often resolved in the agency's favour.
How can Cardflo effectively support U.S. Federal Government Agencies with their payment processing needs?
Cardflo offers a highly secure and compliant payment gateway that meets stringent federal security standards, including PCI DSS. Our platform provides for high availability and reliability essential for government operations.
Additionally, our comprehensive APM support, including ACH, helps federal agencies offer diverse and accessible payment channels to the public, improving efficiency and citizen satisfaction.
What specific receipt information is critical for US Federal Government transactions to prevent chargebacks?
For US Federal Government payments, receipts should be exceptionally clear, detailing the specific agency, the purpose of the payment (e. g. , 'Passport Application Fee', 'National Park Entry', 'IRS Tax Payment'), the exact date, amount, and a unique transaction ID.
Including a reference to the specific form, application, or case number the payment relates to is highly effective.
This level of detail helps prevent 'non-receipt of merchandise' or 'services not rendered' disputes by unambiguously linking the payment to the public service or obligation it fulfils, providing concrete evidence against claims of unfulfilled transactions. Clearly state any no-refund policies applicable to fees.
How can federal agencies minimise potential disputes related to payment processing errors or duplicate charges?
Federal agencies should implement robust internal reconciliation processes, performing daily checks between payment gateway reports and internal accounting systems to promptly identify and address any processing discrepancies.
Ensure that payment portals prevent users from submitting the same payment multiple times without clear confirmation prompts, especially for one-off fees. Providing distinct transaction identifiers that are prominently displayed on screen and on emailed receipts helps citizens track their payments.
For any detected errors, pro-active communication and swift refunds can prevent disputes escalating to chargebacks, maintaining public trust and reducing administrative overhead.
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.