Skip to content

Merchant of record vs payment processor for SaaS

Merchant of record or payment processor? Who sells, who owes VAT, who handles chargebacks, what Paddle and iyzico charge, and when a SaaS should use both.

Payrudder team9 min read

A merchant of record (MoR) is the company that legally sells your product to the customer: its name is on the card statement, it collects and remits sales tax and VAT, and it answers refunds and chargebacks. A payment processor (or payment service provider, PSP) only moves the money; you stay the seller, and the tax, invoices and disputes stay yours.

That one difference decides most of what follows: how much you pay per transaction, how much tax work lands on your desk, and which provider fits which customers. This guide walks through it with two concrete providers, Paddle (a merchant of record) and iyzico (a Turkish payment provider), and ends with when it makes sense to run both.

What a merchant of record does

Paddle’s own explainer defines a merchant of record as “a legal entity responsible for selling goods or services to an end customer” (Paddle: what is a merchant of record). In practice the MoR acts as a reseller. The sale is really two transactions: the customer buys from the MoR, and the MoR pays you for the product.

Because the MoR is the seller, it takes on the seller’s duties:

  • It appears on the card statement. Paddle notes that it is the MoR’s name on the customer’s statement, which is why the MoR is the liable party.
  • It calculates, collects and remits tax. Sales tax in the US, VAT in the EU and UK, and the equivalents elsewhere. Paddle’s pricing page says it collects the correct rate of tax, tracks filing deadlines, and files and remits on your behalf (Paddle pricing).
  • It handles refunds and chargebacks. The same pricing page lists “fraud protection, chargebacks, and buyer support” as included.
  • It pays you out. You receive the net proceeds, not the customer’s payment.

You give up some control in exchange. The customer’s receipt comes from the MoR, the checkout is the MoR’s, and the payout schedule is the MoR’s.

What a payment processor does

A payment processor charges the customer’s card and settles the money into your account. Everything around that is yours:

  • You are the seller of record. Your company (or a descriptor you configure) is on the statement.
  • Tax is your job. You decide which rate applies, put it on the invoice, file returns and pay the tax office. If you sell to many countries, that can mean many registrations.
  • Invoices are yours. The processor confirms a payment; it does not issue your tax invoice.
  • Disputes come to you. The processor forwards the chargeback and asks you for evidence.

iyzico is a good example for SaaS companies selling in Türkiye. Its help center describes how disputes work: card owners can challenge transactions made without their consent, and if the merchant does not send the required documents in time, or they are insufficient, the disputed amount is withdrawn from the merchant’s account (iyzico help center). In other words, you fight the chargeback, not iyzico.

Merchant of record vs payment processor at a glance

Question Merchant of record (e.g. Paddle) Payment processor (e.g. iyzico)
Who is the legal seller? The MoR You
Whose name is on the card statement? The MoR’s Yours
Who calculates and remits sales tax / VAT? The MoR You
Who issues the customer’s receipt or invoice? The MoR You
Who answers chargebacks? The MoR You, with evidence
Typical fee Higher, because tax and liability are included Lower, because tax and liability stay with you
Payouts On the MoR’s schedule On the processor’s schedule, per your contract
Best fit Selling to many countries with a small team Selling in one market you know well

Fees: what Paddle and iyzico publish

Fees are where the two models are most often compared, and least often compared fairly, because an MoR fee includes work a processor fee does not.

Paddle. The pay-as-you-go price is 5% + 50¢ per checkout transaction, with no monthly fee; sellers with products under $10 can ask for bespoke pricing (Paddle pricing). On a $20 monthly plan that is $1.50, or 7.5% of the sale. On a $100 plan it is $5.50, or 5.5%. The fixed 50¢ hurts low-priced plans most.

iyzico. iyzico does not publish one rate for everyone. Its help center lists commission “starting from 4,29%” plus a ₺0.25 transaction fee per successful transaction for corporate sellers, and starting from 4.49% plus ₺0.25 for individual sellers, and points merchants to the “Instalments and Commission Settings” section of the iyzico control panel for their actual rates (iyzico help center). “Starting from” means your rate can differ, so treat the published numbers as a reference point, not as your price. At the published corporate starting rate, a ₺500 sale costs ₺21.70.

When you compare, add your own cost of tax compliance to the processor’s number: registrations, filings, an accountant’s time, invoice software. For a team selling to customers in dozens of countries, that is often the larger number. For a team selling only inside Türkiye, it is work you already do for the rest of your business.

Payouts

