Lyzi

• Name: Lyzi
• URL: https://lyzi.io/
• Category: merchant and PSP crypto-acceptance middleware / euro-settlement orchestration
• Tags: ethereum-ecosystem
• Summary: Lyzi is euro-settlement merchant middleware. Keep this note on the payment flow itself: checkout, collector objects, wallet/exchange routing, webhook truth, and euro payout behavior. The named operator boundary around KYB approval, backoffice roles, partner composition, and payout policy now lives in lyzi. Real operator plumbing, not a payment rail.
• What it does:
  • Lets merchants accept cryptocurrency and stablecoin payments while receiving euro settlement through Lyzi’s payout flow
  • Integrates into point-of-sale, ecommerce, and mobile payment environments without requiring a full replacement of existing payment infrastructure
  • Aggregates regulated exchanges and self-hosted wallets behind one payment layer, with official materials emphasizing multi-wallet and multi-exchange compatibility
  • Offers a merchant backoffice for KYB-approved operators to create payment buttons, salespoints, collectors, cashier accounts, API credentials, and settlement workflows
  • Exposes developer integration paths including buy-button flows, collector-linked payment links, embedded iframe payments, API credentials, webhooks, and status checks
  • Markets a white-label crypto-payment orchestration layer for PSPs and banks that want to add crypto and stablecoin acceptance inside their own existing distribution networks
• Key claims:
  • Lyzi is mainly euro-settlement and merchant-orchestration middleware wrapped around crypto acceptance, not a base rail.
  • The useful operating surface is the KYB-gated backoffice: managers, collectors, cashiers, API credentials, and settlement workflows.
  • Wallet and exchange breadth matters because it shows routing policy and partner dependence, not because a long support list makes the stack deeper.
  • The docs are clear that redirects are not authoritative. Merchants are supposed to trust webhooks and status checks, which is where the real control sits.
  • White-label PSP and bank packaging broadens distribution, but the product remains operator middleware with euro payout attached.
• Whitepaper: No canonical standalone Lyzi whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site, FAQ, PSP-and-banks solution page, and developer GitBook; see ../whitepapers/lyzi-primary-sources-2026-05-04.md.
• Sources:
  • https://lyzi.io/
  • https://lyzi.io/solution/psp-banques
  • https://lyzi.io/faq
  • https://lyzi.gitbook.io/developer/getting-started/quickstart
  • https://lyzi.gitbook.io/developer/getting-started/integration-with-iframe

Internal linkages

• Company boundary for merchant admission, cashier / collector roles, partner composition, and euro-settlement policy: lyzi.
• Best upward reads: walletconnect-pay and coinflow.

Protocol / company boundary

• Keep projects/lyzi on the payment workflow itself: merchant checkout, collector objects, wallet-or-exchange routing, iframe or button integration, webhook handling, and the merchant-facing euro-settlement path.
• Use lyzi when the sharper question is who approves KYB access, creates the backoffice roles, chooses the partner shell underneath the product, and controls payout or callback workflow in production.
• That split matters because the payment flow can be described as product behavior, while the admission, settlement-policy, and operator-truth questions are company-shaped.

Control surface

• Practical authority sits in checkout and collector configuration, wallet-and-exchange routing, euro-settlement behavior, webhook truth, and which payment sources Lyzi treats as first-class.

• Keep the operator shell visible too: lyzi is the better read for KYB approval, role issuance, partner composition, and payout-policy authority around this flow.

• Read it as merchant-and-PSP middleware with euro payout attached, not a new rail.

• Last reviewed: 2026-08-13 UTC