Online Gaming and Fantasy Sports Merchant Accounts in 2026: High-Risk Underwriting, Compliance, and Chargeback Control

Call Bridge Capital Partners now at 866-305-6454 to discuss a compliant payment structure for online gaming or fantasy sports.

This article provides payment-processing information. It does not provide legal advice. Confirm product legality, licensing, age rules, and market access with qualified gaming counsel and the applicable regulator before processing transactions.

Online gaming and paid fantasy sports require specialized payment underwriting.

A standard e-commerce account may not support these businesses. A payment facilitator may decline the application. A bank may require reserves, transaction limits, enhanced monitoring, and detailed compliance documentation.

The correct structure starts with the business model.

Determine whether the platform:

• Accepts real-money wagers.
• Charges fantasy contest entry fees.
• Pays monetary prizes.
• Offers free-to-play games.
• Offers casino-style gaming.
• Offers sports betting or proposition-style contests.
• Serves customers across state or national borders.
• Uses credit cards, ACH, e-wallets, or prepaid funding.
• Stores payment credentials.
• Operates recurring deposits or withdrawals.

Each factor affects licensing, card-network classification, underwriting, pricing, and dispute exposure.

Why online gaming and fantasy sports receive high-risk treatment

Online gaming and fantasy sports combine several risk categories.

They involve card-not-present transactions. The customer is not physically present. The transaction may involve a digital service, stored credentials, rapid deposits, account withdrawals, recurring activity, or cross-border access.

They may also involve regulated activity.

A bank must understand:

• Where the operator is licensed.
• Where the customer is located.
• Whether the contest is legal in that jurisdiction.
• Whether the customer is old enough to participate.
• How the platform blocks restricted locations.
• How the operator identifies customers.
• How customer funds are held and paid.
• How disputes are handled.
• How suspicious activity is escalated.

The risk is not limited to ordinary fraud.

A customer may file a dispute because:

• The transaction descriptor was not recognized.
• A deposit was made by an unauthorized person.
• A promised withdrawal was delayed.
• The customer did not understand the contest terms.
• A recurring deposit was not properly canceled.
• The account was suspended.
• The customer claims the platform was unavailable.
• The transaction was associated with an unlicensed activity.
• The customer disputes the result or payout.

Regulators and card networks also examine consumer protection.

Age verification is central. A platform that permits minors to deposit funds creates legal, reputational, and refund exposure. Geolocation is equally important. A customer physically located outside an approved jurisdiction must not be permitted to enter a restricted contest or place a prohibited wager.

Responsible gaming controls also matter.

A responsible program may include:

• Deposit limits.
• Loss limits.
• Time limits.
• Cooling-off periods.
• Self-exclusion.
• Account closure procedures.
• Risk alerts.
• Customer support escalation.
• Advertising restrictions.
• Identity and age rechecks.

These controls support compliance and payment stability.

A specialist high risk merchant account can help align the operator’s business model with an acquiring bank that understands regulated, card-not-present activity.

The state-by-state legal structure

The United States does not use one nationwide fantasy sports license.

State law controls many important questions:

• Whether paid fantasy sports are permitted.
• Whether the state treats fantasy sports as a skill-based contest.
• Whether a registration or license is required.
• Whether the state imposes taxes or fees.
• Whether the operator must segregate player funds.
• Whether a minimum age applies.
• Whether certain contest formats are prohibited.
• Whether proposition-style contests are treated as sports wagering.
• Whether the state requires self-exclusion or responsible gaming controls.

The operator must maintain a jurisdiction matrix.

The matrix should identify:

Control area	Required record
Jurisdiction	State or territory served
Product	Classic DFS, pick’em, casino, sportsbook, or free-to-play
Legal basis	Statute, regulation, license, registration, or counsel opinion
Regulator	Applicable gaming, lottery, racing, or consumer agency
Age rule	Minimum participant age
Product limits	Prohibited events or contest structures
Geolocation	Approved and blocked locations
Tax obligations	Applicable filings and remittances
Responsible gaming	Required customer controls
Payment restrictions	Card, ACH, wallet, or withdrawal limits

Do not rely on a generic “legal states” map as the final compliance source.

Use the state legislature, gaming commission, attorney general, lottery authority, or other official regulator. Laws and agency interpretations can change. Product changes can also change the legal analysis.

New York

