Skip to main content

What are you looking for?

Explore our services and discover how we can help you achieve your goals

Client Workspace

Tokenized Loyalty and Rewards: Product Questions Before Choosing Blockchain

Before choosing blockchain for a loyalty program, settle ten product questions about point value, transfer, redemption, partner settlement and member onboarding; most programs that answer them honestly need a well-run points database, and a token fits only when members must hold and move value across companies. This Netbase guide gives the screen and the operating duties.

Book a solution review See the digital wallet and payments solution

By Netbase Commerce and Platform Engineering Desk · Reviewed by David (CEO) · Updated · 9 min read

star

This guide is for loyalty product owners, marketing technology leads and CTOs who have been asked to "put the points on a chain". It sits in the emerging technology guides of the IoT development pillar and leads into blockchain development when a ledger is the right tool.

In this guide

Which product questions decide whether loyalty points need a blockchain?

A loyalty point is a promise from a company to a member. The technology choice follows from how that promise behaves, so the screen starts with the promise, not the chain. Ask the ten questions below in a product workshop with marketing, finance, legal and engineering in the room, and write each answer down.

Value. (1) What is one point worth, and who may change that value later? (2) Do points expire, and who books the unredeemed balance as a liability? If finance must be able to change the value or expiry rules at any time, a token that members hold outside your systems makes that harder.

Transfer. (3) May members send points to each other, sell them or move them to an outside wallet? (4) If a transfer turns out to be fraud, who reverses it? A program that answers "no transfers" or "we must reverse fraud" has removed most of the reason for a public ledger.

Redemption. (5) Where are points spent: your own shop, partner shops, or anywhere that accepts the token? (6) Can a member pay part in points and part in cash, and how are refunds handled when the cash part comes back?

Partners. (7) Do several companies issue and accept the same points, and do they distrust one central operator enough to want a shared record? This is the strongest case for a ledger. (8) How do partners settle with each other today, and would a shared record replace that settlement or only duplicate it?

Members. (9) What must a member install or learn before the first reward? A wallet, a seed phrase or a network fee before the first earn loses most members at sign-up. (10) What happens when a member loses access: can support restore the balance?

If most answers point to central control, reversible transactions and one issuer, the program needs a ledger in a database with an audit trail. If several issuers, member-held value and portable collectibles appear in the answers, read the architectures below.

Database ledger, hybrid or on-chain token: how do the options compare?

Option What it is Main risk Choose it when
Points database ledger Append-only transaction table with balances, audit log and admin reversal One operator must be trusted; partners rely on reports One issuer, reversible transactions, members never hold points outside the app
Hybrid Database stays the system of record; selected items (badges, tickets, collectibles) are minted as tokens Two records to reconcile; support for both One issuer wants portable collectibles or proofs while points stay central
Fully on-chain token Points are fungible tokens (for example ERC-20) or non-fungible tokens (ERC-721) held in member wallets Legal classification, key loss, fees, no reversal Several issuers share one point, members must hold and move value, and legal review has cleared the design

The ERC-20 token standard describes interchangeable units, which mirrors a classic point, while EIP-721 describes unique tokens, which suits tickets, badges or collectibles. Neither standard answers the product questions above; it only fixes how a token is represented once you have decided to have one.

When is the hybrid the honest middle?

The hybrid is often the honest middle. The points balance, the expiry rules and the fraud reversal stay in the database where finance and support can act, while a small number of items that benefit from being owned outside the program become tokens.

What operational duties does a token add?

  1. Reconciliation owner

    Name the person who reconciles the token supply against the loyalty database every day, and decide which record wins when they differ.

  2. Liability and breakage

    Agree with finance how outstanding tokens are counted as a liability, and how expired or abandoned tokens are written off when no one can burn them for the member.

  3. Fraud and reversal

    Write the rule for a fraudulent earn or a stolen wallet before launch; on a public chain you can block redemption in your own shop, but you cannot undo the transfer.

  4. Legal classification

    Ask counsel whether the token is a loyalty point, a utility token or a financial instrument in each country where members live, and whether a transferable token changes the answer.

  5. Key custody

    Decide who holds the issuing keys and the admin roles of the contract, how they are split between people, and how a lost key is handled.

  6. Member support

    Train support on wallets, network fees and lost access, and decide whether the program offers a custodial wallet so that members never see a seed phrase.

  7. Contract review

    Plan an external review of the token contract before value moves; smart contract audit preparation covers scope and tests.

Legal clarity on whether a loyalty token is a security, a utility token or a loyalty point should come before launch, and the review depends on the company's jurisdiction, where members live and how the token is structured. In the EU, the Markets in Crypto-Assets Regulation exempts offers of crypto-assets usable only within a limited network of merchants from its white-paper duty, which is one reason many programs keep tokens inside their own network.

Where AI fits

AI helps with the analysis around the decision. A model can summarise transaction exports to show how members actually earn, redeem and abandon points, draft the reconciliation checks between the token supply and the database, and flag unusual earn patterns for a fraud analyst to review. Engineers and analysts still confirm every rule, because a reconciliation check that silently passes hides a liability. Netbase works with the major commercial and open-source AI tools and models, chosen per project.

