Every payment provider you can bolt onto WooCommerce falls into one of two camps. Most move money on your behalf. A smaller group actually becomes the seller. That single distinction drives everything else: who registers for VAT, who files sales tax returns, whose account a chargeback lands in, and whose name the customer sees on their bank statement.
What a payment processor does
Stripe, PayPal, and most WooCommerce payment gateways are payment processors, or gateways sitting in front of one. Their job is narrow and well understood: capture card details securely, authorize the charge with the card networks and the issuing bank, settle the funds into your account, and hand your store back a result it can act on. They are very good at it, and the integration surface is mature.
What a processor does not do is change who the seller is. In this model your business is the seller of record. The contract for the sale is between you and the buyer, and the obligations that come with being the seller stay with you:
- Working out which countries and states you have a tax obligation in.
- Registering for VAT, GST, or sales tax wherever that obligation exists.
- Charging the correct rate at checkout and filing returns on each jurisdiction's schedule.
- Fighting chargebacks, and absorbing the reversal and the fee when you lose one.
- Issuing compliant invoices and answering billing questions yourself.
Processors increasingly sell tax add-ons that calculate the right rate at checkout, flag when you cross a registration threshold, and in some places help with filing. Those tools are genuinely useful, but they do not move the underlying liability. The registrations stay in your company's name, and if a return is wrong, your company answers for it.
What a merchant of record does
A merchant of record (MoR) is a legal entity that sells your product to the end customer on your behalf. Paddle, the provider PimiPay connects WooCommerce to, works this way: it describes itself as the reseller in the transaction, taking on the liabilities that come with being the party that made the sale.
Based on Paddle's own public positioning, that means:
- Tax. Paddle calculates, collects, and remits taxes across the markets it supports, and states that you do not need to register for VAT, GST, or sales tax in the countries where your customers are.
- Fraud and chargebacks. Paddle screens transactions and fights chargebacks. Disputes are raised against the merchant of record, not against a merchant account in your name.
- Buyer billing support. Paddle handles billing queries from customers, so you are not running a payments support desk.
- Invoicing. Invoices and credit notes are issued by the merchant of record, in the format the customer's jurisdiction expects.
- PCI scope. Card details are entered in Paddle's hosted checkout, so they never reach your server.
The trade is simple to state: you give up being the legal seller, and in exchange someone else carries the tax and payment liability that comes with that role.
Side by side
| Responsibility | Payment processor | Merchant of record |
|---|---|---|
| Legal seller of the transaction | Your business | The MoR, reselling your product to the buyer |
| Tax calculated at checkout | You, usually through a paid tax add-on | The MoR |
| Tax registration, filing, remittance | You, in every jurisdiction where you owe | The MoR, for the sales it makes on your behalf |
| Chargeback liability | Your merchant account absorbs it | The MoR's account absorbs it |
| Fraud screening | Processor tooling, tuned and owned by you | The MoR screens transactions |
| Name on the customer's card statement | Yours | The MoR's, next to your descriptor |
| Billing and invoice support emails | Your team | The MoR handles buyer billing queries |
| Where orders and customer records live | Your store | Your store, if the MoR is integrated into it |
What this means when you sell digital products internationally
For a store selling to one country, this whole discussion is academic. A processor is simpler and cheaper, and your accountant already handles one tax regime. The calculation changes the moment your download, plugin, template, or course starts selling across borders.
EU VAT follows the customer
Digital services sold to EU consumers are taxed where the customer is, not where you are. The same small download can attract a different rate depending on which member state the buyer sits in, and you are expected to hold evidence of where that was. Sellers established in the EU have an EU-wide annual threshold for cross-border B2C digital sales, currently €10,000, below which they can keep charging their home rate. Above it, and for sellers established outside the EU from the first sale, the customer's rate applies. The One Stop Shop schemes let you file one return instead of registering in every member state, but you still have to register, collect location evidence, apply the right rate, and file on time.
US sales tax is fifty moving targets
Since the Supreme Court's decision in South Dakota v. Wayfair in 2018, US states can require sellers with no physical presence to collect sales tax once they cross an economic nexus threshold. Each state sets its own threshold, its own filing frequency, and its own view on whether downloadable software, SaaS, and other digital goods are taxable at all. Those rules change regularly, and rates vary below the state level, so getting it right means resolving an address down to the local jurisdiction.
Invoices have to satisfy the buyer's rules
Business customers need an invoice that names the legal seller, breaks out the tax, and carries the right registration numbers. Selling B2B across EU borders adds reverse charge handling and VAT number validation, and a growing list of countries now mandates structured e-invoicing. None of this is difficult in isolation. All of it is a standing operational job that keeps changing and has nothing to do with your product.
That is the real argument for a merchant of record. Not that cross-border tax is impossible to handle yourself, but that handling it is a permanent cost you take on forever, in exchange for revenue that may be a small share of your sales.
The honest trade-offs
A merchant of record is not free and it is not the right answer for every store. The costs are real and worth knowing before you commit.
It costs more than raw processing
MoR pricing bundles payment processing together with tax calculation and remittance, compliance, dispute handling, and buyer support, so the headline rate is higher than a bare processing rate. The fair comparison is not rate against rate. It is the MoR rate against what the same work costs you directly: a tax engine subscription, registrations and filing fees per jurisdiction, accountant time, and the chargebacks you absorb. Rates change, so check the provider's current pricing page.
Their name appears alongside yours
Because the MoR made the sale, the MoR appears on the customer's card statement. With
Paddle, the descriptor takes the form PADDLE.NET* YOURNAME,
where the second part is a short descriptor you choose. Some customers will not
recognise it and will email you asking what the charge is, so pick a descriptor that
matches your product or domain.
Less low-level control over the charge
Payment runs through the provider's hosted checkout. Which payment methods appear, which fields are collected, how retries behave, what the receipt looks like: these are largely the provider's decisions, configured rather than coded. If your business needs bespoke control of the charge itself, a direct processor API gives you more room.
Disputes are argued by someone else
Having the MoR fight chargebacks is mostly an advantage, but it does mean you are not the party assembling the evidence. You also add a counterparty between you and your money, with payouts arriving on the provider's schedule.
Not every product qualifies
MoR providers accept the seller's liability, so they are selective about what they resell. Paddle's model is built around software and digital products rather than physical goods, and acceptable-use rules apply. Confirm your catalogue is eligible before building around it.
Where PimiPay fits
The usual way to get merchant-of-record billing is to move your products onto the provider's hosted storefront and run your business from their dashboard. That solves tax, but it costs you your store. PimiPay exists so you don't have to make that trade.
PimiPay is a WooCommerce payment gateway plugin that connects your store to Paddle Billing. WooCommerce stays the system of record for your business, and Paddle acts as the merchant of record for the transaction:
- Orders, customers, products, and order notes live in your own WooCommerce database, with High-Performance Order Storage supported. Your data stays in your install, queryable by every other plugin and report you already run.
- Products and variations sync to Paddle so prices stay consistent, and checkout opens as a Paddle overlay from your own order flow.
- Order status is driven by Paddle webhooks, each verified with an HMAC SHA256 signature, so your store reflects what actually happened at the payment provider.
- PimiPay registers as a standard WooCommerce gateway, so you can keep Stripe, PayPal, or any other gateway active alongside it and route international digital sales through Paddle.
Sell worldwide, keep your store
PimiPay connects WooCommerce to Paddle Billing in an afternoon. One licence, every feature, 30-day money-back guarantee.
More detail in the documentation and the FAQ.
Not tax advice. This page explains two commercial models in general terms. Tax rules differ by country, state, and product type, and they change. A merchant of record handles transaction taxes on the sales it makes for you; it does not remove the tax obligations your own business has where it is established. Check your situation with a qualified tax adviser, and confirm any provider's current terms and coverage on their own site.