Coder Legion - Recent posts tagged records

15+ Merchant of Record Examples by Business Type (Plus What the Digital River Shutdown Teaches Us)

Mon, 21 Sep 2026 13:28:49 +0000

A flat list of "top merchant of record companies" isn't actually that useful, because the right example depends entirely on what you're selling. An indie developer selling a $19 app has almost nothing in common, requirement-wise, with an enterprise software company negotiating custom procurement terms — and a list that treats them as comparable choices tends to obscure more than it clarifies.

This piece organizes real merchant of record examples by the business type they actually serve, from self-serve SaaS to creators and indie sellers to niche verticals like gaming, before covering enterprise-scale providers and a genuinely important cautionary example: Digital River, once one of the most established names in this space, wound down its entire ecommerce and MoR services, business in January 2025 — a real-world lesson in vendor risk worth understanding regardless of which provider you're actually considering.

Merchant of Record Examples for SaaS and Digital Products

For self-serve and mid-market SaaS specifically, a handful of providers show up consistently as the best merchant of record for SaaS use cases.

Paddle is frequently the first name mentioned for scaling self-serve B2C SaaS without complex software licensing needs, offering merchant-of-record coverage across roughly 300 markets with recurring billing and analytics (via its ProfitWell integration) built directly in. Its typical pricing runs around 5% plus $0.50 per transaction, covering payment processing, global sales tax and VAT remittance, subscription billing, and fraud handling — though it's worth noting Paddle doesn't cover physical products, fulfillment, or customs at all, staying strictly within digital goods.

FastSpring serves a similar core audience but differentiates on breadth — better suited to diverse product catalogs spanning both software and other digital assets, or businesses running a more traditional hosted storefront with multi-SKU management. Pricing typically runs slightly higher, around 5.9% plus $0.95 per transaction, varying by plan, with a long operating history specifically in B2B SaaS.

Cleverbridge targets a distinctly different stage: negotiated contracts, reseller channel support, formal procurement processes, and dedicated account support — a fit for enterprise software complexity and quote-based deals rather than a fast, self-serve signup flow.

PayPro Global positions itself as a full-service MoR and payment infrastructure partner specifically for software, SaaS, and digital products, emphasizing global payment method coverage, flexible subscription support, and multilingual billing with a more hands-on, guided onboarding posture than some faster self-serve competitors — its pricing is generally quote-based rather than published as a fixed rate.

Examples for Creators, Indie Sellers, and Niche Verticals

Below the SaaS-focused providers, a distinct set of examples serves smaller sellers and specific verticals with genuinely different needs.

Lemon Squeezy is commonly recommended specifically for indie developers, small SaaS operations, and digital downloads — typically priced around 5% plus $0.50 per transaction, with Stripe-style integration, subscription support, and built-in sales tax handling, but explicitly not covering physical fulfillment. Its appeal for creators and small sellers rests heavily on having no monthly platform fee and a genuinely fast setup process.

Gumroad has operated as a full merchant of record on every transaction since January 2025, automatically calculating, collecting, and remitting sales tax, VAT, and GST worldwide for creators selling digital products, courses, and similar goods — appealing specifically to solo sellers who want global tax compliance handled without any separate setup process.

Freemius is worth specific mention for software businesses with licensing requirements — activation controls, seat management, subscription-aware license revocation — that broader platforms like Paddle and FastSpring generally don't build for, making it a more specialized example for a specific software distribution model rather than a general-purpose choice.

Xsolla stands out as the clear example for merchant of record for gaming specifically — purpose-built for game studios and in-game commerce, a vertical with distinct requirements (virtual goods, in-game currency, console platform compliance) that general-purpose MoR platforms aren't specifically optimized to handle.

Common Questions About Choosing Among These Examples

Why do so many "best MoR" lists mention Digital River, when it's no longer operating? Digital River wound down its ecommerce and merchant-of-record business entirely in January 2025, suspending services to the large majority of its global customers, closing its Minnesota headquarters, and seeing several international subsidiaries enter insolvency or liquidation proceedings. Older content and outdated comparison lists sometimes still reference it out of habit — but it's no longer an operating option, and any current list still recommending it as a live choice is stale.

What does the Digital River shutdown actually teach a business evaluating MoR providers today? It's a concrete reminder that MoR vendor selection carries real business continuity risk, not just a feature and pricing comparison. Businesses that relied on Digital River had to migrate to another provider under real time pressure, which is meaningfully harder than a planned, voluntary switch — a reasonable takeaway is to weigh a provider's financial stability and market position alongside its feature set, not just its published pricing.

