How D-commerce works: from payment to delivery

© D-commerce

D-commerce looks like a store — and that is the point. The buyer sees the offer, terms and price before paying. After payment they land in a cabinet: subscriptions, invoices, plan changes, support tickets. Nobody messages you asking “where is my access”.

Three product types — one storefront

  • Subscription — a dedicated instance of a cloud app for the buyer. The store takes payment and queues the deploy.
  • Key — a digital code from inventory. Issued right after a successful payment.
  • Archive — a file from inventory. Same rule: payment → delivery, no manual shipping.

Every type is tied to payment status: unpaid access never goes out.

Where the buyer’s product lives

When a dedicated instance is needed, Deployer — part of the D-commerce contour — launches it on your VPS next to Docker. Source code, images and data stay on your infrastructure. The store owns commerce: offers, money, delivery rules. The server owns runtime.

Keys and archives do not need a VPS: upload them to the digital inventory in advance.

AI speeds you up — it does not replace control

Both the store and Deployer expose MCP — a way to connect Cursor, Claude or another AI client. The assistant updates the catalog, replies to tickets, reads logs and checks container status in plain language. Setup takes about five minutes. The admin panel stays: you still decide what can be delegated.

Three steps to start

  1. Pick a D-commerce plan and activate your store.
  2. Connect a VPS only if you sell deployable instances.
  3. Add a product, place a test order and verify delivery.

Next — plans and the store Quick start. If your case is unusual — write to us.