Ambulance Services.
Emergency and non-emergency medical transport.
- MCC
- 4119
- Category
- Transportation Services
- Cardflo support
- Yes
What MCC 4119 covers
Merchant Category Code 4119 is the ISO 18245 identifier used by the card networks for ambulance services. Acquirers, issuers and regulators use this code to set interchange, scheme fees, fraud rules and reporting categories for every transaction your business processes.
Emergency and non-emergency medical transport. Choosing the right MCC is critical: an incorrect code can lead to higher interchange, surcharges, or, in regulated categories, declined transactions and account holds.
Merchants in MCC 4119 provide ambulance services, encompassing both emergency and non-emergency medical transport. Transactions are often urgent and distressed.
Ticket sizes vary significantly, ranging from moderate co-pays for insured patients to very high costs for uninsured emergency transport. Payment frequency is typically one-off per service event.
Settlements can be complex due to insurance billing and patient responsibility.
Chargebacks are moderately low but can arise from 'services not rendered' (e. g. , cancelled transport), 'duplicate processing,' or 'not recognised' disputes, especially when patients are discharged from care and later receive a bill they don't immediately recognise or dispute.
There are no specific card scheme programmes for this MCC.
Cardflo’s robust transaction monitoring and detailed reporting can help identify and reconcile complex billing scenarios common in healthcare, reducing 'duplicate' or 'not recognised' chargebacks. Our ability to process both card and alternative payment methods ensures flexibility for patients settling medical bills.
For ambulance services, payment configurations must handle distressed and often high-value, one-off transactions. Implement robust tokenisation for recurring patient payment plans, but ensure clear consent.
Due to the sensitive nature, prioritise clear and compliant billing descriptors to minimise 'unrecognised' disputes. Cardflo's acquirer partners typically require strong KYB verification and operational licences.
Reserve expectations may be slightly higher due to potential payment delays from insurance processing, so ensure your risk team is prepared with transparent settlement reconciliation and chargeback documentation.
Acquirer and acquirer assessment stance.
Medium-low risk standard board. While essential services, there can be complexities with insurance claims and patient billing that occasionally lead to disputes.
Due diligence often focuses on state/national licensing and clear billing practices.
Dispute and chargeback profile.
The main chargeback reasons are 10.4 (other fraud – card absent environment), 13.1 / 4853 (goods or services not as described), and 13.3 / 4855 (non-receipt of goods or services). Fraud can arise from compromised cards used for medical transport.
Service disputes often relate to billing discrepancies or perceived service quality. To combat these, securely capture and link patient consent to service provision, itemise services clearly on all invoices, and maintain dispatch logs showing time, location, and service provided.
For fraud, match billing details to patient records rigorously. Evidence of insurance claims and patient portion billing is also vital.
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 4119
- Placement with acquirers that actively board MCC 4119 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 4119. 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.
- Chargeback ratio and dispute history covering the last six months, including any Visa or Mastercard monitoring-programme status.
See also: Know Your Customer (KYC) · high-risk merchant · smart routing.
Talk to an acquiring specialist about your MID setup.
Common questions
How can ambulance services reduce 'not recognised' chargebacks, especially in emergency situations?
To reduce 'not recognised' chargebacks, ambulance services should ensure that their payment descriptors are clear and identifiable on cardholder statements, including the service provider's name.
For emergency services, follow-up communication with patients (or their guardians) explaining the charges and billing process, along with providing accessible payment portals, can help prevent disputes. Explicitly educating patients on potential out-of-pocket costs contributes to transparency.
What specific challenges arise when processing payments where insurance is involved?
When insurance is involved, challenges include verifying coverage, processing co-pays and deductibles, and handling the patient's remaining balance after insurance claims. Merchants need robust billing systems that can integrate with insurance clearings and clearly differentiate between the amount covered by insurance and the patient's responsibility.
This complexity can lead to 'duplicate' or 'incorrect amount' disputes if not managed meticulously through clear communication and accurate billing statements.
What security considerations are paramount for processing patient payments in this MCC?
Paramount security considerations include strict adherence to PCI DSS standards for card data and compliance with healthcare data privacy regulations (e. g. , HIPAA in the US, GDPR in Europe) even though payment processing is separate from medical data.
Secure payment gateways, tokenisation of card data, and encryption are essential to protect sensitive financial information. Cardflo's secure payment infrastructure and compliance support help merchants meet these critical requirements.
How can we navigate the complexities of disputes arising from insurance billing and patient co-pays for ambulance services?
Managing disputes involving insurance and co-pays requires meticulous documentation and clear communication. First, ensure patients are fully aware of their financial responsibility upfront, including any co-pay or deductible.
Your payment system should clearly differentiate between amounts covered by insurance and the patient's out-of-pocket share. Provide itemised bills that explain each charge, cross-referenced with the service provided.
For disputes, furnish evidence of insurance submission, the Explanation of Benefits (EOB) from the insurer, and communication logs with the patient regarding their balance. This transparency often resolves issues before they escalate to chargebacks.
What are the key considerations for setting up a payment gateway to accept medical transport payments, given the sensitive nature of patient data?
When setting up a payment gateway for medical transport, PCI DSS compliance is paramount to protect sensitive patient payment data. Ensure your chosen gateway and internal systems are fully certified.
Prioritise a Payment Card Industry Data Security Standard (PCI DSS) compliant service provider (PSP) that offers tokenisation, reducing your direct handling of cardholder data. Implement strong access controls for payment systems and ensure all staff handling payments are trained on data protection protocols.
Use billing descriptors that clearly identify your service (e. g. , "AMBULANCE SERVICE"), but avoid protected health information (PHI) within the descriptor itself to comply with GDPR and HIPAA.
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.