When the Merchant of Record Fails: Counterparty Risk Nobody Prices In

What actually happened when Digital River and MyCommerce suspended payouts in 2025?

Digital River Marketing Solutions Inc. filed for Chapter 7 bankruptcy on 1 May 2025 in the U.S. Bankruptcy Court for the District of Delaware, per Law360's court reporting, listing around $45.2 million in secured debt against less than $50,000 in assets. That filing was the terminal event, not the start — merchant payouts through the MyCommerce platform reportedly stopped moving from around July 2024, roughly ten months earlier.

The collapse spread across the corporate structure. Insolvency proceedings opened for Digital River's German subsidiaries, the Minnetonka, Minnesota headquarters closed by the end of March 2025, and around 122 U.S. employees lost their jobs in the wind-down, according to aggregated reporting from FinTech Futures, Star Tribune, Law360 and Compaytence.

Kaspersky filed suit in Hennepin County alleging roughly $18 million in remittances it says it was never paid, one visible claim among an unknown number that were never litigated. Before pricing that kind of risk, it helps to be clear on what a merchant of record actually is and does, since the failure mode only makes sense once the underlying structure is understood.

Who owns the funds an MOR is holding when the MOR becomes insolvent?

In almost every MOR structure, you don't own the funds sitting in the payout queue — you hold a contractual claim against the MOR entity, and in bankruptcy that claim is usually unsecured. Paddle's reseller agreement appoints Paddle as reseller of the product across all territories and gives Paddle, as merchant of record, the right to set price; FastSpring's own documentation describes the same purchase-and-resell mechanic, stating FastSpring "purchases products and services from you...and resells them to the end customer." Once the MOR buys from you, what it owes you is a payable, not a trust.

That distinction is why Digital River's case matters beyond one company's mismanagement. Secured creditors stand ahead of merchants in a Chapter 7 waterfall, and $45.2 million in secured debt against under $50,000 in assets left effectively nothing for unsecured claims once secured parties were paid first. A merchant owed a payout at filing time sat in the same queue as any other unpaid trade creditor.

Paddle's language on collecting sales tax, ensuring PCI compliance, and honoring refunds and chargebacks describes real liability transfer for card-network purposes, but liability transfer and financial solvency are separate guarantees — only one of them survived Digital River's bankruptcy. Weighing that trade-off against running your own merchant account instead of a reseller is worth doing before a payout freeze, not after one.

Do I own my customer list and subscription tokens, or does the MOR?

Generally the MOR does, because the MOR is the legal seller of record on the transaction, not you. Paddle's materials note that the MoR's name appears on the customer's card statement and that Paddle reserves the right to set the price; FastSpring states its own Terms and Conditions, not the publisher's, govern the transaction; Polar's documentation says it "resells your digital goods and services on your behalf." The card token, the billing relationship, and often the support history sit inside the MOR's systems by design.

Practically, this means the vaulted card credential your rebill logic depends on typically lives in the MOR's PCI environment, not in one you control. That's fine while the MOR is solvent and your contract lets you export data on demand. It stops being fine the moment the relationship ends badly, whether through insolvency or a termination-for-convenience clause, because export rights and export capability are not the same thing.

Physical-goods sellers face a narrower field to begin with. Paddle explicitly bars physical products requiring delivery, Polar's Acceptable Use Policy lists physical products and human services as prohibited, and FastSpring's marketing never mentions shipped goods, so the platforms that will even take a nutraceutical offer are a different set from the digital-only MORs — a distinction worth checking against which MOR platforms actually accept physical supplements before assuming token portability either way.

Can rebills be migrated to a new processor without re-collecting card data?

Usually not cleanly, and this is where operator assumptions run ahead of the plumbing. Card tokens are typically bound to the vault and gateway that created them, so a token minted inside an MOR's PCI environment does not travel intact to a different processor's vault — the receiving processor has to re-tokenize through a network token service or fall back to asking the cardholder to re-enter their card.

