> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://learn.nuwebgroup.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://learn.nuwebgroup.com/_mcp/server.

# What is merchant of record in ticketing?

> What merchant of record means in event ticketing, who can hold the role, and how it differs from a payment gateway, processor and technology provider.

**The [merchant of record (MoR)](https://stripe.com/resources/more/merchant-of-record) is the entity identified as the merchant responsible for accepting a customer payment for a ticket transaction under the relevant payment arrangement.** The role affects how payments are contracted, described, reconciled and handled when a customer requests a refund or disputes a charge. Depending on the business model, the merchant may be the event organiser, a ticketing operator or another contracted seller.

**Merchant of record is not the same as ticketing software provider.** A company can supply the booking technology without necessarily being the merchant for the customer's payment. Exact legal, tax, consumer-rights and card-network responsibilities depend on the jurisdiction and contracts involved.

## What does a merchant of record do in a ticket sale?

**The merchant of record is the payment-side business accountable for the transaction under its acquiring and related contractual arrangements.** It is often associated with the cardholder statement descriptor, transaction records, refund flows and dispute response.

Consider a hypothetical concert sale. A customer buys two tickets through a venue-branded website. The website might be operated by a ticketing technology company while payments are accepted through an account held by the venue operator. In that arrangement, the venue could be the merchant of record even though the supplier runs the checkout interface.

Another ticketing business might contract to sell on behalf of organisers using the ticketing company's own merchant arrangement. The same event can look similar to the customer while the underlying financial responsibilities differ.

Typical responsibilities to examine include:

* Which legal entity contracts with the acquiring bank or payment service provider.
* Which entity is named in payment, merchant and transaction documentation.
* Which party initiates, funds and administers refunds.
* Who responds to card disputes and bears chargeback costs under the agreements.
* Who calculates, invoices, collects or remits relevant taxes where required by law.

These responsibilities can be shared or allocated in specific ways by contract. The fact that a business is the merchant for card processing **does not by itself settle every tax, consumer-law or accounting question**.

## Who can be the merchant of record in ticketing?

**Different ticketing business models can place the merchant role with different parties.** There is no universal rule that every organiser—or every ticketing provider—must be the merchant.

| Possible model                                      | Illustrative arrangement                                                | Main question to verify                                             |
| --------------------------------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------- |
| **Organiser or venue as merchant**                  | Event organiser accepts payment through its contracted merchant account | Does the organiser control refunds, disputes and settlement?        |
| **Ticketing operator as merchant**                  | A ticketing company sells events through its merchant arrangement       | How do organisers receive and reconcile their proceeds?             |
| **Contracted reseller or intermediary as merchant** | Another authorised selling business processes the customer's payment    | What sale, tax, consumer and remittance duties attach to that role? |

These are simplified examples, not prescribed structures or legal classifications. Ticketing businesses can operate across several countries or brands, and the appropriate setup may differ by payment method, sales channel or contract.

**The checkout brand is not sufficient evidence.** A buyer may see an organiser's logo, while the card statement and legal seller details identify a different entity. Those differences should be clear in customer-facing terms and operational records.

## How is merchant of record different from a payment processor or gateway?

**A merchant of record is a business role; a gateway and processor perform payment technology and transaction services.** Confusing them makes it harder to understand who is responsible when money moves or a transaction is challenged.

* **Merchant of record:** The merchant entity identified for the transaction within the applicable commercial and payment arrangements.
* **Payment gateway:** Technology that securely transmits payment details or payment requests between checkout and the payment ecosystem.
* **Payment processor or payment service provider:** An organisation delivering payment services such as authorisation, capture, routing and reporting, according to its offering.
* **Acquirer:** A financial institution or acquiring service responsible for the merchant acquiring relationship and card-network settlement, depending on the model.
* **Ticketing technology provider:** The system that manages event products, baskets, orders and tickets; it may or may not also perform another payment-related role.

The boundaries vary between suppliers. One provider may combine gateway, processing and merchant services; another may separate them. Payment facilitation and platform-payment arrangements also have their own contractual rules.

For example, a venue might use a ticketing checkout that connects to a third-party card processor. That integration does not make the ticketing software provider the merchant of record. Nor does selecting a familiar payment processor tell the venue who is liable for every dispute under the agreement.

## Why does merchant-of-record setup affect fees and settlements?

**The merchant arrangement determines how payment flows are recorded and how the parties account for the proceeds of ticket sales.** It can influence settlement timing, processing fees, refund deductions, chargeback handling and reporting.

Consider a purely illustrative £100 ticket order with £5 in stated ticketing charges. Before anyone can say how much each party receives, they need to know whether those charges are part of the ticket price or separately disclosed fees, which party accepted the payment, how processor fees are calculated, whether taxes apply and what the commercial agreements require.

A report labelled "gross sales" may include amounts that are not the organiser's net proceeds. Payment settlement may occur on a different date from order confirmation. Refunds and disputes can adjust balances after an event has already taken place.

That is why finance teams should reconcile **orders, successful captures, refunds, processor settlements, fees and transfers to organisers** as distinct records. A successful ticket issue does not necessarily mean all funds have already settled into the final beneficiary's account.

PCI DSS is a related but separate consideration. [PCI Security Standards Council guidance](https://www.pcisecuritystandards.org/faqs/1092/) explains that a merchant outsourcing payment processing can still retain obligations to ensure its service providers protect account data. Outsourcing checkout is not a substitute for identifying and managing the applicable security responsibilities.

## What should a ticketing business check before choosing a model?

**The best merchant arrangement is one whose financial, technical and legal responsibilities the parties can actually operate and reconcile.** The choice affects far more than whose name appears on a payment statement.

Before signing an agreement, ask:

1. Which entity is the merchant for each payment method, country and sales channel?
2. Who signs the acquiring agreement, and whose name appears on the buyer's receipt and statement?
3. Who initiates refunds, funds them and responds to disputes or chargebacks?
4. How are payment-processing charges, ticketing fees, taxes and organiser proceeds calculated and reported?
5. How and when do funds move between the processor, ticketing business and event organiser?
6. What happens when an event is cancelled, a seller becomes insolvent or a charge is disputed after payout?
7. Can different organisers use different authorised merchant arrangements where necessary?
8. Who is responsible for payment security, customer notices and the records needed by finance and regulators?

Answers should be verified in the actual contracts and reviewed against the jurisdictions involved. The same label can hide meaningful differences in risk allocation.

**The key distinction:** merchant of record identifies the merchant-side entity for a payment arrangement, not the brand or software that happens to display the checkout. Ticketing companies should map the payment relationships, refunds, settlements and legal duties explicitly before selecting a model.

## Related explanations

#### [How should ticketing businesses evaluate payment ownership when choosing software?](/strategy-selection/how-should-ticketing-businesses-evaluate-payment-ownership-when-choosing-software)

Strategy & Selection · Choosing a provider

#### [What are payment settlement and reconciliation in ticketing?](/checkout-commerce/what-are-payment-settlement-and-reconciliation-in-ticketing)

Checkout & Commerce · Payments and settlement

#### [How do ticket deposits and instalment payments work?](/checkout-commerce/how-do-ticket-deposits-and-instalment-payments-work)

Checkout & Commerce · Payments and settlement

#### [How can ticketing platforms automate payment reminders?](/checkout-commerce/how-can-ticketing-platforms-automate-payment-reminders)

Checkout & Commerce · Payments and settlement

[More in Checkout & Commerce →](/checkout-commerce)