Paddle pays out once a month. On the 1st your balance becomes a payout if it is above your threshold (minimum $100, adjustable up to $100,000), and Paddle sends it by the 15th, by wire transfer or Payoneer. For most countries Paddle charges no payout fee, though a $15 SWIFT fee can apply in some (Paddle: when and how do I get paid).

iyzico pays out faster but on terms that depend on your contract. Its help center describes weekly payouts for corporate users and says payout timing “can vary according to the business model in line with the contract terms” (iyzico help center). Check your agreement and control panel for your actual schedule.

When each one fits

Choose a merchant of record when:

  • You sell to customers in many countries and do not want to register for tax in each one.
  • Your team is small and nobody wants to own chargebacks and VAT filings.
  • You accept a higher fee and a monthly payout in exchange for that work disappearing.

Choose a payment processor when:

  • Most of your customers are in one country whose tax rules you already handle.
  • Local payment habits matter. For Turkish customers paying in lira with local cards, a Turkish provider such as iyzico is the natural fit; its control panel even has a dedicated instalments section.
  • Margin matters and you already have an accountant and an invoicing setup.

Using both at once

Many SaaS companies based in Türkiye end up with both: iyzico for Turkish customers paying in TRY, and Paddle for everyone else. That split is reasonable, but it creates real engineering problems:

  1. Routing. Each new customer has to land on the right provider, and the decision has to stick. Moving an existing customer because someone edited a rule is how double charges happen.
  2. Two ownership models. With Paddle, the provider runs renewals and retries failed payments. With iyzico, you do. If both your code and the provider retry the same failed payment, the customer can be charged twice.
  3. Two sets of receipts. Paddle, as the seller, sends its own receipts. If your billing system also mails a “payment received” email, the customer gets two.
  4. Two ledgers. Revenue, refunds and disputes arrive in two formats, in different currencies, on different payout schedules. Reports that add TRY to USD are wrong.
  5. Moving customers between providers. Cards do not move between providers. The customer has to enter a payment method on the new provider’s form, and the old subscription must stop only once the new one has charged.

How Payrudder handles this

Payrudder is a usage metering, subscription billing and payment orchestration platform. It is not a merchant of record and does not calculate tax; it sits above the providers and lets each one do what it does.

  • Each provider declares what it does. Payrudder’s Paddle adapter declares that Paddle owns renewal and dunning, calculates tax, hosts checkout and sends its own receipts. The iyzico adapter declares hosted checkout and refunds, and leaves renewal and retries to Payrudder. Every subscription gets exactly one owner for renewals and retries, so two engines never retry the same payment.
  • No double receipts. Because the Paddle adapter declares that Paddle sends its own receipts, Payrudder does not send its paid-invoice email for a payment Paddle took.
  • Routing by country and currency. Ordered rules (customer country and subscription currency to provider, first match wins, one default) choose the provider when a subscription is created. The choice is stored on the subscription, so editing a rule never moves existing customers, and a rule that points at a provider unable to charge that currency is rejected when you save it.
  • Tax rates per customer country, not a tax engine. For subscriptions on iyzico, Payrudder applies the rate you configure for the customer’s country. For Paddle, Paddle’s tax stays Paddle’s. For Turkish e-invoices, Payrudder has a Nilvera (UBL-TR) integration that is built but has not yet been run against Nilvera’s test portal.
  • One payment ledger and reports by provider, country and currency, with a reconciliation of invoices against the ledger. Currencies are never added together.
  • Moving subscriptions between providers without both being live at once: the old subscription is untouched until the new provider confirms.

One honest limit: the Paddle and iyzico adapters are written from the providers’ documentation and tested against recorded fixtures. They have not yet been run against the providers’ sandboxes, and the points only a sandbox can settle are marked in the code. Until that is done, treat them as built, not production-proven.

See the payment orchestration feature and the selling SaaS from Türkiye use case for the details.

The short answer

If you sell worldwide with a small team, a merchant of record buys you out of tax and chargeback work, and Paddle’s 5% + 50¢ is the price of that. If you sell mostly to Turkish customers, a payment processor like iyzico costs less per sale and fits local payment habits, but the tax, invoices and disputes stay with you. If you sell to both, run both and route by country and currency, with one system deciding who owns each subscription.

Payrudder Cloud is in early access, priced by system usage, never by a share of your revenue. See pricing.

Still adding up usage in a spreadsheet at month end?

Payrudder meters usage, issues the invoice and collects through iyzico, Paddle or bank transfer.

Keep reading