Marketplace Payment Licensing

Marketplace Payment Licensing: When Platforms Need Regulatory Authorization

Marketplace payments create a regulatory question that ordinary ecommerce often does not: whose money is the platform receiving?

A traditional merchant generally accepts payment for goods or services that it sells itself. A marketplace brings together buyers and independent sellers, creators, contractors, hosts, service providers or other third parties. Once the platform also starts receiving customer money, deciding how much belongs to each seller, holding funds until a condition is met or instructing payouts, its role can move beyond simply operating a marketplace.

That does not mean every marketplace needs its own payment licence.

The answer depends on the jurisdiction and, more importantly, on the actual payment architecture: who receives the customer payment, who legally controls it, who owes the seller, whether the marketplace ever holds third-party funds and which entity performs the regulated payment service.

UK regulator guidance illustrates the issue directly. The Financial Conduct Authority says an online marketplace or business bringing buyers and sellers together may be providing payment services if it receives customer money before passing it to a seller, including where the money enters a bank, e-money or merchant-acquirer account in the platform's name.

In the United States, the federal money-transmitter definition focuses on accepting funds or other value from one person and transmitting them to another person or location, while expressly making the determination dependent on the facts and circumstances. State money-transmitter licensing has to be analysed separately.

For marketplaces, the most useful question is therefore not:

"Are marketplaces regulated?"

It is:

"What role does our marketplace perform between the buyer paying and the seller receiving the money?"

That distinction can determine whether a platform can launch with a regulated marketplace-payment provider, needs a different payment structure or has to consider licensing of its own.

Why marketplace payments create licensing questions

The marketplace business model separates two relationships that are combined in a conventional retail transaction.

A traditional merchant sells a product to its customer and receives the purchase price. If a retailer sells a $100 pair of shoes, the $100 is fundamentally payment for the retailer's own sale.

A marketplace may instead facilitate a $100 transaction between an independent seller and a buyer. If the platform receives that $100, retains a $15 commission and sends $85 to the seller, the platform is handling money economically attributable to another party.

That distinction is why payment regulation can become part of marketplace architecture.

Regulators do not generally determine the result from labels such as platform, marketplace, escrow, seller balance or payout. They look at the regulated activity performed under the applicable law and the rights and responsibilities created by the contracts and flow of funds. FinCEN's U.S. rules, for example, state explicitly that money-transmitter status is a matter of facts and circumstances.

A marketplace can therefore operate sophisticated payment functionality without necessarily performing the regulated payment service itself. Conversely, a business that thinks of payments as a minor feature can create licensing exposure if the payment structure puts it in control of buyer funds destined for sellers.

Does a marketplace need a payment licence?

Not automatically.

A marketplace may be able to operate without obtaining its own payment licence where an appropriately regulated payment provider receives, holds, splits and settles customer funds and the marketplace itself does not perform the regulated service.

At the other end of the spectrum, a marketplace that directly receives customer money into an account it controls and later transfers amounts to independent sellers creates a much stronger licensing question.

Between those two models are numerous variations: payment facilitators, agent structures, segregated accounts, provider-controlled ledgers, escrow-like flows, delayed settlement arrangements and reseller or Merchant of Record structures.

The regulatory answer can change based on relatively small architectural differences.

For example, a marketplace may calculate that Seller A should receive $80 and Seller B $20. That calculation does not necessarily mean the marketplace itself holds or transfers either seller's money. A licensed provider could receive the original payment and execute the split according to instructions while keeping legal control of the regulated funds flow.

Alternatively, the marketplace might receive the full amount into its own account, hold it for seven days and then originate transfers to Seller A and Seller B. Economically the user experience may appear almost identical. Legally and operationally, the marketplace has assumed a substantially different role.

Follow the flow of funds

Marketplace payment licensing is easier to analyse when the transaction is drawn as a funds-flow diagram rather than described as a product feature.

The critical issue is not simply where payment data travels. It is where the money and legal control over the money travel.

A useful pre-launch analysis should answer:

•Who is legally selling to the buyer? Is the seller the marketplace, an independent merchant or another party?

