Event Ticket Merchant Accounts: Future-Delivery Risk, the FTC Fees Rule and the BOTS Act

Selling tickets looks like simple ecommerce: a customer picks a seat, pays by card and gets a barcode. To the bank that sponsors your merchant account, you are taking money today for a service that will be performed weeks or months from now, by someone who may not be you, at an event that may be cancelled. That gap between payment and performance is what decides how ticket sellers get underwritten, and since May 2025 the checkout itself has also been governed by a federal pricing rule that the FTC is now enforcing.

This guide is for primary sellers such as promoters, venues and festival organisers, and for resellers and brokers. It covers how the card networks treat a ticket that is paid for but not yet used, what the FTC's fees rule requires on every displayed price, and what recent BOTS Act cases mean for a broker's inventory. Rules are cited as in force in October 2026.

How the card networks classify ticket sellers

Visa's Merchant Data Standards Manual (April 2026) assigns ticket sellers to MCC 7922, Ticket Agencies and Theatrical Producers (Except Motion Pictures), a code that covers live theatrical productions, services associated with productions and concerts, and theatrical ticket agencies. MCC 7922 is not on Visa's list of high integrity risk MCCs, the codes such as 5967 adult content and 7995 betting that trigger Visa's separate registration regime. Ticketing is treated as high risk because of what the dispute rules allow a cardholder to do long after the sale.

Why a ticket sale stays open until the event

Most chargebacks have to be filed within 120 days of the day the transaction was processed. Non-receipt disputes are different, because the clock can start from the date the customer expected to receive the service rather than the date they paid.

• Visa, dispute condition 13.1 (Merchandise/Services Not Received): an issuer may file within 120 calendar days of the Transaction Processing Date or within 120 calendar days of the last date the cardholder expected to receive the merchandise or services, but never more than 540 calendar days after the Transaction Processing Date.
• Mastercard, goods or services not provided (charged back under reason code 4853, which Mastercard recommends, or 4855): where the merchant specified a delivery or performance date, the issuer may charge back within 120 calendar days of the latest anticipated delivery or performance date the merchant specified. Where the issuer learns the merchant will not provide the goods or services, for example because it is no longer in business, it may charge back immediately rather than waiting for that date.

For a ticket, the expected date is the event. A ticket sold seven months before a festival can therefore come back as a non-receipt chargeback up to four months after the festival date, within Visa's 540-day ceiling. Every ticket sold for an event that has not yet happened is a refund the acquiring bank may have to fund if you cannot. That pool of sold-but-unperformed sales is the number underwriters care about, and it is why ticketing accounts tend to carry reserves or delayed funding sized against upcoming events rather than against past chargebacks.

Visa's rules contain two details written specifically with ticket sellers in mind. First, when an event is cancelled, the issuer must normally wait 15 calendar days from the cancellation before filing a 13.1 dispute, but for ticket agencies that sell third-party event tickets, as for travel agencies under MCC 4722, the wait is 30 calendar days from the date the service was cancelled. That is your window to refund before the dispute arrives, and a refund that has already posted is the cheapest answer to a cancelled show. Second, Visa lists as an invalid 13.1 dispute a transaction the cardholder cancelled before the expected service date, for example out of buyer's remorse.

What underwriters will ask a ticket seller

Because the exposure is forward-looking, expect the acquirer to ask about:

• Your event calendar: how far ahead of each event tickets go on sale, and how much volume you expect to have sold for events that have not yet taken place at any one time.
• Who performs the service. A venue selling its own shows is in a different position from an agency selling tickets to events run by third parties, because the agency cannot control whether the event goes ahead.
• Your refund policy for cancelled, postponed and rescheduled events, where it is shown before checkout, and how quickly refunds are issued in practice.
• For resellers, where inventory comes from, whether you list tickets you do not yet hold, and how you deliver them. The BOTS Act section below explains why the source of inventory has become a compliance question as well as a credit one.
• Your pricing display, because a checkout that breaks the FTC Fees Rule is a regulatory risk the bank is underwriting along with you.

The FTC Fees Rule: the total price, everywhere a price appears

The FTC's Rule on Unfair or Deceptive Fees, 16 CFR part 464, took effect on May 12, 2025. In its final form it applies to two industries only, live-event tickets and short-term lodging, and the FTC's business guidance says it covers any business that offers, displays or advertises live-event tickets, including third-party platforms and resellers. It does three main things.

1. It requires the total price to be disclosed clearly and conspicuously in any offer, display or advertisement of a price, and shown more prominently than any other pricing information except the final amount of payment. Total price means the maximum total of all fees or charges a consumer must pay, including any mandatory ancillary good or service. Only three things may be left out: government charges, shipping charges that reasonably reflect the cost of sending physical goods, and fees for optional ancillary goods or services.
2. It requires the final amount of payment, including any excluded charges, to be disclosed clearly and conspicuously before the consumer is asked to pay.
3. It prohibits misrepresenting the nature, purpose, amount or refundability of any fee, or the identity of the good or service the fee is charged for.

The rule does not displace state laws that give consumers more protection, so a state all-in pricing law still has to be checked on its own terms.

Card fees under the rule