New York regulates interactive fantasy sports under Article 14 of the Racing, Pari-Mutuel Wagering and Breeding Law.

The New York statute addresses:

• Interactive fantasy sports registration.
• Contest operations.
• Player protections.
• Age restrictions.
• Responsible play.
• Fair competition.
• Prohibited contest formats.

The New York State Gaming Commission also publishes interactive fantasy sports materials and rules.

New York’s framework is specific to interactive fantasy sports. It does not authorize an operator to offer sports betting, casino gaming, or other regulated products without the required separate authority.

A New York operator should confirm:

• Current registration status.
• Approved platforms.
• Approved contest types.
• Age-verification controls.
• Promotional restrictions.
• Self-exclusion procedures.
• Transaction and reporting requirements.

Review the New York interactive fantasy sports statute and the New York State Gaming Commission’s interactive fantasy sports resources.

Massachusetts

Massachusetts regulates fantasy contests through consumer-protection rules administered by the Attorney General’s Office.

The Massachusetts framework addresses unfair and deceptive practices. It also includes requirements related to customer protections, minors, contest disclosures, and operator conduct.

The state has published materials concerning:

• Daily fantasy sports contest operators.
• Fantasy contest operations.
• Consumer-protection obligations.
• Proposed or updated regulatory language.

Review the Massachusetts fantasy contest regulations and the official fantasy contest operations materials.

Florida and changing legislative frameworks

Florida demonstrates why operators must verify current law before opening a market.

Florida’s official statutes address gambling and related activities. Proposed or pending legislation may create or modify a fantasy sports framework, including licensing, age restrictions, contest definitions, and regulator authority.

Do not treat a bill, legislative analysis, or industry summary as enacted law.

Confirm the current position through the Florida Statutes and the official Florida Senate bill resources.

Practical state compliance

Before processing a new state, document:

1. The legal basis for offering the product.
2. The exact product format.
3. The applicable license or registration.
4. The required age.
5. The geolocation method.
6. The customer disclosures.
7. The responsible gaming controls.
8. The payment methods permitted.
9. The tax and reporting process.
10. The procedure for regulatory changes.

Submit this package during underwriting.

UIGEA and Regulation GG

The Unlawful Internet Gambling Enforcement Act of 2006 is important to payment processing.

UIGEA addresses the acceptance of payments connected to unlawful Internet gambling. Regulation GG implements the banking and payments provisions through 12 CFR Part 233.

Regulation GG does not create a universal gaming license.

It requires covered payment-system participants to maintain written policies and procedures reasonably designed to identify and block, or otherwise prevent or prohibit, restricted transactions.

The key issue is legality.

A transaction may create exposure when it funds an activity that is unlawful under applicable federal, state, or tribal law. Lawful activity may qualify for statutory exclusions or exceptions, but the operator must document the basis for the conclusion.

Underwriting teams may request:

• A legal opinion.
• Licenses and registrations.
• Jurisdictional controls.
• Customer location controls.
• Product terms.
• Transaction-monitoring procedures.
• Restricted-activity policies.
• Escalation procedures.
• Evidence that unlawful activity is blocked.

A business should not attempt to disguise a gaming transaction as ordinary digital goods.

Do not use an inaccurate merchant category code. Do not split transactions to avoid monitoring. Do not board a gaming business under an unrelated corporate description. These practices can produce account termination, reserve action, chargeback exposure, and network penalties.

Read the Federal Reserve’s Regulation GG guidance and the current 12 CFR Part 233 text.

Visa and Mastercard policy treatment

Visa and Mastercard distinguish between merchant categories and transaction types.

The classification depends on the actual business activity. The acquiring bank determines the final boarding structure. The operator must provide a complete and accurate description.

MCC 7995 and gambling transactions

MCC 7995 is associated with betting and gambling transactions.

Visa’s merchant data standards identify MCC 7995 for betting activity, including transactions involving wagers and monetary prizes. Visa rules also provide special treatment for online gambling transactions.

Mastercard’s merchant rules identify MCC 7995 for gambling transactions involving wagers, lottery activity, or value used for gambling.

Other gambling-related codes may apply in specific circumstances, including government-owned lotteries, government-licensed online gambling, and government-licensed racing. The correct code depends on the transaction and the applicable network rules.

Do not select an MCC based on the lowest available rate.

