Sell digital goods, including the payments.
Licence keys, accounts and files, delivered the second a card clears. Turn on RunePay and it is the merchant of record on every sale, so the chargebacks, the VAT and the risk reviews are ours rather than yours.
Store
Welcome back, Mara
How your store is doing over the last 30 days.
Revenue · 30d
€18,240.50
Orders · 30d
412
Keys in stock
1,284
Products
17
- RuneTools Pro — Lifetime4 left
- Aim Trainer — 30 daysSold out
RS-02186
m.alvarez@… · 2 min ago
delivered€89.00RS-02185
k.novak@… · 14 min ago
delivered€24.00RS-02184
Guest · 31 min ago
delivered€149.00RS-02183
t.okafor@… · 1 hr ago
refunded€12.00
01 — Why RuneSell
Sellers here do not churn over storefront features.
They churn because the payments stopped. Every other platform in this market treats that as somebody else's problem, because for them it is.
Risk review closed · 14 days notice
The storefront is never what fails
Sellix, SellHub and SellAuth are capable products. What ends a business on them is the processor bolted on beside them, which was never built to carry this category and says so eventually, with notice.
Live on its own hostname
RunePay, same form
Here the processor is the platform
RuneSell's payment layer is RunePay, built for gaming software, PC tools and licence keys specifically. Opening a store and getting a merchant account are one action.
The liability moves off you
Merchant of record is not a marketing word: it is the name on the buyer's statement and the entity a card network bills for a dispute. You keep the product and the customer.
How it works
Three steps, and payments come with the shop.
Create your store
An email and a password. Nothing to deploy, nothing to host, and no theme to choose before you can add a product.
aldergrove.runesell.com
Put your stock in
Paste a pool of keys, point us at the endpoint that mints them, or upload the files. Price each edition on its own.
47 keys in stock
Get paid, they get delivered
Your processor takes the payment and settles to you on its schedule. The buyer has their key before the tab closes.
Delivered on authorisation
02 — What you can sell
Serials, dynamic codes, files. Or all three on one product.
How stock is counted is the only thing your choice here decides. It does not decide what a buyer ends up receiving.
Serials
A pool of keys you upload. One is claimed per purchase, never handed out twice, and the pool size is the stock count buyers see.
POST /issue → 201Dynamic
Your own endpoint mints the code when the sale completes. For when the credential has to come out of your system, not a spreadsheet.
build-4.2.1.zipFiles
Builds, archives, documents. Served through authenticated links tied to the buyer's account rather than a URL that can be forwarded.
Any product can do all three
Delivery type decides how stock is counted, not what a buyer receives. A serial-backed product can carry the installer that serial unlocks.
Editions are separate stock
“30 days” and “Lifetime” are two pools, not two prices for one. A buyer who paid for a year is never handed a month’s key.
03 — Delivery
The part that has to work is the part after the card clears.
This is the whole reason the category exists, so it is where the mechanisms are worth reading rather than taking on trust.
Stock is enforced in the cart, not at payment
A buyer cannot reach a payment form holding a key that no longer exists. The pool size is mirrored onto sellable stock after every claim, release and revocation, so the storefront refuses the sale rather than taking the money and failing.
Every edition has its own pool
Editions are not prices for a shared pool. A buyer who paid for a lifetime licence cannot be handed a thirty-day key, because the two were never in the same pile.
Keys are encrypted before they touch disk
AES-256-GCM, decrypted only on the delivery path, masked by default in your dashboard. A database dump, a replica or a stolen backup is not a copy of your stock.
A refunded key is retired, not recycled
Full refunds and cancellations revoke every key issued for the order and correct the stock count. Revoked keys never return to the pool — the buyer has already seen them, so reselling one would be selling a credential in circulation.
Buyers fetch their purchase again themselves
Keys and downloads stay in the buyer’s account for as long as the account exists. The defining anxiety in this category is a dead link and an unanswered ticket; the answer is a page, not a support queue.
Your redemption instructions travel with the key
Written once on the product, rendered beside the key on the receipt and in the email. A key with no idea what to do with it is the most common ticket in this market, and you are the only one who knows the answer.
RS-02186
RuneTools Pro
Lifetime · 1 licence
············9F3CInstaller
Build 4.2.1 · 68.4 MB
runetools-pro-4.2.1.zipDownloadScarcity is the count, and the count is the pool. No countdown timers, no invented urgency — buyers in this market have seen all of it, and it reads as a warning rather than a nudge.
One cart, several sellersA buyer can check out products from more than one seller in a single card charge. We split it into an order per seller behind the scenes; they see one total, one payment, and one receipt carrying each seller's reference.
04 — Payments
Whose merchant account takes the money.
You can bring an account you already have. The reason to use ours is what happens when a dispute or a tax authority comes looking for the merchant.
Use RunePay, and it stops being your problem
Early access
RunePay is a payments product built for this category, and it can be enabled on any store here. It takes the payment as merchant of record, which means the card networks bill it for a dispute and the tax authorities bill it for the VAT.
- RunePay is the merchant of record, not you
- Chargebacks, VAT and compliance sit with us
- Underwritten for gaming software and licence keys
- One sign-up covers the store and the payments
Or connect an account you already have
Your keys, your account, your liability. Fees and limits are yours to set per method, and buyers see the surcharge on the method itself.
Stripe
Cards, Apple Pay, Google Pay
PayPal
PayPal balance and cards
Coinbase Commerce
BTC, ETH, LTC, USDC
NOWPayments
Over a hundred coins
Stripe takes payments today. The rest are configurable in your dashboard and are being wired to the charge path in turn — a method that looks switched on and silently declines every checkout is worse than one that is visibly not ready, so we mark them.
05 — Coming from elsewhere
Where we differ, and where we honestly do not.
Sellix, SellHub and SellAuth are capable products, and the first three rows say so. The rows that matter are the ones about who takes the payment.
| Capability | Sellix, SellHub, SellAuth | RuneSell |
|---|---|---|
| Storefront and product pages | Sellix, SellHub, SellAuthYes, and well built | RuneSellYes |
| Serials, files, dynamic codes | Sellix, SellHub, SellAuthYes | RuneSellYes |
| Discount codes, analytics, customers | Sellix, SellHub, SellAuthYes | RuneSellYes |
| Who takes the payment | Sellix, SellHub, SellAuthA third-party processor you connect yourself | RuneSellRunePay, built for this category — or one you connect |
| Merchant of record | Sellix, SellHub, SellAuthNone. Compliance and VAT sit with you | RuneSellRunePay, when enabled. Chargebacks and VAT sit with it |
| If a risk review goes against you | Sellix, SellHub, SellAuthFind another processor, or stop selling | RuneSellAlready on rails built for this category |
06 — Pricing
Free to use. You pay when you sell something.
There is no monthly plan and no setup fee. The only thing that costs anything is taking the payment, and that is your processor's fee — RunePay's if you turn it on, your own provider's if you connect one instead.
RuneSell
Free to useNothing to pay before your first sale. The only cost is taking the payment, and that is your processor's fee rather than ours — RunePay's if you turn it on, your own provider's if you connect one instead.
- Your shop on its own hostname, or a domain you own
- Products, editions and key pools without a cap
- Serials, files and dynamic codes on any product
- Discount codes, analytics, orders and customers
- Keys encrypted at rest, masked in your dashboard
- Delivery on authorisation, revocation on refund
- RunePay as merchant of record, or your own processor
- No monthly fee, no setup fee, no fee per store
Store creation is not open yet. There is nothing to pay until it is.
When RunePay takes the payment it also holds a reserve against disputes raised after a sale, and releases it back to you. Your exact rate and reserve are confirmed in writing before you sell anything.
Common questions
What sellers ask before they move.
What stops my payments being shut off here too?
Nothing removes risk review entirely, and we will not pretend otherwise — any regulated payment arrangement can end an account. What differs is what triggers it. On a mainstream processor, selling licence keys or game software is itself the trigger, regardless of how clean the business is. RunePay underwrites that category deliberately, so the thing that ends you elsewhere is the thing it was built to carry.
Is RuneSell live?
Not yet — we are pre-launch. The storefront, the seller dashboard, key pools, dynamic codes, file delivery, multi-seller checkout and refund revocation are built and running, but store creation is not open to the public. This page will say so when it is.
What does it cost?
Nothing to use. There is no monthly fee, no setup fee and no cut of your storefront. The only thing that costs anything is taking the payment, and that is your processor's fee — RunePay's if you turn it on, or the provider you connect instead. Never sell anything and you never pay anything.
Do you hold any of my money?
RunePay holds a reserve against disputes raised after a sale, and releases it back to you on a fixed schedule. It is not a fee, and the exact figure is confirmed in writing before you start selling. Every payout arrives with a statement showing what was deducted and why.
Can I use my own domain?
Yes, and it costs nothing extra. Every store gets an address like aldergrove.runesell.com immediately, and you can point a domain you own at it instead. One shop per hostname, so buyers only ever see your brand.
I already sell on Sellix. How much work is moving?
Your catalogue and your key pools. Products are created with their editions and prices, and key pools are pasted in — duplicates within the batch and against existing stock are detected for you. There is no code to write and nothing to host.
If your database leaked, would my keys be in it?
Not in a usable form. Licence keys are encrypted with AES-256-GCM before they touch disk and decrypted only on the delivery path, so a dump, a replica or a stolen backup is not a copy of your stock. Duplicate detection runs against a keyed HMAC rather than the plaintext, so it works without storing anything redeemable.
What does a buyer see if their cart has two sellers in it?
One total, one card charge, one receipt. We split the order per seller behind the scenes because each of you needs your own order and your own payout, but that is our problem rather than theirs. The receipt carries each seller’s reference beside their items.
Can I sell a key and the file it unlocks on one product?
Yes, and this is worth saying plainly because most platforms make you choose. Delivery type decides how stock is counted — a finite pool, minted per sale, or unlimited — and any product can carry attached files regardless of which it is.
Stores open soon.
The storefront, the seller dashboard, key pools, delivery and payments are built and running. When store creation opens, this page will say so — and RuneSell stays free to use.