Miscellaneous StoresCardflo prend en charge ce MCC
MCC 5812

Lieux de restauration et restaurants

Restaurants à service complet, bistrots et restauration.

Ce que couvre le MCC 5812

Le Merchant Category Code 5812 est l'identifiant ISO 18245 utilisé par les réseaux de cartes pour lieux de restauration et restaurants. Les acquéreurs, les émetteurs et les régulateurs utilisent ce code pour définir l'interchange, les frais de réseau, les règles de fraude et les catégories de reporting pour chaque transaction traitée par votre entreprise.

Restaurants à service complet, bistrots et restauration. Choisir le bon MCC est essentiel : un code incorrect peut entraîner des commissions d'interchange plus élevées, des surprimes ou, dans les catégories réglementées, des transactions refusées et des blocages de compte.

MCC 5812 encompasses a broad range of businesses providing food and beverage services for immediate consumption, including full-service restaurants, cafes, bistros, and fast-casual establishments. Ticket sizes can vary from small coffee purchases to large group dining bills.

Transaction frequency is generally high, particularly during peak hours, and cash flow is regular.

Chargebacks are often due to 'services not as described' (e. g.

, food quality, incorrect order), 'duplicate processing' (common in busy environments), or 'fraud' where stolen cards are used for dining. Non-receipt of a gratuity added after the fact can also generate disputes.

For smaller ticket sizes, chargebacks are less frequent due to customer's choice to not dispute incidental charges.

Cardflo's acquiring network provides robust authorisation rates and fast settlement for high-volume transactions common in restaurants, ensuring reliable cash flow. Its specific chargeback tooling allows for rapid response to 'duplicate processing' or 'not as described' claims with transactional details and receipts.

Acquirer & underwriting stance

Low-risk standard board for most businesses. High-end restaurants with large average tickets may see increased fraud monitoring.

Clear pricing displays and efficient transaction processing are key to minimise disputes.

Comment Cardflo gère le MCC 5812

  • Souscription avec des acquéreurs qui acceptent activement les entreprises du MCC 5812 dans votre région.
  • Examen du MCC pendant l'intégration pour confirmer le bon code pour vos produits.
  • Support de reclassification si les règles de système ou la composition des produits changent après le lancement.
  • Routage multi-acquéreurs pour maintenir la stabilité des approbations pour les catégories de marchands larges.
  • Support des litiges adapté au profil de chargeback des produits mixtes que ce MCC voit.

Payment methods typically enabled

Apple Pay
Google Pay
Samsung Pay
QR Code Payments
PayPal
Pay by Link

Questions fréquentes

How can restaurants effectively handle 'duplicate processing' chargebacks due to errors during busy periods?

To defend against 'duplicate processing' (Visa Reason Code 12. 6, Mastercard 4834), restaurants should immediately issue a refund for the erroneous duplicate charge and notify the customer.

Providing the acquirer with clear evidence of the single intended transaction (e. g.

, POS logs showing one order, customer receipt) and proof of the refund for the duplicate will resolve the dispute quickly. Proactive reconciliation and staff training on POS usage help prevent these errors.

What are the scheme rules regarding disputed gratuities or service charges added to a restaurant bill?

If a customer disputes a gratuity or service charge (often falling under 'not as described' or 'no authorisation'), the restaurant must prove the customer authorised the amount. This typically requires a signed receipt clearly showing the tip or service charge included in the total.

For mandatory service charges, these must be conspicuously displayed on menus or price lists. For discretionary tips, cardholders can dispute if they claim it was added without their consent, in which case the restaurant faces liability if no signature is present.

Are there specific scheme rules for 'dine and dash' scenarios where a customer leaves without paying?

If a customer 'dines and dashes' and a card transaction was attempted but declined (or no card was presented), this is not typically a chargeback scenario. Chargebacks occur when a valid card transaction is processed, and the cardholder later disputes it.

If a restaurant manager manually keys in a card number when a declined transaction occurs to force a payment, this is against scheme rules and would almost certainly result in a 'no authorisation' or 'fraud' chargeback against the restaurant,

with a high chance of merchant liability.

Commencer

Prêt à accélérer ?

Parlez-nous de votre activité. Nous vous mettrons en relation avec les bons partenaires acquéreurs et la bonne route, généralement en moins d'une semaine.

Postuler