The MCC must reflect the business.

Fantasy sports classification

Fantasy sports require careful analysis.

A classic contest involving multiple athletes and accumulated statistical performance may be treated differently from:

• A single-player proposition.
• An over-under selection.
• A fixed-odds wager.
• A sportsbook transaction.
• A casino-style game.
• A social casino product.
• A free-to-play contest with no monetary prize.

The fact that a product is described as a “game of skill” does not automatically determine its card-network treatment.

The acquirer may ask for:

• Contest rules.
• Scoring mechanics.
• Prize rules.
• Entry-fee terms.
• Product screenshots.
• State-by-state availability.
• Legal opinions.
• Licensing records.
• Payout procedures.

Submit the actual customer flow. A product name is not enough.

Restricted does not mean universally prohibited

Visa or Mastercard rules do not mean that every online gaming business can process automatically.

The activity may be:

• Permitted by the network but restricted by the acquirer.
• Legal in one state but prohibited in another.
• Approved for cards but restricted for ACH.
• Permitted for deposits but subject to withdrawal controls.
• Approved for one product but not another.
• Accepted by one acquiring bank and rejected by another.

Review the current Visa Core Rules, the Visa Merchant Data Standards Manual, and the Mastercard Rules.

Underwriting documents acquirers expect

An application should be complete before submission.

Incomplete applications create delays. Contradictory information creates risk flags. Missing licenses can result in a decline.

Prepare the following package.

Corporate and ownership records

Provide:

• Formation documents.
• Ownership information.
• Government-issued identification.
• Business address.
• Website and application links.
• Management biographies.
• Beneficial-owner information.
• Bank account details.
• Tax documentation.
• Prior processing relationships.

Product and customer-flow records

Provide:

• A full description of each product.
• Screenshots of registration.
• Screenshots of age verification.
• Screenshots of deposits.
• Screenshots of withdrawals.
• Contest terms.
• Fee disclosures.
• Prize calculations.
• Refund policy.
• Account closure policy.
• Customer support contacts.
• Transaction descriptors.

Legal and licensing records

Provide:

• State licenses.
• Registrations.
• Regulator correspondence.
• Legal opinions.
• Jurisdiction matrix.
• Geolocation policy.
• Restricted-state list.
• Product approval documentation.
• Responsible gaming policy.
• AML and KYC procedures.

Technical and security records

Provide:

• Gateway architecture.
• Tokenization design.
• Data-flow diagram.
• PCI validation documents.
• Fraud tools.
• 3-D Secure capability.
• Device and IP controls.
• Access-control policies.
• Incident-response plan.
• Vendor list.
• Hosting and security information.

Financial and processing history

Established operators should provide:

• Recent processing statements.
• Monthly volume.
• Average ticket.
• Highest ticket.
• Refund percentage.
• Chargeback history.
• Chargeback reason categories.
• Funding history.
• Reserve history.
• Prior terminations.
• Outstanding disputes.
• Bank statements.

A new operator should provide a credible launch plan.

Include:

• Expected monthly volume.
• Customer acquisition method.
• Marketing restrictions.
• Launch jurisdictions.
• Expected average deposit.
• Expected withdrawal volume.
• Funding needs.
• Reserve capacity.
• Compliance staffing.
• Technology vendors.

Bridge states on its high-risk service page that it works with more than 30 acquiring banks, reports a 94% approval rate for high-risk applications, and indicates typical approval times of 3 to 5 business days. These are company-published claims, not guarantees. Actual timing and approval depend on the application, business model, licensing, documentation, and acquiring-bank review.

Reserves, holdbacks, and rate expectations

Gaming and fantasy sports accounts may carry higher costs than ordinary retail accounts.

Pricing can include:

• Discount rates.
• Per-transaction fees.
• Gateway fees.
• ACH fees.
• Chargeback fees.
• Retrieval fees.
• Cross-border fees.
• Currency-conversion costs.
• Compliance fees.
• Rolling reserves.
• Volume-based pricing.
• Withdrawal or payout costs.

A rolling reserve holds a percentage of processing volume for a defined period. The reserve protects the acquirer against future chargebacks, refunds, reversals, and other liabilities.

A holdback may apply to:

• New operators.
• Operators with limited processing history.
• Operators with high average tickets.
• Operators with elevated refund activity.
• Operators with prior account closures.
• Operators with cross-border exposure.
• Operators with delayed fulfillment or payout risk.
• Operators with regulatory uncertainty.

