- Every JS file parses cleanly (acorn AST, no execution)
- Slash command count + names match what the seller promised
- Command handlers are not empty stubs or placeholder text
- No bot tokens, AWS keys, or env secrets committed
- README present with setup + env vars at archive root
Deterministic verification for digital deliveries.
The protected handoff layer for two things we deep-verify today: Discord bot ZIPs and n8n workflow JSON. Money locks under Stripe. The file the seller uploads is checked against the agreed terms. Funds release in ~30 minutes when it matches — automatic refund when it doesn’t. No live account access. No chargebacks. No judgement calls.
Two categories. Deep verification on both.
We started narrow on purpose: Discord bot ZIPs and n8n workflow JSON. For both, the engine reads inside the file, finds the structural facts, and writes them into the deal. No login. No live access. No "trust me, it works." Other categories arrive only when the verifier reaches the same depth.
- Valid n8n shape with at least one trigger node
- Workflow size + trigger type match what was agreed
- Credentials are named references — no values in the JSON
- No raw API keys or tokens in any node parameter
- Graph has no orphan nodes or broken connections
Build the deal in under a minute.
Pick what you're shipping. Answer a few chips. Get a link to send the other side. Every answer becomes a check we'll run on the delivery.
Two sides. Same protection.
Pay only when the file actually matches.
Your money locks under Stripe the second you pay. It doesn't reach the seller until the file passes every automated check you both agreed on — format, hash, contents, link reachability. Anything subjective is a one-tap confirmation from you. If something doesn't match, full refund, no dispute.
- Stripe holds the money, never us
- Hard-evidence checks, not AI guesses
- One tap to confirm anything subjective
Get paid when the file matches.
The buyer's money is locked before you start working. Deliver the file or URL, the system runs the agreed checks automatically — format, resolution, ZIP contents, dep manifest, link reachability. When it passes and the buyer ticks the subjective items, funds release in ~30 minutes. No "did they like it". No chargebacks 90 days later.
- Money locked before you ship anything
- Spec-based release, not taste-based
- Verified receipts you can post anywhere
How it works
-
Pin the spec.
Pick the deliverable, answer a few chips. Every answer becomes a check the system will run on the file.
-
Money locks.
Buyer pays into a Stripe manual-capture authorization. Not us. Not the seller. Auditable.
-
File checks. Funds release.
Automated checks run live. Buyer ticks the subjective items. Pass — seller paid in 30 minutes. Mismatch — buyer refunded.
Honest answers
What can I sell here?
Two categories today, both deeply verified: Discord bot ZIPs and n8n workflow JSON exports. The buyer self-hosts in their own environment — no ownership transfer, no live access.
We start narrow on purpose. Other categories arrive only when the verifier reaches the same depth — opening the file, reading the structural facts, and writing them into the deal. What we won't take today: source code outside a bot context, GitHub repo delivery, domain or hosting transfers, bot ownership transfers, live access to Shopify / Webflow / Notion / Figma, account transfers, follower services, license keys, gift cards, crypto, NFTs, custom-built websites, consulting. The rule: if we can't verify it from the file the seller uploads — without logging into anything — we don't list it.
How does verification actually work?
Automated checks read the uploaded file — SHA-256 hash, format, resolution, duration, codec, ZIP contents, package.json, dependency manifest, README, slash command count, no committed secrets, and (for code deals) every JS file is passed through a real parser (acorn) to confirm it parses cleanly. No execution. No install. Just static checks on the bytes. These pass or fail with hard evidence. Anything the seller committed to that is subjective (license terms, source files included) is surfaced for the buyer to confirm before funds release. The system never decides things it can't prove from the bytes.
Where's the money during a deal?
Under a Stripe manual-capture authorization. Stripe is the regulated payments provider. TrustDeal never takes custody of funds — we can only instruct Stripe to capture to the seller or void back to the buyer. Every deal page tells you exactly where the money is at every step.
What if a check is uncertain?
No auto-release. The money stays locked and a 48-hour buyer review window opens. The buyer accepts or refunds. If the seller thinks the result was wrong, they can formally request release and the buyer has a shorter window to actively refuse before funds go through.
What does it cost?
5% on deals that complete. Seller keeps 95%, in their account within 30 minutes. Plus what Stripe takes for the card. Nothing if it refunds. Nothing if it never funds.
What does TrustDeal NOT promise?
We don't grade creative taste. We don't certify "the work is good". We don't enforce ownership transfer of a domain, account, or platform. We don't run untrusted code or open links inside the seller's environment. We verify what's verifiable, and surface the rest to the buyer to decide. That line is deliberate.