Skip to main content

​
13 September 2026 · Current product snapshot

This summary describes the local repository, not a production release notice. Check feature availability before relying on a deployed capability.

​
Kardy and Kardy Network

Brown is now Kardy. The chosen public domain is getkardy.com. The kardy | MERCHANT identity marks the business workspace; kardy | NETWORK marks public rewards discovery. They are two surfaces of the same product, not separate customer accounts. Kardy Network lets customers search eligible published rewards, browse categories and locations, inspect shops and continue to joining. An empty marketplace stays empty rather than being filled with fictional offers.

​
Account setup and previews

Signup separates email entry from personal details and password setup. Phone input is country-aware and validated on submission. Merchant signup includes a read-only workspace preview; uneditable example actions appear as placeholders. The login illustration pairs a merchant dashboard with the consumer phone view. Neither preview signs in, saves a profile, issues a pass or creates a membership. See Accounts and access and Joining a programme.

​
Consumer wallet

The browser wallet and PWA remains the place to review current memberships, stamp balances, rewards and recent activity. Its mobile navigation links to Wallet, Places, Rewards and Activity. Adding Kardy to the Home Screen is separate from saving an Apple Wallet or Google Wallet pass. The coffee-claim demonstration now uses a consumer PWA screen. Its iPhone-style notification is a concept, not an implemented push-delivery service. Native passes identify the member; they do not automatically update stamp balances.

​
Merchant operations

  • Overview: shared date/store filters, visits and redemption totals, trend comparisons, location performance and current member progress.
  • Activity list: member search, store/action filters, pagination and recorded event details.
  • Live view: store globe and recent events, checked every 15 seconds while visible—not a customer-location tracker.
  • Rewards and referrals: programme rules, eligible outlets, performance and recorded claims.
  • Branding, join pages and QR signs: saved customer-facing design and joining materials.
  • Members, outlets, team access and multiple brands: organisation-scoped management with role boundaries.
Destructive controls use red styling and confirmation where provided. This does not make every item deletable: scans and redemption events remain append-only.

​
Services with activation requirements

Native wallet issuance, broadcast delivery and billing need the relevant deployment configuration. Merchant MCP is scoped and read-only, requires Owner approval and an active subscription, and does not expose consumer data. Usage allowances remain finite and enforced independently of what a preview displays.