Reserve terms should be reviewed in writing.

Confirm:

• Reserve percentage.
• Reserve calculation.
• Reserve start date.
• Release period.
• Release schedule.
• Minimum reserve.
• Termination treatment.
• Treatment of refunds.
• Treatment of chargebacks.
• Conditions for reduction.

Do not evaluate an account on rate alone.

A low rate with sudden reserve action is not a stable payment solution. Compare total cost, funding speed, reserve exposure, gateway capability, fraud tools, and support.

Review Bridge’s transparent credit card processing pricing to understand the company’s published interchange-plus pricing structure. High-risk gaming pricing remains subject to underwriting and may differ from standard plans.

Chargeback control for gaming and fantasy sports

Chargeback prevention starts before authorization.

The customer should understand:

• The legal name of the operator.
• The billing descriptor.
• The deposit amount.
• Any service or entry fee.
• The contest format.
• The payout formula.
• The withdrawal process.
• The refund policy.
• The account closure procedure.
• The recurring billing terms.
• The customer support process.

Use a recognizable descriptor.

A customer who sees an unfamiliar business name may contact the issuer instead of the operator. Descriptor consistency supports dispute prevention.

Common dispute categories

Gaming and fantasy sports disputes often involve:

• Fraudulent transactions.
• No authorization.
• Duplicate processing.
• Credit not processed.
• Canceled recurring payments.
• Services not received.
• Services not as described.
• Incorrect amount.
• Processing errors.
• Account-access disputes.

The exact network reason code depends on the network, transaction type, card product, and dispute facts. Use the current Visa and Mastercard rules rather than an outdated code chart.

Evidence for representment

Build evidence at the time of the transaction.

Useful records may include:

• Customer name.
• Account ID.
• Verified email.
• Verified phone number.
• Device information.
• IP address.
• Geolocation result.
• Age-verification result.
• KYC result.
• Login history.
• Authentication result.
• 3-D Secure result.
• CVC and AVS response.
• Deposit timestamp.
• Contest entry timestamp.
• Contest rules accepted.
• Entry fee.
• Contest result.
• Prize calculation.
• Payout record.
• Withdrawal request.
• Refund record.
• Customer communications.
• Account suspension reason.
• Terms version accepted.

Do not submit irrelevant data.

Organize the response around the dispute claim. Show what was purchased, how the customer authorized it, how the service was delivered, and how the platform handled the customer’s account.

Prevention tools

Deploy:

• Account velocity controls.
• Deposit velocity controls.
• Device fingerprinting.
• IP reputation screening.
• Geolocation checks.
• AVS.
• CVC validation.
• 3-D Secure.
• Tokenization.
• Fraud scoring.
• Transaction alerts.
• Chargeback alerts.
• Clear refund workflows.
• Manual review for unusual activity.

Set thresholds before launch.

Monitor:

• Declines.
• Reversals.
• Refunds.
• Chargebacks.
• Unauthorized claims.
• First-time deposits.
• High-value deposits.
• Multiple cards per account.
• Multiple accounts per device.
• Geographic inconsistencies.
• Rapid deposits and withdrawals.
• Unusual login changes.

Payment methods and gateway routing

Use more than one payment method where permitted.

Potential methods include:

• Credit cards.
• Debit cards.
• ACH.
• E-check.
• Bank transfers.
• E-wallets.
• Prepaid instruments.
• Alternative payment methods.

Each method has separate risk.

Credit and debit cards

Cards offer fast authorization and familiar customer access. They also create card-not-present fraud and dispute exposure.

Use:

• Tokenization.
• CVC checks.
• Address verification.
• 3-D Secure.
• Risk scoring.
• Velocity filters.
• Descriptor controls.
• Network-compliant transaction coding.

ACH

ACH may support larger deposits, recurring funding, and customers who prefer bank payments.

ACH is not a replacement for compliance.

For internet-authorized consumer debits, operators should address:

• Electronic authorization.
• Account validation.
• Authorization record retention.
• Return monitoring.
• Fraud detection.
• Revocation handling.
• Duplicate-debit prevention.
• Customer notification.

