Miscellaneous StoresCardflo supports this MCC
MCC 5811

Caterers

Catering services for private and corporate events.

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.

Acquirer & underwriting 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.

How Cardflo handles MCC 5811

  • Underwriting 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.

Payment methods typically enabled

Bank Transfer
Apple Pay
Google Pay
PayPal
Invoice Payments
Trustly

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.

Get started

Ready for velocity?

Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.

Apply now