Lyzi primary sources — 2026-05-04

Project status in this pass

• No canonical standalone Lyzi whitepaper or litepaper surfaced.
• The clearest current sources of truth were the official site, the PSP-and-banks solution page, the FAQ, and the developer GitBook.
• The documentation makes Lyzi look much broader than a simple crypto checkout button.

Primary-source snapshots

1) Main site overview

• URL: https://lyzi.io/
• Key excerpt:
  • The homepage says merchants can accept crypto and receive euros, describes the product as plug-and-play, and says fiat payout occurs within 24-48 hours.
  • It also says Lyzi is connected to more than 1 million points of sale and positions itself as an open universal payment solution linking exchanges, wallets, merchants, and payout infrastructure.
  • This page is the clearest high-level signal that the product is about operational merchant acceptance, not consumer wallet UX.

2) PSP-and-banks orchestration page

• URL: https://lyzi.io/solution/psp-banques
• Key excerpt:
  • This page describes Lyzi as a unified payment orchestrator for PSPs and banks with one plug-and-play integration.
  • It says the stack is multi-stablecoin, multi-exchange, and multi-wallet, covers acceptance through payout, and supports white-label deployment across POS, ecommerce, and mobile environments.
  • That positioning is what makes Lyzi look like payment orchestration infrastructure instead of a simple merchant widget vendor.

3) FAQ and operational claims

• URL: https://lyzi.io/faq
• Key excerpt:
  • The FAQ says Lyzi supports more than 300 cryptocurrencies and works with more than 500 wallets and exchange-connected payment sources.
  • It says the company works with authorized PSP and VASP partners and can deploy in the eurozone and selected international markets depending on local regulation.
  • It also describes dashboard-based merchant transaction tracking, compliance workflows, and cybersecurity posture, which reinforces the control-plane framing.

4) Developer quickstart and backoffice model

• URL: https://lyzi.gitbook.io/developer/getting-started/quickstart
• Key excerpt:
  • The quickstart says a manager account must be created and approved through a KYB process before full backoffice access is granted.
  • It says operators can create payment buttons, payment links, salespoints, collectors, cashier accounts, and API credentials from the backoffice.
  • The guide also says payments can be linked either to ecommerce-style payment buttons or to collector-based in-store flows, and that webhooks plus status checks are authoritative for backend confirmation.

5) Embedded iframe flow

• URL: https://lyzi.gitbook.io/developer/getting-started/integration-with-iframe
• Key excerpt:
  • The iframe guide shows Lyzi can also be embedded directly into merchant sites using collector-linked payment URLs.
  • It documents return_url, cancel_url, optional webhook_url, collector IDs, and repeated backend-verification guidance via status checks and server-to-server notifications.
  • This matters because it shows the product supports several integration modes while keeping the operational verification model consistent.

Working conclusion

Lyzi is best cataloged as a crypto-and-stablecoin payment orchestration control plane. The deciding evidence in this pass was the combination of PSP-and-bank white-label positioning, KYB-gated operator backoffice flows, buy-button and collector payment models, webhook-driven backend verification, and explicit multi-wallet / multi-exchange / multi-stablecoin orchestration claims. That mix makes Lyzi look like a real merchant-and-rail operating layer rather than a simple hosted checkout page.