Running a programme · For a brand's operations team
Running a rewards programme
A label earns what its batch's campaign says, or nothing. The money moves on your own payment account, and every rule that stops it is a hold a person can release, not a silent rejection.
Campaigns #
A campaign is the offer: points or cashback, the amount per scan, a start and end, a budget, and an optional hold. A batch is attached to at most one campaign, and moving a batch between campaigns is one transaction, so a batch is never left with no campaign.
Only a code the buyer had to reach earns: the hidden code under the panel, or the reward QR inside the pack. A code printed openly on the outside would pay anyone who scanned a shelf, so a single batch cannot carry a campaign at all.
Budgets #
The budget is computed from the claims, never stored as a counter, so it cannot drift from the ledger. At 80% and at 100% of a budget the brand is emailed. Once it is spent the claim card is not shown at all — nobody is offered what is gone — and two scans racing for the last of it cannot both earn.
Caps and holds #
Claims and cashback per member, and total spend per brand, are capped over rolling 24 hours, and a burst from one phone or across brands is flagged. A claim that breaks a rule is held, not rejected: the money stops before it leaves, and a person releases or rejects it. Automatically rejecting a real electrician is worse than a queue.
PAN and TDS under section 194R #
A channel reward is a benefit given in the course of business. Once a member's successful payouts cross the section 194R threshold in a financial year, a PAN is required before the next payout, and it is stored encrypted and visible only to the brand that collected it. The console exports a TDS file per financial year for your finance team.
Payouts on your own gateway #
Each brand connects its own Razorpay X or Cashfree account. AVRA holds no float and is not in the money's path; a payout's final state comes from the gateway's signed webhook, not from polling. Payout credentials are encrypted per brand and cannot be read back, by anyone, including us.
What the member is told #
Every credit, hold, voucher, payout and failure is a WhatsApp message on a pre-approved template — see the eight templates.
Last reviewed 18 Sep 2026 · Something wrong? connect@avrascan.com