DSR Marketplace

Seller rules

The DSR Marketplace sells working software: apps, CRMs, SaaS, AI agents, automation tools and the code that builds them. DSR sits in the middle of every sale: buyers pay DSR, receive the product through DSR, and DSR pays you. That's what lets buyers trust a seller they've never met.

1. What you can sell

Every listing must be working software in one of these categories.

CategoryExamples
Business appsComplete apps a business runs onCRM, ERP, POS, inventory, HR and payroll, school or clinic management, booking systemsWorking demo required
SaaS productsSoftware sold as a subscription, hosted by youCRM subscription, WhatsApp inbox, invoicing SaaS, review managerWorking demo required
AI agentsAssistants that do a job on their ownSupport agent, sales agent, lead qualifier, WhatsApp booking botWorking demo required
Automation toolsWorkflows and bots that connect tools and save manual workn8n, Make or Zapier workflows, WhatsApp automations, report generators, data-sync bots
E-commerce toolsSoftware for online sellersStore templates (code), COD order confirmation, abandoned-cart recovery, product feed tools
Finance, tax and invoicing toolsBusiness finance softwareFBR-ready invoicing, tax calculators, ledgers, expense trackers
Mobile and desktop appsReady apps people installAndroid or iOS apps (source or white-label), Windows or macOS toolsWorking demo required
SaaS boilerplates and starter kitsCode foundations developers build onAuth + billing + dashboard starters, multi-tenant kits, admin panels
Website and app templatesReady-made coded templates (code, not documents)Business, restaurant and real-estate site templates, landing pages, dashboards
UI kits and componentsCoded components, not design files aloneReact, Flutter or Tailwind component libraries, dashboard kits
APIs and scriptsCode or services other software callsExchange-rate API, scrapers that respect site terms, Python or Node scripts, data APIs
Plugins and integrationsAdd-ons for existing platformsWordPress, Shopify and WooCommerce plugins, Chrome extensions, connectors
Trading tools (software only)Indicators, backtesters, risk tools and bots, sold as software licencesMT5 or Pine indicators, backtesters, journals, risk dashboards

Trading tools are sold only as software licences: they carry an educational label, make no promise of profit, and never include signals or managing anyone's money. Optional paid add-ons (installation, customisation, extra support) may be offered with a software listing, but not on their own.

2. What you can't sell

  • Courses, tutorials, ebooks, PDFs, guides and playbooks
  • Design-only files: Figma files, mockups, icons, fonts, stock photos and videos
  • Document templates: Word or Excel templates, contracts, business plans
  • Memberships, communities, coaching and events
  • Services sold on their own, with no software
  • Trading signals, managed trading, copy-trading and any promise of profit
  • Crypto tokens, NFTs and anything crypto as the product itself
  • Accounts, licences or credentials for other companies' software; cracked or resold software; code you don't own
  • Hacking or spam tools: credential stealers, bulk spam senders, scrapers that break a site's terms, ad-click bots
  • Anything illegal in Pakistan, the United Kingdom or the buyer's country

3. How buyers receive it

Pick one for each listing. The product is always delivered through DSR, never sent to the buyer directly, so access can be checked, renewed and removed after a refund.

  • Source code download. Upload the code as a .zip (or .tar.gz / .7z) with a README.
  • Private repository access. Your private GitHub, GitLab or Bitbucket repository URL; DSR invites each buyer.
  • Installable app with a licence key. Upload the installer or package (.apk, .aab, .exe, .msi, .dmg, .zip).
  • SaaS access (subscription). Your app's sign-up URL (https); buyers get access through DSR.
  • API access with a key. Your API's base URL (https) and docs link in the description.

4. Prices and plans

  • Each listing has 1 to 4 price plans: a one-time licence (owned for good), monthly or yearly. Every plan has a PKR price and can have a USD price.
  • Licence tiers are plans too, for example "Regular licence" and "Commercial licence".
  • SaaS and API products need at least one monthly or yearly plan.
  • A monthly or yearly plan gives access for that period. Buyers renew from their DSR library; nothing is charged without them. When a plan ends, downloads, licence keys and plan checks stop until it's renewed.
  • DSR sets the price of every order from the plan; it can't be changed in the browser.

