MoR to Direct PSP Migration: A Phased Operator Playbook

Leaving a Merchant of Record changes the legal seller and operating responsibilities alongside the PSP and infrastructure stack. The central workstreams are tax obligations, subscription continuity and B2B invoice changes. Compare a hybrid with full cutover using your own costs and constraints.

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

Use three readiness phases rather than a universal calendar. These gates are an authored operating framework, not measured migration-duration benchmarks.

Phase 1: Registration and Infrastructure

Three workstreams run in parallel.

Tax registration where required. Map seller, product, customer type, location, nexus or threshold, registration deadline, collection obligation and filing owner. Not every country requires registration before every sale. EU OSS simplifies eligible VAT reporting; it is not a global licence to sell. Tax software can support calculation and filings but does not make the PSP the seller.

PSP contracting and integration. Direct PSP relationships need to be established — the MoR vs PSP decision framework covers how to make this choice and what each model implies — 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; scope engineering against your billing and reconciliation needs.

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.). Estimate implementation using your actual integrations. Custom integrations with your CRM, finance system, and revenue recognition tooling add more time.

Phase 1 exit gate: applicable tax obligations and deadlines documented, PSP onboarded and tested, billing and reconciliation passing test transactions, and compliant invoice templates.

Phase 2: 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.

Phase 3: Subscriber Migration

Obtain a written plan from the departing MoR and receiving PSP covering transferable payment methods, vault export, merchant identifiers, consent, schedules and cancellation notices. Tokens are not automatically portable, but neither does every migration require every subscriber to re-enter their card. Pilot the supported path and prevent duplicate billing.

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

• Communication 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? Set and disclose a cohort-specific grace period

Measure completion, voluntary cancellation, failed payments and support contacts separately on a pilot cohort. Use downside scenarios labelled as assumptions; no observed 10–25% churn benchmark is established here.

The Tax Continuity Problem

The hard constraint on migration timing is tax registration. Identify the registrations required for your direct sales in each jurisdiction, including the applicable nexus tests and effective dates. Complete required registrations by the legal deadline; the MoR's prior coverage does not establish your own registration status.

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.

Allocate historical and future obligations. The MoR's seller role does not settle all indemnities, refunds, reserves or historic tax obligations between the parties. Identify the seller and filing owner for each period and review surviving obligations before termination.

Invoice number sequencing. Follow the new seller's applicable numbering and correction rules; do not assume every jurisdiction requires a restart or allows reissuing old invoices under a new seller.

Tax record retention. Set retention by jurisdiction and document type. Export historic invoices, tax evidence, refunds and reconciliation records while available; confirm post-termination access contractually.

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, with notice timed to their onboarding needs:

• 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. Obtain onboarding lead times from the affected enterprise customers. 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 follow the MoR/acquirer workflow; evidence duties, reserves and economic loss allocation depend on your contract. Agree ownership and continued evidence access after cutover.

Disputes on direct-PSP-period transactions are yours. You need representment infrastructure operational from day one of the direct period: evidence collection workflow, processor-supplied deadlines for each dispute stage, 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. Ask the new acquirer how applicable programmes and fraud/dispute measures apply. A new MID does not assure that merchant history or risk assessment resets.

The Hybrid Landing

A hybrid may retain the MoR for selected segments. Compare these configurations with full cutover:

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 — review the MoR provider comparison across Paddle, Polar, and FastSpring to select the right provider for retained segments; use actual segment economics rather than a universal revenue-share threshold.

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. An option 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).

Evaluate the hybrid from the start. Account for the extra reconciliation, customer-support and billing complexity of two sellers before deciding it is preferable.

The Reverse-Migration Case

Some companies migrate back to MoR after starting direct. One possible trigger is 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: customer-specific 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

Complete migration by readiness gate: compliant seller setup, tested billing, supported credential or re-authorisation path, customer notice, dispute ownership and rollback criteria. Use actual costs and coverage rather than universal calendar or revenue thresholds.