•Who contracts with the buyer for the underlying transaction?

•Who is the payment recipient shown to the acquirer or payment provider?

•Into whose account does the customer payment first arrive?

•Can the marketplace withdraw, redirect or otherwise control those funds?

•Is money held between customer payment and seller settlement?

•Who calculates the marketplace commission and seller entitlement?

•Who technically and legally executes the split?

•Who instructs the seller payout?

•Can the marketplace delay settlement because of refunds, fraud, reserves or contractual disputes?

•Who is responsible for returning customer funds when a transaction is refunded?

•Are balances maintained for sellers rather than immediately settled?

•Does any seller value remain available for future transactions or transfers?

•Which regulated bank, acquirer, payment institution, e-money institution or money transmitter participates in the flow?

•In which countries or U.S. states are the marketplace, buyers, sellers and payment providers located?

No single answer establishes the licensing outcome everywhere.

Together, however, they reveal whether the platform is primarily instructing a regulated provider or performing the movement and control of third-party funds itself.

The ability to delay or redirect settlement deserves particular attention. It is evidence that the marketplace may have substantive control over funds, although it is not by itself a universal licensing test.

Marketplace payment models compared

Three structures illustrate how marketplace payment architecture can change the regulatory analysis.

Marketplace model

How funds typically move

Marketplace regulatory position

Principal trade-off

Licensed marketplace-payment provider

Regulated provider receives customer funds and handles seller settlement, often using provider-controlled accounts or ledgers

Can reduce the marketplace's direct payment-licensing exposure if the regulated services genuinely sit with the provider

Less direct control and more dependence on provider onboarding, operating rules and geographic coverage

Marketplace directly collects and pays sellers

Customer funds reach an account controlled by the marketplace before the marketplace sends money to sellers

Creates a substantially greater need to analyse payment-service or money-transmission licensing

Greater control over settlement, but potentially significant regulatory and compliance infrastructure

Merchant of Record / reseller

The MoR or reseller is positioned as the seller to the customer and separately compensates the underlying supplier

Can materially change the regulatory analysis because the commercial relationships and ownership of receivables differ

More commercial, tax, consumer, refund and contractual responsibilities shift to the MoR

These are operating-model categories, not guaranteed regulatory outcomes.

The contract, funds flow and jurisdiction still determine whether the structure works as intended.

U.S. money-transmission considerations

Marketplace payment licensing in the United States is especially important because federal Bank Secrecy Act requirements and state money-transmitter licensing operate as separate regulatory layers.

At the federal level, FinCEN's current regulation defines money-transmission services as accepting currency, funds or other value that substitutes for currency from one person and transmitting it to another location or person. The rule also says whether a person is a money transmitter depends on the facts and circumstances and contains defined limitations and exclusions.

For marketplaces, that creates an obvious question when a platform accepts buyer money and subsequently sends the seller's share to the seller.

But acceptance and onward movement of money should not automatically be equated with money transmission in every commercial transaction.

FinCEN has addressed payment-processing and transaction-settlement structures in several administrative rulings. In one ruling involving an independent sales organisation and payment processor, FinCEN found that the company's ISO activity was not money transmission because the company did not take possession or control of merchant funds. It also explained that a payment-processing exemption can depend on factors including the underlying purchase of goods or services, use of qualifying clearing and settlement systems and appropriate contractual relationships.

In a separate secured-transaction ruling involving buyers and sellers, FinCEN again emphasised the fact-specific nature of the analysis rather than treating every intermediary handling transaction funds as a money transmitter.

Those rulings should not be read as blanket marketplace exemptions.

A platform should determine whether its own facts satisfy the federal rule and any applicable limitation or exemption rather than assuming that being part of a purchase transaction is sufficient.

State licensing is a separate question

Even a federal FinCEN analysis does not answer whether state licensing is required.

FinCEN itself has stated that federal MSB registration and state licensing are independent questions and that whether a person must obtain a state licence must be determined under the relevant state's requirements.