Nacha publishes risk thresholds for ACH debit returns, including a 0.5% unauthorized return rate threshold, a 3% administrative return rate threshold, and a 15% overall debit return rate threshold. These thresholds are compliance triggers, not operating targets. Keep activity below them and confirm current requirements with the originating bank.

Review the Nacha ACH Network risk and enforcement information and Nacha’s unauthorized return-rate calculation guidance.

E-wallets and prepaid methods

Wallets and prepaid products can create additional issues:

• Account ownership.
• Funding-source verification.
• Withdrawal matching.
• Name mismatches.
• Chargeback allocation.
• Third-party funding.
• Transaction tracing.
• Regulatory restrictions.

Document how funds enter and leave the customer account.

Gateway routing

Gateway selection affects approval rates, fraud controls, reporting, tokenization, recurring billing, and failover.

A suitable payment gateway integration should support the operator’s:

• Website or application.
• API.
• Recurring billing.
• Tokenization.
• Hosted payment page.
• Virtual terminal.
• ACH capability.
• Fraud filters.
• Reporting.
• Refund workflow.
• Multi-currency requirements.
• Backup-routing plan.

Do not add routing complexity without controls.

A multi-gateway structure can improve resilience, but every connection must be approved, documented, and monitored. Do not route transactions to an account that was not approved for the activity.

Age verification and geolocation

Age verification is a payment requirement because it reduces regulatory and refund exposure.

The platform should:

1. Collect required identity details.
2. Verify the customer’s age.
3. Screen for duplicate or suspicious accounts.
4. Recheck when risk changes.
5. Restrict deposits until verification is complete.
6. Maintain verification records.
7. Refund or escalate prohibited accounts under the applicable rule.
8. Prevent promotional outreach to restricted users where required.

Geolocation must operate in real time.

Useful signals include:

• IP location.
• Device location.
• Wi-Fi or network data.
• Mobile location.
• Account address.
• Payment instrument country.
• Browser and device consistency.
• VPN and proxy indicators.

No single signal is always reliable.

Use a risk-based combination. Record the result for each paid entry or wager. Block or hold transactions when signals conflict.

The geolocation policy should define:

• Approved jurisdictions.
• Blocked jurisdictions.
• Border-area treatment.
• VPN handling.
• Remote-access handling.
• Location rechecks.
• Manual review.
• Customer messaging.
• Audit records.

Responsible gaming and processing stability

Responsible gaming is not only a regulatory issue.

It can improve payment stability.

Effective controls may reduce:

• Unauthorized family-member use.
• Rapid repeat deposits.
• Customer confusion.
• Refund pressure.
• Account disputes.
• Negative customer contacts.
• Regulatory complaints.
• High-risk transaction patterns.

Implement:

• Deposit limits.
• Loss limits.
• Session limits.
• Reality checks.
• Cooling-off periods.
• Self-exclusion.
• Account closure.
• Marketing suppression.
• Support escalation.
• Vulnerability review.
• Documented intervention.

Do not design responsible gaming tools as hidden features.

Make them accessible. Explain them in plain language. Apply them consistently. Keep an audit trail.

The payment processor may request evidence that these controls function in practice. A policy document without system evidence has limited underwriting value.

PCI DSS 4.0.1 for gaming payment pages

Online gaming and fantasy sports platforms commonly use web and mobile payment pages.

PCI DSS 4.0.1 applies according to the payment architecture and the entity’s role.

The operator must determine whether it:

• Hosts the payment page.
• Embeds a payment iframe.
• Redirects to a hosted payment page.
• Uses direct API submission.
• Stores payment credentials.
• Transmits payment data.
• Uses client-side scripts.
• Operates a mobile application.
• Relies on third-party providers.

PCI DSS Requirement 6.4.3 addresses payment-page scripts. The operator must maintain control over scripts that can affect payment security, including inventory, authorization, and integrity considerations.

Requirement 11.6.1 addresses change and tamper detection for payment-page content and relevant security-related HTTP headers.

Use:

• Hosted payment pages where appropriate.
• Tokenization.
• Strong access controls.
• Multi-factor authentication.
• Secure development.
• Vulnerability management.
• Logging.
• Change management.
• Incident response.
• Vendor oversight.
• Current SAQ or other validation required by the acquirer.

Review the PCI Security Standards Council PCI DSS library and the Council’s payment-page security guidance.

The correct validation document depends on the implementation. Ask the acquiring bank or qualified security assessor before launch.

