Loyyo|

Loyyo Identity Resolution Simulator: Instructions

Welcome to the interactive Proof of Concept for the Loyyo Data Engine. This simulator demonstrates how fragmented, anonymous payment data is stitched together into a rich Unified Customer ID (UCI) to power Agentic Commerce.

About this demo

This simulator is the interactive companion to our YAYA Use Case — the reference scenario we use to show how a fashion retailer collapses the gap between physical and digital commerce. To keep the story concrete, the simulator is wired up against one specific stack:

  • Merchant: YAYA (yaya.eu)
  • PSP (online + in-store): Adyen — both the e-commerce checkout and the in-store payment terminal run on Adyen, which is what makes a single PAR/card token usable across channels.
  • POS: Sitoo — provides the order ID and SKU-level line-items for every in-store transaction.
  • Webshop: Shopify — provides the e-commerce orders carrying email, name, and shipping address.
  • Digital lifestyle hub: Google Wallet — via WalletPass, the loyalty pass that ties the physical card to the user's authenticated Google account.

Loyyo is stack-agnostic — that's the point

The names above are just the YAYA case. Loyyo's identity engine is deliberately agnostic to the underlying stack — and that flexibility is precisely the power of the architecture. The same handshake, the same UCI, and the same downstream personalisation work with whichever systems a merchant already has in place:

  • Other PSPs: Stripe, Mollie, Worldline, CCV, Checkout.com, Nexi, Global Payments, Worldpay — anything that exposes secure network tokens (PAR, card alias, shopperReference equivalents) via webhook.
  • Other POS systems: Lightspeed, NewStore, Oracle Retail, NCR, Adyen POS, custom POS — any system that emits an order ID and line-items via API.
  • Other webshops / e-commerce platforms: WooCommerce, Magento, BigCommerce, Salesforce Commerce Cloud, headless / custom storefronts — any platform with an order export.
  • Other CDPs and customer data layers: Segment, Tealium, mParticle, Treasure Data, Snowflake-native CDPs — Loyyo writes the resolved UCI back into whichever profile store the merchant already trusts.
  • Other loyalty engines: Antavo, Talon.One, Voucherify, LoyaltyLion, Punchh, in-house loyalty platforms — Loyyo provides the identity and the tier signal; the loyalty engine handles redemption mechanics.
  • Other wallets: Apple Wallet, Samsung Wallet, branded mobile apps — anywhere a digital pass can live and be tied back to an authenticated account.

Loyyo sits as a thin identity layer between these systems: it ingests their tokens and references, resolves the graph, and pushes the unified profile back out. No rip-and-replace, no migration. That is why the same architecture you see in this demo can be deployed against virtually any modern retail tech stack.

For the full narrative behind the YAYA choices (the ghost customer, the dressing-room QR, the handshake, the unlock), read the YAYA Use Case.

Step 1: Start the automated journey

Action: Click the "Auto-Simulate Journey ⚡" button at the top of the simulator.

The engine automatically generates a realistic mix of POS (Sitoo) and Shopify e-commerce transactions, building up the identity graph step by step. Watch the logs on the right as each transaction is captured, showing the raw payment tokens (Adyen shopperReference, card token, scheme PAR), SKUs, and references Loyyo collects at every touchpoint.

After all transactions are generated, the Loyyo Handshake triggers automatically. A progress overlay shows the identity resolution in real time. Once complete, the Unified Customer ID (UCI) is created and the unified purchase history graph appears, showing all POS and E-commerce transactions merged into a single timeline with CLV metrics, RFM clusters, and full product data.

Step 2: Add transactions to the UCI

Action: After the UCI is created, the POS and E-com cards show "+ Add to UCI (POS)" and "+ Add to UCI (E-com)" buttons.

Any new transaction you add, whether physical or online, is now automatically linked to the known UCI in real time. The unified graph updates instantly. No new handshake is required.

Step 3: The Agentic Demo's (the unlock)

Action: Click the "View Result in Agentic Demo's →" button that appears after the handshake.

You will see six tabs, each showing how the UCI drives personalisation and decision-making across different surfaces. The first four are customer-facing; the last two are merchant-facing.

Customer-facing

  • Webshop — A mock YAYA webshop (Shopify-style) with products dynamically ranked and priced based on the loyalty tier and purchase history derived from the UCI.
  • Search Results — A Google-style results page where Loyyo Smart Pricing surfaces the loyalty discount directly in sponsored listings, before the customer even reaches yaya.eu.
  • Chatbot — A Gemini-powered personal shopper that greets the customer by name, references their last in-store purchase, and recommends matching items with the tier discount applied.
  • Loyalty App — The YAYA loyalty web app showing the customer's points balance, available vouchers, activity history, and personal benefits derived from the unified purchase data.

Merchant-facing

  • Insights — A pre-built analytics dashboard for the YAYA team. Compare known members vs. ghost shoppers at a glance: revenue split, RFM clusters (One-time, Occasional Dormant, Occasional Active, Loyal at Risk, Loyal Active), CLV, APV, churn risk, and product-level performance. The picture is there the moment the dashboard loads — no SQL, no BI engineer in the loop.
  • AI Prompt — Beyond the static dashboard, ask the data open-ended questions in plain English: "What promotion should I run to move 'Occasional Dormant' users into 'Active'?" or "Which gateway product converts unknown shoppers to loyalists the fastest?" The Loyyo NL2SQL engine translates the question into SQL, runs it against the pre-aggregated data layer, and returns a natural-language answer with supporting charts — plus concrete suggestions and next actions (the discount to offer, the product to feature, the optimal send time, the wallet pass to push). Transactions become decisions.

Open the "Loyyo Agentic Engine" debug panel in the bottom right corner on any of the customer-facing tabs to see exactly which identity signals and context are injected into the AI, without the customer ever logging into a traditional loyalty portal.