The situation
Consumer brands have wanted a way to reward the person who actually buys the product for as long as there have been products. The usual instruments are all bad in the same way: a coupon book someone has to reconcile, a scratch card that gets forged, a loyalty app nobody installs for a one-off purchase of a ₹200 item.
Every one of them puts work on the customer at the exact moment the brand wants goodwill. Install this. Register that. Wait for the voucher.
So we built the thing we kept describing to people instead.
The question we asked
Not "what features should a rewards platform have." The question that shaped Kyuq was about the packing line: who physically puts the code on the product, and at what point in the day do they do it?
The answer moves everything. Codes go on in a batch, at a printer, before the product ships — often weeks before anybody scans one, and sometimes for a run that never sells through. Whoever is standing at that printer is not going to wait for a network call, and the brand has already paid for the packaging by the time a customer is anywhere near it.
What we decided
A credit is spent when a code is exported for printing, not when it is scanned. You buy credits, generate a batch, export it to print, and that batch is yours. What happens next is between you and your customer.
The obvious alternative — the one almost every platform in this category picks — is to take a percentage of each reward paid out, or to bill per redemption. We rejected it. Redemption billing means a brand cannot know its own cost until after the campaign, and it quietly makes the platform's revenue depend on the brand giving away more money. That is a bad incentive to design into a product you are asking people to trust with payouts.
Burning credits at export makes the cost knowable before a single code is printed. It also makes the pricing legible enough to publish, which is why the per-code rate is on the product's own pricing page rather than behind a call.
What we built
A credit ledger, batch generation, and print export.
Credits are bought in packs, and the per-code rate falls as the pack gets bigger — 1,000 codes at ₹1.00 each down to 10,000 at ₹0.70. Credits stay valid for twelve months and are consumed at export.
Each generated code is single-use and dies on first successful scan, which is what makes it safe to print on a physical product that will sit on a shelf. There is no app: a scan opens a page, the customer enters a UPI ID, and the payout goes to their own bank app.
The batch tooling is the part that gets used most. Codes are generated in runs, exported as a print-ready file, and handed to whoever does the packaging.
What happened
Kyuq is live at rewards.sarvanta.tech, with its credit packs and per-code rates published openly rather than quoted on request.
We are not putting redemption figures on this page. The scan and payout numbers belong to the brands running the campaigns, not to us, and a number we cannot show you the working for is worth about as much as no number at all.
What we would not build
A mobile app. It was the first thing suggested and it defeats the entire premise. The whole point is that someone who bought a ₹200 item gets paid in under a minute without installing anything. An app would have made the product easier to sell to investors and worse for every single person who scans a code.
We also left out campaign analytics dashboards, tiered loyalty levels and referral trees. They are all reasonable features. None of them help the person standing at the printer, which is who this product is actually for.