Airports, Flying Fields & Airport Terminals.
Airport authorities, terminals and ground handling.
- MCC
- 4582
- Category
- Transportation Services
- Cardflo support
- Yes
What MCC 4582 covers
Merchant Category Code 4582 is the ISO 18245 identifier used by the card networks for airports, flying fields & airport terminals. Acquirers, issuers and regulators use this code to set interchange, scheme fees, fraud rules and reporting categories for every transaction your business processes.
Airport authorities, terminals and ground handling. 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 4582 is assigned to airports, flying fields, and airport terminals, including airport authorities and ground handling services. This generally covers airport fees (e. g. , landing fees, parking, terminal usage), concessions, and specific services provided at an airport.
Ticket sizes can vary significantly, from small parking fees to substantial landing and facility usage charges for commercial operators. Transaction frequency can be high for parking or retail concessions, but lower for direct airport authority charges.
Payments for these services are often made by airlines, ground handlers, or individual travellers.
Chargebacks might occur due to disputes over parking fees, facility usage charges, or issues with ground services. 'Service not as described' or 'non-receipt of services' are common, particularly if access was denied or a service was not rendered as agreed.
However, the overall chargeback volume is often lower than for airlines themselves, as these transactions are typically more straightforward. Scheme rules for disputes generally follow standard procedures, though the B2B nature of some transactions with airlines can introduce specific contractual dispute mechanisms.
Cardflo's KYB onboarding processes are tailored to handle complex entities like airport authorities or large service providers, ensuring thorough but efficient verification and compliance checks for securing acquiring services.
Operators within this MCC should prioritise robust invoicing and clear service level agreements, especially for high-value B2B transactions like landing fees or ground handling contracts. For consumer-facing services such as parking, ensure transparent pricing and clear signage.
Given the low dispute rates, focus on optimising transaction routing for cost and efficiency rather than extensive fraud prevention. Tokenisation of cards used for repeat services, like long-term parking, can enhance customer convenience and payment security, while multi-acquirer setup ensures resilience.
The relatively stable nature of transactions means less need for stringent reserve provisions.
Acquirer and acquirer assessment stance.
Low-risk standard board. Given the often governmental or quasi-governmental nature of airport authorities and the B2B focus of many transactions, payment risk is generally well-managed.
No specific reserves are typically expected for established entities unless there are systemic operational issues.
Dispute and chargeback profile.
The primary dispute reason codes for this MCC are typically 13.1 / 4853 ("services not as described") or 13.3 / 4855 ("cancelled merchandise/services"), predominantly for consumer-facing aspects like parking or facility access.
Disputes often arise when a consumer claims a parking space was unavailable, or access was denied despite payment. To counter these, provide photographic evidence of facility usage, clear entry/exit timestamps, and signed terms and conditions outlining service parameters.
For B2B services, signed contracts and proof of service delivery are crucial.
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 4582
- Placement with acquirers that actively board MCC 4582 businesses in your region.
- Fleet, fuel-card and dynamic-pricing transaction flows handled natively.
- Multi-acquirer routing that survives outages during peak travel windows.
- Tokenised storage of payer credentials for repeat journeys and fleet drivers.
- Surcharge rules and pass-through fees configured per scheme and region.
- Dedicated onboarding manager experienced with transport and mobility merchants.
Payment methods typically enabled.
Onboarding checklist.
What acquirers typically ask to see when boarding MCC 4582. Cardflo collects this once and reuses it across every acquirer we route you through.
- Business registration and beneficial-owner documentation (KYB, UBO).
- Operator licence, PSV/HGV credentials or equivalent regulator reference.
- Fleet insurance and passenger liability certificates.
- Refund, delay and cancellation policy aligned with local passenger-rights rules.
- Six months of processing statements demonstrating average ticket size and daily volume.
- Six months of processing statements or bank statements demonstrating trading pattern.
See also: Know Your Customer (KYC) · high-risk merchant · smart routing.
Talk to an acquiring specialist about your MID setup.
Common questions
What are the common chargeback reasons for airport parking services?
Common chargeback reasons for airport parking include 'service not as described' (e. g. , the parking location was different, or facilities unusable), 'cancelled services' (if the booking was cancelled but charged), or 'unauthorised transaction' (if the cardholder disputes the charge itself).
Critical evidence for defence includes proof of booking, entry and exit times logged by automatic systems, CCTV footage, and clear signage regarding terms and conditions at the parking facility.
Do airports have specific PCI compliance requirements beyond standard retail?
Airports must meet all relevant PCI DSS requirements, often involving complex infrastructure due to multiple tenants (airlines, retailers, restaurants) and diverse payment acceptance points (parking, fuel, retail).
Centralised airport IT departments typically oversee compliance for shared infrastructure, but each merchant operating within the airport is responsible for their own specific POS systems and networks. Robust network segmentation and point-to-point encryption (P2PE) are crucial for securing vast payment ecosystems.
How can airports manage transactions for concessionaires and ground handlers efficiently?
Airports can implement a unified payment gateway and processing system that supports multiple MIDs (Merchant IDs) for different concessionaires or business units. This allows for centralised reporting and reconciliation while enabling individual entities to manage their own transactions.
Cardflo's multi-MID routing capabilities are ideal for such complex environments, allowing efficient management of diverse revenue streams under one umbrella while optimising transaction flow for each business.
What specific measures can an airport authority take to minimise parking chargebacks, particularly from CNP transactions?
To minimise parking chargebacks, an airport authority should implement clear, time-stamped digital receipts and enforce strict ANPR (Automatic Number Plate Recognition) integration with payment systems.
Customers should receive immediate email confirmation detailing entry/exit times, duration, and total cost, with a clear link to terms and conditions. For CNP transactions, particularly through apps or websites, strong customer authentication such as 3DS2 should be mandatory.
Additionally, providing self-service kiosks that issue physical receipts upon payment can significantly reduce 'service not received' claims, enhancing transparency and providing tangible proof of purchase that can be used to challenge disputes effectively.
How should an airport terminal optimise its payment gateway to handle both high-volume, low-value transactions and lower-volume, high-value B2B payments?
An airport terminal should employ a smart routing payment gateway that can intelligently direct transactions to the most appropriate acquirer based on transaction value, type, and associated fees.
For high-volume, low-value transactions like food concessions or short-stay parking, prioritise acquirer partners offering competitive micro-payment rates and fast authorisation. For lower-volume, high-value B2B payments, such as landing fees or ground handling, route these through acquirers with strong B2B invoicing support and robust reporting capabilities.
Tokenisation is key for recurring B2B payments, improving security and reducing PCI DSS scope, alongside multi-acquirer failover for payment resilience.
Other MCCs in Transportation 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.