What delivery record exists, and what does not?

Netbase has delivered loyalty software on a conventional stack. For a loyalty and rewards technology company (client not named), Netbase delivered a headless multi-store reward shop platform on Magento 2 Open Source with a Next.js front end: individually branded reward shops per client program, a hybrid points-plus-cash checkout, and merchandise, gift cards and travel bookings with a multi-vendor module. The reward shop record describes that work.

That record is the reason this guide starts with redemption and partner questions: points-plus-cash checkout, refunds and vendor fulfilment are where a loyalty program spends most of its engineering, whatever record holds the balance. The commerce platforms Netbase has delivered include WooCommerce, Magento 2, Laravel and headless commerce.

Netbase designs, builds, integrates and runs software in every technology that large software market players offer, and blockchain applications are part of that scope. No Netbase record publishes a tokenized loyalty program, token volumes or member outcomes, and none is claimed here.

Published security practices include secure code review and version control, role-based access control, MFA for admin dashboards, and vulnerability scanning and penetration testing. Delivery follows a six-step lifecycle from discovery to ongoing support.

Most Netbase projects are delivered on fixed-price contracts.

Alternatives: who answers the product questions, and how to choose

A loyalty platform vendor. Many loyalty-token platforms sell a ready program with wallets and a dashboard. Choose one when your program fits its model and you accept its rules on transfer and custody; ask the vendor to show the actual wallet, partner and integration features for your planned program.

An in-house product team. Choose this when you already run the loyalty database and have finance and legal owners for the duties above; add a blockchain specialist only for the contract and custody work.

A build partner. Choose a partner such as Netbase when the program must integrate with your commerce, CRM and partner systems and the decision between database, hybrid and token is still open. Related reading: subscription billing and entitlement systems covers the ledger and entitlement patterns a points database reuses, and e-commerce development covers the redemption shop.

When not to tokenize at all. Do not tokenize when there is one issuer, members never need to hold points outside your app, and fraud must be reversible. A points database with a clean audit log is cheaper to run and easier to explain.

Limits of this guide

  • It does not give legal advice; token classification depends on each jurisdiction and the token's design.
  • It does not compare chains or loyalty-token vendors by name.
  • It covers loyalty and rewards; payment wallets and stored value are a separate decision, see digital wallet and payments.

Plan the next step with a Netbase consultant

Frequently asked questions

Usually not. A single company issuing points that members spend in its own shop is best served by a database ledger with an audit trail. A blockchain earns its place when several companies issue and accept the same points and want a shared record none of them controls.

On a public chain a transfer cannot be undone. A program can block redemption of the stolen tokens in its own shop, but the token stays where it was sent, so many programs keep points in a database and tokenize only collectibles.

It depends on the jurisdiction and the design. A token that can only be spent in a limited network is treated differently from one that members can sell, so counsel should review the design before launch.

Decide the value and expiry rules, whether transfers are allowed, where points are redeemed, which partners settle against them and what a member must install. With those answers, the architecture choice and the estimate become specific.

Next step

If your team is weighing a points database against tokens, book a solution review and bring the answers to the ten questions.

IoT development with AI analytics that connects devices to the business IoT development with AI analytics that connects devices to the business

Netbase provides IoT development for manufacturers, logistics operators and product companies to connect devices and sensor data to the business platforms that act on them, with AI that spots anomalies and forecasts what needs attention. We design the device-to-cloud data path, build the back end, dashboards and integrations, and treat security, data ownership and AI as design decisions.

Learn More
line
AI-enabled ecommerce development for merchants who outgrew templates AI-enabled ecommerce development for merchants who outgrew templates

Netbase provides custom ecommerce development for merchants that have outgrown templates, to turn traffic into orders with less manual work, using AI for search, recommendations and catalog work where it pays. We build on WooCommerce, Magento 2, Laravel and headless stacks; 4over4, whose store gained an AI recommendation engine, reported 82% more revenue within six months.

Learn More
line
Blockchain development: smart contracts, wallets and tokenisation built to last Blockchain development: smart contracts, wallets and tokenisation built to last

Netbase designs and builds blockchain applications: smart contracts, wallet integrations, tokens and permissioned ledgers, connected to the web, mobile and business systems you already run. We start by checking whether a blockchain is the right tool at all, test every contract against known attack patterns and plan an independent audit before anything holds real value.

Learn More
line
Digital wallet and payments with AI: balances, transfers, merchant payments and payouts on one ledger Digital wallet and payments with AI: balances, transfers, merchant payments and payouts on one ledger

A digital wallet from Netbase is web and mobile software where customers hold a balance, top up, pay merchants, send money to each other and receive payouts, while operations and finance teams reconcile every movement on one ledger. We design and build it custom on licensed payment partners, and add AI that flags fraud while analysts decide.

Learn More
line

Work with Netbase remotely

Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.

Contact Netbase

Discuss a project

Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.
Project enquiries

project@netbasejsc.com

WhatsApp

+84 937 869 689

Office address

91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam

Get in touch

Tell us what you want to build, modernize, or operate.

Tell us what you want to build, modernize, or operate.

Contact Netbase