Use Readable text for larger type, or zoom in on the pages.
Platform Council
Notice, Reasons and Review: German Members’ Evidence on Account Restrictions and Held Funds
1. Purpose and scope
1.This submission places a set of member records before the Platform Council as evidence for agenda item PL-001. The six submitting members are based in Germany and have consented to publication of an anonymized account. None has authorized publication of a personal name, business name, platform name, account identifier, customer information or other identifying detail. The accounts below therefore refer to “a large marketplace” and “a payment provider,” not to any named company.
2.The members describe separate episodes in which a business account was restricted, a listing was removed, or money due to a seller was held. They report that the explanations and review routes available to them were inadequate to determine what action was being taken, why it had been taken, how to challenge it, or when held funds would be released. The evidence is relevant to the proposed requirement for written notice, a specific reason, review by a person and a time limit on payout holds.
3.The Secretariat treats the accounts as member-submitted evidence, not as findings against any company. The material described was supplied by the members; this submission does not independently authenticate platform records or adjudicate the underlying account decisions. The members’ consent permits publication in this anonymized form and does not waive their rights or establish that every restriction was unlawful.
2. What the members submitted
4.The six members described records they say they retained during the events: automated account notices, screenshots of account-status pages, support correspondence, transaction or payout statements, listing-status records, and copies of invoices or order records relevant to the activity queried. Some members also kept dated notes of telephone or online support contacts. This description records the material identified by the members; it does not reproduce private customer data or disclose account credentials.
5.In each account, the member could identify the practical consequence—loss of access, removal of a listing, or delay in receiving funds—but reported difficulty identifying the precise rule or conduct said to justify it. Several described receiving a generic notice first and an explanation only after they initiated contact. Members also described uncertainty about whether a support response represented a review of the decision or merely repeated the original notice.
6.Amounts below are the members’ reported sums affected in their individual episodes, not a combined loss calculation. The US-dollar equivalents use a fixed arithmetic convention of EUR 1 = US$1.10 solely to make the amounts easier to compare. This is not a statement of the market exchange rate on any incident date. The submission does not add the individual figures together, because the records cover different types of exposure and different periods.
3. Anonymized timelines
| Member | Timeline and records described | Reported amount affected |
|---|---|---|
| A | On 11 February 2026, the member found that access to a marketplace seller account had been suspended. The first notice described a policy concern but, according to the member, did not identify a listing, transaction or specific conduct. The member retained the notice and an account-status screenshot. On 13 February, a support response referred to the same policy category without addressing the member’s request for the evidence relied upon. The member says access remained restricted when the account was last checked. | €4,000 (approximately US$4,400) |
| Member | Timeline and records described | Reported amount affected |
|---|---|---|
| B | On 16 February 2026, a listing was removed and the member received a short notification referring to a possible compliance issue. The member retained the notice, a listing-status record and invoices relating to the goods. A request for review was submitted on 17 February. The response received on 20 February did not, in the member’s account, explain which item of information was considered insufficient. The member reports that the listing could not be restored through the appeal route shown in the account. | €2,500 (approximately US$2,750) |
| Member | Timeline and records described | Reported amount affected |
|---|---|---|
| C | On 20 February 2026, a payout expected by the member did not arrive. The account showed a payment review but no release date. The member retained a payout statement and a screenshot of the review notice. On 24 February, the member asked what transactions were under review and when the money would be available. The reply, as described by the member, referred to a continuing review and requested patience but supplied neither a specific transaction explanation nor a time limit. | €5,200 (approximately US$5,720) |
| Member | Timeline and records described | Reported amount affected |
|---|---|---|
| D | On 2 March 2026, the member received a notice that access to account functions had been limited. The notice cited unusual activity without identifying the activity or distinguishing an automated flag from a finding made after review. The member retained the notice, account screen and a dated record of a subsequent support contact. The member says the contact did not establish whether a person had examined the account or what steps would end the restriction. | €3,600 (approximately US$3,960) |
| Member | Timeline and records described | Reported amount affected |
|---|---|---|
| E | On 5 March 2026, a payout was placed on hold while a large marketplace requested additional information. The member retained the request, the response sent through the account, and a payout statement. The member says the request did not explain whether the hold covered all funds or particular transactions. After the requested material was supplied, the account continued to show a hold without a stated decision date. The member described difficulty planning supplier payments while the amount remained unavailable. | €6,000 (approximately US$6,600) |
| Member | Timeline and records described | Reported amount affected |
|---|---|---|
| F | On 9 March 2026, a payment provider limited a payment-related account used in connection with online sales. The member retained a restriction notice and two support responses. The notice referred to a review but did not, according to the member, identify the transaction or action at issue. The member reports that the responses did not say whether a person had reviewed the restriction, what further information was required, or when the member could expect a final decision. | €1,800 (approximately US$1,980) |
7.The episodes do not all concern the same action or service. Their evidential value lies in the repeated practical difficulty members describe: the notice did not reliably identify the particular decision and reason; the route to contest it did not clearly establish meaningful human review; and, where money was held, the
member did not receive a definite limit or release timetable. These are reported experiences, not a conclusion that the providers acted for the same reason or under the same terms.
4. Assessment against the five-part pattern test
8.The Secretariat applies the five-part test used by the Assembly: Volume, Frequency, Consistency, Spread and Corroboration. A pattern finding identifies a recurring problem suitable for consideration; it is not a legal determination in an individual dispute. The Platform Council had 66 members from 29 countries and 323 reports from 44 countries as of 17 March 2026. The reported median amount at stake was approximately US$4,525. The recorded Platform Council situations included 151 funds-held reports and 172 account-suspended reports. These figures provide the wider context; they do not prove the merits of these six German accounts.
9.Volume. The six-member submission is a small, consented sample and is not presented as a prevalence estimate. It is relevant alongside the 323 Platform Council reports already recorded by the date of this submission. Within these six accounts, more than one type of restriction appears: account access, listing availability and payout access. The sample therefore supports further specification of safeguards across the range of actions named in PL-001, while leaving the Council to assess the wider report base.
10.Frequency. The reported events occurred between 11 February and 9 March 2026. Members describe more than one contact or notification in several episodes, but repeated contact did not necessarily produce a more specific reason or a clear review outcome. This is evidence of recurrence within the submitted accounts, not a claim about the frequency of such conduct across all platform users. The Council’s wider record includes 286 Platform Council reports in the last 30 days, a figure that indicates continuing reporting activity but does not by itself establish how many concern the same practice.
11.Consistency. The accounts differ in service and consequence, but share a recognizable sequence: a restriction or hold appears; the initial notice gives a broad category or says a review is in progress; the member seeks clarification;
and the response, as reported, does not settle the specific basis, the human-review question or a definite endpoint. This consistency is sufficient to test a common procedural remedy without assuming that the underlying policy grounds were identical.
12.Spread. The submission itself concerns one country and six members. The broader Platform Council reports came from 44 countries, while Platform Council membership covered 29 countries. The Secretariat does not infer from those totals that every country has the same law, process or experience. They do show why a proposed standard should be capable of application across borders and should not depend on a seller being able to obtain a remedy only in one jurisdiction.
13.Corroboration. The members describe multiple forms of contemporaneous material: notices, account screens, payout records, correspondence and, where relevant, transaction or invoice records. These are potentially cross-checkable records, especially where dates and account status can be compared. Their existence and consistency have not been independently authenticated for this publication. Corroboration is therefore assessed as present in the form of described records, but limited pending any review of the underlying documents under an agreed privacy-protective process.
14.Taken together, the submission supports drafting safeguards that make decisions intelligible and reviewable. It does not support a presumption that every restriction is mistaken, that every delay is improper, or that a platform must disclose information that would compromise an investigation or another person’s privacy. Any exception should be specific, proportionate and itself communicated as far as the law permits.
5. Relevant legal context
15.For business users in the European Union, the Platform-to-Business Regulation provides a relevant existing point of reference. Article 4 requires providers of online intermediation services to give a statement of reasons when restricting or suspending a business user, subject to the terms and scope of that provision. It also addresses notice before termination of the whole service. The members’
accounts raise a practical question about whether a reason is sufficiently specific to let a business user understand the restriction and make an effective response. The Regulation is not a substitute for the proposed standard’s separate attention to payout holds, review by a person and a time limit.1
16.The Digital Services Act requires statements of reasons for specified decisions by providers of intermediary services, including information about whether automated means were used, within the scope of Article 17. Its requirements are relevant to transparent decision-making, but this submission does not treat the DSA as creating identical duties for every payment, account or business relationship described by members. Applicability depends on the service and decision concerned. The proposed standard should therefore be drafted as a practical baseline and should not imply that existing European rules apply to every provider or every incident in this submission.2
17.The Council should preserve this distinction between existing law and a voluntary or adopted Assembly standard. The standard can ask for operational protections beyond a minimum legal requirement, but it should not describe those protections as already guaranteed by law in every country. Nor should the Assembly offer legal advice about an individual member’s case. The present evidence is offered to inform the content of the draft, not to determine any member’s legal claim.
6. Recommendations for the draft
18.The Secretariat recommends that the draft Platform Fairness Standard state the following requirements in direct and testable terms:
Written notice before action, where practicable. Before suspending an account, removing a listing, holding a payout or changing a fee, the provider should send notice through a durable channel accessible to the business user. Where urgent action is necessary to prevent a concrete and immediate risk, notice may follow promptly, but the provider should explain why advance notice was not practicable.
A specific reason tied to the decision. The notice should identify the action taken, its effective date, the relevant policy or contractual basis, and enough information about the conduct or transaction at issue for the business user to respond. A broad label such as “policy concern” or “review” should not, by itself, satisfy this requirement. Information may be withheld where disclosure is prohibited or would create a defined risk, but the notice should explain the nature of the limitation to the extent permitted.
A usable review route and human review. The provider should identify how and by when the user may request review, what material may be supplied, and how the request will be acknowledged. A person should review the decision, rather than merely repeat an automated result or the original notice. The resulting communication should state whether the decision was upheld, changed or lifted and provide a reason. The standard should not require disclosure of internal systems or confidential information unrelated to the decision.
A time limit for payout holds. Each hold should have a stated start date, the funds or transactions affected, the reason for the hold, and a review or release date. Where a hold must continue beyond that date, the provider should give an updated reason and a further definite date. A hold should not remain open-ended solely because the account displays that a review is ongoing. The draft may permit legally required holds, but should require notice of the applicable constraint where disclosure is permitted and periodic reassessment.
Consistent protections across countries. The same core notice, reason, human-review and time-limit protections should apply in every country in which the provider operates. The provider may explain that local law requires a different procedure, but should identify that difference and preserve the greatest protection it can lawfully provide. A business user should not have to infer which country-specific process applies from a generic account message.
Records and accessible language. Notices and review outcomes should remain available to the business user, with dates and reference identifiers sufficient to follow the matter. They should use clear language, avoid unexplained internal codes, and state what the user can do next. A provider should avoid requesting the same material again where it can reasonably identify that it has already been submitted.
19.These recommendations do not prevent a provider from enforcing its terms, protecting users, complying with law, or taking proportionate urgent action. They require the provider to communicate the decision in a way that allows a business user to understand its consequences and pursue review. For payout holds, a stated time limit is especially important because a seller may have continuing obligations to suppliers, workers and customers while funds are unavailable.
7. Evidentiary limits and next steps
20.The submission is intentionally narrow. It contains six accounts from Germany, and the events described took place within a short period. It cannot establish the rate of account restrictions or payout holds among all members, compare the conduct of different providers, or show that the reported explanations were technically inaccurate. The Secretariat has not received authority through this submission to publish underlying documents or identify the members.
21.The Council should consider the accounts together with the wider report base and invite further evidence during the applicable consultation. Any follow-up request should minimize collection of personal, commercial and customer information. Where supporting records are reviewed, access should be limited to the purpose of testing the reported notice, timeline and review process. Public reporting should continue to use anonymized descriptions unless a member makes a separate, informed choice to occupy a public seat.
22.This submission recommends that the draft distinguish between a decision’s substantive merits and the procedural quality of the notice and review. A provider may have a legitimate basis for action; the member may still be unable to understand or challenge that action if the explanation is generic, the review route is unclear, or the payout hold has no endpoint. Conversely, a well-specified notice does not determine whether the underlying decision is correct. Keeping those questions separate will make the standard clearer and easier to assess.
8. Conclusion
23.The six members’ accounts describe different restrictions but a recurring information and review problem. They report contemporaneous records that could support further assessment, while the Secretariat recognizes that the materials have not been independently authenticated and that the sample is not representative by itself. Considered with the Platform Council’s existing reports, the submission supports a draft standard requiring a specific written reason, a meaningful review by a person, and a definite, reviewable limit on payout holds.
24.The Platform Council is invited to use these recommendations when preparing the next draft of PL-001. The central test for the language should be practical: after receiving a notice, can a business user identify what happened, why, what information is needed to challenge it, who will review it, and when held funds will be reconsidered or released?
Sources
Regulation (EU) 2019/1150, Article 4, online intermediation services: 1
European Commission, Digital Services Act: questions and answers on the Transparency Database and related framework: 2
Notes and sources
Sources
This document has no standing until adopted under the Founders Charter. Reseated Councils is not affiliated with the United Nations.