Outgrowing Your MoR: The Migration Playbook from Paddle, Polar, or Lemon Squeezy to Direct PSP

Leaving a Merchant of Record is rarely a clean cutover. It is a 6-12 month migration project with three operationally significant problems — tax registration sequencing, subscription re-authorisation, and B2B invoice continuity — and one strategic outcome that almost every company eventually accepts: the migration ends at a hybrid configuration, not a full cutover.

This piece covers the playbook for executing the migration well. It assumes the decision to migrate has already been made on the basis of the qualitative thresholds covered in Article 3. If you are still evaluating whether to migrate, that piece is the right starting point. This is the how, not the why.

The Three-Phase Migration Arc

A realistic MoR-to-direct migration runs across three phases. Each has its own work and risks; compressing any one of them is where migrations break.

Months 1-3: Registration and Infrastructure

Three workstreams run in parallel.

Tax registration in every jurisdiction. This is the gating item — if your tax registrations are not active in a jurisdiction by your cutover date, you cannot legally sell into that jurisdiction under your own name. EU OSS application and approval typically takes 4-8 weeks. UK HMRC VAT registration for non-UK businesses runs 4-6 weeks. US state sales tax registrations vary from days to weeks; a tax automation provider (Avalara, TaxJar, Anrok) streamlines this significantly and is worth the cost for any operator with US sales footprint. Australia GST, India OIDAR, Japan JCT, Singapore GST, and any other relevant markets each need their own application — most are weeks rather than months, but the cumulative time adds up.

PSP contracting and integration. Direct PSP relationships need to be established — Stripe, Adyen, Checkout.com, or whichever provider matches your market and product mix. Onboarding involves KYB documentation, processing volume forecasts, expected chargeback rates, and (for higher-volume operators) commercial negotiation on take rate. Integration work runs in parallel with onboarding; budget at least 6-8 weeks for engineering integration even when using off-the-shelf SDKs.

Billing system and infrastructure. The MoR typically handles billing, subscription management, invoicing, and reporting. Direct PSP arrangements require you to bring some of these in-house or contract a separate billing platform (Stripe Billing, Chargebee, Recurly, Maxio, etc.). Selection and implementation typically takes 6-10 weeks. Custom integrations with your CRM, finance system, and revenue recognition tooling add more time.

By the end of month 3, you should have: tax registrations active or imminent, direct PSP onboarded and tested, billing system live with test transactions, and an invoice template that matches your jurisdictional requirements.

Months 3-6: Parallel Operation

In this phase, new customers go directly to the new stack. Existing subscribers remain on the MoR. The purpose is to test the new infrastructure under real conditions before exposing the existing subscriber base to the migration.

What to test:

• Checkout conversion on the new direct PSP relative to MoR baseline
• Subscription billing functioning correctly through renewal cycles
• Invoice generation working correctly per jurisdiction
• Tax calculations matching expected rates
• Chargeback management workflow operational
• Customer support team trained on the new system
• Reconciliation between direct PSP settlements and your accounting

If anything is wrong, it surfaces here — with new customers only, not with your full subscriber base. Resolve issues before initiating the subscriber migration.

Months 6-12: Subscriber Migration

This is the operationally hardest phase. Existing subscribers — whose card payment tokens were issued against the MoR’s MID — need to re-authorise their payment method on the new direct PSP. Card tokens do not automatically transfer between MIDs; even network tokens via Visa Token Service or Mastercard MDES typically require issuer participation that is not universally available.

Re-authorisation campaign design drives the outcome. The components:

• Communication 30-60 days before migration: explain the change to subscribers, with continuity-of-service framing rather than vendor-switch framing
• Multiple touchpoints: email, in-product banner, account dashboard notification, and (for higher-value subscribers) direct outreach
• Simple re-authorisation flow: one-click where possible, minimal friction, clear value reinforcement
• Customer support coverage: agents trained to handle re-authorisation questions, with escalation paths for B2B customers
• Grace period management: how long do subscribers have to re-authorise before service interruption? Typically 30-60 days post-cutover

Expected churn: typically 10-25% of subscribers do not complete re-authorisation. Drivers: subscribers who were dormant and use the prompt to cancel, expired or replaced cards, ignored notifications, and small percentage who actively object to the change. Model conservatively in your migration business case — this is the most commonly underestimated cost.

The Tax Continuity Problem

The hard constraint on migration timing is tax registration. Every jurisdiction where you will be the seller of record post-migration needs an active tax registration before your first sale under your name. A gap — even a single day — creates a real compliance problem.

What this means in practice:

Sequential cutover by jurisdiction. If your tax registration in one market completes before another, you can cut over that market while keeping the MoR active in markets where your registration is not yet live. This avoids the all-or-nothing cutover that creates timing pressure on the slowest registration.

Forward liability only. Tax obligations for periods when the MoR was the seller of record stay with the MoR. You inherit forward liability from your cutover date. The MoR is responsible for filing any final returns covering the period up to cutover; you handle returns from cutover forward.

Invoice number sequencing. Your invoice numbering starts fresh from your cutover date. Some jurisdictions (Italy, Brazil, others) require specific invoice numbering sequences with no gaps; coordinate with the MoR on cutover timing to ensure their final invoices and your first invoices fit the jurisdiction’s requirements.

