Why: the goal or problem
Imagine a music-practice app sold in several countries. Buyers need receipts and help, but its small team cannot handle every market’s sales duties.
How: work toward a solution
For a fictional music practice license, the customer pays the MoR, which settles agreed proceeds to the business. The MoR owns the illustrated receipt, refund and transaction-tax workflows. The business still delivers the product and agreed product support. Amounts, exclusions and country-specific tax rules are outside this diagram.
Music practice license · illustrative example
Merchant of record model
Music practice license · assumed contract
Customer ↔ Contracted MoR
Customer → MoR → agreed settlement → Business
| Task | Owner |
|---|---|
| Receipt identity | Contracted MoR |
| Refund / transaction-tax workflow | Contracted MoR |
| Product and product support | Product business |
Covered duties follow the agreement. No country-specific tax rules or universal coverage claim.
The learner buys the practice license from the merchant of record, which later settles with the app business. The diagram assigns receipts, refunds and transaction-tax duties to that seller. The app business continues product delivery and support.
What: the concept
Merchant of record model — An outsourced merchant of record acts as seller for covered transactions. Its responsibilities follow the agreement; product creation and every business obligation do not automatically transfer.
Combine with subscriptions while checking retained duties.
Discuss this idea
Comments are shared across languages. GitHub login required to post.