Are creator-focused examples like Lemon Squeezy or Gumroad "lesser" versions of SaaS-focused providers like Paddle? Not really — they're optimized for a different scale and complexity level rather than being a downgraded version of the same thing. A solo creator selling a single digital product generally doesn't need Paddle's or FastSpring's more complex subscription and enterprise billing tooling, and a platform built around fast, simple setup with no monthly fee is often the better fit at that scale, not a compromise.

Is a gaming-specific example like Xsolla ever the wrong choice, even for a gaming company? It depends on the specific business model within gaming — a studio selling primarily through console platform stores with their own built-in payment and compliance systems has different needs than one selling directly to consumers via its own website or launcher. Xsolla's specific strength is direct-to-consumer and in-game commerce; it's worth confirming that matches your actual distribution model before assuming any gaming company automatically needs a gaming-specific MoR.

Can I switch between these examples later if my business outgrows my first choice? Yes, businesses do this regularly — the wave of migrations following Digital River's exit demonstrated that switching is possible, even under pressure — but it's genuinely more work than choosing well the first time, since subscription data, tax history, and customer billing relationships all need to transfer. Starting with a provider that fits your current stage while having a credible path to your next stage (several providers, like Paddle and FastSpring, serve a fairly wide range of SaaS scale) reduces how often you'll need to go through a full migration.

Enterprise and Broad-Reach Examples — And a Cautionary Tale

2Checkout (now operating under the Verifone brand) has been operating in digital commerce since 2006, and that longevity shows up directly in its coverage: support for over 45 payment methods, more than 100 currencies, and reach across 200+ countries — breadth that newer entrants generally haven't fully replicated yet. It's commonly recommended specifically when payment method coverage and global reach are the primary decision driver, with strong subscription billing, dunning management, and an affiliate system built in — though its cost structure tends to be a point of concern at scale compared to some newer competitors.

Digital River deserves its own mention specifically as a cautionary example, not a current option. For years, Digital River was one of the most established names in the merchant-of-record space, but it wound down its ecommerce and MoR business entirely in January 2025 — suspending services to most global customers, with several subsidiaries entering insolvency proceedings. Businesses that had built their billing infrastructure around Digital River had to migrate under real time pressure, to alternatives like Dodo Payments, Paddle, FastSpring, Cleverbridge, PayPro Global, or 2Checkout, depending on their specific needs. The lesson generalizes well beyond Digital River specifically: an MoR relationship is a genuinely deep infrastructure dependency, and vendor stability deserves real weight in the decision, not just feature comparison.

Gapp Group is mentioned in current industry coverage specifically as one of the enterprise-focused options that absorbed businesses migrating away from Digital River — illustrating how the competitive landscape actively shifted in response to a major provider's exit, with several established and newer players positioning themselves to catch that specific wave of enterprise migrations.

How These Examples Actually Differ in Practice

Pulling these examples together, a few practical distinctions matter more than any single feature comparison:

Scope of coverage. Nearly all of these examples are strictly digital-goods focused — Paddle, FastSpring, Lemon Squeezy, and similar platforms explicitly exclude physical fulfillment, customs, and shipping entirely, which matters immediately if your business sells anything physical alongside digital products.

Onboarding speed vs. procurement fit. Self-serve-oriented examples (Paddle, Lemon Squeezy, Dodo Payments) prioritize fast signup and integration; enterprise-oriented examples (Cleverbridge, PayPro Global, 2Checkout at scale) prioritize negotiated terms and dedicated support, generally at the cost of a longer, heavier onboarding process.

Pricing transparency. Some providers, notably Dodo Payments and Paddle, publish clear baseline pricing publicly; many enterprise-oriented vendors use custom, quote-based pricing models instead — worth factoring into how easily you can comparison-shop early in your evaluation versus needing to go through a sales process for real numbers.

Vertical specialization vs. general purpose. Most examples in Sections 1 and 4 are general-purpose across digital products and SaaS; a smaller number, like Xsolla for gaming and Freemius for licensed software, specialize deeply in one vertical's specific requirements — worth checking if your business fits one of these narrower categories before defaulting to a general-purpose provider.

Vendor stability, post-Digital River. Given the real disruption Digital River's exit caused for its customers, it's reasonable to weight a provider's financial position and market trajectory as a genuine evaluation criterion now, alongside the more standard comparison points of pricing, coverage, and feature set.

Conclusion

The most useful way to think about merchant of record examples isn't as a single ranked list, but as a set of options matched to specific business types: Paddle and FastSpring for self-serve to mid-market SaaS, Cleverbridge and PayPro Global for enterprise procurement needs, Lemon Squeezy and Gumroad for creators and indie sellers, Xsolla for gaming specifically, and 2Checkout/Verifone for the broadest global payment method reach. Digital River's 2025 exit from the MoR business is worth remembering as a genuine, recent example of vendor risk in this space — a reminder to weigh provider stability alongside features and price.