Tax record retention. Most jurisdictions require tax records to be kept for 6-10 years. Records for the MoR period remain accessible through the MoR (most contracts include data export and retention obligations). Records from cutover forward are your responsibility. Both sets need to be auditable.

The B2B Communication Workstream

B2B customers’ accounts-payable systems do not handle silent vendor changes gracefully. The invoice issuer change matters operationally for them, and they need notice and information to update their records.

What to send B2B customers, 60-90 days before migration:

• Notice of the upcoming change (continuity framing)
• New invoicing entity name, address, and VAT/tax ID
• New banking details if applicable
• Instructions for updating their vendor record / AP system
• Effective date of the change
• Contact for questions

Some B2B customers will require a vendor onboarding process to add you as a new vendor in their ERP — credit checks, supplier compliance forms, sanctions screening. This is normal and adds time. Larger enterprise customers (regulated industries, government, large multinationals) often have 30-90 day vendor onboarding cycles. Initiate these in parallel with your migration timeline.

If you don’t notify B2B customers proactively, expect: AP teams flagging unfamiliar invoices, payment delays, requests for credit notes and re-invoicing, and a few customer service escalations. The communication cost upfront is meaningfully cheaper than the downstream remediation cost.

The Chargeback and Dispute Transition

Chargebacks are filed against the seller of record’s MID. During migration:

Disputes on MoR-period transactions remain the MoR’s responsibility. They run through the MoR’s representment process. Your involvement is providing evidence as the underlying merchant when the MoR requests it; the MoR represents the case to the issuer.

Disputes on direct-PSP-period transactions are yours. You need representment infrastructure operational from day one of the direct period: evidence collection workflow, response timelines (typically 7-14 days from receipt of dispute), and an internal owner for the function. The MoR’s standing chargeback management was probably better than what you build initially; budget for a learning curve as your direct chargeback ratio stabilises.

Card scheme monitoring. Visa’s Acquirer Monitoring Programme (VAMP) and Mastercard’s Excessive Chargeback Merchant programme apply per-MID. The MoR’s aggregate chargeback ratio carried you through programme thresholds. Your direct PSP relationship starts with a clean book but applies the same thresholds. New high-risk merchant categories should expect monitoring; planning for chargeback ratio management from day one is essential.

The Hybrid Landing

Most migrations do not end with the MoR fully retired. The hybrid landing is the operationally honest outcome and typically takes one of these forms:

Geographic hybrid. Direct PSP for your largest markets (US, UK, EU). MoR retained for smaller markets where the compliance overhead of direct registration exceeds the MoR premium on the volume — typically markets representing under 5% of revenue.

Customer segment hybrid. Direct PSP for enterprise B2B with custom invoicing and net-term billing. MoR for self-serve / SMB customers where the MoR’s all-in-one product fits better than a direct PSP plus billing system combination.

Payment method hybrid. Direct PSP for cards and major wallets. MoR retained for local payment methods (specific A2A rails, regional wallets) where the MoR has integrations that your direct PSP doesn’t.

Product line hybrid. Direct PSP for one product line; MoR for another. Common for businesses with both subscription SaaS (direct PSP works well) and digital downloads or course sales (MoR’s tax handling on consumer purchases is more efficient).

Design the hybrid landing from the start of migration planning. Trying to force a full cutover when a hybrid would be the right outcome typically results in reverse-migration of specific segments back to MoR within 12-24 months — a costlier path than just designing the hybrid correctly the first time.

The Reverse-Migration Case

Some companies migrate back to MoR after starting direct. The most common trigger: rapid new-market expansion outpacing the compliance team’s capacity to register and file in each new jurisdiction. A company that migrated to direct PSP for its US/UK/EU markets may find, expanding into ten new countries in 12 months, that direct registration in each new market is slower and more expensive than using MoR.

If this happens, the right move is not “we made a mistake” but “MoR is the right tool for the new-market cohort.” Run new markets through MoR while keeping established markets on direct. As specific new markets cross revenue thresholds that justify direct registration, migrate those markets off MoR — the same migration playbook, but at smaller scale per market.

Treating MoR-vs-direct as a permanent binary creates the most unnecessary migration cycles. Treating them as different tools for different market conditions, and reaching the right tool for each market, is the mature operator approach.

The Migration Checklist

Before initiating migration:

1. Decision is right: validated against the qualitative thresholds in Article 3
2. Hybrid landing designed: which markets / segments / payment methods go direct, which stay on MoR
3. Tax registration plan: every jurisdiction listed, timelines mapped, tax automation provider selected
4. PSP selected and contracted: integration timeline aligned with migration timeline
5. Billing system selected: configuration and integration timeline aligned
6. Re-authorisation campaign designed: communication, UX, support, churn model
7. B2B communication plan: 60-90 day notice cadence, AP onboarding plan
8. Chargeback infrastructure operational: evidence collection, response workflow, monitoring
9. Customer support trained: agents ready for migration questions
10. Reconciliation plan: how the parallel period reconciles across MoR and direct PSP

The MoR migration is one of the more complex payment infrastructure projects a digital business undertakes. The companies that handle it well plan for 6-12 months, expect re-authorisation churn, design the hybrid landing from the start, and treat the MoR-versus-direct decision as a portfolio rather than a binary. The companies that compress timelines, underestimate churn, force full cutovers, and skip the communication workstream are the ones telling cautionary tales 18 months later.