The FTC's FAQ on the rule answers the question most ticket sellers ask first. Businesses may charge or pass through a credit card or payment processing fee where the law otherwise permits it. If a customer has to pay by card, the card fee is mandatory and belongs in the total price. If there is another viable payment method on the same platform that carries no fee, the fee is optional and need not be in the advertised total, but it must still be disclosed, included in the final amount before the customer pays, and described accurately.

Any fee tied to paying by card is also governed by the card networks' rules:

• A Visa credit card surcharge in the US is allowed on credit transactions only, never debit, requires 30 days' written notice to your acquirer before you announce or start it, must not exceed 3% or your average merchant discount rate on credit card transactions, whichever is lower, and has to be disclosed at the point of entry and at checkout, with an ecommerce cardholder given the chance to cancel after seeing it.
• A convenience fee, under Visa's rules, is only allowed for a bona fide alternative payment channel outside the merchant's customary channels, and may not be charged at all by a merchant that operates exclusively card-absent. It must be a flat amount, apply to every form of payment in that channel, and may not be added to a recurring or installment transaction. An online-only ticket seller cannot rename a percentage card fee a convenience fee to get around the surcharge rules.

Surcharging rules are also the subject of the pending Visa and Mastercard merchant settlement, which is not yet in force. Our guide to that settlement explains what would change if it is approved.

How the FTC is enforcing it

The first major case under the rule involved a reseller platform. On April 9, 2026 the FTC filed a complaint against StubHub in the Southern District of New York, together with a proposed order, which needs the court's approval, under which StubHub would pay $10 million to fund refunds to consumers. The complaint alleges that StubHub, which had publicly supported all-in pricing during the rulemaking, planned internally to phase in compliance after the May 12, 2025 effective date, holding back NFL tickets because the league released its 2025 schedule on May 14, which the company's own plan called a 99th percentile traffic event. The FTC sent StubHub a warning letter on May 14 about prices that left out mandatory fulfilment and service fees. The FTC brought a case over a compliance delay measured in days.

Earlier, on September 18, 2025, the FTC and seven state attorneys general sued Live Nation and Ticketmaster in the Central District of California. Their complaint alleges, among other things, that Ticketmaster advertised prices that left out mandatory fees until checkout, and that it allowed brokers to get around its own ticket limits using large numbers of accounts. Those are allegations, not findings.

The BOTS Act and where a broker's tickets come from

The Better Online Ticket Sales Act, 15 U.S.C. 45c, makes it unlawful to circumvent a security measure, access control system or other technological control that a ticket issuer uses to enforce its posted purchase limits. It also makes it unlawful to sell a ticket obtained that way if the seller took part in the circumvention, had the ability to control it, or knew or should have known the ticket was obtained in violation of the Act. The FTC enforces it as an unfair or deceptive practice, and state attorneys general may also sue.

Two recent FTC cases show what the agency looks for, and both involve payment cards on the buying side:

• Key Investment Group. On August 18, 2025 the FTC sued this Maryland broker and three of its executives, alleging that it used thousands of Ticketmaster accounts, thousands of virtual and traditional credit card numbers, proxy and spoofed IP addresses and SIM boxes to buy at least 379,776 tickets for nearly $57 million in just over a year, including 273 tickets to a single Taylor Swift show with a six-ticket limit. The Daily Record reported in April 2026 that the court denied the company's motion to dismiss, holding that the Act applies to any person and not only to automated bots.
• Elite Events. On July 27, 2026 the FTC filed a complaint and a proposed stipulated order against Elite Events and Tickets, which did business as Smart Scalpers, and its two owners, alleging they used hundreds of accounts in fictitious names, virtual card accounts generating thousands of unique card numbers and IP proxies, with many agents overseas, across more than 2,400 events. The proposed order would impose more than $10.7 million in civil penalties, suspended after a $300,000 payment because of the defendants' inability to pay.

For a reseller, the knew-or-should-have-known clause matters as much as the circumvention ban: a broker who resells inventory bought from a limit-busting operation can be exposed too. That is why a credible answer to where your tickets come from now belongs in the application.

Before you apply: a checklist for ticket sellers

• Make every displayed price the all-in total, including service, fulfilment and any mandatory card fee, and make it more prominent than any other price figure on the page.
• If you pass on card costs, decide whether the fee is a credit card surcharge, and follow Visa's surcharge rules and your state's law, or offer a genuinely viable fee-free payment method and disclose the fee before payment.
• Publish a cancellation and postponement refund policy before checkout, and be able to refund a cancelled event inside Visa's 30-day waiting window.
• Keep order records, delivery confirmation and event correspondence for at least 540 days after each sale.
• Prepare an event calendar showing on-sale and event dates and your expected volume sold ahead of events, so the acquirer can size a reserve on real numbers rather than assumptions.
• If you resell, document where your inventory comes from and how it was bought, and do not buy from anyone you cannot vouch for.
• Put the event date on the receipt and in the order confirmation. Mastercard's non-receipt window runs from the performance date the merchant specified, and you want that date on the record.

A well-run ticket seller can still be one cancelled tour away from a run of chargebacks it did not cause. The sellers who get approved on workable terms arrive with that exposure already measured, the refund policy written and the checkout compliant.