Automated Cash Disbursements, ATMs.
ATM cash withdrawals.
- MCC
- 6011
- Category
- Business Services
- Cardflo support
- Yes
What MCC 6011 covers
Merchant Category Code 6011 is the ISO 18245 identifier used by the card networks for automated cash disbursements, atms. Acquirers, issuers and regulators use this code to set interchange, scheme fees, fraud rules and reporting categories for every transaction your business processes.
ATM cash withdrawals. Choosing the right MCC is critical: an incorrect code can lead to higher interchange, surcharges, or, in regulated categories, declined transactions and account holds.
This MCC is used by Automated Teller Machines (ATMs) for cash disbursements. Merchants are typically financial institutions or independent ATM operators.
Transaction frequency is generally high, with varying ticket sizes depending on the withdrawal limits, but individual transactions are usually low-to-medium value.
Chargeback issues for ATMs are relatively low, primarily stemming from disputes where cash was not dispensed, or incorrect amounts were received. These are often investigated with audit trails of the ATM.
Scheme rules require robust reconciliation processes for ATM transactions.
Cardflo's acquiring network can support efficient processing for ATM operators, ensuring quick settlement of funds. Our robust dispute management tools can assist with the specific types of chargebacks encountered in this sector, helping to provide evidence from transaction logs.
Operators of ATMs should prioritise robust daily reconciliation processes and automated 3DS-capable authorisation systems that flag anomalies. Given potential disputes around non-dispense and incorrect amounts, ensure your acquirer offers fine-grained transaction logging and a clear audit trail between authorisation, settlement, and ATM activity.
Expect low reserve requirements, reflecting a typical low-risk profile. Optimal configuration involves direct integrations that minimise latency, critical for maintaining synchronisation between the ATM and authorisation host, especially for high-volume deployments.
Your acquirer should validate the speed and resilience of their authorisation network.
Acquirer and acquirer assessment stance.
low-risk standard board
Dispute and chargeback profile.
The most frequent dispute reason codes for ATMs are 13.1 / 4808 (services not rendered) or 13.1 / 4853 (incorrect amount). These typically arise when cash is not dispensed, or an insufficient amount is given.
To defeat these, provide ATM journal logs and electronic audit trails that confirm the dispense amount, time, and cardholder interaction. Evidence of CCTV footage of the transaction can also be highly effective in challenging claims of non-dispense.
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 6011
- Placement with acquirers that actively board MCC 6011 businesses in your region.
- B2B card-not-present processing with Level 2 and Level 3 data support.
- Virtual-card, AP-automation and procurement-card acceptance.
- Invoice-linked payment flows and pay by link options for receivables teams.
- Settlement and reconciliation that maps cleanly to ERP and accounting systems.
- Dedicated onboarding manager experienced with B2B and corporate merchants.
Payment methods typically enabled.
Onboarding checklist.
What acquirers typically ask to see when boarding MCC 6011. Cardflo collects this once and reuses it across every acquirer we route you through.
- Business registration and beneficial-owner documentation (KYB, UBO).
- Six months of processing statements or bank statements demonstrating B2B volume.
- Standard master services agreement or engagement letter template.
- Level 2 / Level 3 data capability evidence for commercial-card processing.
- Refund, cancellation and dispute-handling policy for recurring or retainer billing.
- 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 MCC 6011?
The primary chargeback reasons include 'cash not dispensed' (reason code 4834 for Visa, 4853 for Mastercard) and 'incorrect amount dispensed' (reason code 4834 for Visa, 4853 for Mastercard). These usually require robust terminal logs and reconciliation data for effective representment.
Are there any scheme-specific programmes for ATM transactions?
While there are no specific 'programmes' like those for high-risk merchants, both Visa and Mastercard have detailed operating regulations for ATM transactions, including requirements for terminal messaging, transaction logging, and dispute resolution specific to cash disbursements to prevent fraud and ensure consumer protection.
How does Cardflo help ATM operators manage their transactions?
Cardflo provides direct acquiring connections and settlement services that enhance fund flow efficiency. Our platform includes advanced reporting for transaction reconciliation and specific dispute management workflows tailored to capture essential evidence, such as terminal journal entries, improving chargeback representment success for ATM operators.
How can 3DS improve authorisation rates and reduce fraud for ATM withdrawals?
Although 3DS is not typically applied directly to ATM cash withdrawals due to the card-present nature of the transaction, its underlying technology can still support broader fraud prevention.
Strong Customer Authentication requirements, analogous to 3DS for CNP, can be integrated into the card issuance process, ensuring cardholder identity before a card is even used at an ATM.
For card-not-present services linked to ATM access, such as mobile banking integrations, 3DS2 can authenticatethe cardholder, reducing the risk of account takeover that could lead to disputes about unauthorised ATM usage. Implementing tokenisation further protects card data at rest.
What specific data points are critical from an ATM transaction log to fight chargebacks?
Key data points critical for chargeback defence include the exact transaction timestamp, unique ATM identifier, card PAN (truncated), authorisation code, requested amount, dispensed amount, and any error codes or dispense mechanisms.
Crucially, a journal entry indicating a 'successful dispense' or 'no dispense' status, along with the cashbox inventory before and after the transaction, provides irrefutable evidence.
Integrating this log data directly with your payment gateway's dispute resolution module significantly streamlines the evidence submission process and reduces manual effort.
Other MCCs in Business 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.