Velvet lets you sell custom content without the usual chaos of DMs and unpaid promises. Fans describe what they want and pay when they submit; you approve, deliver on your schedule and get paid, with no invoice to chase.
You price each request for the work it actually is. A request reaches the accepted state only by way of an amount you named for it, which is what stops a two-minute clip and a two-hour shoot from sharing one number.
The minimum is checked in the service and again by a constraint on the table itself. Your own minimum can raise it as far as you like; nothing in the product can lower it, including a future caller nobody has written yet.
The request lifecycle refuses the closer role on every action. Someone working your inbox can talk about a request and pass it to you; pricing it, refusing it and delivering it are decisions only you can record.
You publish what kinds of requests you accept. A fan describes what they want without naming a price, because the price is yours to set.
You review each request and either decline it or counter with your amount, from $20 up. Accepting moves it into your delivery queue, and the fan pays when they unlock what you deliver.
Your request menu, pricing, turnaround time and hard limits are all defined by you. Anything outside your rules, you simply decline.
Because payment comes first, you never negotiate with someone who was never going to pay. Your time goes only to confirmed, funded work.
Every action is checked against the creator the request belongs to. A request that is not yours does not come back as a permission error: it comes back as nothing at all, because confirming to a stranger that a particular request exists is itself a leak.
The response you attach is normalised and stored with the request, so the exchange leaves a record on both sides rather than living in a chat thread somebody scrolls past three days later.
Velvet does not invent a second delivery mechanism for custom work. You deliver by attaching a locked link, so the finished piece sits in the same private storage, behind the same signed URLs and the same entitlement check as everything else you sell.
That also means a delivered request behaves like a link afterwards. It appears in the per-link purchase view, and the buyer holds a session that re-signs the media rather than a file you emailed and can never take back.
Funds from accepted requests are processed by a secure payment provider and credited to your Velvet wallet, tracked in your ledger per request.
Completed request earnings join the rest of your balance and clear the same 7-day hold, so custom work is not a separate payout to reconcile.
Refuse it while it is pending. Refusal is a final state reached in one action, and the only thing you owe alongside it is the response you decide to write. Declining never puts the request back into your queue later.
No. Every action in the lifecycle returns a forbidden response to the closer role. Closers sell what already exists; what gets made is a decision Velvet will only record under your own account.
As a custom_request entry in the wallet ledger, with the platform commission already applied at your plan rate and the seven-day pending reserve running like any other sale. It is a revenue line, not a side arrangement.
Decline it. Nothing was charged, so nothing has to be unwound and no one owes anyone anything.
When they unlock the delivery. You price the request, you make the work, and the fan pays by buying the link you send, so you are never delivering against money that has already changed hands.
Yes. You define categories, prices and boundaries, and fans can only submit within the menu you publish.
Twenty dollars. It is enforced twice, once in the service and once as a constraint on the table, so no client and no future caller can slip a cheaper one through.
Yes, per creator profile, as high as your work warrants. The platform floor only ever acts as a lower bound on the figure you choose.
No. The closer role is refused at the service boundary for every action in the request lifecycle. A closer can raise a request with you; the commercial decision stays with you.
Yes, because it is one. Delivery attaches a locked link, so the file lives in the same private storage and is served through the same expiring signed URLs, checked against the same entitlement record.