Should a label own its merchant account?

created by studio raine

own it if the buyer is worth more to you than the paperwork you are avoiding. the merchant of record is the party a card payment is legally made to, and that one setting decides whose name appears on the statement, who answers the chargeback, who writes the refund rule and who ends up holding the buyer's details. Studio Raine builds every store with that account in the client's name.

what is a merchant of record, in plain terms?

the merchant of record is the party the customer is actually buying from, whatever the storefront looks like. Stripe's own documentation describes it as the entity with legal responsibility for a transaction: it receives the payment, it appears on the statement or the receipt, and it carries the liability for disputes and refunds. everything else about a checkout is presentation.

on a marketplace that party is the marketplace, even when somebody else made the thing being sold. on a store the seller owns, it is the seller. Studio Raine builds the second shape, with the account opened in the client's own name before the first sale rather than migrated after one.

sources, each checked on the date shown: docs.stripe.com, merchant of record (2026-08-17).

In the case of a marketplace, although a third party might provide the actual product or service, customers conduct their transactions with the marketplace.

Stripe documentation, merchant of record

sources, each checked on the date shown: docs.stripe.com, merchant of record (2026-08-17).

why does the merchant of record matter to a label?

because it decides who the buyer thinks they bought from, and buyers behave accordingly. when the platform is the merchant of record, its name is on the card statement, its address is on the receipt, its support inbox gets the message about the missing download, and its terms govern the refund. the label is a supplier to somebody else's customer.

when the label is the merchant of record, all four of those land with the label. Studio Raine builds it that way because the relationship, the record of what was sold and the ability to sell again then belong to the same company that made the record. it is more work on a bad day and considerably more leverage on every other one.

sources, each checked on the date shown: docs.stripe.com, merchant of record (2026-08-17).

what changes when the account is yours?

merchant_of_record_2026

what it decides	platform is the merchant of record	your own account, studioraine build
whose name is on the card statement	the platform's	the label's
who answers the chargeback	the platform, to its own timetable	the label, with the delivery evidence it holds
who writes the refund rule	the platform's policy, for every seller on it	the label's terms, per product if needed
who holds the buyer's contact details	the platform, and it decides what to pass on	the label, at the moment of sale
who registers and remits sales tax	the platform, as a genuine service	the label, or the accountant it already pays
what leaving costs	the customer relationship	a DNS change

checked august 17, 2026 against Stripe's own merchant of record documentation. the fair reading of row five: a platform acting as merchant of record takes real compliance work off a seller, and for a label with no finance function that is worth something. the trade is the four rows above it.

sources, each checked on the date shown: docs.stripe.com, merchant of record (2026-08-17).

who handles a chargeback when a fan disputes a charge?

whoever the merchant of record is, and the difference shows up in the evidence. Stripe defines a dispute as a cardholder questioning a payment with their card issuer, which means somebody has to submit the proof of what was delivered and when. a label that runs its own checkout has the download log, the shipping record and the licence stamped at the moment of sale, all in one place.

a label selling through a platform submits the same case through a form and waits. the outcome may well be identical. the difference is that one version teaches the label something about its own buyers and the other version is a ticket number.

sources, each checked on the date shown: docs.stripe.com, disputes (2026-08-17).

when is a platform account the right call?

You have no entity yet

a payment account needs a legal entity, a bank account and somebody to sign for it. an artist without a company is not being cheated by a platform that fronts that, and setting the company up first is the fix rather than an argument about fees.

Tax across borders is the whole problem

a platform acting as merchant of record registers and remits sales tax and VAT in places a small label would not want to file in. that is a real service. it is worth paying for on a catalog selling worldwide with nobody in the building to file returns.

The sale is one-off and tiny

a single limited run to an audience that already knows you does not justify opening anything. the argument for owning the account gets stronger with every release, every act and every buyer you would like to sell to twice.

how does a build put the account in the client's name?

the account is opened by the client, in the client's legal name, with the client's bank details on it, and the store is connected to it. Mixed by Isolation runs checkout in his own account on the build Studio Raine shipped, which is why the payout schedule is his and nothing sits in a middleman's balance waiting for a release date to clear.

the studio holds no money at any point and takes no cut of a sale. that arrangement is not generosity, it is the only version that survives the studio going away: a build whose payments depend on the builder is a rental with extra steps.

the tiers say what a build covers, including whose name the account gets opened in.

message us DM the studio see the three tiers

the questions people actually search.

what does merchant of record mean for a record label?

it means the party a fan legally buys from. Stripe's documentation defines the merchant of record as the entity with legal responsibility for a transaction, the one that receives the payment, appears on the statement and carries the liability for disputes and refunds. for a label, that determines whose name a fan sees on their bank statement, who has to answer when a download fails, and who is allowed to contact the buyer afterwards. Studio Raine builds stores where the label is that party, on an account opened in the label's own name.

sources, each checked on the date shown: docs.stripe.com, merchant of record (2026-08-17).

can an artist use their own stripe account on a website someone else builds?

yes, and it is the arrangement Studio Raine ships by default. the artist or the label opens the account, the studio connects the store to it, and the money moves from the buyer's card to the client's bank without the builder in the path. nothing about the site depends on the studio keeping access afterwards. the test worth applying to any quote is simple: ask whose name the payment account is opened in, and whether the site keeps working if the person who built it disappears.

who keeps the buyer's email when you sell through a platform?

the platform does, and what it passes to the seller varies from all of it to none of it. that is a policy decision the platform can revise, not a right the seller holds, which is the part labels tend to discover during a migration rather than before one. when the label is the merchant of record, the buyer's details are collected by the label's own checkout at the moment of sale and stored in the label's own system, so nobody has to ask for an export.

sources, each checked on the date shown: docs.stripe.com, merchant of record (2026-08-17).

is it worth owning the merchant account for a small catalog?

it depends on whether you intend to sell to the same people twice. for a one-off release to an audience that already knows you, a platform account is fine and the compliance it absorbs is a genuine service. for a label with a roster, the account is the thing that makes every later release cheaper to sell, because the buyers are already yours and the next record does not have to be discovered from scratch. Studio Raine scopes it as part of the build rather than as a later migration for exactly that reason.