Apache-2.0 · LIP 0.2.0 · Node 22

The open loyalty API built for restaurant checkout.

Evaluate the cart, reserve before payment, accrue and capture after settlement, then reverse or refund safely. Use the open protocol and reference stack—or work with us to operate it.

Full transaction lifecycleEvaluate, reserve, accrue, capture, reverse, adjust
Foodservice edge casesModifiers, split tender, offline replay, void, refund
Executable evidenceOpenAPI, schemas, SDK, fixture certification, conformance

Run checkout through refund.

This deterministic simulation runs entirely in your browser with synthetic data. It sends no order, identity, or credential anywhere. Select a step or run them in sequence.

600 points · 600 available
REQUEST
RESPONSEsynthetic
Ledger / account effect

Idempotency key:

The hard part is lifecycle correctness.

Generic campaign breadth is not the claim. LIP focuses on portable transaction behavior and the evidence needed to trust an ordering integration.

Retry without double posting

Stable business keys, exact replay, explicit payload conflict, immutable ledger linkage.

Read idempotency →

Certify the source mapping

A typed adapter contract and fixture runner cover modifiers, combos, tenders, comps, offline delivery, void, and refund.

Read adapter guide →

Leave with your state

Checksummed full-state archives plus member/opening-balance plans and reconciliation reports.

Read migration guide →

Operate the open stack

SQLite or normalized tenant-scoped Postgres, Admin, webhooks, metrics, key rotation, and conformance.

Reference platform →

Choose with evidence

Compare lifecycle, portability, recovery, integration effort, marketer workflow, and ownership.

Provider selection →

Keep identity separate

Your BFF verifies the customer and retains the merchant key. LIP receives only an opaque member id.

Identity boundary →

Choose the next proof.

The protocol, reference implementation, and managed path stay explicit so adoption never depends on lock-in.

Evaluate

Browser walkthrough

Finish the synthetic lifecycle above and inspect every request, result, key, and ledger effect.

Reset and run it →
Build

Self-host

Clone the Apache-2.0 stack, start Docker, inspect Admin, then run black-box conformance.

Open quickstart →
Partner

Map a real source

Bring one ordering/refund edge. Produce a certified adapter, migration rehearsal, and cutover record.

Design partner details →
Truthful boundary: LIP 0.2.0 is pre-1.0 software. The repository tests and reports prove behavior of the supplied implementation and fixtures; they do not prove independent adoption, vendor endorsement, production SLO attainment, or benchmark leadership.