Use Readable text for larger type, or zoom in on the pages.
Platform Council
Evidence of Unexplained Restrictions and Delayed Payouts: Submission of the EU Platform Evidence Group
RC/PL/2026/S.2
20 May 2026
Submission — Published
Submitted by the Secretariat on behalf of the EU Platform Evidence Group, seven consenting Reseated members
1. Purpose and scope
1.This submission places seven member accounts from the European Union before the Platform Council as evidence for PL-001. The submitting members have consented to publication of the accounts in anonymised form. Their group is identified here as the EU Platform Evidence Group. No member’s business, platform, payment provider, customer or individual identity is named.
2.The accounts concern restrictions on access to a marketplace or related business service, and delays in receiving funds. They are not findings against any particular company. Each account is a member’s description supported by one or more records retained by that member, including notices, account-page captures, support correspondence, payout histories or transaction records. The Secretariat has reviewed the materials as evidence of reported experiences, not as an independent audit of the underlying platform systems.
3.The submission has four aims: to describe the evidence and its limits; to assess it against the five-part pattern test; to identify the relevant European Union rule in the dossier; and to recommend drafting
choices for the Platform Fairness Standard. It does not ask the Assembly to decide the merits of an individual account dispute.
2. The members’ evidence
4.The seven members operate in different EU Member States. They submitted records relating to events between January and May 2026. Dates and figures below are stated as supplied by the members and checked against the descriptions of their supporting records. Where a figure is described as an amount at stake, it represents the member’s estimate of funds delayed, withheld, or made inaccessible at the relevant point; it is not a calculation of final loss.
5.Euro amounts are accompanied by approximate US-dollar equivalents for comparison only. This submission uses a rounded conversion convention of €1 = US$1.10. The equivalents are not statements of exact exchange rates on the dates of the events.
| Member record | Reported sequence and supporting material | Amount at stake |
|---|---|---|
| EU-1 | On 12 January, the member received an automated notice that access to selling tools had been restricted. The notice referred generally to “unusual activity.” The member retained the email and a capture of the account page. On 14 January, a support response requested identity documents; on 19 January the member uploaded them. A further message on 2 February confirmed receipt but gave no decision date. The member’s payout history showed funds awaiting transfer during the restriction. | €2,400 (about US$2,640) |
| Member record | Reported sequence and supporting material | Amount at stake |
|---|---|---|
| EU-2 | On 3 February, a listing was removed and the account was placed under review. The notice identified a policy category but not the listing feature or transaction at issue. The member saved the notice, listing record and two support exchanges. A response on 11 February said the case had been escalated; the member reported no reasoned outcome by 6 March. A payout shown as pending remained unavailable during that period. | €1,180 (about US$1,298) |
| Member record | Reported sequence and supporting material | Amount at stake |
|---|---|---|
| EU-3 | On 17 February, the member’s account was suspended after a request to confirm business details. The member retained the suspension email and the confirmation submission receipt. On 20 February, support acknowledged the documents. On 7 March, access was restored, but the member’s records show a further delay before the scheduled payout was released. The member could not identify from the notice whether the delay arose from the suspension or a separate payment review. | €6,700 (about US$7,370) |
| Member record | Reported sequence and supporting material | Amount at stake |
|---|---|---|
| EU-4 | On 9 March, the member received notice of a payout hold, with the reason described as a routine review. A screenshot of the payout page showed an estimated release date that was later removed. The member retained messages sent on 12 and 21 March asking for the reason and expected end date. A response on 28 March repeated that the review was ongoing, without stating a deadline. The funds were released on 15 April. | €3,250 (about US$3,575) |
| Member record | Reported sequence and supporting material | Amount at stake |
|---|---|---|
| EU-5 | On 24 March, the member’s listings became unavailable following an account restriction. The email identified a broad compliance concern but did not specify the item or action requiring correction. The member saved the email, the affected listing page and the date-stamped appeal submission. On 8 April, the member received a request for additional records. The member supplied them on 10 April and reported that the restriction remained in place on 20 May. | €920 (about US$1,012) |
| Member record | Reported sequence and supporting material | Amount at stake |
|---|---|---|
| EU-6 | On 6 April, the member was notified of a change to a transaction-related fee. The notice described the revised rate and effective date, but the member’s retained message did not explain which transactions would be affected or provide a route to review the change. The member compared the notice with account statements from the preceding month and estimated the additional charge over the first four weeks. | €540 (about US$594) estimated additional charges |
| Member record | Reported sequence and supporting material | Amount at stake |
|---|---|---|
| EU-7 | On 4 May, the member received notice that selling access would be suspended pending verification. The notice listed documents to provide, but did not state when a human review would occur or how long a payout hold could last. The member retained the notice, upload confirmation dated 5 May and a payout-page capture dated 12 May. The member reported that the review and hold were unresolved when the submission was prepared. | €4,100 (about US$4,510) |
6.The seven reported amounts at stake total €19,090 (about US$20,999), counting EU-6’s estimated additional charges and the other members’ reported inaccessible or delayed funds. This total is a description of the submitted cases only. It is not a measure of the Platform Council’s total reported exposure, and it should not be read as an estimate of economy-wide loss.
7.The records vary in strength and completeness. EU-1, EU-2, EU-4 and EU-5 supplied a notice or account capture together with later correspondence or a payout record. EU-3 and EU-7 supplied records spanning the restriction and verification process. EU-6 supplied a fee-change notice and a comparison based on account statements. These materials help establish what information was communicated and when; they do not establish the platform’s internal reason, the accuracy of its risk assessment, or whether a restriction was justified.
3. Assessment against the five-part pattern test
Volume
8.The submission contains seven member accounts. Seven cases alone are not a population-level estimate and cannot establish the prevalence of the reported practices in the EU or across platforms. They do, however, add distinct, documented experiences to the Platform Council’s larger body of evidence. As of 20 May 2026, the Council recorded 1,034 Platform reports from 50 countries, including 220 Platform Council members from 45 countries. The Council’s report categories at that date included 583 account-suspension reports and 451 funds-held reports. These are Reseated report counts, not verified incidents or a count of unique companies.
Frequency
9.The seven records describe events across five months, from January through early May. Several accounts include repeated contact attempts, further document requests, or a continuing restriction rather than a single notification. The evidence therefore points to recurring stages in the member experience: an automated or general notice, an attempt to obtain a specific explanation, submission of requested material, and uncertainty about review or release timing. The sample does not prove that any one platform follows this sequence routinely.
Consistency
10.Four shared features appear in more than one account. First, the initial explanation was expressed at a broad level, leaving the member uncertain about the particular conduct, transaction or listing at issue. Second, members had difficulty distinguishing a restriction on selling from a separate payment or verification review. Third, members described follow-up responses that acknowledged a case or repeated a general status without stating a decision date. Fourth, the records show
that funds or selling access could remain unavailable while the member waited for a review.
11.The accounts are not identical. EU-6 concerns a fee change rather than an account suspension or payout hold. EU-3 reports restoration of access followed by delayed release of a payout. EU-4 reports a dated release after a period without a stated end date. These differences matter: the evidence supports examining common procedural safeguards, not collapsing distinct events into a single claim about motive or outcome.
Spread
12.The members are based in different EU Member States and describe events involving marketplace selling tools, listings, account verification, payout processing and transaction-related fees. This provides some geographic and functional spread within the EU evidence group. The submission does not identify or compare individual services, and it cannot show that the same practice occurs across every market, Member State or provider. The Platform Council’s international report totals offer wider geographic context, but they do not establish that the seven EU accounts are representative of those reports.
Corroboration
13.The members’ accounts are supported by contemporaneous records described in paragraph 5. The records corroborate the dates, wording and sequence that the members say they experienced. In some cases, a payout-page capture or account statement supplies a second record of the financial effect. Multiple members independently describing a similar lack of specificity or a missing review timetable strengthens the basis for drafting a general procedural standard.
14.Corroboration has limits. The Secretariat has not obtained internal decision records from any service, verified each underlying transaction, or contacted a provider to test its explanation. Nor does a member’s copy of a notice establish that no other notice or policy information was available elsewhere. The submission therefore supports a finding about the evidence members can access and the practical uncertainty they report; it does not establish that every restriction was wrongful.
15.Taken together, the seven accounts contribute evidence on all five dimensions, with strongest support for consistency and corroboration within the sample. In combination with the broader Platform Council record, they support continuing consideration of PL-001. They should not be treated as a substitute for the Council’s full pattern review or as an independent statistical finding.
4. Relevant European Union law
16.Regulation (EU) 2019/1150, commonly known as the Platform-to-Business Regulation, addresses relations between online intermediation services and business users. Article 4 requires a provider that restricts or suspends an individual business user’s service to provide that business user, at or before the restriction or suspension takes effect, with a statement of reasons on a durable medium. The stated reasons must refer to the specific facts or circumstances that led to the decision and the applicable grounds. The Regulation also contains a distinct rule on notice before termination of the whole service to a business user; that termination rule should not be confused with the requirements for an individual restriction or suspension.1
17.Article 4 is directly relevant to the members’ reported difficulty understanding which particular event or conduct led to a restriction. It provides a legal point of reference for reason-giving, but this submission does not determine whether the Regulation applies to a
particular service or case, whether a particular notice satisfies its requirements, or what remedy may be available. Those questions depend on the facts and applicable law.
18.The evidence also identifies matters that the cited Article 4 provision does not, by itself, resolve in the terms proposed by PL-001. Members seek a clear route to review by a person, information about the expected review period, and a defined limit or update schedule for payout holds. The draft may therefore set a common operational standard that goes beyond the particular requirements described here, while stating clearly that it is a voluntary standard and not a replacement for applicable law.
5. Recommendations for the draft
19.The EU Platform Evidence Group recommends that the draft preserve the four core safeguards in PL-001 and express them as requirements that can be checked from the member’s communications and account record:
- Written notice. Send notice to the affected business user through a durable, accessible channel before the measure takes effect where practicable, and promptly where an urgent measure is necessary. The notice should identify the measure and its effective time.
- A specific reason. Identify the relevant account, listing, transaction, policy ground or other facts with enough detail for the member to understand what is being reviewed and what response is invited. A broad label alone should not be treated as a complete explanation where more specific information can safely be provided.
- Human review. Provide a clear route to request review by a person with authority to reconsider the measure. A confirmation that a request was received should not be presented as a review decision.
- Time limits for payout holds. State the start date, the basis for a hold, the next review date and the expected release date or the conditions that must be met before release. If the hold continues beyond the stated period, provide an updated reason and a new review date.
- Consistent protection across countries. Apply the same minimum protections in every country where the service operates, while allowing stronger local legal protections to prevail.
20.The draft should also address changes to fees separately from emergency restrictions. A fee-change notice should identify the affected transaction types, the effective date, and where the member can ask for clarification or review. Where a change is based on individual account circumstances rather than a general schedule, the notice should say so. This recommendation follows from EU-6’s account and should not imply that the member’s estimate is a verified charge across a wider user group.
21.The standard should distinguish notice of a decision from an explanation of how to challenge it. At minimum, communications should identify the channel for review, the information the member should submit, and how the member can see the status of the request. If disclosing a detail would create a specific security or legal risk, the service should still provide the most useful explanation it can and identify the nature of the limitation, rather than defaulting to an unexplained general label.
22.The draft should avoid promising that all appeals will succeed or that every restriction will be lifted within a fixed number of days regardless of the case. It should instead require a stated, reasonable review period, progress updates when that period cannot be met, and a final communication that identifies the outcome and the principal reasons. For a payout hold, the standard should require periodic reassessment and a clear account of what remains unresolved.
23.Finally, the standard should specify what records a service should retain and make available to the affected member: the notice as sent, the date and type of action, the reasons communicated, the review request and response, and the dates on which a payout hold was reviewed or changed. This would make it possible for members and services to reconstruct the sequence without requiring public disclosure of confidential data.
6. Conclusion
24.The seven members submit a limited but coherent set of records. Across different EU locations and types of platform-related action, they describe uncertainty about the specific basis for an intervention, the status of human review, and the duration or release conditions for funds. The records support precise, testable drafting choices; they do not support naming or accusing any provider, estimating sector-wide losses, or concluding that every restriction was improper.
25.The Secretariat submits this evidence for the PL-001 draft process and public record. The evidence should be considered alongside the wider reports, the five-part pattern review, and other consultation submissions. The members’ central recommendation is practical: when a business user loses access, a listing, a payout or a fee arrangement, the communication should make clear what happened, why it happened, how a person can review it, and when the member will next receive an update.
Sources
- Regulation (EU) 2019/1150 of the European Parliament and of the Council, especially Article 4. 1
This document has no standing until adopted under the Founders Charter. Reseated Councils is not affiliated with the United Nations.