Lyzi

• Name: Lyzi
• URL: https://lyzi.io/
• Category: euro-settlement crypto-payments company / merchant-and-PSP onboarding shell / checkout-and-payout workflow operator
• Tags: ethereum-ecosystem
• Summary: Lyzi belongs in companies/ because the useful cut is not only what payment API or iframe exists? but which named operator approves KYB access, creates the merchant backoffice roles, chooses which wallets and exchanges sit behind the payment flow, decides euro-settlement and payout behavior, and publishes the webhook-backed lifecycle merchants, PSPs, and banks are expected to trust? lyzi stays the product-layer note for checkout flow, collector objects, wallet routing, and integration mechanics. This note is for the operator boundary where admission, partner composition, settlement policy, and day-to-day workflow truth sit together.
• What it does:
  • Operates a KYB-gated merchant backoffice where approved organizations can create salespoints, collectors, cashier accounts, API credentials, payment buttons, and settlement workflows
  • Packages crypto and stablecoin acceptance with euro-denominated settlement for merchants while also selling white-label integration paths to PSPs and banks
  • Aggregates self-hosted wallets and regulated exchanges behind one payment shell, which makes partner composition and routing policy part of the company boundary rather than only a product feature
  • Exposes iframe, payment-button, collector, and webhook integration modes while keeping the authoritative account and payout workflow inside Lyzi-managed interfaces
  • Controls the business-facing support and onboarding shell around merchant acceptance, wallet or exchange connectivity, and payout configuration
• Key claims:
  • The official site frames Lyzi as a crypto-payment solution for merchants, ecommerce, and points of sale, while a separate PSP-and-banks page markets the company as a white-label partner for incumbent payment distributors rather than only as a merchant widget vendor
  • The docs show that production use depends on an approved backoffice hierarchy with roles such as managers, collectors, and cashiers, which is a strong signal that the real dependency is a named operator-managed account model rather than a neutral payment primitive
  • The quickstart and iframe docs make clear that Lyzi expects merchants to trust webhook and status-check paths instead of browser redirects, which makes lifecycle publication and callback behavior part of the company-controlled workflow truth
  • Official materials emphasize compatibility with multiple wallets and exchanges plus euro settlement to merchants, which means Lyzi is packaging counterparties, payout logic, and operational routing under one brand instead of exposing a simple pass-through rail
  • The PSP-and-banks materials matter because they show Lyzi selling distribution through other institutions, widening the operator boundary from direct merchant tooling into embedded payment-infrastructure packaging
• Whitepaper: No classic standalone company whitepaper is the point here. The clearest primary materials are Lyzi’s official site, PSP-and-banks page, FAQ, and developer docs, already captured in ../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

• Product-layer note: lyzi.
• Useful adjacent company reads: coinflow, depay, and openpayd.
• Reusable lens: payment vendors often need a separate company cut when KYB admission, dashboard roles, partner composition, settlement routing, and webhook truth live behind one named operator.

Protocol / company boundary

• Keep lyzi focused on the payment surface itself: checkout flow, iframe or button integration, collector objects, wallet or exchange routing, webhook handling, and euro-settlement behavior as a merchant-facing product.
• Keep this note focused on the operator boundary above that surface: KYB approval, backoffice role issuance, partner and rail composition, payout workflow, white-label PSP and bank packaging, and the named company shell that merchants or distributors depend on in production.
• That split matters because how does Lyzi's payment flow behave? and which company controls who gets access, which counterparties sit underneath, and how settlement or callbacks actually run? are related but not identical questions.

Control surface

• Practical authority sits in merchant and partner admission, KYB workflow, manager or cashier role issuance, wallet and exchange composition, euro-settlement policy, collector configuration, API credential issuance, and webhook-backed lifecycle publication.

• The sticky dependency is not just the checkout UX. It is the company-run operating shell that decides who can use the product, how payouts and conversions are routed, and which status or callback events downstream systems should treat as authoritative.

• Read Lyzi as a merchant-and-PSP payments operator first, not as a neutral payment rail.

• Last reviewed: 2026-08-13 UTC