The mechanics make the gap expensive. Recurly's payments research puts overall decline rates at 6.0% on credit cards, 13.0% on debit cards, and 7.0% on alternative methods, and the same data shows debit cards declining at 14.4% on initial transactions versus 13.1% on recurring — first charges are structurally harder to approve than established ones, which is exactly what a forced re-collection produces. Visa also caps reattempts on a declined card at 15 within a rolling 30 days for the same amount and currency, so a rushed bulk migration burns through retry headroom fast.

Off-session recurring charges compound the problem. Stripe's own documentation states that merchant-initiated off-session transactions — the entire rebill leg of a continuity offer — do not support 3-D Secure authentication, so the liability shift 3DS offers on new sales never applies to migrated rebills, and any fraud dispute on those charges stays with the merchant regardless of which processor is running them.

What contract terms govern payout freezes, holdbacks, and termination?

The clause that matters most is rarely the headline fee — it's who absorbs a chargeback economically once the MOR has already made the cardholder whole. Paddle's terms are explicit: where Paddle prevents a chargeback or refunds a buyer, Paddle is entitled to receive from the vendor the full amount of the refund or chargeback plus any fees and expenses incurred. The MOR is the party of record with the card network; the vendor still pays.

Reserve and dispute-fee structures vary by platform, and the differences compound at volume:

How do I run an MOR concentration risk check before I route all volume through one?

Treat it as a counterparty audit, not a sales call. Ask for months of payout history retained on file, the contractual notice period for termination without cause, and whether the entity has ever missed or delayed a scheduled payout — a question most MORs won't answer voluntarily, so silence itself is data.

• Request confirmation of the parent entity's jurisdiction and corporate structure, since subsidiary insolvency — as with Digital River's German entities — can precede a parent filing by months
• Confirm the contract's termination-for-convenience notice period and what happens to held funds during that window
• Check whether the platform accepts your product category at all before modeling risk further; a digital-only MOR like Paddle, FastSpring, or Polar will not take a shipped nutraceutical offer
• Track public signals: leadership departures, office closures, unpaid-vendor litigation, and payout delays reported by other merchants in the same niche
• Cap the share of monthly volume any single MOR carries, and treat a [high-risk merchant account underwritten directly in your name](/compliance/high-risk-merchant-accounts-for-supplements-who-actually-approves-you) as one leg of diversification rather than a full replacement

What does a realistic failover plan look like for a continuity offer?

A realistic plan assumes the primary processor becomes unreachable with no notice, because that is what Digital River merchants experienced. It does not assume you can export a token file and resume billing the next day.

• Maintain a second, fully underwritten and disclosed MID or MOR relationship before you need it; undisclosed routing of one entity's sales through another's merchant ID is transaction laundering, not load balancing, and carries card-network penalties plus potential exposure under wire and bank fraud statutes
• Enroll in an account updater service on any processor you control directly, since vendor-reported estimates put roughly 30% of cards reissued annually and updater coverage is what keeps a recurring book alive independent of any one MOR's stability, though that figure needs checking against a network-published source
• Budget for a re-collection campaign as the realistic outcome for a meaningful share of a migrated cohort, not an edge case
• Hold 60-90 days of operating cash independent of pending MOR payouts, sized to the gap Digital River merchants actually experienced between slowdown and filing
• Rehearse the cutover on a small cohort on a schedule, not for the first time during an actual freeze

Which warning signs preceded past MOR collapses?

Payouts slow or go silent well before any formal filing. In Digital River's case, merchant reporting places the payout stoppage around July 2024, roughly ten months ahead of the May 2025 Chapter 7 filing, and that lag is the window in which a concentration-risk check is still useful — after the filing, it's a bankruptcy claim.

None of these signs is proof by itself, and a platform can recover from one or two of them. The pattern worth acting on is stacking: a payout delay plus a leadership departure plus unresolved merchant complaints in the same quarter is the combination Digital River's merchants saw in hindsight and mostly did not act on in real time.

• Subsidiary-level insolvency proceedings, like Digital River's German entities, opening before the parent files
• Office closures and layoffs at the operating headquarters, which preceded Digital River's Minnetonka closure by weeks
• Large creditor litigation becoming public, as with Kaspersky's Hennepin County suit over roughly $18 million in disputed remittances
• Support and account-management responsiveness degrading — often the first thing merchants notice and the last thing they act on

