Loyalty a player owns, and finance can still account for.
Tokenization turns a loyalty balance, a membership tier, or a collectible into an asset the player holds and can verify. neoMint™ is a token factory for those three things, with sponsored gas and passkey wallets so a player never sees a seed phrase, a network fee, or a chain name. Every design is classified against MiCA before it deploys.
NEOPOINTS · token specification
configuredclassification reviewed before issuance
Highlighted fields are the ones a regulator reads first. Every token is configured against them before a contract is deployed.
€0
Gas paid by the player
4
Token standards supported
12 min
Approved spec to deployed contract
0
Seed phrases shown to players
Four things worth putting on a chain
A token earns its place when the player benefits from verifying something: supply rules, a tier they were promised, a win that happened. Where a database row would do, we use a database row.
Loyalty balances
Points held as an on-chain balance, so a player can see the supply rules, the expiry, and the burn history that govern them.
Membership passes
Tiered access as a token a player holds: VIP tables, tournament entry, withdrawal-priority queues. Tier changes are visible on-chain.
Tournament trophies
A permanent, verifiable record of a leaderboard finish that survives the operator archiving the tournament.
Jackpot provenance
A hand that pays a life-changing jackpot gets an anchored record of the round: seed, outcome, and timestamp, tied to the neoProof™ verifier so the win is checkable years later.
The chain is invisible, deliberately
Wallets are created silently at first award through account abstraction. Gas is sponsored by the operator. Chain names never appear in the player interface.
- ERC-4337 smart accounts created silently at first award
- Passkey or existing login: no seed phrase, no extension, no recovery ritual
- Paymaster-sponsored gas: the player's cost is zero, always
Steps the player takes
7 → 2Typical web3
neoMint™
gas paid by paymaster
player cost €0.00
Four standards, picked by what the token has to do
Standard selection is an engineering decision with cost and capability consequences. These are the four we deploy and what each is for.
| Standard | Shape | Typical use | Why this one |
|---|---|---|---|
| ERC-20 | Fungible balances | Loyalty points, credits | Optional non-transferable mode |
| ERC-721 | Unique items | Trophies, provenance records | One-of-one, individually addressed |
| ERC-1155 | Mixed batches | Passes, seasonal collectibles | Cheap batch mint and transfer |
| ERC-4337 | Account abstraction | Every player wallet | Sponsored gas, passkey recovery |
Provenance
An NFT records something unique and worth keeping: a tournament win, a jackpot hand, a founding membership. It is the wrong tool for anything whose pitch to the holder is a return.
What we build
Trophies, membership passes, jackpot provenance, and founding-member records, issued for something the holder did and tied to a verifiable event in the platform's anchored log.
How it stays honest
Metadata pinned and content-addressed so the artefact cannot be swapped after issue. Royalty and transfer policy set at deployment. No operator-run venue where the items trade.
What we decline
Engineered scarcity, roadmaps implying future value, fractionalised collections, and anything whose pitch to the holder is a return.
Supply discipline, and a number finance can book
Loyalty-token programmes fail in two ways: supply inflates because nothing burns it, or nobody told the finance team that outstanding tokens are a liability. Both are design decisions, made before launch.
Design
Earn rules and sinks defined together
A token that is only ever earned inflates until it is worthless. Sinks (what the token is spent on and burned for) are specified in the same session as the earn rules.
Model
Simulated against real behaviour
Issuance is modelled against your own player activity: earn rates, redemption propensity, and expiry. The output is a projected circulating supply curve.
Account
Booked as a liability from day one
Outstanding tokens are a deferred obligation on your balance sheet. The reporting treats them that way from launch.
Operate
Supply visible, controls live
Circulating supply, burn rate, and redemption velocity sit in the operator dashboard. Emission and expiry parameters are versioned configuration with an audit entry per change.
Supply controls available at design time
Awards fire from rules you already maintain
The token engine reads the same player graph and CRM triggers as the existing bonus engine. A campaign that awards points can award tokens without a second rules system.
{ "symbol": "NEOPOINTS", "standard": "erc20", "transferable": false, "expiry_months": 18, "jurisdictions": ["MT", "EE", "RO", "CW"], "classification_review": "required"}// 202 Accepted, deploy is gated on review{ "token_id": "tkn_4c81de", "status": "awaiting_classification_review", "estimated_deploy": "12 minutes after approval"}Deploy is gated on review
The endpoint returns 202 and waits. A token cannot reach production without a completed classification assessment.
Idempotent awards
Every award takes an idempotency key, so a retried campaign never double-mints into a player's balance.
Liability in the response
Supply calls return the euro-denominated liability alongside circulating supply.
Runs beside your bonus engine
Tokens and conventional points can run in parallel indefinitely.
The token work we turn down
The boundaries on this module are stated plainly because the gap between a good idea and a regulatory problem is narrow.
No investment framing, anywhere
No price, no yield, no return, no appreciation, no buyback. Loyalty tokens are a redemption right against your own brand.
We do not create a secondary market
Non-transferable is the default. Where transferability is enabled, we do not operate, list on, or take a fee from any venue where your tokens trade.
NFTs here are provenance
Trophies, passes, and jackpot records. No drops engineered for scarcity, no floor-price mechanics, and no roadmap promising future value.
Classification is reviewed before deployment
Every token design is assessed against MiCA's asset-referenced and e-money categories before deployment, and the deploy call refuses to proceed without that assessment.
What CRM and finance teams ask
Players dislike seed phrases, gas fees, and network names, and they never encounter any of the three here. Wallets are created silently at first award using account abstraction and authenticated with a passkey or the existing login. Gas is sponsored by the operator.
Model what tokenizing your loyalty programme does
A 45-minute session with a solutions architect and a compliance lead: the classification question answered for your design, a projected supply curve against your own activity, and the liability figure finance will book.