Platform overview

Understand how your organization, the customer wallet, and Kardy’s backend work together.

Kardy has two application surfaces. Your organization uses the management portal; customers use the browser wallet. The backend stores memberships and confirms operations.

The repository has three projects: the consumer Next.js app (public site and browser wallet), the merchant Next.js app, and this standalone Mintlify docs site. All three use a thin purple navigation-progress indicator. Documentation is also linked from the public footer and the Support help panel.

Where information lives

Component	Responsibility
Organization portal	Configure the programme, manage outlets, and operate scans.
Customer wallet	Join programmes, present a QR, and view membership progress.
Backend	Authenticate requests, enforce organization access, and record changes.
Wallet integration boundary	Sign native QR passes when issuer credentials and scanner readiness are configured.

The apps use Next.js and TypeScript, with InsForge for authentication and data. Merchant-only, read-only agent access is documented in Merchant MCP. It uses scoped Owner-approved OAuth connections or expiring manual keys; there is no consumer MCP or general-purpose database API.

For a rollout, read QR and security, wallet integrations, and availability.