Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Loyalty Interchange Protocol review

Free#10 of 25 in Restaurant Loyalty SoftwareLoyalty Program Software

A flexible, API-first loyalty stack for teams prepared to self-host and implement it.

8.3/10Editor score
Loyalty Interchange Protocol8.3 Visit site

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Loyalty Interchange Protocol is an Apache-2.0 open-source loyalty platform and vendor-neutral transaction protocol for restaurant, QSR, coffee, convenience, and franchise technology teams. It combines a loyalty engine with transaction and checkout APIs, customer profiles, campaigns, attribution analytics, a guest wallet, restaurant adapters, an Admin dashboard, and developer tooling. It is aimed at technical teams connecting loyalty with ordering, payments, refunds, locations, and existing identity systems.

Its ecosystem is built for integration rather than isolation. The platform includes a Square Orders adapter with webhook signature verification, integrations for Clerk, Auth0, OIDC providers, SQLite, PostgreSQL, and Stripe, plus a TypeScript SDK and generated OpenAPI client. The published capabilities cover member enrollment, balances, ledger history, pre-checkout order evaluation, post-payment accrual, redemption reservation and capture, refund-safe adjustments, imports, segmentation, scheduled campaigns, and attribution. A responsive reference guest wallet uses OIDC Authorization Code and PKCE, while OpenAPI, JSON Schema, and HTTP conformance tests support the portable /lip/v1 contract.

The main trade-off is implementation ownership. Teams can self-host the reference platform with Docker and choose SQLite or PostgreSQL, but they must handle deployment and connect external customer authentication. The local Admin dashboard supports program drafts, publishing, and rollback, giving operators program controls without turning the product into a no-code service. Choose Loyalty Interchange Protocol when extensibility, portability, and control over the loyalty stack matter. Consider an alternative if the priority is a fully managed, no-code restaurant marketing system with minimal engineering involvement.

Loyalty Interchange Protocol pros and cons

  • Where it wins
    • Supports points, visits, stamps, wallet credit, memberships, and hybrid programs
    • Includes checkout, redemption, accrual, refund, campaign, and attribution workflows
    • Offers APIs, SDKs, Admin tools, Docker, PostgreSQL, SQLite, and conformance testing
  • Where it doesn't
    • Requires self-hosting and implementation effort
    • Customer authentication remains external
    • Not designed as a turnkey no-code marketing service

Loyalty Interchange Protocol fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update