MCC Codes
Cardflo supports this MCC
MCC 5811

Caterers.

Catering services for private and corporate events.

MCC
5811
Category
Miscellaneous Stores
Cardflo support
Yes
Apply now

What MCC 5811 covers

Merchant Category Code 5811 is the ISO 18245 identifier used by the card networks for caterers. Acquirers, issuers and regulators use this code to set interchange, scheme fees, fraud rules and reporting categories for every transaction your business processes.

Catering services for private and corporate events. 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 5811 is assigned to caterers, businesses that provide food and beverage services for events, parties, and functions, typically off-site. This can include corporate catering, wedding catering, and private event services.

Ticket sizes are generally high, often involving significant deposits and final payments. Purchase frequency is sporadic and event-driven, rather than recurring.

Chargebacks frequently arise from 'services not rendered' (e. g. , caterer no-shows, significant delays) or 'services not as described' (e. g. , food quality below expectation, insufficient quantity, wrong menu items). Disputes can also stem from cancellations where refund policies are contested.

Due to the service-based nature, strong contracts and clear communication are paramount.

Cardflo's flexible payment gateway supports phased payments, allowing for deposits, interim payments, and final balances, which is ideal for catering businesses to manage cash flow and customer commitments. Additionally, its chargeback management tools help caterers provide compelling evidence for services rendered.

Caterers dealing with high ticket sizes and forward-dated services must configure acceptance to manage cancellation risk effectively. Implement clear, prominent refund and cancellation policies, requiring customer acknowledgement during booking.

For larger events, consider a deposit structure that aligns with service delivery milestones. Focus on securing card-present transactions where possible for deposits, or robust CNP authentication using 3DS2 online.

Our multi-acquirer routing can ensure high authorisation rates for valuable bookings, while our risk tools help flag high-risk transactions. Given the service-based nature, be prepared for 'services not as described' disputes.

Acquirer and acquirer assessment stance.

Medium-risk standard board, mainly due to potential 'services not rendered/as described' disputes and high ticket values. Clear cancellation policies, detailed contracts, and transparent pricing are essential for a stable processing relationship.

A small reserve may be requested for new or high-volume merchants.

Dispute and chargeback profile.

Caterers commonly encounter 13.3 / 4853 (services not as described) and 13.1 / 4853 (services not rendered). 'Not as described' arises from quality issues, incorrect menu items, or insufficient quantity.

'Not rendered' occurs if the service is cancelled or significantly delayed. To counter these, provide signed contracts detailing menu, quantity, date, time, and service terms.

Collect testimonials, photographic evidence of the event setup and food served. For 'not rendered', show proof of service provision, email correspondence, and delivery confirmations.

Acknowledge customer complaints and attempt resolution prior to chargeback to show good faith.

See also: chargeback management · payment response codes · Compelling Evidence 3.0.

Payments built for Caterers.

Book a scoping call to see how Cardflo would set you up.

Apply now

How Cardflo handles MCC 5811

  • Placement with acquirers that actively board MCC 5811 businesses in your region.
  • MCC review during onboarding to confirm the right code for your products.
  • Reclassification support if scheme rules or product mix change post-launch.
  • Multi-acquirer routing to keep approvals stable for broad merchant categories.
  • Dispute support tuned to the mixed-product chargeback profile this MCC sees.
  • Dedicated onboarding manager rather than a generic ticket queue.

Payment methods typically enabled.

Visa Credit / Debit
Mastercard Credit / Debit
Apple Pay
Google Pay
AMEX
Open Banking

Onboarding checklist.

What acquirers typically ask to see when boarding MCC 5811. 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 trading pattern.
  • Product catalogue extract confirming the MCC covers the goods actually sold.
  • Refund, exchange and cancellation policy shown at point of sale and on the website.
  • PCI DSS SAQ appropriate to the environment (A, A-EP or D as relevant).
  • 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.

Route MCC 5811 traffic with confidence.

Talk to an acquiring specialist about your MID setup.

Apply now

Common questions

What specific evidence is crucial for caterers to defend against 'services not as described' chargebacks?

To defend against 'services not as described' (Visa Reason Code 13.3, Mastercard 4853), caterers should provide comprehensive evidence such as signed contracts detailing menu, quantity, and service expectations; client communications (emails, messages) confirming agreements; testimonials or positive feedback from the event; and, if available,

photographs or video of the actual food and service provided. Any amendments or special requests should be documented in writing.

Proof of a tasting session or client approval of sample menus can also strengthen a defence.

How do scheme rules handle chargebacks for event cancellations by either the client or the caterer?

Chargeback liability for cancellations (Visa Reason Code 13.4, Mastercard 23.3) hinges on the merchant's cancellation policy, which must be clearly disclosed at the time of booking.

If the client disputes a non-refunded deposit after cancelling, the caterer must prove the policy was accepted and that it complies with local consumer protection laws regarding reasonable cancellation fees.

If the caterer cancels, they are typically liable for 'services not rendered' unless extenuating circumstances are covered in a force majeure clause, and a full refund was not issued.

Are deposits for catering services treated differently by card schemes than final payments?

From a scheme perspective, deposits and final payments are generally treated as parts of the same service transaction. However, the timing of the dispute window can differ slightly.

For deposits, the window might open from the deposit date, while for 'services not rendered,' it often opens from the event date or when the service was expected.

Merchants must clearly label deposits as non-refundable (if applicable) and ensure this policy is acknowledged by the customer. Failure to deliver the event after taking a deposit would almost certainly lead to a 'services not rendered' chargeback.

How should caterers structure their payment collection to mitigate risk, considering large event bookings and potential cancellations?

Caterers should implement a phased payment structure, starting with a non-refundable deposit upon booking, followed by interim payments, and a final balance due before the event. This approach spreads risk and aligns payments with service delivery milestones.

Ensure your terms and conditions, outlining cancellation policies and refund eligibility, are explicitly accepted by the client, ideally with a digital signature.

For high-value transactions, consider requiring bank transfers or secure online payments with 3DS2 for initial deposits, as these offer stronger authentication and less chargeback risk than manual card entry. Clear invoicing and timely payment reminders also help manage cash flow effectively.

What specific documentation is most effective for caterers to defend 'services not as described' chargebacks?

To robustly defend 'services not as described' chargebacks, gather comprehensive documentation. This includes the signed catering contract detailing the agreed menu, quantity, services, date, and venue.

Photographic or video evidence from the event showing the food presentation, setup, and guest satisfaction is highly compelling. Collect customer testimonials or positive feedback through surveys.

Keep all communication logs, including emails and messages, proving agreement to terms or post-event satisfaction. If a complaint was raised, evidence of your attempts to resolve the issue amicably before the chargeback indicates good faith and can strengthen your defence against the claim.

Apply with Cardflo

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.

Apply now
Apply now