Anything a winner redeems as text: Steam keys, gift card codes, Discord Nitro links, coupon codes, account vouchers. Paste them one per line (optionally as CODE,Label) or upload a CSV and pick which columns hold the code, an optional label, and an optional image URL. Duplicates are detected and skipped automatically.
Prize Pools & Code Delivery
Deliver Prize Codes to Winners Automatically, From an Encrypted Vault
Import your codes once. When a Discord giveaway or auction ends, each winner gets one reserved and revealed privately in their claim ticket. Nobody else sees it, not even your staff.
A prize pool holds your prize codes: Steam keys, gift card codes, Nitro links, anything a winner redeems. Import them by pasting one per line or uploading a CSV, duplicates are skipped automatically, and every code is encrypted with AES-256-GCM before it touches the database.
You can link a pool to any giveaway or auction that uses claim tickets. When it ends, each winner gets one code reserved from the pool, and when they claim, the code is revealed privately inside their ticket. Your staff see delivery status, never the code, and every reveal is recorded in the server audit log.
Delivery can be instant or verified first: switch auto-deliver off and each winner's code stays locked after they claim. You check their submission in the ticket, press the staff-only release button right there in Discord, and the winner reveals the code themselves. Everything else, reservation, delivery records, rerolls, stays automatic.
How It Works
From imported codes to delivered winners, in the order it happens
- 1
Import your codes into a pool
Paste your codes one per line, optionally as
CODE,Label, or upload a CSV and map the columns yourself: the code column is required, a label and an image URL are optional. Duplicates are matched by hash and skipped, so re-importing an updated file never creates doubles.Every code is encrypted with AES-256-GCM before it is stored; the vault never holds plaintext. The dashboard shows labels, images, and statuses only, a dedicated sensitive role permission decides who can manage pools, and every decrypt is recorded in the server audit log with who triggered it.
5 imported, 1 duplicates skipped - 2
Link the pool when you build a giveaway or auction
In the builder, link your pool right from the prize field and pick what the launch advertises. Three modes:
My own title and image
You write the prize title; the pool fulfills it. Each winner receives one of the pool's codes. Best when the codes are identical, like a stack of $10 Steam gift cards.
A random prize from the pool
One random code is picked and locked at launch, and its label and image become the public prize. Two launches can never advertise the same code.
A specific prize from the pool
Pick the exact item from a searchable list. The prize title and image prefill from it, the code locks at creation, and the winner is guaranteed to receive exactly it. Single-winner prizes only.
Prize pools pair with claim tickets: each winner gets a private ticket channel where their code is revealed, you see who has claimed and who has not, and a winner who never claims is rerolled at the deadline, their code flowing to the replacement automatically. Linking a pool enables them together in the builder.
- 3
Winners claim; codes reveal privately
When the giveaway ends, each winner gets one code reserved from the pool. On claim, the code is revealed privately: an ephemeral message plus a persistent winner-only "Reveal my code" button that stays in their ticket. Staff working the ticket see the delivery status, never the code itself.
Auto-deliver is a toggle. On, the code is revealed the moment the winner claims. Off, you verify the winner in the ticket first, then release their code. You can release it with a staff-only button right inside the claim ticket, without leaving Discord, or from the dashboard. Either way the winner's reveal unlocks the moment you release, and only they can see the code.
You are in the ticket as
claim-kai— private: the winner and your staff
ScopliDropAppToday at 2:31 PMScopliDropAppToday at 2:31 PMCongratulations @kai, you won Starforge Odyssey. Your code is reserved for you.
Auto-deliver off: staff release first, then the winner reveals. Try both buttons as each person.
- 4
Stock manages itself
When a winner is rerolled or their claim deadline expires, their reserved code is released back to the pool automatically and the replacement winner gets one reserved. Delivered codes are burned: they will never be issued to another winner.
A pool cannot be deleted while codes are still reserved for live winners, so an in-flight giveaway cannot lose the prizes it advertised.
- 5
Edit, rotate, or revoke codes
Each code carries an editable label and image. An invalid or compromised code can be rotated: the replacement takes its place and the winner's reveal button serves the new one. Codes you no longer trust can be revoked, and codes you handed out yourself can be marked as delivered with a recipient record.
Every code is therefore always in one of four states: available, reserved, delivered to a named winner, or revoked. The pool table doubles as a delivery record.
Sample pools. Open one to see its codes and their status.
Setups This Enables
The same flow, arranged three ways
Mystery drops
Import codes without labels into a pool named "Mystery Steam Game". The embed advertises the pool name; the winner discovers what they won when they redeem the key.
Recurring prize rotation
A recurring schedule in random-prize mode: load a bundle of labeled codes once, and each occurrence advertises a different one until the pool runs dry. At that point the schedule skips with a visible reason instead of launching without a prize.
Auction fulfillment
Bidders commit their coins to a specifically advertised item, and the winner claims it through the same private ticket flow, code revealed on claim.
The Final Piece of Giveaway Autopilot
Claim tickets handle the claiming, recurring schedules handle the launching. Delivery was the last manual step.
We built claim tickets so winners confirm their prize in a private channel, with deadlines that reroll no-shows automatically. We built recurring giveaways so a schedule relaunches itself week after week without anyone thinking about it. One step still needed a human: someone had to hand the winner their prize.
Prize pools close that last step. The code sits encrypted until its winner claims, nobody on your team ever handles it, and the audit log records every reveal, so "who saw this code" always has an answer. To our knowledge, no other Discord giveaway platform delivers prize codes end to end. Everywhere else, delivery is the host copy-pasting keys into DMs.
Put the pieces together: a recurring schedule in random-prize mode with auto-deliver on, or an auction on a pool item. The whole engagement loop then runs on autopilot. The giveaway launches, advertises its prize, draws winners, delivers codes, rerolls no-shows, and restocks itself, with nobody at the keyboard.
Combine It With
The features prize pools plug into
Prize Pool Questions
Encryption, rerolls, dead codes, and which plan you need
Related Features
Recurring Giveaways
Configure once and relaunch on a cadence: every Monday, the 1st of the month, any rhythm.
Explore Recurring GiveawaysTask Verification
How every task gets verified, from instant Discord checks to video codes.
Explore Task VerificationPrizes That Deliver Themselves
Encrypted at import, reserved at the draw, revealed only to the winner, and accounted for in the ledger forever.