State regulators license money transmitters through the Nationwide Multistate Licensing System, or NMLS. The Conference of State Bank Supervisors has developed the Money Transmission Modernization Act to harmonise substantial parts of state regulation, but adoption remains state based. As of its 2026 update, CSBS reported that 31 states had enacted the model framework in full or in part.

For a marketplace planning a nationwide U.S. launch, the practical implication is significant.

A conclusion that a platform is outside federal money-transmitter regulation does not automatically provide a nationwide state licensing answer. Likewise, registration with FinCEN does not substitute for licences required by individual states.

A marketplace considering direct collection and seller payouts should therefore resolve its U.S. money-transmission model before treating payments as a simple fifty-state rollout.

For a deeper examination of this layer, link to Money Transmitter Licensing.

European and UK payment-service considerations

European and UK regulation uses a payment-services framework rather than the U.S. state-by-state money-transmitter model, but the same fundamental marketplace question appears: is the platform itself providing a regulated payment service?

United Kingdom

The FCA is unusually explicit about marketplaces.

Its guidance states that an online marketplace, booking business or company bringing buyers and sellers together may be providing payment services where it receives customer money before passing that money to the seller. This includes circumstances in which the funds enter a bank, e-money or merchant-acquirer account held in the marketplace's name.

Depending on the structure, the activity could potentially involve services such as money remittance or operation of a payment account. The precise classification depends on the model.

The fact that a marketplace's main business is not payments does not necessarily resolve the question. FCA guidance also notes that payment services may be provided as part of a broader package of services.

This is why a marketplace should not rely on a statement such as payments are only ancillary to what we do without analysing whether the underlying activity falls within the Payment Services Regulations 2017.

The commercial-agent exclusion needs careful analysis

Marketplace operators sometimes look to the commercial-agent exclusion as a reason they should fall outside payment-services regulation.

In the UK, the exclusion covers certain transactions through a commercial agent authorised to negotiate or conclude the sale or purchase of goods or services on behalf of either the payer or the payee, but not both. The FCA's perimeter guidance specifically discusses how this can apply to platform businesses.

The key point is that calling the marketplace an "agent" is not enough.

The legal authority conferred on the platform, whose interests it represents and its role in the actual transaction matter.

European Union

PSD2 remains the operative EU payment-services framework as of August 2026. It establishes rules governing payment institutions and regulated payment services across the EU.

The European Banking Authority has considered the commercial-agent exclusion specifically in the ecommerce-platform context.

In one Q&A, the EBA concluded that a platform receiving payment on behalf of a seller is not automatically outside PSD2 simply because the customer's payment to the platform legally settles the customer's debt to the seller.

In another, the EBA explained that a B2C ecommerce platform may potentially rely on the commercial-agent exclusion where it is genuinely authorised to negotiate or conclude sales on behalf of the payee and does not also act on behalf of the payer. Whether the exclusion applies requires evaluation of the actual business model by the competent authority.

That is an important warning for marketplace design.

An exemption should be the conclusion of the legal analysis, not the starting assumption used to design the payment flow.

What about PSD3 and the new Payment Services Regulation?

The EU is in the process of replacing and updating substantial parts of the PSD2 framework through the proposed PSD3 and Payment Services Regulation.

Political agreement was reached between the European Parliament and Council in November 2025, and the European Parliament's ECON Committee approved the negotiated text in May 2026. However, current EU legislative tracking still describes the procedure as ongoing and states that formal adoption is required before the new framework can enter into force.

Marketplace operators planning future European payment architecture should therefore monitor the transition, but they should not treat the proposed PSD3/PSR framework as though it has already replaced current PSD2 requirements.

Holding seller money can create obligations beyond licensing

Licensing is only one part of the regulatory effect of controlling marketplace funds.

Where a regulated payment institution receives or holds funds for users, safeguarding requirements may apply.

In the UK, for example, payment and e-money institutions within the applicable safeguarding regime must protect relevant customer funds. The FCA's strengthened safeguarding rules took effect on May 7, 2026, and require covered institutions to maintain arrangements designed to protect client rights and prevent relevant funds from being used for the institution's own account.

For the marketplace, this matters even where the licensed provider—not the marketplace—is the regulated institution.

