Monerium

• Name: Monerium
• URL: https://monerium.com/
• Category: regulated e-money issuer / IBAN-linked stablecoin payments company / bank-rail-and-wallet orchestration operator
• Tags: ethereum-ecosystem
• Summary: Monerium belongs in companies/, not mainly projects/, because the durable dependency is a named licensed issuer that decides who gets wallet-linked bank-account behavior, how IBAN provisioning and redemption workflow operate, which chains receive first-class support, and how regulated e-money rules are packaged for developers and downstream partners. The useful question is not just which token contract exists? but which company controls onboarding, account linkage, issuance, redemption, and SEPA-connected operating policy behind EURe, GBPe, ISKe, and USDe?
• What it does:
  • Issues regulated e-money tokens such as EURe, GBPe, ISKe, and USDe across multiple blockchains
  • Lets developers and partners link blockchain wallets to Monerium profiles and provision IBANs tied to approved users or businesses
  • Runs incoming and outgoing SEPA payment flows, redeem-order workflow, and API-driven transaction lifecycle around its issued money
  • Offers three operating models — full whitelabel lifecycle management, OAuth-based user authorization via Monerium, and private access for a firm’s own account — which makes the company-run workflow shell more important than any single token surface
  • Publishes SDKs, an OpenAPI surface, React provider packages, sandbox tooling, and AI-oriented integration context files that reinforce Monerium’s role as a managed operator stack rather than a standalone protocol
• Key claims:
  • Official docs position Monerium as an API for issuing regulated e-money on-chain, automating SEPA payments, and connecting bank accounts to blockchain wallets
  • The tokens page says Monerium e-money tokens are live on Ethereum, Gnosis, Polygon, Arbitrum, Base, Linea, Scroll, Noble, and Camino, with sandbox support on major testnets
  • The whitelabel docs explicitly promise dedicated IBANs and onchain addresses per customer under a partner’s own brand
  • Monerium’s smart-contract repo describes the product as onchain fiat infrastructure where users can transfer regular money directly between offchain banks and Web3, with fully authorized, regulated, and backed onchain fiat
  • The smart-contract docs also frame Monerium EMI as a licensed e-money institution and note MiCA-compliant stablecoins, which is exactly the kind of legal-and-operating boundary that deserves an entity note
• Whitepaper: No standalone company whitepaper is the point here. The strongest primary materials remain Monerium’s official site, developer docs, token and API surfaces, whitelabel integration docs, AI context-file page, and public code repositories; see ../whitepapers/monerium-primary-sources-2026-04-26.md.
• Sources:
  • https://monerium.com/
  • https://docs.monerium.com/
  • https://docs.monerium.com/tokens
  • https://docs.monerium.com/whitelabel
  • https://docs.monerium.com/use-with-ai
  • https://docs.monerium.com/api
  • https://github.com/monerium
  • https://github.com/monerium/smart-contracts
  • https://github.com/monerium/js-monorepo

Internal linkages

• Project-layer alias: monerium.
• Useful adjacent issuer and bank-rail operator comparisons: paxos, circle, and openpayd.
• Useful product-level contrasts where the main object is still the asset or protocol surface more than the operating company: circle-usdc and m0.

Protocol / company boundary

• monerium is intentionally only an alias now because the prior note had already become an issuer-and-operator analysis rather than a clean protocol or product-mechanism note.
• The durable control surface sits with Monerium as a named regulated entity: wallet linking, IBAN issuance, direct issuance and redemption, supported-chain expansion, and customer admission do not reduce cleanly to one token contract.
• Keep token-specific questions on asset notes when possible; use this company note when the real question is who controls the issuer window, bank-rail attachment, account provisioning, and the regulated shell around those flows.

Control surface

• Practical authority sits in customer onboarding, wallet linking, IBAN issuance, SEPA access, redemption handling, supported-currency and supported-chain coverage, whitelabel partner configuration, and the compliance gates that decide which users and businesses get bank-account behavior.

• The sticky dependency is operational rather than purely contractual: once an app depends on Monerium-managed identity, IBAN assignment, API lifecycle truth, and issuer-backed redemption, the lock-in is to the company-run workflow shell rather than to a generic onchain euro token.

• Read Monerium as a regulated issuer-and-payments company first. The real choke point is the entity that attaches bank rails and redemption rights to wallets, not the bare existence of tokenized fiat onchain.

• Last reviewed: 2026-08-07 UTC