Letter from the table: A hold is not always a suspension

To the members of the Platform Council,

At the last council session, I understood more clearly why the revised draft has reached this point. People were not arguing that a platform should be free to act without explanation. They were asking what protection means when a decision affects a business in different ways. I agree with the first principle. I oppose the draft as written because it treats several different actions as if the same procedure can safely govern all of them.

Here is the episode I keep returning to. On 11 June, a payout of BDT 186,400 that I was expecting was marked for review. The account remained accessible, but the money did not arrive. The notice gave me a broad category, not the specific issue or a date by which the review would end.

I used the platform’s help channel the next day. I submitted the documents it requested on 13 June, then followed up again. I also called my bank in Chattogram. For an incoming cross-border payment, my bank needed the settlement statement and supporting invoices to document and classify the receipt. In Bangladesh, foreign-exchange transactions are handled through authorized dealer banks under Bangladesh Bank’s framework. My bank could tell me what it would need; it could not explain why the platform had stopped the payout.

That left me in the middle: the bank wanted documents connected to money I had not received, while the platform had not told me what question its review was trying to answer. I sent the settlement information available to me through the review channel and asked whether the hold concerned identity, a transaction, or a compliance check. I received no specific answer during the first part of the review. The funds arrived on 24 June. I was relieved, but the delay had already forced me to rearrange payments due that week.

I do not tell this story to suggest that the platform should have released the money sooner whatever the reason. A genuine fraud signal, a court order, a sanctions concern, or a request for documents from a bank may require an immediate pause. Giving a person advance notice of every detail could sometimes frustrate a legitimate investigation. Nor do I claim that my experience proves every hold is justified. It proves something narrower: a hold can have consequences even when the account itself is still open, and the person waiting may have obligations that do not pause with it.

What I support, and what I cannot support yet

The proposed Standard asks for written notice, a specific reason, review by a person, and a time limit on payout holds, with the same protections in every country where a platform operates. Those are understandable aims. I support a written notice that tells a business what kind of action has been taken, a route to request human review, and an end point that cannot be ignored indefinitely.

My concern is that the draft puts account suspension, listing removal, payout holds, and fee changes under one broad procedural promise. They are not interchangeable. A fee change can normally be explained in advance. An account suspension may need a prompt appeal. A payout hold may be tied to an unresolved payment, a bank’s documentation request, or a legal restriction. The same fixed clock and same level of detail may not work for all of them. The draft should say what happens when a platform cannot disclose the full reason immediately, what counts as the start of the clock, and whether a hold can be extended for a documented reason.

“The same protections in every country” also needs careful drafting. I want the same basic respect everywhere: a notice, a route to challenge an action, and a timely answer. But a single procedure cannot pretend that the payment path, documentation, and legal constraints are identical in Bangladesh and elsewhere. If the rule does not recognize those differences, it may produce either a promise platforms cannot keep or a standard that is quietly applied less honestly when a difficult case arrives.

I would ask the Council to separate ordinary enforcement from urgent holds. For ordinary cases, require a specific reason, a named review channel, and a clear deadline. For urgent cases, allow a temporary hold where necessary, but require prompt notice in terms that can safely be given, review by a person within a short

stated period, and updates when the hold continues. The Standard should require platforms to identify the basis for any extension and release any amount that is not genuinely in dispute, where that is possible. It should also make clear that an explanation can be staged: an immediate category and next step first, fuller reasons when disclosure will not undermine a lawful review.

These changes would not excuse silence. They would make the promise more usable. In my case, even a notice saying “we need a settlement document to complete a cross-border payment review; submit it here; we will update you by this date” would have told me what to do and when to ask again. That is different from asking for a guaranteed release by a date regardless of the reason for the hold.

The revised draft is better than a rule that leaves every decision entirely to platform discretion. But the Assembly should not mistake a strong-sounding universal rule for a workable one. I ask members to vote against this version and return it for the distinctions above. I would support a revised Standard that protects small businesses without making a necessary review impossible to conduct responsibly.