starter.wiki中文

Payments

Merchant of Record

Choose whether and where to delegate the seller-of-record role for covered software and digital-product transactions.

Recommendation

Choose by contractual seller boundary and eligibility.

The four candidates differ in supported products, seller countries, checkout, billing, tax operations, payouts, policies, contracts, data, and migration.12

For: Software sellers evaluating a Merchant of Record

Main trade-off

A Merchant of Record can assume covered seller operations while adding product approval, contract, payout, checkout, data, reserve, termination, and migration dependence.1234

Why there is no single default: No provider can be a default without the exact product, owners, seller country, customer markets, contract, commercial terms, and migration requirements.

Decision criteria

Verify the executed operating boundary rather than relying on the Merchant-of-Record label.

  1. Eligibility and seller scope

    Verify product, owners, seller country, buyer markets, prohibited use, approval, and the transactions covered.12

  2. Covered operations

    Map payments, tax, refunds, disputes, buyer support, invoices, chargebacks, reserves, and reporting.12

  3. Payout and economics

    Model price, optional fees, FX, payout countries, timing, deductions, holds, reserves, refunds, and disputes.12

  4. Data and exit

    Verify customer, subscription, invoice, tax, payment, event, export, termination, and migration rights.12

Merchant-of-Record routes

All candidates require current policy and contract verification.

A software-commerce platform boundary fits

Evaluate Paddle.

Paddle combines seller role with subscription, checkout, tax, and buyer operations.

Verify: Validate eligibility, agreement, commercial schedule, payout, data, support, and migration.1

A digital-product store model fits

Evaluate Lemon Squeezy.

Its store and Merchant-of-Record model can fit eligible digital products and small teams.

Verify: Verify prohibited products, store review, fees, payout, support, data, and exit.2

A newer software-focused route is acceptable

Evaluate Creem.

Creem provides a software and digital-product Merchant-of-Record route.

Verify: Operating history, eligibility, geography, reserves, terms, payout, and migration require close review.3

An established sales-led contract fits

Evaluate FastSpring.

FastSpring provides a contract-led store and Merchant-of-Record route.

Verify: Activation, product approval, quote, contract, tax coverage, payout, data, and migration must be verified.4

Official resources

Verify current product scope, eligibility, pricing, policy, data, payout, and contractual boundaries in first-party material before implementation.

DocumentationHow Paddle works
DocumentationCreem introduction

Starter stacks

Sources

Official product and policy sources supporting the bounded routes on this page.

  1. 1
    How Paddle works

    Paddle · Accessed Official

  2. 2
    Lemon Squeezy payments and Merchant of Record

    Lemon Squeezy · Accessed Official

  3. 3
    Creem introduction

    Creem · Accessed Official

  4. 4
    FastSpring store activation

    FastSpring · Accessed Official