Notanother
loyaltyprogram.
Punch cards, promo codes, and deal marketplaces all share one flaw: the coupon is a string, not a voucher.
Flicp treats every coupon as a funded, scoped, provable digital item with a life of its own — issued by a brand or a venue, verified by one network, and settled without spreadsheets.
A code dies in an inbox.
Promo tools mint copyable strings with no funding model and no lifecycle. Most expire unseen; the rest leak.
20% off
Product-scoped · venue-universal · hard-capped
0xF11CP…LEDGER
The old world · no funding · no arbiter · no record
Points sit in a silo until they expire.
Traditional loyalty locks value inside one business's program. It doesn't travel, and every report must be taken on trust.
20% off
Product-scoped · venue-universal · hard-capped
0xF11CP…LEDGER
The old world · no funding · no arbiter · no record
One code, infinite screenshots.
No double-spend protection, no arbiter, no proof. The budget drains and nobody can say where it went.
20% off
Product-scoped · venue-universal · hard-capped
0xF11CP…LEDGER
The old world · no funding · no arbiter · no record
Flicp treats every coupon as a funded, scoped, provable digital item. Everything else follows from that.
20% off
Product-scoped · venue-universal · hard-capped
FLICP-2049-XR
Where the categories end and Flicp begins.
Who funds the discount
- Traditional loyalty
- Ambiguous — venues absorb it and chase reimbursements
- Promo-code tools
- Nobody — codes are created without a funding model
- Flicp
- The issuer, always. Issuance is liability, capped server-side
Where a coupon works
- Traditional loyalty
- Locked to one program at one business
- Promo-code tools
- Anywhere the string is pasted — including where it shouldn't
- Flicp
- Exactly where its scope says: products for brand coupons, the home venue for venue coupons
Double-spend protection
- Traditional loyalty
- Per-store databases that don't talk to each other
- Promo-code tools
- None — one code, infinite screenshots
- Flicp
- One redemption arbiter — first server-accepted redemption wins, everywhere
Fraud & resale
- Traditional loyalty
- Points fraud and account gaming
- Promo-code tools
- Codes leak, get scraped, get resold
- Flicp
- Venue coupons are soulbound — resale is impossible by construction
Proof of redemption
- Traditional loyalty
- Monthly reports you have to trust
- Promo-code tools
- A row in someone's analytics tool
- Flicp
- An immutable record on FlicpLEDGER, our private enterprise chain
Life after issuance
- Traditional loyalty
- Points sit in a silo until they expire
- Promo-code tools
- The code dies in an inbox
- Flicp
- Wallet-held vouchers: gift, trade P2P, win in drops and auctions
Settlement for venues
- Traditional loyalty
- Invoices, disputes, and waiting
- Promo-code tools
- Doesn't exist
- Flicp
- Redemption records drive settlement — no invoice chasing
Developer surface
- Traditional loyalty
- A CSV export if you're lucky
- Promo-code tools
- A REST endpoint and good luck
- Flicp
- Typed SDK, sandbox, signed webhooks, idempotency, offline mode, real POS
Kill-switch control
- Traditional loyalty
- Email support and wait
- Promo-code tools
- Deactivate the code, hope caches expire
- Flicp
- Pause an agreement and validation stops instantly, at every venue
Every coupon knows exactly where it works.
Flicp coupons follow one geometry. A brand coupon is scoped to products and works across approved venues. A venue coupon works on anything, but only at that venue. A coupon that travels is product-scoped. A coupon that stays home is product-universal.
Brand coupons: product-scoped, venue-universal — the offer follows the product, not one store's program.
Venue coupons: venue-scoped, product-universal — a store rewards its whole basket without leaking spend elsewhere.
Deterministic stacking: brand coupons apply at the product layer, venue coupons at the cart layer — carts never surprise anyone.
The same stacking rules run as shared test vectors across backend, SDK, and POS.
Every discount is funded by its issuer before it exists.
On Flicp, issuing a coupon means accepting the liability for it. Discounts are capped server-side, redemptions are arbitrated centrally, and agreements between brands and venues act as an instant kill-switch.
Issuance is liability — the issuer funds the discount, so offers can't be hollow.
Every coupon carries hard caps: max redemptions and max total discount, enforced by the server.
One redemption arbiter — the first server-accepted redemption wins, across every venue.
Agreements gate validation. Pause an agreement and validation stops instantly.
Every coupon's life is an immutable record.
FlicpLEDGER, our private enterprise chain, anchors the full lifecycle of every coupon — issuance, transfer, redemption, expiry. Nobody reconciles from screenshots and monthly reports.
Dual-signature model: Flicp pays the network cost, the actor signs the intent — provable actions with zero friction.
Venue coupons are soulbound — they cannot be resold or transferred, so scalping is impossible by construction.
Redemption is terminal — a redeemed coupon is burned, not marked in a spreadsheet.
The whole lifecycle is anchored: issuance, purchase, transfer, redemption, expiry.
Elsewhere a coupon is a code. Here it's a voucher with a life.
Flicp coupons live in a wallet and keep moving: gift them, trade them on the marketplace, win them in drops and auctions. Value that would expire in an inbox stays in circulation.
One wallet holds every coupon, with its full history.
Peer-to-peer exchange: gift or trade brand coupons instead of letting them expire.
Venue coupons stay soulbound — the marketplace can't be gamed by scalpers.
Timed drops and live auctions turn offers into events, not spam.
Built like a payments network, not a marketing plugin.
Flicp ships the surface serious teams expect: a typed SDK with idempotency and offline mode, a real POS, signed webhooks, and a developer model where access can be revoked instantly.
@flicp/sdk covers coupons, drops, auctions, loyalty, POS sessions, disputes, payouts, and webhooks.
Idempotency keys, retries, and offline mode are built in — not left as an exercise.
Organisations nominate developers; revoking a nomination kills that developer's keys instantly.
FlicpPos runs the counter; the same rule engine runs everywhere.
Different for you, specifically.
Brands
You fund it, you control it, you see it.
Spend can't leak
Every coupon carries hard caps on redemptions and total discount, enforced by the server — not by hope.
Live truth, not monthly reports
Follow claims, transfers, and redemptions as they happen, anchored on FlicpLEDGER.
Instant kill-switch
Pause a venue agreement and validation stops immediately. No support tickets, no cache lag.
Offers follow your product
Brand coupons are product-scoped, so the promotion belongs to your product — not to one store's loyalty silo.
Partners
You do the work, you get paid — automatically.
Settlement without invoices
Server-arbitrated redemption records drive reimbursement. No spreadsheets, no chasing.
Your own coupons, your whole basket
Venue coupons are product-universal at your counter — reward the visit, not one SKU.
Forged coupons can't reach you
Validation runs against the network, so a screenshot or copied code dies before checkout.
Your counter, your choice
Run FlicpPos, or plug your existing system into the SDK with offline mode built in.
Platforms
A coupon layer you don't have to build.
Resale fraud solved by design
Platform coupons are soulbound — they can't be transferred or scalped, ever.
Co-funded promotions
Split funding with brands under explicit budget caps and revenue-share terms.
Carts never surprise you
Deterministic two-layer stacking: product-layer brand coupons, cart-layer platform coupons. Same result, every time.
Control that scales
Agreements gate every validation, so one pause propagates everywhere instantly.
Customers
Coupons that behave like things you own.
One wallet, everything in it
Every coupon you claim, win, or receive lives in one place — with its history.
Can't be faked, can't be double-used
Each coupon is verified against the network at redemption. Screenshots don't work.
Gift it or trade it
Won't use it? Send it to a friend or list it on the marketplace instead of letting it expire.
Earn while you spend
FlicpTokens and loyalty tiers accrue on real purchases — and gifts can be claimed right from WhatsApp.
Developers
An integration surface, not an afterthought.
A real SDK
@flicp/sdk ships typed clients for coupons, drops, auctions, loyalty, POS, disputes, payouts, and webhooks.
Failure-proof by default
Idempotency keys, retry handling, and offline mode are part of the SDK — not your problem to invent.
Same rules everywhere
Stacking and validation logic is verified by shared test vectors across backend, SDK, and POS.
Keys with a kill-switch
Orgs nominate developers; a revoked nomination instantly kills the keys. Rotation and one-time reveal built in.
Pick your side of the counter.
Walk the full loop, check the pricing, or tell us what you want to launch — the network is ready when you are.