It affects questions such as where seller money is held, how balances appear, whether funds can be netted against marketplace receivables and what happens if the payment provider fails.

Payment-provider architecture therefore changes not only who needs the licence, but also whose regulated safeguarding infrastructure protects the funds.

Seller onboarding and KYC/KYB

Moving seller payments out of the marketplace's own regulated perimeter does not make seller onboarding disappear.

A licensed marketplace-payment provider may need information about the sellers for regulatory, financial-crime, underwriting and risk-management purposes.

That typically means the marketplace integration has to support some combination of identity and business verification commonly described as KYC—Know Your Customer—or KYB—Know Your Business.

The exact information required is not globally uniform.

A regulated provider may need to establish who the seller is, whether a business actually exists, who owns or controls it, what activity it conducts, where it operates and whether additional due diligence is warranted based on risk. Current FCA supervisory work on customer due diligence, for example, emphasises that regulated firms should tailor CDD and enhanced due-diligence procedures to customer risk and maintain evidence of those controls.

U.S. money services businesses that fall within FinCEN's regime are subject to anti-money-laundering programs and applicable transaction reporting and recordkeeping requirements.

Sanctions create another layer. U.S. persons are subject to OFAC sanctions requirements, and OFAC encourages financial institutions to use risk-based sanctions controls appropriate to their payment activities.

For marketplace operators, the operational lesson is more important than the terminology:

If a regulated provider needs to know the seller, the marketplace's seller-onboarding experience becomes part of the payment compliance architecture.

That can affect conversion and launch schedules.

A marketplace that waits until integration testing to discover that sellers need beneficial-owner information, identity documents, banking evidence or additional verification can find that the "payments integration" is actually an onboarding-product project.

The marketplace should also distinguish between the regulated provider's legal due-diligence obligations and the marketplace's own contractual, fraud, platform-safety or seller-quality controls. They can overlap, but they are not automatically the same requirement.

Using a licensed marketplace-payment provider

For many platforms, the most practical alternative to becoming directly licensed is to use infrastructure specifically designed for marketplace or platform payments.

Under an appropriately structured model, the regulated provider can perform functions such as receiving customer funds, maintaining regulated payment accounts or ledgers where applicable, onboarding sellers, executing payment splits and settling funds to sellers.

The marketplace may still determine the commercial economics—such as the seller price, marketplace fee or contractual payout schedule—without necessarily becoming the entity that legally receives and transmits the seller's money.

That distinction is crucial.

Control over the commercial relationship is not necessarily the same as control over regulated funds.

A marketplace evaluating such a provider should look beyond whether its API supports "split payments."

The more important questions are which regulated entity contracts with the seller, which licence covers the activity, who legally receives the payment, in whose name accounts are maintained, who performs settlement, which countries and seller types are supported, and which party carries AML, safeguarding and reporting responsibilities.

A provider's licence also needs to match the proposed market and service. Being regulated somewhere does not automatically authorise every marketplace activity in every jurisdiction.

Using a regulated provider can therefore reduce direct licensing complexity, but it replaces part of the licensing project with a provider-selection and operating-model project.

That trade is often commercially attractive, particularly during early international expansion, but it should be made deliberately.

Merchant of Record as an alternative structure

A Merchant of Record or genuine reseller model can alter the marketplace licensing analysis more fundamentally because it changes the underlying commercial transaction.

In a conventional marketplace, the independent seller generally sells to the customer and the platform facilitates the transaction.

In a genuine reseller or Merchant of Record structure, another entity becomes the contractual seller to the end customer and receives payment for its own sale. It then has a separate commercial obligation to compensate the original supplier.

That difference can change whether a payment represents third-party seller funds or the MoR's own sales proceeds.

But Merchant of Record should not be treated as a licensing label that can simply be added to a checkout.

The contractual and operational reality needs to support the model. The MoR typically assumes substantially more responsibility for the customer transaction, potentially including payment acceptance, refunds, chargebacks, consumer-facing obligations, indirect tax administration and other responsibilities associated with being the seller.

The underlying supplier may still retain regulatory, contractual, product, tax or compliance obligations of its own.

