Skip to content
CAFENITYThe Digital Operating System for Café Shops
Sign inStart free

CAFENITY / platform/oneqr

OneQR is lifetime identity, not a data container.

An opaque handle connects a customer to permitted next steps.

CAFENITY connected customer, operator, and workspace surfaces

CONNECTED SURFACES

Customer MobileDiscover and begin intent when published.
Operator MobileSee the next role-aware operating signal.
Canonical WorkspaceConfigure and govern the authoritative record.

FOUR GOVERNED MODES

ProfileIdentity, relationship, preferences, consent, loyalty, recovery.
PaymentBegins or associates transaction-specific payment intent.
RetentionConnects verified activity to reward and return eligibility.
PromotionResolves tenant-specific offer eligibility dynamically.

Identity ≠ consent ≠ campaign source ≠ tenant authority ≠ payment authority. A scan is never a purchase or payment.

The operator problem

QR shortcuts often expose identity or merge consent with payment.

How CAFENITY responds

CAFENITY resolves an opaque OneQR handle against server-owned authority.

Concrete operating use

  • Connect a repeat visit
  • Attribute a source path
  • Begin identity only with consent

Current capability state: Approved architecture — not yet live

Truth boundary: OneQR never contains PII, tenant IDs, consent, loyalty balance, or payment credentials.

Explore OneQR