Government-Licensed Horse / Dog Racing (US Region).
Licensed pari-mutuel horse and dog racing (US).
- MCC
- 7802
- Category
- Business Services
- Cardflo support
- Yes
What MCC 7802 covers
Merchant Category Code 7802 is the ISO 18245 identifier used by the card networks for government-licensed horse / dog racing (US region). Acquirers, issuers and regulators use this code to set interchange, scheme fees, fraud rules and reporting categories for every transaction your business processes.
Licensed pari-mutuel horse and dog racing (US). 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 7802 is specific to Government-Licensed Horse and Dog Racing operators in US regions where pari-mutuel wagering on these events is legal. These merchants facilitate betting online or via licensed outlets for racing events.
Transaction patterns involve frequent, generally smaller bets, often with multiple transactions per customer during a race day. Some accounts may hold larger balances for continuous wagering.
Chargeback risk is moderate to high, similar to other regulated gaming. Primary reasons include 'unauthorised transactions' (e. g. , family fraud, stolen cards), 'processing errors' (e. g. , incorrect odds applied), or 'disputes' over race outcomes or payout calculations.
Schemes classify this activity under high-risk gambling, which can trigger enhanced monitoring programmes. Cardflo is experienced in supporting regulated sectors, offering tailored solutions for payment processing, fraud prevention, and compliance in the US pari-mutuel racing industry.
Operators in this sector should concentrate on optimising approval rates for frequent, smaller bets through intelligent routing and robust fraud detection. Implement dynamic 3DS2 for new accounts or higher-value wagers, while allowing frictionless experiences for trusted, repeat customers, particularly during peak racing events.
Anticipate significant rolling reserves, typically 10-20% held for 180-365 days, due to the regulatory nature and potential for chargeback liability, despite strong KYC. Leverage multi-acquirer strategies to enhance resilience and minimise downtime.
Acquirer and acquirer assessment stance.
Regulated specialist board. This is a high-risk, regulated industry requiring strict licensing.
Acquirers conduct intensive due diligence and may require substantial financial guarantees. Rolling reserves of 10-20% are common, usually held for 180-365 days, to cover chargeback liabilities and potential regulatory penalties.
Dispute and chargeback profile.
Primary chargeback reasons include "10.4 / 4837 (frauds, no cardholder authorisation)" and "13.1 / 4853 (goods/services not as described)". Unauthorised transactions are common, often from shared devices or compromised credentials.
Service disputes may arise from perceived incorrect odds, race outcome disagreements, or settlement issues.
Combat these by providing detailed betting logs, IP addresses, device IDs, evidence of account access, clear bet confirmation, and comprehensive display of terms and conditions covering all racing rules and payout calculations.
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 7802
- Placement with acquirers that actively board MCC 7802 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 7802. 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.
- Regulator authorisation reference and any statutory notice, licence or product-certification documents that apply to the category.
See also: Know Your Customer (KYC) · high-risk merchant · smart routing.
Talk to an acquiring specialist about your MID setup.
Common questions
What unique compliance requirements does MCC 7802 have when processing payments with Cardflo?
Government-licensed horse and dog racing operators must comply with state-specific regulations, including age verification, geolocation to ensure legal wagering within designated boundaries, and adherence to responsible gambling protocols.
Cardflo provides tools and integrations for these compliance checks, ensuring transaction legality and reducing regulatory exposure for the merchant.
How can Cardflo help manage chargebacks stemming from disputed race outcomes or payout errors?
While race outcome disputes are often handled internally, Cardflo can assist with 'processing error' chargebacks by enabling merchants to provide detailed transaction logs, wagering slips, and official race results.
Our chargeback management tools facilitate the submission of this compelling evidence, supporting the merchant's case during the dispute resolution process.
Are there limits on transaction amounts for horse/dog racing with Cardflo?
Transaction limits are typically set by the card schemes or issuing banks, and often vary due to the high-risk nature of gambling.
While Cardflo does not impose arbitrary limits, our fraud detection system monitors for unusual transaction patterns, which can prompt additional verification steps or velocity checks to prevent fraud and remain within risk tolerance levels.
What specific data points should we capture and store to effectively challenge chargebacks related to bet outcomes or processing errors?
To successfully challenge chargebacks related to bet outcomes or processing errors, meticulously record the specific event, the odds offered at the time of the bet, the exact time of bet placement, the customer's accepted terms, and the official race result.
Additionally, store detailed logs of the transaction, including authorisation codes, IP addresses, device identifiers, and any customer service interactions. Evidence of your transparent payout calculations, matching official results, is vital.
This comprehensive data set acts as robust proof of legitimate service delivery.
How can we efficiently manage high transaction volumes during major racing events while maintaining fraud security and compliance?
During peak racing events, optimise your payment flow by leveraging multi-acquirer routing to distribute traffic and prevent single points of failure, ensuring high authorisation rates.
Implement a tiered fraud strategy: frictionless processing for established, low-risk customers, and dynamic step-up authentication (3DS2) for new users or high-value transactions. utilise real-time fraud scoring engines that can rapidly analyse behavioural data and transaction patterns to identify anomalies without introducing undue friction,
ensuring compliance and security amidst surge volumes.
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.