A Merchant of Record structure can therefore change the allocation of payment responsibilities, but it does not mean that "compliance disappears."

The deeper allocation of responsibilities belongs in Merchant of Record Regulatory Responsibilities.

Fraud, reserves and delayed seller settlement

Marketplace risk management can unintentionally affect the funds-flow analysis.

Platforms often want the ability to delay a seller payout because a transaction may be fraudulent, a customer may request a refund, a service may not yet have been delivered or the seller may have accumulated excessive chargeback exposure.

Commercially, those controls can be essential.

Regulatorily, they raise an important architectural question: who is exercising that control over the funds?

There is a difference between a marketplace instructing a regulated provider that a seller is not yet contractually eligible for payout and the marketplace itself holding seller money in an account it controls.

Likewise, a "seller reserve" held and safeguarded by a regulated provider can have a different legal structure from funds retained in the marketplace's ordinary operating account.

This is one reason payment architecture should be designed jointly by product, treasury, payments, finance and regulatory teams. A feature intended to manage fraud exposure can change the legal character of the funds flow if implemented differently.

Cross-border marketplaces add another layer

Marketplace payment licensing becomes harder when buyers, sellers and payment entities are located in different countries.

A platform may initially launch with domestic buyers and sellers but later add international sellers, cross-border customer payments, multi-currency settlement or currency conversion.

Those changes can introduce new questions about payment licensing, money transmission, foreign exchange, local payment providers and geographic regulatory scope.

A regulated provider that can support seller payouts in one country may require a different regulated entity or partner in another. A marketplace structure permitted under one jurisdiction's commercial-agent rules may not be treated identically elsewhere.

This is why "our marketplace payment model" should not be treated as a universal architecture.

The better approach is:

one commercial marketplace model, with a documented regulatory and payment operating model for each material market.

Deeper treatment of those issues belongs in Cross-Border Payment Regulations and Regulatory Requirements by Market rather than expanding the marketplace-licensing article into a country-by-country licensing guide.

Why payment architecture should be decided before launch

Marketplace licensing problems become expensive when discovered after the payment product has already been built.

Consider what has to change if a late regulatory review concludes that the marketplace should not receive seller funds directly.

The company may need a new regulated provider, revised seller agreements, new customer-payment terms, a different account structure, provider-led seller onboarding, redesigned payout logic, new refund processes and changes to how marketplace fees are calculated and collected.

Engineering work that appeared complete can have to be rebuilt around an entirely different movement of funds.

The alternative is to answer the regulatory architecture question while the payment flow is still being designed.

At that stage, the company can decide whether direct licensing is strategically justified, whether a regulated marketplace provider should handle the flow, whether the commercial-agent model is legitimately available in a particular jurisdiction or whether a reseller/Merchant of Record structure better matches the business.

This is where compliance can either slow a launch or help design a launch that does not need to be re-engineered later.

The regulatory requirements themselves are not the avoidable problem. Discovering the requirements too late is.

Questions to answer before launching marketplace payments

A marketplace should be able to describe its proposed structure in plain operational language before asking counsel or a payment provider whether it requires licensing.

The starting point is straightforward: identify the buyer, seller, contracting entities, payment recipient, account holder, entity controlling the funds and entity executing settlement.

Then establish whether the marketplace ever possesses or controls funds that economically belong to a seller, whether it can delay or redirect those funds, whether balances persist between transactions, and whether a regulated provider performs those functions instead.

Finally, repeat the analysis for every material jurisdiction.

For a U.S. launch, that includes analysing federal FinCEN treatment and applicable state licensing independently. For the UK, it means analysing the Payment Services Regulations and any genuinely available exclusions. For EU markets, it means applying current PSD2-derived national requirements while monitoring the transition toward the PSD3/PSR framework.

The objective is not to find a regulatory label that describes the business.

It is to understand which entity is legally responsible for each step between customer payment and seller receipt.

Key takeaways

A marketplace does not automatically need its own payment licence simply because customers pay through its platform.

The licensing question becomes more significant when the platform receives, holds, controls, splits or transfers money associated with independent sellers. The exact outcome depends on the jurisdiction, contractual relationships and actual payment flow.

