Skip to content
SPECIFICTION
Get listed

Loyalty Interchange Protocol

github.com

Free plan WebLinuxAPISelf-hosted
Visit github.com
Spec score 8.5 #7 of 39 in Loyalty Program Software

What it is

Loyalty Interchange Protocol (LIP) is an open-source loyalty platform and vendor-neutral transaction protocol for restaurant technology teams that own integration work. Its checkout lifecycle includes member lookup and enrollment, balances and ledger history, order evaluation, accrual, redemption, reversal, and refund-safe adjustments. Its restaurant order model represents items, modifiers, discounts, fees, taxes, tips, tenders, and totals across channels such as drive-thru, kiosk, web, mobile, pickup, delivery, and catering. Supported program types include points, visits or stamps, wallet credit, paid membership, and hybrid multi-account programs.

The `/platform/v1` API covers profiles, consent, behavioral events, segments, campaigns, connectors, imports, analytics, and attribution. The maker provides an Apache-2.0 reference stack for self-hosting with Docker Compose or Node.js 22 and newer. Storage described includes SQLite-backed local storage and tenant-scoped PostgreSQL for multi-instance use. Customer sign-in remains external. LIP 0.2.0 is described as pre-1.0 infrastructure, not a turnkey no-code marketing service; CSV member imports are limited to 1 MiB and 1,000 rows.

Spec sheet

Purpose
LIP is an open-source loyalty platform and vendor-neutral transaction protocol for restaurant technology teams.Read 8 Oct 2026 · github.com
Product
LIP is an open-source loyalty platform and vendor-neutral transaction protocol for restaurant technology teams.Read 8 Oct 2026 · github.com
Intended users
The maker describes the product for POS and ordering platforms, restaurant integrators, and multi-unit technical teams.Read 8 Oct 2026 · github.com
Deployment
The maker documents self-hosting with Docker Compose or Node.js 22 and newer with npm.Read 8 Oct 2026 · loyalty-interchange.mintlify.app
Security
The security policy says implementations must use TLS, authenticate non-health endpoints, avoid direct customer identifiers in logs or idempotency keys, and encrypt sensitive identity claims at rest.Read 8 Oct 2026 · github.com
Support
The repository directs users to its support guidance and asks security vulnerability reports to be sent privately to maintainers.Read 8 Oct 2026 · github.com
Checkout lifecycle
It supports member lookup and enrollment, balances and ledger history, order evaluation, accrual, redemption, reversal, and refund-safe adjustments.Read 8 Oct 2026 · loyalty-interchange.mintlify.app
Engagement
The platform API supports customer profiles, marketing consent, behavioral events, imports, segments, campaigns, connectors, and attribution analytics.Read 8 Oct 2026 · github.com
Engagement tools
The `/platform/v1` API covers customer profiles, consent, behavioral events, segments, campaigns, connectors, imports, analytics, and attribution.Read 8 Oct 2026 · loyalty-interchange.mintlify.app
Guest wallet
The reference guest wallet is a responsive BFF using OIDC Authorization Code with PKCE, with access tokens and merchant credentials kept server-side.Read 8 Oct 2026 · github.com
Identity
A BFF can validate Clerk, Auth0, or generic OIDC access tokens and map provider identities to LIP member IDs.Read 8 Oct 2026 · github.com
Integration
The repository describes a typed Square Orders adapter with webhook signature verification and synthetic certification fixtures.Read 8 Oct 2026 · github.com
Limits
Platform API CSV member imports are limited to 1 MiB and 1,000 rows.Read 8 Oct 2026 · loyalty-interchange.mintlify.app
Loyalty lifecycle
It supports member lookup and enrollment, balances and ledger history, order evaluation, accrual, redemption, reversal, and refund-safe adjustments.Read 8 Oct 2026 · loyalty-interchange.mintlify.app
Maturity
The maker describes LIP 0.2.0 as pre-1.0 infrastructure and says repository tests and fixtures do not establish independent adoption or production SLO attainment.Read 8 Oct 2026 · opensource-loyalty.vercel.app
Maturity limit
The README says LIP is not yet a turnkey no-code marketing service for restaurants without an integration team.Read 8 Oct 2026 · github.com
Order model
Its foodservice order model includes items, modifiers, discounts, fees, taxes, tips, tenders, totals, and rules for restaurant ordering channels.Read 8 Oct 2026 · github.com
Program types
Supported program models include points, visits or stamps, wallet credit, paid membership, and hybrid multi-account programs.Read 8 Oct 2026 · loyalty-interchange.mintlify.app
Restaurant orders
Its foodservice order model covers items, modifiers, discounts, fees, taxes, tips, tenders, and totals across channels including drive-thru, kiosk, web, mobile, pickup, delivery, and catering.Read 8 Oct 2026 · loyalty-interchange.mintlify.app
Security requirements
The security policy says implementations must use TLS, authenticate non-health endpoints, avoid direct customer identifiers in logs or idempotency keys, and encrypt sensitive identity claims at rest.Read 8 Oct 2026 · github.com
Self-hosting
The maker offers an Apache-2.0 reference stack that can be started with Docker or Node.js 22 and newer.Read 8 Oct 2026 · loyalty-interchange.mintlify.app
Storage
The repository describes SQLite-backed local storage and normalized, tenant-scoped PostgreSQL storage for multi-instance use.Read 8 Oct 2026 · github.com

Plans and prices

Loyalty Interchange Protocol Free Apache-2.0 open-source stack; self-hosted Read 8 Oct 2026 · github.com

Every Loyalty Interchange Protocol plan and price →

Strong points and limits

Strong points

  • Supports multiple restaurant loyalty program models.
  • Covers accrual, redemption, reversals, and adjustments.
  • Order model spans restaurant channels and order components.
  • Offers an Apache-2.0 self-hosted reference stack.
  • Supports local SQLite and multi-instance PostgreSQL storage.

Limits

  • Customer sign-in remains external.
  • CSV member imports are limited to 1 MiB and 1,000 rows.
  • Described as pre-1.0 infrastructure.
  • Not a turnkey no-code marketing service.

Who it suits

LIP is aimed at POS and ordering products, multi-unit technical teams, and restaurant integrators that can own the integration work. It is not positioned as a no-code marketing service for restaurants without an integration team.

Verdict

LIP provides a broad loyalty and restaurant-order model for teams prepared to integrate and operate the stack. Its stated pre-1.0 maturity and integration requirements are important considerations for prospective adopters.

Where Specifiction places it

Alternatives to Loyalty Interchange ProtocolAll alternatives →