A factual account of a USD 330 hold, what freelancers can do next, and why I built a small awareness site with open comments.

I did not expect a payout to stay held after the platform had already said it received the money.

On 13 November 2026, Skydo marked a payment of USD 330 as received, and wrote that I should expect settlement by 16 November. Nothing had been asked for before that receipt. Then came a document loop, the expected date moved to 17 November, and the funds were still held.

I built Payment Stuck so new and existing freelancers can see that pattern from real stories and an open discussion. It is an English-language awareness site, not a complaint site, and not a tool for tagging companies.

The pattern I mean

A held payout after receipt is specific: the platform has already received the money — a dashboard or an email says so — but the payout has not been released. It is not an ordinary delay, or a payment that never arrived.

That can look like four things:

Held without reason. After the payment already shows as received, the payout stays on hold with no written reason, or only a generic “under review,” while expected dates move.

New terms after receipt. After the money is already received, a new condition, fee, or process appears that was not asked for before receipt.

Endless unrelated document demands. After receipt, document or question requests continue in a loop — including items not requested before the payment arrived, and sometimes new asks after documents were already marked received.

Account closed with funds held. The account is closed or restricted while a payout that was already received is still held.

My own case sits in the third of those. The first story on the site is mine. This is not a legal finding; it is the email sequence I wish I had been able to read in public beforehand.

What happened to the USD 330

On 13 November 2026 at 5:34 AM IST, Skydo emailed that it had “successfully received the payment” of USD 330, and asked for the invoice to be mapped to it.

At 8:03 AM IST the same day, it emailed “Payment received in your Skydo account” for USD 330, and wrote “Expect settlement by 16 Nov.” That email did not ask for documents. No earlier email had asked for documents for this payment.

At 10:52 AM IST, Compliance asked, within 24 hours, for email correspondence with the client, including the dates and email addresses of the parties involved, plus the client’s online presence and my LinkedIn or website.

At 10:53 AM IST, a second Compliance email asked for a “Payment receipt or the proof of payment for this transaction from the sender platform,” and said “Your payment cannot be processed until we receive this.”

At 3:39 PM IST, Skydo emailed that the payment had been received, the account was “undergoing a review,” and Compliance would “reach out to you within 1 business day.” At 3:40 PM IST it said the documents already sent were “received and are under review,” with an update expected “within 1 business day.”

On 16 November 2026 at 1:00 PM IST, Skydo emailed a “Slight delay in payment,” citing “necessary and routine due diligence checks,” and set the new expected date as 17 November.

At 8:31 PM IST the same day, after a call with Compliance, it asked again for documents within 24 hours: “Relevant email or other business correspondence”; “Screenshots of the relevant profiles, dashboards and workspaces” of the tools used; “Screenshots, workflow configurations or other available supporting materials” showing the work delivered; and “Bank statements for the last six months.”

At 8:49 PM IST, Skydo emailed that further documents were “received and are under review.”

As of 17 November 2026, the payout is still held. This is a record of what was received and what was asked for after receipt. It is not a claim about anyone’s intent.

What you can do if this happens

Start with a dated record: the received confirmation, later messages, ticket or case numbers, and any note that an expected date moved. Ask the company in writing what is still outstanding and when the payout will be released. Keep the terms and messages from before receipt, and any later message that adds a new requirement. If you later share the story in public, leave out tax IDs, account numbers, and other private data.

If the company is a regulated payment service in India, use its published grievance process first. Payment companies typically name a grievance officer and a nodal officer on their website or in their terms. If that does not resolve the issue, you can use the Reserve Bank of India’s Complaint Management System at https://cms.rbi.org.in. Keep the ticket numbers and a factual timeline.

If you are dealing with a regulated payment or banking service outside India, use that firm’s official complaint channel, then the financial services regulator or ombudsman in the country where the company or your account is regulated. The exact body depends on the country.

Payment Stuck does not file a complaint with a company, the RBI, or any other body on your behalf. It is not a court or a regulator. The site is for awareness, not for filing a complaint.

Why the comments are open

Comments on every story are open. You can post immediately, with no email required. A full experience is previewed, then goes public immediately. A private manage link is shown once, so you can edit or delete the story, or mark it Released if the payout arrives. Email is optional, and useful if a moderator later needs to reach you.

A moderator reviews new stories and comments daily. A post may be removed, and the public page then shows the reason. A company may post an official reply only through a verified company channel. The site never posts on your behalf.

I kept comments open because a private ticket is easy to lose in a thread only you can see. A public discussion, even a small one, lets people compare sequences: when the payment showed as received, what was asked after that, and whether the expected date moved.

A short note on how it is built

Payment Stuck runs on Cloudflare Pages. A Pages Function, served as a _worker.js, server-renders the pages. Stories and comments sit in D1, Cloudflare’s SQLite database. Posts go live immediately, comments stay open, a daily review can remove a post and show why, and private identifiers stay off the public page.

I shipped it because I needed the place to exist. I am not claiming traction, and I am not promising that a post will release anyone’s funds.

If a payout of yours was marked received and then held, I would like to hear what the sequence looked like. You can read the stories, join the discussion, or share your own experience on Payment Stuck.