Gateway, Processor or Merchant of Record
A gateway, processor, and merchant of record are three distinct roles often hidden behind the phrase payment provider: checkout connectivity, transaction processing, and legal seller. The merchant of record is the one that changes who sold the product to the customer, with consequences for tax, receipts, disputes, refunds, and compliance.
The confusion exists because many payment companies bundle several roles behind one brand and one API. Engineers integrate a checkout SDK or payments endpoint, then people inside the business say the provider “takes payments”. That phrase hides the important distinction: some services only route payment data, some help move money through banking or card networks, and some actually become the seller in the transaction.
A gateway is the technical entry point for a payment. It captures or receives payment credentials, may tokenise them, and passes transaction messages to the next party. A processor is closer to the financial rails: it helps authorise, capture, refund, and settle transactions through acquirers, schemes, or bank payment systems. A merchant of record is different in kind. It is the party contracting with the customer as the seller.
The trade-off is control versus delegation. If your company remains merchant of record, you keep the direct customer sale, branding, contract, pricing, and often more flexibility, but you also own tax, disputes, refund policy, compliance posture, and operational edge cases. If a provider is merchant of record, they take on much of that burden, but their rules, supported countries, product categories, checkout constraints, and customer-facing identity may limit you.
In practice, engineers meet this distinction when choosing between a payment API, a hosted checkout, a marketplace model, or a software commerce platform. The useful test is not the provider’s logo or SDK name. Ask who appears as the seller on the receipt and statement, who invoices the customer, who remits tax, and who answers chargebacks. That answer, not the integration surface, identifies the merchant of record.
Common questions
- Does using a payment provider mean they are the merchant of record?
- No. This is a common misunderstanding. The same company may offer gateway, processing, and merchant of record products, but those are not automatically the same arrangement. If your company is named as the seller on the customer receipt or invoice, you are still the merchant of record even if another provider processes the payment.
- What is the practical difference between a gateway and a processor?
- A gateway is mainly the secure software front door that collects, tokenises, or routes payment information from checkout. A processor handles the transaction lifecycle through financial networks, including authorisation, capture, refund, and settlement. Some vendors combine both, so the product boundary can blur, but the conceptual split is routing versus transaction execution.
- Why does merchant of record status matter to engineers?
- It affects system behaviour, not just legal paperwork. Receipt content, tax calculation, refund flows, dispute handling, customer support ownership, country availability, and ledger design can all change depending on who the legal seller is. An integration that looks like a simple payment API decision can therefore alter product, finance, and compliance requirements.
- How can I tell who the merchant of record is?
- Ask who the customer is buying from in the transaction documents. Check the receipt, invoice, statement descriptor, terms shown at checkout, tax collection responsibility, and chargeback owner. If the provider is the named seller, they are likely merchant of record. If your company is named, the provider is probably supplying gateway or processing services.