How a merchant account broker supports approval

A broker can reduce avoidable application errors.

The broker’s role may include:

• Reviewing the business model.
• Identifying the appropriate acquiring channel.
• Matching the account to the vertical.
• Preparing underwriting documents.
• Coordinating gateway setup.
• Reviewing reserve terms.
• Explaining transaction limits.
• Supporting compliance questions.
• Helping plan a transition from an existing processor.
• Coordinating chargeback tools.
• Supporting account maintenance.

This is particularly useful when the business has:

• Prior processing termination.
• High chargebacks.
• Limited processing history.
• Cross-border customers.
• Complex ownership.
• Multiple products.
• Gaming licenses in several jurisdictions.
• Recurring deposits.
• Large withdrawals.
• ACH return exposure.
• A custom payment stack.

Bridge Capital Partners states on its high-risk page that it works with 30+ acquiring banks, reports a 94% approval rate for high-risk applications, and indicates approval often takes 3 to 5 business days. These are Bridge-published claims. They are not a promise of approval or a substitute for licensing and legal review.

Before applying, assemble:

• Corporate documents.
• Ownership records.
• Processing statements.
• Bank statements.
• Licenses.
• Legal opinions.
• Product terms.
• KYC and AML policies.
• Age-verification details.
• Geolocation controls.
• Responsible gaming policy.
• Chargeback procedures.
• PCI documentation.
• Gateway architecture.
• Forecasted processing volume.

Then request written terms.

Confirm:

• Rate.
• Per-item fee.
• Reserve.
• Funding schedule.
• Volume cap.
• Chargeback fee.
• Gateway fee.
• ACH pricing.
• Cross-border pricing.
• Contract term.
• Termination provisions.
• Compliance obligations.
• Reporting requirements.

Review the available merchant account features before selecting a structure. Fraud screening, chargeback management, reporting, ACH, recurring billing, tokenization, and funding speed can matter more than the headline rate.

Launch checklist for 2026

Complete this checklist before accepting paid entries or wagers:

• Confirm the exact product classification.
• Identify every served jurisdiction.
• Verify each license or registration.
• Document prohibited states and territories.
• Confirm minimum-age rules.
• Test age verification.
• Test geolocation.
• Test VPN and proxy controls.
• Confirm contest rules.
• Confirm payout rules.
• Confirm withdrawal procedures.
• Confirm customer disclosures.
• Confirm billing descriptors.
• Confirm refund procedures.
• Confirm responsible gaming controls.
• Confirm KYC and AML procedures.
• Confirm PCI scope.
• Confirm gateway configuration.
• Confirm MCC assignment with the acquirer.
• Confirm card-network approvals.
• Confirm ACH authorization controls.
• Confirm ACH return monitoring.
• Confirm reserve terms.
• Confirm funding timing.
• Confirm dispute evidence retention.
• Confirm chargeback-alert procedures.
• Confirm incident escalation.
• Confirm regulator-change monitoring.

Final payment-processing decision

Online gaming and fantasy sports should be treated as regulated, high-scrutiny payment businesses.

Approval depends on more than a website and an application.

The acquiring bank will assess:

• Legality.
• Licensing.
• Product structure.
• Customer location.
• Age controls.
• Identity controls.
• Transaction flow.
• Payment methods.
• Chargeback exposure.
• Financial strength.
• Security controls.
• Responsible gaming.
• Management experience.
• Processing history.

Use accurate information.

Select an acquirer that understands the business model. Use the correct merchant category. Keep jurisdiction controls active. Monitor disputes and ACH returns. Maintain sufficient liquidity for reserves and refunds.

Call Bridge Capital Partners at 866-305-6454 to review a high-risk payment-processing structure for an online gaming or fantasy sports business.

Sources

• Visa Core Rules
• Visa Merchant Data Standards Manual
• Mastercard Rules
• Regulation GG, 12 CFR Part 233
• Federal Reserve Regulation GG resources
• PCI DSS from the PCI Security Standards Council
• PCI payment-page security guidance
• Nacha ACH Network risk and enforcement topics
• Nacha unauthorized return-rate calculation
• New York interactive fantasy sports statute
• New York State Gaming Commission interactive fantasy sports resources
• Massachusetts fantasy contest regulations
• Florida Statutes, Chapter 849