Ready to shortlist your own examples? Match your business type against the categories above first — SaaS, creator/indie, vertical-specific, or enterprise — then pull two or three finalists within that category and compare their published (or quoted) pricing and coverage directly, rather than starting from a single flat "best of" list that doesn't account for how differently these examples are actually built to serve different businesses.

Why Records in C# Are Great (and So Nice to Work With)

Sat, 10 May 2025 20:37:38 +0000

Why Records in C# Are Great

If you’ve been working with C# lately, you’ve probably encountered records , a feature introduced in C# 9 that many developers have come to love.

They’re elegant, powerful, and remove a lot of boilerplate when modeling data.

But what actually makes them great? Here’s why records aren’t just nice , they’re game-changing.

What Are Records?

At their core, records are reference types designed for immutable data modeling. Think of them as classes optimized for holding data with extra features built in.

You can define a record in two main ways:

✅ 1. Positional Syntax (Concise and Clean)

public record Person(string FirstName, string LastName);

This one-liner gives you:

Constructor
Equals(), GetHashCode(), and ToString() overrides
init-only properties (immutable)
Deconstruction support

Ouaaa...

In order to implement all that in a regular class, you'd need to write a lot of code constructors, equality logic, ToString() overrides, and possibly even a deconstructor.
Records do it all for you, automatically and cleanly.

✅ 2. Classic Syntax (More Flexible)

public record Person
{
    public string FirstName { get; init; }
    public string LastName { get; init; }
}

Need mutability? You can use set instead of init, but that sacrifices immutability and thread safety.

What is init?

init is a special accessor introduced in C# 9 that allows properties to be set only during initialization making them immutable afterward.

var person = new Person { FirstName = "Alice", LastName = "Green" };
// person.FirstName = "Bob"; ❌ Not allowed

✅ Cleaner than readonly fields
✅ Safer than public setters
✅ Perfect for records, DTOs, and configuration objects

Reference:
Microsoft Docs – Init-only Setters

✅ 1. Value-Based Equality — Finally Done Right

With classes, equality checks compare references. With records, it's based on content:

var a = new Person("Alice", "Smith");
var b = new Person("Alice", "Smith");

Console.WriteLine(a == b); // True ✅

Reference:
Microsoft Docs – Records

✅ 2. Immutability by Default — and Thread-Safe by Nature

Records are immutable by default, which leads to safer, more predictable code.

var p1 = new Person("John", "Doe");
var p2 = p1 with { FirstName = "Jane" }; // Creates a copy

And since their state can't be changed after creation, records are thread-safe for read operations — perfect for:

Parallel tasks
Background services
Blazor state containers
Event sourcing

Reference:
Immutability in C#

✅ 3. Concise and Readable Code
Records eliminate boilerplate. You define what matters — and the compiler handles the rest.

public record Invoice(string Id, DateTime Date, decimal Amount);

Clean. Lightweight. Clear.

✅ 4. Deconstruction and Pattern Matching

Records play perfectly with modern C# features:

var (first, last) = new Person("Ana", "Lopez");

if (p1 is { FirstName: "John" })
{
    Console.WriteLine("Hello John!");
}

Reference:

Pattern Matching in C#

✅ 5. Functional Programming Friendly

Records align with functional principles:

No side effects
Easy transformations
Clear data flow

var updatedInvoice = invoice with { Amount = invoice.Amount + 10 };

Reference:

Welcome to C# 9 – Records

✅ 6. Supports Inheritance, Structs, and More

You’re not locked into one pattern:

record struct — value-type records
readonly record struct — fully immutable
Abstract and sealed record inheritance supported

Reference:
What's New in C# 10 – Record Structs

Records and the Value Object Pattern
In Domain-Driven Design (DDD), Value Objects are small objects that:

Represent a concept (e.g., Money, Email)

Are immutable
Have no identity
Compare by value

✅ Records Are Ideal for Value Objects

public record Email(string Address)
{
    public Email
    {
        if (!Address.Contains("@"))
            throw new ArgumentException("Invalid email");
    }
}

You get a clean, reusable object with built-in validation and equality , no fuss.

public record Money(decimal Amount, string Currency);

public record Product
{
    public Guid Id { get; init; }
    public string Name { get; init; }
    public Money Price { get; init; }
}

Reference:
Martin Fowler – Value Object

When Not to Use Records

Avoid records if: