What multiparty payment compliance means, and why marketplaces need it

A marketplace with multiple sellers—think Etsy, Uber, or Shopify—moves money between at least three parties: the buyer, the seller, and the platform itself. Each of those parties has legal obligations. The buyer needs protection against fraud. The seller needs to know their funds are coming. The marketplace needs to prove it is not laundering money, not facilitating illegal sales, and not holding customer funds without proper licensing. Multiparty payment compliance is the set of rules and systems a marketplace uses to satisfy all three at once.

The complexity comes from the fact that these obligations come from different places. Some are federal banking rules. Some are state money transmitter laws. Some are payment processor requirements. Some are tax rules. A marketplace that gets any one of them wrong can lose its payment processor, face fines, or have its bank account frozen.

The reader who lands here usually wants to know: what does a marketplace actually have to do, and how do they do it? Not the legal theory—the mechanics.

Key Takeaways

  • Marketplaces must separate customer funds from operating funds, either by holding money in a segregated account or by using a third-party payment processor that holds it instead.
  • Every transaction must be documented with the buyer's identity, the seller's identity, what was sold, and the amount—because regulators and payment processors audit this trail.
  • Marketplaces must screen sellers against sanctions lists and watch for patterns that suggest money laundering, fraud, or sales of prohibited goods.
  • Tax reporting to the IRS requires the marketplace to track seller earnings and issue 1099 forms when thresholds are met, which varies by state and transaction type.
  • Payment processors set their own rules on top of legal rules, and a marketplace that violates processor terms loses access to payment processing entirely.

How marketplaces hold and move customer money

A marketplace cannot straightforward take customer payments and hand them to sellers whenever it wants. The law treats customer funds as something the marketplace is holding on behalf of the customer, not money the marketplace owns. This is called a fiduciary duty.

There are two main ways to handle this. The first is to open a segregated account—a bank account separate from the marketplace's operating account, held in the customer's name or in trust. When a buyer pays, the money goes into this account. When the seller is paid out, it comes from this account. The marketplace's own money never touches customer funds. This approach requires the marketplace to have a money transmitter license in most states, because it is holding other people's money.

The second way is to use a payment processor or acquiring bank that holds the funds instead. Stripe, PayPal, Square, and similar services take the customer payment, hold it in their own account, and pay the seller on the marketplace's instruction. The marketplace never touches the money. This is simpler for the marketplace because the processor handles the segregation and the licensing. But the processor charges a fee, and the processor's rules become the marketplace's rules.

Most modern marketplaces use the second approach because it is simpler and because processors have already built the compliance infrastructure. But the marketplace still has to tell the processor what is happening—who the buyer is, who the seller is, what the transaction is for—because the processor has to report it too.

Identity verification and transaction documentation

Every transaction on a marketplace generates a record that must be kept and made available to regulators. This record includes the buyer's name and identity, the seller's name and identity, the date, the amount, and a description of what was sold. This is not optional. Payment processors require it. Banks require it. The Treasury Department's Financial Crimes Enforcement Network (FinCEN) requires it if the marketplace is handling money transmission.

For buyers, most marketplaces collect a name and email at signup, and verify the payment method (usually a credit card or bank account). The payment processor does the actual verification—they confirm the card is real and the bank account exists. The marketplace stores the record.

For sellers, the requirements are stricter. A marketplace must collect the seller's legal name, address, and tax identification number (usually a Social Security Number or EIN). Many marketplaces also require a photo ID and verify it against a database. This is called Know Your Customer (KYC) verification. The reason is that the marketplace is responsible for knowing who it is paying money to. If a seller turns out to be on a sanctions list—a list of people or entities the U.S. government has prohibited from receiving payments—the marketplace is liable.

The transaction description matters because it is the first line of defense against prohibited goods. A marketplace that knowingly processes payments for counterfeit goods, stolen items, or services that violate its terms is liable for those transactions. The description does not have to be perfect, but it has to exist and it has to be honest enough that the marketplace could reasonably have caught a problem.

Screening sellers and monitoring for fraud or prohibited activity

A marketplace must screen new sellers against sanctions lists maintained by the Office of Foreign Assets Control (OFAC). These lists include individuals and entities that the U.S. government has designated as terrorists, drug traffickers, or targets of economic sanctions. If a marketplace pays someone on an OFAC list, the marketplace itself can be fined and its bank account can be frozen.

Screening is usually automated. A marketplace submits the seller's name and address to a screening service (or does it in-house if it is large enough), and the service returns a match score. A high match triggers a manual review. A very high match blocks the seller. This happens at signup and sometimes periodically afterward.

Beyond sanctions screening, a marketplace must watch for patterns that suggest fraud or money laundering. This is called transaction monitoring. Red flags include: a seller who receives many small payments that total a large amount, a seller whose transaction pattern changes suddenly, a seller who receives payments and when ready withdraws them, or a seller who receives payments from many different buyers in a short time with no corresponding sales activity. These patterns do not prove wrongdoing, but they trigger a review.

The marketplace's payment processor also does transaction monitoring. If the processor flags activity as suspicious, it will freeze the account and ask the marketplace for an explanation. The marketplace then has to investigate and either explain the activity or cooperate with the processor's decision to close the account.

Tax reporting and 1099 requirements

When a marketplace pays a seller, that payment is income to the seller. The seller is supposed to report it on their tax return. The IRS wants to know about it too. This is where 1099 reporting comes in.

