> For the complete documentation index, see [llms.txt](https://docs.lid.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lid.pro/help/is-lid-safe.md). # Is Lid safe? How splits settle and who holds the money, what protects buyers and funders, who decides a dispute, and what is still being built. Short version: no company ever holds the money. Budgets sit in a pool the funder controls until the result verifies; the moment it does, the split settles in the same transaction. Here is how that works, and the one case where our team decides where money goes: a disputed refund. ## Who holds the money No company. When a buyer pays, the payment splits the second it happens. The seller gets their share. The person who shared the link has their commission assigned to them, and only they can claim it. Lid gets a flat 3%. The sale, the split and the payout are one transaction. Unless the seller set a refund window, there is no waiting period and no payout day. Your balance is yours the moment you earn it. ## Why the split can't be changed later The split rules are set on each product, and everyone can see them before they share or buy. Once a sale happens, the record of that sale is permanent and public. Nobody can go back and change who got paid, including Lid. ## What protects buyers Sellers can set a refund window on their products. During that window, the money is held to one side. The buyer can release it to the seller early, or open a dispute; a person on our team then decides whether it goes to the seller or back to the buyer, and it can go nowhere else. Services, which are being built, will release only when the buyer confirms the work was delivered. Payments become final when both sides are done. ## What protects funders When you fund a challenge or a campaign, the budget sits in a pool you control until the result verifies. The moment it does, the split settles in the same transaction. Until then, nobody else can move it. ## Is this crypto? Lid runs on Solana, which is what lets payments split and settle in seconds. You never have to touch, understand, or own any of it. You sign up with your email, you see prices in dollars, and you get paid in digital dollars (USDC). One USDC is worth one US dollar. ## What is still being built Cashing out to a bank account and services are being built. Card payments are already live through MoonPay. The technology behind Lid is reviewed continuously, and an independent external security review is planned. {% hint style="info" %} If this page and the app at [lid.pro](https://lid.pro) ever disagree, the app is right. {% endhint %} ## Questions Email . You will get a reply from a person. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.lid.pro/help/is-lid-safe.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.