The most important distinction is between a marketplace that controls third-party funds and a marketplace that instructs a licensed payment provider that controls and settles those funds.

In the United States, direct marketplace payment flows can raise federal money-transmission questions under FinCEN's facts-and-circumstances framework, while state money-transmitter licensing must be assessed separately.

In the UK, the FCA specifically warns that marketplaces receiving customer money before passing it to sellers may be providing regulated payment services. In the EU, marketplace operators should not assume that the commercial-agent exclusion applies merely because the customer's payment to the platform settles the seller's invoice.

Using an appropriately licensed marketplace-payment provider can materially change the platform's regulatory role, but it does not eliminate seller onboarding, fraud, sanctions, consumer, contractual or other compliance responsibilities.

A genuine Merchant of Record or reseller model can change the analysis further by changing who actually sells to the customer, but that structure brings its own commercial and compliance responsibilities.

The most effective time to resolve these questions is before the marketplace payment flow is built.

Once product architecture, seller contracts, bank accounts and settlement logic assume that the marketplace itself will control seller money, changing the regulatory model can delay launch far more than analysing the licensing position at the beginning.

Marketplace payment licensing is therefore not merely a legal question.

It is a decision about who should own the regulated parts of the marketplace's payment infrastructure—and whether owning them is worth the operational cost.

Specific licensing conclusions depend on the business model, contracts, payment flow, jurisdictions involved and applicable exclusions or exemptions. Material conclusions should be confirmed with qualified regulatory counsel and, where appropriate, the relevant regulator.

🙂 🙂 🙂 🙂 🙂 🙂 🙂

SEO & editorial recommendations — not part of the article

The article stays within the requested Marketplace Payment Licensing boundary rather than recreating the broader Payment Licensing Explained, Money Transmitter Licensing or Merchant of Record Regulatory Responsibilities articles. That separation is important to the knowledge architecture described in the supplied brief.

Recommended SEO title: Marketplace Payment Licensing: Does Your Platform Need a Licence?

Recommended URL: /marketplace-payment-licensing/

Recommended meta description: Learn when marketplace payment flows can create licensing requirements, how seller funds affect the analysis, and when a regulated payment provider can reduce licensing complexity.

Primary internal-link anchors: use payment licensing early in the article to link to Payment Licensing Explained; money-transmitter licensing from the U.S. section to Money Transmitter Licensing; Merchant of Record responsibilities from the MoR section; and consumer-protection requirements where the broader obligations of seller/customer payment models are discussed.

The strongest featured-snippet opportunity is the direct answer near the top: a marketplace does not automatically need a payment licence; the answer depends primarily on whether it performs regulated activities such as receiving, controlling or transmitting third-party seller funds. That wording answers the central query without overclaiming.

The strongest visual opportunity is a three-column funds-flow infographic comparing Traditional Merchant → Marketplace Holding Seller Funds → Marketplace Using a Licensed Payment Provider. Show the customer, platform, regulated provider and seller, with arrows indicating both the movement and legal control of funds. This would make the central regulatory distinction substantially easier to understand.

A second valuable visual would be a Marketplace Payments Regulatory Decision Tree, beginning with: “Does the platform ever receive or control money owed to a third-party seller?” It could branch into provider-controlled funds, marketplace-controlled funds, persistent seller balances, cross-border payouts and MoR/reseller structures.

For FAQ/schema coverage, the highest-value questions are “Does a marketplace need a payment licence?”, “Is a marketplace a money transmitter?”, “Can a marketplace collect payments for sellers?”, “Does using Stripe/Adyen/a marketplace PSP remove licensing requirements?” and “Does the commercial-agent exemption apply to marketplaces?” The provider-specific question should be answered generically rather than implying that any named provider automatically solves the licensing issue.

One editorial maintenance item matters more than usual here: the EU PSD3/PSR transition. As of August 2026, the replacement framework has advanced substantially but has not yet become the operative replacement for PSD2 according to the current EU legislative record. The European section should therefore be reviewed when formal adoption and application dates are finalized.