A 1099-NEC (for non-employee compensation) or 1099-K (for payment card transactions) is a form the marketplace sends to the seller and files with the IRS. It reports the total amount the seller earned in a calendar year. The threshold for when a marketplace must issue a 1099 varies. For 1099-K, the threshold is currently $5,000 in a calendar year, though this has changed and may change again. For 1099-NEC, the threshold is $600. Some states have lower thresholds.

The marketplace must collect the seller's tax identification number (SSN or EIN) and their address to file the form. If the seller does not provide this information, the marketplace cannot pay them. The marketplace must file the form with the IRS by January 31 of the following year and send a copy to the seller by the same date.

This is a compliance requirement, not a choice. A marketplace that fails to issue 1099s when required faces IRS penalties. A marketplace that issues 1099s with wrong information also faces penalties. The marketplace is responsible for accuracy.

Payment processor rules and how they layer on top of legal rules

A payment processor like Stripe or PayPal has its own terms of service. These terms often go beyond what the law requires. For example, a processor might prohibit certain categories of goods (like weapons or adult content), require a marketplace to have a certain dispute resolution process, or require the marketplace to maintain a reserve fund.

These rules matter because if a marketplace violates them, the processor can freeze the account or terminate the relationship. When that happens, the marketplace loses the ability to process payments at all. This is often more damaging than a regulatory fine because it shuts down the business when ready.

A marketplace must therefore track both legal requirements and processor requirements, and often the processor requirement is the binding one. For example, the law might allow a marketplace to hold funds for 30 days before paying a seller, but the processor might require payment within 7 days. The marketplace follows the processor's rule.

Processors also require marketplaces to have documented policies on refunds, chargebacks, and disputes. A marketplace must be able to show the processor that it has a process for handling these situations and that it follows the process consistently. If a marketplace has a high chargeback rate or a pattern of disputes, the processor will either raise fees or close the account.

How compliance systems actually work in practice

A marketplace's compliance system is usually a combination of software and people. The software side includes: a payment processor integration that captures transaction data, a KYC verification tool that checks seller identity, a sanctions screening tool that checks names against OFAC lists, and a transaction monitoring system that flags suspicious patterns.

The people side includes: someone who reviews flagged transactions and decides whether to block or allow them, someone who responds to processor inquiries about disputes or chargebacks, and someone who prepares tax reporting. For a small marketplace, this might be one person wearing all three hats. For a large one, it is a team.

The data flows like this: a seller signs up and provides identity information. The system verifies the identity and screens against sanctions lists. If the seller passes, they can list items. A buyer purchases an item. The payment processor captures the transaction and holds the funds. The marketplace records the transaction details. The system monitors the transaction against fraud patterns. If nothing is flagged, the processor pays the seller (minus fees) on the scheduled payout date. At the end of the year, the marketplace calculates earnings and generates 1099 forms.

When something is flagged—a sanctions match, a suspicious pattern, a high chargeback rate—the system alerts a compliance person. That person investigates and decides whether to allow the transaction, block it, or ask for more information. The decision is documented and kept on file in case a regulator or processor asks about it later.

What happens when compliance fails

A marketplace that does not handle compliance properly faces several consequences. The payment processor can freeze the account, which stops all payments when ready. The bank can close the account if it discovers the marketplace is not following KYC or sanctions screening rules. Regulators can fine the marketplace or pursue criminal charges if the marketplace knowingly facilitated illegal activity. The marketplace can also face civil liability from buyers or sellers who were harmed.

The most common failure is not implementing KYC or sanctions screening properly. A marketplace that skips identity verification or does not screen sellers against OFAC lists is taking on massive risk. Even if nothing illegal happens, the processor will eventually audit and discover the gap, and will close the account.

The second most common failure is poor transaction documentation. A marketplace that does not record what was sold, who bought it, or who sold it cannot defend itself if a regulator asks questions. It also cannot defend itself against chargebacks because it has no proof of the transaction.

The third is tax reporting errors. A marketplace that does not track seller earnings or issues 1099s with wrong information faces IRS penalties. These are usually smaller than processor or regulatory penalties, but they add up.

Frequently Asked Questions

Does a marketplace have to hold customer funds in a segregated account?

Not if it uses a payment processor that holds the funds instead. Most modern marketplaces use a processor like Stripe or PayPal, which means the processor holds the funds and the marketplace never touches them. If a marketplace wants to hold funds itself, it must open a segregated account and usually needs a money transmitter license.

What happens if a seller fails sanctions screening?

The marketplace must block the seller from receiving payments. If the marketplace has already paid the seller, it must freeze the account and report the transaction to FinCEN. Paying someone on an OFAC list can result in fines to the marketplace and criminal liability.

Can a marketplace refuse to pay a seller for compliance reasons?

Yes. If a seller's activity is flagged as suspicious, the marketplace can hold the funds pending investigation. If the investigation confirms fraud or prohibited activity, the marketplace can refuse to pay and may refund the buyer instead. The marketplace should document the reason for the hold.

Who is responsible for 1099 reporting—the marketplace or the seller?

The marketplace is responsible for issuing the 1099 to the seller and filing it with the IRS. The seller is responsible for reporting the income on their tax return. If the marketplace issues a 1099 with wrong information, the IRS will contact the seller, and the seller may face penalties even though the marketplace made the error.

What if a payment processor closes a marketplace's account?

The marketplace loses the ability to process payments and must find a new processor. This can take weeks or months, during which the marketplace cannot operate. The marketplace should maintain a relationship with a backup processor or have a plan to switch quickly if the primary processor closes the account.