Merchant of record vs. payment processor: what your business still owns

A payment processor helps a business accept and manage payments. A merchant of record takes the seller role for transactions within its contracted service. That difference affects customer invoices, transaction-related taxes, refunds, and the information your accountant needs. It is a business arrangement as well as a checkout choice.

Paddle describes its merchant-of-record model for digital product businesses in its developer documentation. Its agreement sets out the reseller relationship and the supplier's remaining obligations. Use the contract for the specific product you are considering; the phrase 'merchant of record' is not a substitute for reading the scope.

Compare the contracted product rather than assigning an entire vendor to one permanent category. Stripe separately documents Managed Payments as a merchant-of-record service for digital products. Buying ordinary payment processing does not establish that those responsibilities are included. The proposal must identify the selected service.

Ask both finalists to complete the same responsibility table. Replace broad promises about compliance or support with named tasks and the party responsible for each. Confirm the answer for your products, customer countries, and legal entity rather than relying on a general homepage description.

A provider handling tax on covered customer transactions does not settle every tax question your business faces. Ask your adviser to distinguish the customer sale from your company's own income, payroll, registrations, reporting, and any other sales channels. The answer depends on your jurisdiction and actual operating arrangements.

Paddle's agreement requires accurate product and supplier information. It also leaves the supplier responsible for its own invoicing and reporting obligations concerning the amounts Paddle pays it, which the agreement calls Supplier Fees. Those are separate from the customer transaction taxes covered by the service. Stripe's Managed Payments documentation likewise says the business remains responsible for indirect-tax compliance on transactions in countries outside its covered scope.

Maintain a short scope record beside the contract. List the covered products and channels, what information must be kept current, and who checks changes with the provider and your tax adviser. Review this record when the business expands, not just when it renews the software.

A processing rate and a merchant-of-record fee may pay for different work. Compare the full annual cost of the services you would actually buy, including retained tax administration, engineering, billing support, refunds, currency conversion, and finance time. Do not compare one headline percentage with a bundle that includes several additional responsibilities.

Ask for a settlement illustration using your own order values and currencies. Include a partial refund and a disputed transaction. Check which charges reverse, which remain, whether reserves apply, and when money becomes payable to your business. Cash timing can matter even when two annual cost estimates look similar.

Separate quoted terms from scenarios. If you model an assumed refund rate or a future sales mix, label it as an assumption and show how changing it affects the result. Avoid treating a vendor's marketing example as a forecast for your company.

The bank deposit alone is not a sufficient explanation of the sale. Obtain the underlying transaction detail, fees or contractual deductions, tax information, refunds, currency movements, and the bridge to the settlement. Retain identifiers that connect these records to your own customer and subscription data.

For ordinary payment processing, Stripe's payout-reconciliation documentation offers an example of the reporting detail to request, subject to that report's scope. A merchant-of-record settlement follows its own contractual structure and may require a different accounting workflow. Ask for an actual sample from the product under consideration.

Your accountant should determine gross-versus-net presentation, revenue timing, and the appropriate accounts using the contract and applicable accounting standards. Do not let the label on an integration's default account make that decision. Test a month-end settlement that includes sales from one period and cash received in another.

Imagine a buyer who recognizes your product name but not the name on the payment receipt. Who answers the question, locates the order, authorizes a refund, and confirms that access should end? Write the handoff clearly enough that customer support can follow it without consulting a developer.

Then test a duplicate purchase, a cancellation after renewal, an incorrect invoice detail, and an enterprise customer asking to pay by bank transfer. The provider may have a clear standard process that conflicts with how your sales team has promised to work. Resolve that mismatch before moving customers.

A merchant-of-record service deserves consideration when its product eligibility and commercial terms fit your sales, and the assigned transaction responsibilities are valuable to your team. A processing arrangement deserves consideration when you need the relevant control and have a credible plan to own the remaining work.

Before committing, obtain a migration plan for existing subscriptions, payment credentials, customer notices, open refunds, and historical reports. Name the person responsible for each item. The final decision should explain the responsibility split, expected annual cost, cash timing, and exit route in language both finance and product teams can use.