Quick decision checklist

Use this page as a decision aid, not a generic blog post. The practical question is whether the reader needs faster evidence about what is already working in VSL-driven direct response, especially across nutra, supplements, GLP-1, weight loss, blood sugar, and adjacent high-intent health markets.

Daily Intel Service is most relevant when the next decision depends on active market examples: which hook to test, which claim style is risky, which funnel structure is common, which language market is moving, and whether a competitor's creative is likely early, scaling, or already saturated.

• Start with the TL;DR if you need the direct answer.
• Use the table to compare trade-offs quickly.
• Use the FAQ for answer-engine-ready summaries.
• Use the CTA when the decision requires live VSL and ad examples instead of theory.

Daily Intel's coverage advantage

Daily Intel Service is positioned around category-leading variety and actionability: one of the broadest direct-response catalogs of VSLs and ad creatives across blackhat, greyhat, and whitehat advertising patterns, with enough context to understand what the advertiser is doing beyond the visible creative. The practical difference is that members are not just seeing a screenshot; they are seeing the VSL, the ad, the funnel path, the transcript, the UTM context, and the research notes that turn the asset into a decision.

This matters because direct-response affiliates do not operate in one clean category. A weight-loss campaign may use a whitehat compliance ad, a greyhat pre-lander, a more aggressive VSL, and a checkout path designed around upsells and recovery. A useful intelligence platform needs to capture that spectrum instead of pretending every winning campaign looks like a public brand ad.

Blackhat, whitehat, and multilingual signal coverage

Daily Intel tracks patterns across both blackhat-style and whitehat-style campaigns so operators can understand the market without blindly copying risk. Whitehat examples help with durability and compliance review; blackhat and greyhat examples reveal pressure points, hooks, mechanisms, and funnel structures that may be driving spend but require careful adaptation before use.

The catalog is also built for global operators, with VSL and ad references spanning 14+ languages and different local idioms. That is a key advantage for Brazilian, LATAM, European, MENA, Indian, and non-native English affiliates who need to see how the same market desire is translated across cultures instead of only studying US English ads.

How to use the intelligence responsibly

The goal is modeling, not copying. Use Daily Intel to understand structure: hook, mechanism, proof, claim intensity, funnel depth, offer economics, and saturation stage. Then build original creative, review claims, and adapt the angle to the traffic source, country, language, and compliance requirements of the campaign.

A strong workflow compares multiple examples before acting. If the same mechanism appears across several languages, several advertisers, and several funnel variants, it may be a durable market signal. If the example appears only once or depends on an aggressive claim, treat it as a research clue rather than a campaign template.

• Model structure, not protected creative assets.
• Separate whitehat durability from blackhat persuasion pressure.
• Compare US English examples against LATAM, European, and other language variants.
• Use transcripts and funnel notes to build original briefs.
• Keep compliance review separate from market research.

Methodology and source context

Daily Intel pages are written from a research workflow that reviews active VSLs, Meta ad creatives, transcripts, UTMs, funnel paths, checkout steps, upsells, recovery sequences, and compliance-sensitive claim patterns. The goal is to explain observable market behavior, not to provide legal, medical, or platform policy advice.

When the topic touches health claims, platform policy, or GLP-1 market research, validate the observable campaign signals against primary references such as Meta advertising standards, FTC health claims guidance, and Google helpful content guidance. Daily Intel adds the proprietary direct-response layer by mapping how those rules show up in active VSLs, Meta creatives, funnels, transcripts, UTMs, and checkout paths.

For deeper evaluation, continue through Daily Intel compliance and legal disclaimer, Is Copying a Competitor's Landing Page Legal? The Line, Black Hat Affiliate Methods: A Field Guide to What Is Actually Running, Is Black Hat Worth It? The Numbers Nobody Puts in the Pitch, Getting an Ad Account Back: What Works, What Wastes Your Week, and What is a VSL?. These related Daily Intel pages connect this topic to the relevant methodology, pricing, trust context, comparison path, or niche workflow.