Opening an event ticket merchant account through 2Accept keeps your settlement moving on tickets you sold for a show that is still months away — by underwriting the future-delivery window directly, sizing the reserve to your open event exposure rather than to raw volume, and treating a cancelled show as a managed refund event instead of a reason to close the account. Our event ticket merchant accounts include primary ticketing for promoters, venues and festivals, secondary-market resale for licensed brokers, season-ticket and membership billing, and ticketing-platform operators under a single underwriting relationship.
The process of opening an event ticket merchant account with 2Accept takes four steps. First, complete the online application with your EIN, Articles of Incorporation, three months of bank and processing statements, your upcoming event calendar with on-sale dates and average lead time between sale and event, your refund and cancellation policy as published at checkout, and — for resale brokers — your state resale licences and BOTS Act compliance statement. Second, a dedicated ticketing underwriter reviews your primary-to-resale mix, average ticket, open event exposure, cancellation history, and delivery method within one business hour. Third, you receive your MID coded to MCC 7922 and integrate via gateway API, hosted checkout, a broker POS such as SkyBox or Ticket Evolution, or an iOS and Android SDK after signing the merchant processing agreement. Fourth, you go live in 48 hours with event-date reserve release, on-sale capacity, 3-D Secure 2, and chargeback alerts already configured.
Rates for an event ticket merchant account on 2Accept start at 3.49% for primary-market promoters, venues and festivals, with secondary-market brokers and long-lead sellers priced on their future-delivery window and refund record rather than on a blanket high-risk surcharge. Pricing depends on monthly volume, average ticket, the lead time between sale and event date, your cancellation and refund history, chargeback ratio, delivery method, and whether your account requires a domestic U.S. MID, an offshore placement, or a cascading structure across several MIDs.
Ticket sellers evaluate a payment processor on how it treats the gap between the sale and the event — the reserve it holds, when it releases, what happens on a cancellation, whether resale is approved at all, and whether the account survives a 10am on-sale. 2Accept's ticketing desk covers each dimension below and underwrites the seller types, market models, and compliance configurations listed here.
2Accept underwrites the full ticketing spectrum — independent concert and comedy promoters, venues and theaters running their own box office, multi-day festivals, sports clubs and promoters selling single-game and season tickets, licensed secondary-market brokers, and ticketing platforms that process on behalf of event organizers. Primary sellers board under MCC 7922 or 7941; brokers board under 7922 with the resale model documented at onboarding.
Underwriting turns on three questions no general-retail underwriter asks: how long is the gap between the sale and the event, how is the ticket delivered and proven delivered, and what happens to the money if the event does not take place. Those three answers set the reserve, the release schedule, and the rate — not the word "tickets" on its own.
Apply for a Ticket Seller MID →A primary seller controls the inventory and the event: a promoter who books the artist, a venue that owns the room, a club that plays the game. The future-delivery risk is real but it is the seller's own event, so cancellation history and insurance tell the underwriter most of what they need to know.
A secondary-market broker resells tickets originally issued by someone else. The broker does not control whether the event happens, often does not hold the ticket at the moment of sale, and delivers by barcode transfer rather than by scanning a wristband at a gate. That is why aggregators decline brokers outright. 2Accept underwrites licensed brokers on inventory sourcing, delivery method, transfer records, and non-delivery dispute history — and tells you plainly which models it will and will not place.
Apply for a Primary or Resale MID →Every ticket sold before the event is a contingent liability to the acquirer: if the show cancels, every sale can return as a "services not received" chargeback on the same day. Aggregators cover that by holding money blindly — a percentage reserve on all volume, or a 21-day hold on every sale — which traps cash against events that almost always happen.
2Accept replaces the blanket hold with an exposure model. Open event exposure is tracked per event, the reserve is sized to the events still outstanding, and funds release as each event date passes rather than on a fixed calendar. A festival in September does not freeze the cash from a sold-out club show that happened last Friday.
Apply for an Event-Exposure MID →Ticketing compliance runs on three layers that general-retail underwriting never touches. Federally, the BOTS Act prohibits circumventing purchase limits and access controls on primary sales, and the FTC's rule on unfair and deceptive fees — in force for live-event tickets since May 2025 — requires the total price including mandatory fees to be shown up front, not at the last checkout step.
At the state level, several states license or register resale brokers, a few cap resale prices or restrict resale within a radius of the venue, and most require a clear refund guarantee on resale. The card networks add their own layer: a merchant in a delayed-delivery business must disclose the delivery date and refund terms at the point of sale. 2Accept reads your checkout against each of those before boarding, so the file is not rebuilt after a dispute.
Apply for a Compliance MID →2Accept integrates with the stacks ticket sellers actually run — hosted checkout and REST APIs for promoters running their own storefront, white-label ticketing platforms for venues and festivals, and broker point-of-sale systems such as SkyBox, Ticket Evolution, TicketNetwork and Logitix for resale operations that fulfil across multiple exchanges.
Delivery integrations matter as much as payment ones. Mobile barcode transfer, PDF delivery with download logs, and gate-scan reporting all feed the evidence file that defeats a non-delivery dispute, so the gateway connects to your delivery record as well as your checkout.
Apply for an Integrations MID →Ticketing chargebacks cluster on two reason codes: 13.1, services not received, filed by a buyer who claims the ticket never arrived or did not scan; and 13.7, cancelled services, filed after a show is called off. Both are won or lost on delivery evidence, so the representment package carries the barcode transfer record, the download log, the gate-scan timestamp, the buyer's accepted refund terms, and the event's actual status.
Ethoca and Verifi alerts catch a dispute 24–72 hours before it posts, which is long enough to refund a genuinely undelivered ticket or to answer a "didn't scan" claim with the scan log. The ratio is managed per MID, and a cancellation is run as a scheduled refund event with the acquirer informed in advance, so refunds never land as chargebacks.
Apply for a Dispute Defense MID →Every high risk merchant account is priced by risk tier. Your vertical, volume, and chargeback ratio determine which tier underwrites you. Event ticketing underwrites at the mid tier, with the reserve structure rather than the rate doing most of the risk work; brokers with long future-delivery windows may price toward the top tier. Rates are average and may vary depending on individual circumstances and risk profile. Interchange may be passed to merchants for more challenging approvals.
Complete the 4-minute application. No credit pull, no application fee, no long-term contract.
A 2Accept ticketing underwriter reviews your event calendar, lead times, primary-to-resale mix, and refund record within 1 business hour.
Sign your MPA, receive your MCC 7922 MID, and integrate via gateway API, hosted checkout, broker POS, or mobile SDK.
Scale through a 10am on-sale with pre-authorized capacity, event-date reserve release, and chargeback alerts running.
Connect your merchant account to the storefront, POS, accounting, and CRM software you already run.
2Accept enables smooth payment operations across Shopify stores.
2Accept connects with Clover POS for seamless point-of-sale transactions.
2Accept syncs payments with QuickBooks to simplify accounting and reconciliation.
2Accept supports BigCommerce to facilitate online payment processing.
2Accept integrates with Authorize.net for secure transactions.
2Accept connects with Salesforce to streamline customer relationship management.
2Accept extends payment capabilities to WooCommerce-powered online stores.
Aggregators pool thousands of merchants under one master account and treat future delivery as a reason to hold money — PayPal applies a 21-day hold to ticket sellers by default, and Stripe imposes a percentage reserve the moment lead times lengthen. Resale brokers are declined outright. When a show cancels, the account closes with the refunds still to run. A dedicated MID from 2Accept is coded for ticketing, reserved against real event exposure, and kept open through a cancellation.
| Feature | 2Accept | Stripe | Square | PayPal |
|---|---|---|---|---|
| Licensed secondary-market brokers approved | ✓ | ✕ | ✕ | ✕ |
| Reserve sized to open event exposure, not raw volume | ✓ | ✕ | ✕ | ✕ |
| Reserve releases on event date (no blanket 21-day hold) | ✓ | ✕ | ✕ | ✕ |
| Cancellation handled as a managed refund event, MID stays open | ✓ | ✕ | ✕ | ✕ |
| On-sale spikes without a velocity freeze | ✓ | ✕ | ✕ | ✕ |
| Dedicated MID (not aggregator pool) | ✓ | ✕ | ✕ | ✕ |
| Human ticketing underwriter (not chatbot) | ✓ | ✕ | ✕ | ✕ |
Every 2Accept high risk merchant account includes the monitoring and mitigation stack required to stay under Visa's 1.0% chargeback threshold — and to keep a single cancelled show from becoming an account-level event.
Ethoca and Verifi CDRN integrations catch disputes before they post, letting you refund an undelivered ticket pre-chargeback and protect your ratio.
Open liability is tracked per event, so the reserve follows the shows still outstanding and releases as each date passes rather than on a fixed calendar.
3D Secure shifts liability to the issuer on authenticated high-ticket orders, eliminating fraud-based chargebacks on premium seats and VIP packages.
Our dispute team files barcode transfer, download, and gate-scan evidence against "services not received" claims, recovering revenue within 45 days.
Split primary and resale volume across 2–5 MIDs so a cancellation on one product line never threatens the ratio on the others.
Dynamic billing descriptors carrying the event or artist name the buyer recognises lower "I don't recognize this charge" disputes by 40%+.
"PayPal held every sale for 21 days and we were financing inventory on credit cards to cover it. Event-date release gave us our own cash back."
"A headliner pulled out and we had to refund four thousand tickets. Our old processor would have closed us. 2Accept ran it as a scheduled refund and the MID never blinked."
"They actually understood that a reserve should track the shows still open, not the whole month's volume. Nobody else we spoke to did."
An event ticket merchant account is a specialized payment-processing account that acquiring banks issue to promoters, venues, festivals, sports organizations, licensed resale brokers, and ticketing platforms under MCC 7922 or 7941, designed to handle the future-delivery gap between the sale and the event, the cancellation exposure that gap creates, the non-delivery disputes that cluster around digital ticket transfer, and the resale, bot, and all-in pricing rules that govern how tickets may lawfully be sold.
The account permits card-not-present sales across web, mobile, and broker point-of-sale, supports event-date reserve release and scheduled cancellation refunds, and operates under tailored underwriting terms that include per-event exposure tracking, delivery-method review, state broker licence verification, 3-D Secure 2 on high-ticket orders, Ethoca and Verifi alerts, dynamic event-name descriptors, cascading across multiple MIDs, and discount rates between 2.89% and 4.95%.
A ticketing business gets a high-risk classification for a reason that has nothing to do with the buyer's honesty: the card is charged months before the service is delivered. To the acquirer every open ticket is a contingent refund, and a single cancelled event can convert an entire on-sale into chargebacks on the same afternoon. Brokers add a second layer — they do not control the event, often do not hold the ticket at the moment of sale, and deliver by barcode transfer that a buyer can claim never arrived. Acquirers weigh how long your lead times run, how delivery is proven, whether your refund terms are disclosed at checkout, whether your resale operation is licensed where licensing is required, and what your cancellation history looks like.
Opening an event ticket merchant account differs from opening a standard retail account in three ways. First, underwriting reads your event calendar and delivery method, not just your statements — lead time and proof of delivery drive the file. Second, the reserve is structured rather than flat: it tracks open event exposure and releases as each event date passes, instead of holding a percentage of all volume or every sale for 21 days. Third, the account issues a dedicated MID coded to MCC 7922 that belongs exclusively to your business, so a cancellation becomes a refund event you run with the acquirer rather than a termination you learn about by email.
2Accept underwrites event ticket merchant accounts for concert and comedy promoters, venues and theaters, multi-day festivals, sports clubs and promoters, licensed secondary-market brokers, consignment resellers, and white-label ticketing platforms across the United States. Applications are reviewed by a dedicated ticketing underwriter within one business hour and approved in 48 hours depending on licensing and documentation, then integrated via gateway API, hosted checkout, broker POS, or an iOS and Android SDK after signing the merchant processing agreement.
Acquiring banks segment ticket sellers by control of the event, lead time, and delivery method. The sellers 2Accept underwrites most often are:
A dedicated event ticket merchant account gives you advantages no payment aggregator can match, because the account is reserved, monitored, and priced around the gap between sale and event from the first day:
Qualifying for an event ticket merchant account requires meeting documentation, entity, and compliance requirements that the acquiring bank reviews during underwriting. Standard qualification criteria include:
Keeping an event ticket merchant account healthy long-term requires managing exposure as actively as dispute ratio, because acquirers re-audit MIDs on a rolling schedule, resale law moves state by state, and Visa's VDMP threshold (0.9%) and Mastercard's ECM threshold (1.5%) trigger fines above either limit. The strategies that protect a ticketing MID are:
No. There is no long-term contract and no early-termination penalty — accounts are month-to-month once approved.
Your EIN and formation docs, three months of processing and bank statements, your upcoming event calendar with lead times, your refund and cancellation policy as shown at checkout, delivery-method documentation, government-issued ID for the principal, and — for brokers — state resale licences and a BOTS Act compliance statement.
If you resell in a state that licenses or registers brokers, yes — the licence should be on file. If a filing is pending, apply anyway and we will stage the file against your licensing timeline.
Yes — that is one of the most common reasons sellers come to us. Aggregator termination for future-delivery or resale policy reasons does not disqualify you from a dedicated MID.
Yes. A registered legal entity with a valid EIN is required, and new promoters are approved on the event calendar, venue agreements, refund policy, and a documented delivery method in place of processing history.
Personal credit is one factor, not a gate. Approvals weigh business model, lead times, refund history, and processing record — promoters with weak credit are regularly approved.
Via REST API, hosted checkout, a broker POS such as SkyBox or Ticket Evolution, a white-label ticketing platform gateway, or our iOS and Android SDK. Most sellers are integrated the same day credentials are issued.
No. The application and underwriting review are free.
Event ticketing is priced at the mid high-risk tier, typically from 3.49% + $0.25, quoted before you commit based on volume, average ticket, lead time, refund history, and primary-to-resale mix.
Often, yes. A broker does not control the event and typically has longer lead times and a higher non-delivery dispute rate, so pricing can move toward the top tier. Held inventory and strong transfer records bring it back down.
Usually not. A quarter-point of discount rate is small next to 20% of your volume sitting in a blanket reserve for three weeks — most sellers gain more from event-date release than from a rate negotiation.
Yes. As you build processing history, keep refunds orderly, and hold a low chargeback ratio, rates and reserve terms are reviewed and can be reduced.
Interchange is the fee the card networks set and pay to issuers. Interchange-plus pricing passes it through transparently with a fixed markup, available on qualifying accounts — and high-ticket conference and VIP sales often qualify.
Usually a reserve applies, but it is sized to your open event exposure and releases as each event date passes rather than being a fixed percentage of all volume on a fixed calendar.
Funding is typically next-day to 48 hours depending on the acquirer, with the event-exposure reserve released separately as dates pass.
A per-dispute fee (commonly $15–$25) applies, disclosed in your agreement. Pre-dispute alerts help you avoid most chargebacks entirely.
Yes — licensed brokers reselling held inventory with barcode transfer delivery are underwritten regularly. Aggregators decline brokers by policy; we underwrite them on sourcing, delivery, licensing, and dispute history.
Honestly, it depends. Spec selling carries the heaviest non-delivery risk in ticketing and several acquirers prohibit it outright. We review spec-heavy files case by case, and a broker whose inventory is mostly held will be placed far more easily than one whose inventory is mostly promised.
It affects underwriting. Brokers attest that inventory is sourced without circumventing purchase limits or access controls on primary sales. A file that cannot make that attestation is a file most acquirers will not board.
Yes. A handful of states cap resale prices or restrict resale near the venue, and selling above a cap into one of those states is both a compliance failure and a dispute magnet. Geofencing those rules is part of the onboarding file.
They are structured as separate MIDs under one master relationship, so the dispute and refund profile of each stays isolated and a cancellation on the primary side never touches the resale ratio.
Yes. Selling on behalf of season-ticket holders is underwritten, with inventory source documented per listing so the delivery chain is clear if a dispute arrives.
Yes, with seller KYC and a sub-merchant or payfac structure rather than a single retail MID, because you are moving money to people who are not you.
Yes. Since May 2025 the total price including mandatory fees must be shown up front for live-event tickets, and that applies to resale listings as much as primary sales. We review your checkout against it before boarding.
Because the sale settles months before the event is delivered. If the show cancels, every sale can return as a chargeback at once, so aggregators hold a blanket percentage of all volume or every sale for 21 days. 2Accept sizes the reserve to the events still open instead.
Exposure is tracked per event. As each event date passes and the service is delivered, the reserve attributable to that event releases automatically, so cash from last weekend's show is not held against a festival in September.
You tell your underwriter, the refund batch is scheduled, and refunds run as refunds — not as chargebacks against your ratio. The MID stays open. A cancellation handled this way is a cash-flow event, not a termination.
Exposure is re-dated to the new event date rather than refunded. Buyers who want a refund are refunded on request; everyone else keeps their ticket and the reserve simply moves with the date.
Generally yes, because more is outstanding at any moment. Festivals selling twelve months out carry more exposure than a club selling two weeks out — but the reserve is proportional to what is open, not punitive.
It is not required, but a promoter carrying cancellation cover is underwritten more favourably because the refund source is insured rather than operating cash.
Yes. A clean record of events delivered as sold, orderly refunds, and a low dispute rate lowers the reserve percentage at scheduled reviews.
Not if we know it is coming. Share the on-sale date and expected volume and the MID is pre-authorized for the spike, instead of an automated velocity model reading it as fraud.
Mostly reason code 13.1, services not received — "the ticket never arrived" or "it didn't scan" — and 13.7, cancelled services, after a show is called off. Fraud codes are a smaller share and 3-D Secure handles most of them.
With the delivery record: the barcode transfer confirmation, the download log, the gate-scan timestamp, and the buyer's accepted terms. A ticket that scanned at 7:42pm is a dispute you win.
Our dispute team files evidence packages that typically resolve within 45 days of the chargeback.
No — a refund is not a chargeback. The risk is a buyer who disputes before you refund, which is why the refund batch is scheduled and pre-notified the day the cancellation is announced.
Generally sustained ratios above ~0.9% (Visa) risk monitoring programs. We watch this monthly and intervene early.
A network program (Visa/Mastercard) triggered when your ratio exceeds thresholds. Our alerts and reserves are designed to keep you well below them.
Ethoca and Verifi notify you the moment a cardholder disputes, so you can refund a genuinely undelivered ticket inside the window before it becomes a chargeback.
Significantly. A statement line reading "ACME TIX" is forgotten by the time the card bill arrives; one reading the artist or event name and date is not. Dynamic descriptors cut "I don't recognize this charge" disputes by 40%+.
Stripe and Square treat long lead times as a reserve trigger and close accounts on a cancellation, and neither boards resale brokers. 2Accept gives you a dedicated MID coded 7922, a reserve that tracks open events, and an account that stays open through a cancellation.
PayPal applies a 21-day hold to ticket sellers by default and holds funds aggressively on any dispute spike. A dedicated MID with event-date release keeps your cash and your account under your control.
They are ticketing platforms that bundle processing — you get their fees, their payout schedule, and their terms. If you want your own storefront, your own buyer data, and your own settlement, you need your own MID behind your own checkout.
Yes. Multi-MID cascading load-balances volume across accounts and fails over automatically, which is also how primary and resale volume are kept apart.
We underwrite future delivery specifically — per-event exposure, event-date release, cancellation workflow, broker licensing, and delivery-evidence representment — rather than generic high-risk placement with a flat reserve.
Those are gateways, not acquirers. We provision the underlying MID and can run it behind NMI or Authorize.net if your ticketing software already connects to them.
In most cases yes — we can place a new MID behind your existing gateway with minimal reintegration, which is the fastest way out of a blanket hold.
Most U.S. promoters and brokers are placed domestically. Offshore placement is used where jurisdiction, international touring, or volume calls for it, and 2Accept can cascade across both.
Send us a recent statement and your upcoming event calendar and we'll tell you how much of your reserve should already have been released. The review is free, there's no application fee, and you'll have an answer fast.
Start Your ApplicationTicket sellers rarely stay in one lane as they grow — a promoter adds a VIP travel package, a venue launches a membership with priority on-sale access, a sports club runs a fantasy contest for season-ticket holders, a festival sells merch and camping alongside the wristband. Each of those underwrites on a different basis even though the buyer sees one checkout. 2Accept underwrites these adjacent categories under the same acquiring relationships, so one operator can hold multiple MIDs across related verticals without restarting underwriting from scratch.
If your ticketing business operates across multiple high risk verticals — say, a primary box office, a separate licensed resale brokerage, and a third brand selling travel-and-ticket packages — 2Accept can structure separate MIDs for each entity under one master underwriting relationship. Volume load-balances across the MIDs through our cascading gateway, and each MID's exposure and dispute profile is monitored independently so a cancellation on one product doesn't threaten the others.
Apply now and let's build your business — without hesitation.
SPEAK TO A PAYMENT EXPERT