5. Commission and payments

  • DSR keeps 20% of every sale of every listing, including each subscription renewal. You get the rest: on a PKR 10,000 sale you earn PKR 8,000.
  • DSR collaborations (by DSR invitation only): a solution you build with DSR is sold in Solutions as a DSR Original, without public credit. You get 60% of every sale, renewals included, and DSR keeps 40%. It's paid with your other earnings, after the same hold.
  • Buyers pay DSR only, by card, Apple Pay or Google Pay (and JazzCash or Easypaisa when available).
  • Buyers can ask for a refund within 7 days. To cover refunds and card disputes (which can come later), your share of each sale is held for 14 days after the buyer pays. Then it's available to pay out. USD sales count in PKR at the rate DSR sets.
  • Payouts go only to JazzCash, Easypaisa or a Pakistani bank account in your name. DSR does not pay out in crypto.
  • You can request a payout from your seller dashboard once at least PKR 2,000 is available. Your seller account must be approved and verified first. We email you when a payout is sent, and you can download a statement of all your sales and payouts at any time.
  • Refunds and chargebacks remove the sale from your earnings. If that sale was already paid out to you, the amount is shown as owed back to DSR and is taken from your next payouts. A refund also revokes the buyer's licence key, plan and repository access.
  • Never ask a buyer to pay you outside DSR. Off-platform deals break these rules and end your seller account.

6. Before a listing goes live

  • Sellers are verified (CNIC or company documents and payout details) before their first payout.
  • Every listing is checked: the deliverable must be code, an app, a repository or an app URL (a PDF, document or image pack is refused), files are scanned, and the description must match what's delivered.
  • Business apps, SaaS, AI agents and installable apps need a working demo.
  • First listings and all trading tools are reviewed by a person. Editing a live listing sends it back to review.

7. Support, disputes and removal

  • Talk to buyers through DSR messages. Contact details and outside payment links are hidden before purchase.
  • Answer support questions about your product and fix what's broken or not as described.
  • If a buyer and seller disagree, DSR decides using what was delivered, the listing and the messages. DSR can refund the buyer from the held balance.
  • SaaS and hosted products must stay online and let customers export their data. A product that is abandoned or long offline is removed and its buyers are refunded.
  • DSR can hide a listing, hold a balance or close a seller account that breaks these rules.

8. Seller API

For apps and SaaS sold on DSR. Everything is JSON over HTTPS at https://digitalsilkroute.com/api/v1. The full developer guide has every endpoint, Sign in with DSR, customer API keys, limits and copy-paste examples.

Licence keys (installable apps)

DSR gives each buyer a key like DSR-7F3A1-0C9B2-55E10-AB4D7. On start-up, your app checks it and activates the device (up to the device limit on your listing). Buyers can free a device in their DSR library.

POST /api/v1/licenses/verify
{ "key": "DSR-…", "device_id": "a-stable-id-for-this-device",
  "device_name": "Office PC", "product": "your-listing-slug", "activate": true }

200 { "valid": true, "product": { "slug": "…", "title": "…" },
      "plan": { "billing": "once", "active_until": null },
      "activations": { "used": 1, "max": 3 } }
403 { "valid": false, "reason": "This licence was revoked (for example after a refund)." }

POST /api/v1/licenses/deactivate   { "key": "DSR-…", "device_id": "<the activated device>" }

Plan checks (SaaS and API products)

Buyers sign in to your app with the email of their DSR account. From your server, ask DSR whether their plan is active. Create API keys under Seller dashboard → Delivery, and never put them in an app or web page.

GET /api/v1/entitlements?email=buyer@example.com&product=your-listing-slug
Authorization: Bearer dsr_sk_…

200 { "found": true, "product": "your-listing-slug",
      "active": true, "billing": "month", "active_until": "2026-12-06T10:00:00Z" }

Private repositories

After payment the buyer gives their GitHub, GitLab or Bitbucket username in their library. It appears under Seller dashboard → Delivery: invite them to the repository, then press "Mark invited". With a GitHub token saved there, DSR invites buyers and removes them after a refund for you; otherwise remove the collaborator yourself.

These rules sit alongside the terms of service. Selling, payouts and the seller account are for people aged 18 and over. Questions: contact DSR.