Skip to content

Monerium Integration for Firms That Give Customers IBANs and EURe

Protofire builds the Monerium integration for firms that give customers Monerium IBANs and EURe: onboarding, wallet linking, signed orders and webhooks. Each order is booked once in the firm's ledger and matched daily to the chain. Protofire engineers helped build the Gnosis Safe web app from 2019 to 2021.

Luis Medeiros

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026

On this page
  1. Overview
  2. Order events
  3. Monerium facts
  4. What we build
  5. By wallet holder
  6. Why Protofire
  7. How the build goes
  8. How work starts
  9. Not the right fit
  10. Related guides and services
  11. FAQ

Work shipped for 60+ networks and 95+ protocols, including

  • Chainlink
  • Ethereum
  • Solana
  • Safe
  • Ripple
  • Aave

Monerium runs the IBAN, and your side decides the postings

You have chosen Monerium for euro IBANs on wallets, and your Monerium integration now has to reach your own books. Monerium approves the customer, runs the IBAN and issues the EURe. Your side decides which order becomes a posting and how finance proves it.

For example, a customer's salary arrives in the IBAN you gave them, and Monerium mints EURe to the linked wallet. Which entry does your ledger make?

Monerium webhooks leave out order events by default

Monerium's webhooks report orders only when the subscription names the order events (Monerium API).A new subscription includes profile and IBAN events only. With the default subscription, your app learns that an IBAN exists but hears nothing when money arrives.

A missed order event is hard to replay, because Monerium documents no date filter on the order list (Monerium API). With a second chain, an old EURe contract and a customer who changes wallet, balances shown to customers drift from the ledger that finance signs. Someone then rebuilds the totals by hand.

Pooja Shah of Rain made the case for more on and off ramps in Protofire's Protocol Roundtable episode 6.

I think we need more, cheaper, faster, more flexible on and off ramps that can work for institutions to directly be off-ramping their own treasuries [...]
Pooja Shah, Head of Product, Rain · The Protocol Roundtable by Protofire, Episode 6, 55:06

Monerium's regulator, plans, networks and payment rails

Regulator
Monerium hf. of Reykjavik says it is authorized as an e-money institution by the Financial Supervisory Authority of the Central Bank of Iceland (Monerium).
MiCA register
ESMA's interim register lists "Monerium ehf", authorized on 25 September 2019. It records the EURe white paper as notified on 9 January 2026 (ESMA).
Plans
Monerium offers three plans: Whitelabel, OAuth and Private. Whitelabel and OAuth start with an application that Monerium reviews. OAuth has no webhooks (plans).
Interfaces
Monerium provides REST API v2, webhooks signed with HMAC, a TypeScript SDK and a sandbox. Monerium documents no statement file (API).
Networks
On Ethereum, Gnosis, Polygon, Arbitrum, Base and Linea, EURe is an ERC-20 token with 18 decimals (Monerium). On Noble, a Cosmos chain, EURe has 6 decimals (API). The API's address fields accept only 0x addresses, so a Noble build is confirmed with Monerium first.
Rails and limits
Payments use SEPA Instant where the other bank supports it, and SEPA Credit Transfer otherwise (Whitelabel guide). Monerium asks for a supporting document on personal third-party payouts of 15,000 euros or more (API).

Checked November 2026 against Monerium's documentation.

What Protofire builds in a Monerium integration

Onboarding screens and a queue for stalled profiles

Protofire builds onboarding screens that run Monerium's pre-checks. The screens handle all seven profile states and source-of-funds requests. We also build a queue with an owner for each stalled profile, because a profile left in review with nobody watching is a lost customer.

Wallet linking with the approval quorum of a withdrawal

Protofire builds wallet linking for keys, for Safe owners through EIP-1271 and for custody wallets. Monerium's token contract checks the ownership signature at each burn. Its recover function moves an address's whole balance on the same signature, and only Monerium's system accounts can call that function (Token.sol). So the link message gets the approval quorum of a withdrawal.

Redeem orders that pay out once

Each redeem order goes out with an ID that your system sets. So a request that timed out is looked up before anyone retries it. Monerium treats the signed message as the idempotency key, which means a message re-signed with a new timestamp is a second payout (Monerium FAQ). Monerium's API accepts an order timestamp at any point in the future, so Protofire caps how far ahead a signed order may be dated.

Your ledger books each Monerium order once

The webhook receiver that Protofire builds checks the HMAC signature and drops a repeated webhook ID. It also alerts when the subscription turns inactive and backfills from your own cursor. Each posting is keyed on order ID and state, so an order that arrives twice posts once. A cross-chain transfer is two orders, and the ledger books it as one move (Whitelabel guide).

Daily matching of your ledger against orders and chains

Each day, your ledger is matched with orders, the SEPA payments behind them and the mint, burn and transfer events on each chain. On Ethereum, Gnosis and Polygon, a transfer through an old EURe contract emits a Transfer event on both contracts. So the indexer reads V2 logs, and balances come from the V2 address (Monerium contracts V2). Each break gets an owner. Finance can sign the daily match.

Catching Monerium API changes before production

Monerium's API changelog lists 26 dated entries between 22 January and 4 November 2026 (Monerium API). Some entries rename states and add required fields. Protofire tracks the changelog and pins the API version in each request. We also alert on webhook delivery and stuck profiles. Protofire's managed onchain operations service can take those alerts under a written scope.

Whose wallet holds the EURe decides what you book

A design built for one wallet holder books the other holders wrongly.Such a design can put client EURe on your own balance, or leave fees with no entry. The first column fits wallet apps, the second payment firms and the third licensed crypto firms. The third column comes with a legal rule. Custody of EURe for clients is crypto-asset custody. Under MiCA, an authorized crypto-asset service provider offers that custody, or a bank after notifying its supervisor (Article 60). The EBA's February 2026 opinion advises that, since 2 March 2026, a firm moving e-money tokens for clients should hold a payment or e-money authorization. Otherwise, the firm should act through an authorized payment service provider or have a qualifying application pending. Your counsel decides how these rules apply to your flows.

Your ledger holds

Customer's own wallet: Your fees and costs, such as sponsored gas. The EURe is the customer's claim on Monerium.

Firm's own profile: Your own EURe float under the classification that finance chooses, plus payables and receivables for flows you settle.

Client custody wallets: Client positions in a custody subledger. Balance-sheet treatment is for finance and auditors.

Matched against

Customer's own wallet: Orders and transaction hashes per customer address.

Firm's own profile: Settlement files, onchain movements into your wallet, redeem orders and their SEPA payments.

Client custody wallets: Orders, each wallet's onchain balance and the client subledger.

Where it breaks

Customer's own wallet: A customer changes wallet, and the IBAN keeps minting to the old address until your app moves it.

Firm's own profile: A redeem order is rejected after a card scheme or payee expects the funds.

Client custody wallets: The payout leg, and how a regulator classifies it.

Our record: Safe wallet work since 2018 and an IBAN-to-wallet design

Monerium links each IBAN to a wallet.Protofire's Safe work and our published design deal with the same question: who must agree before the wallet signs.

Safe wallet work since 2018

Protofire engineers helped build the Gnosis Safe web app from 2019 to 2021 (contributors graph). The Safe Ecosystem Foundation wrote in May 2026 that Protofire "has been contributing to Safe since 2018". A Monerium IBAN can point at a Safe. Safe's own SDK documentation includes a guide that combines the Monerium SDK with the Safe SDK. Protofire's Safe multisig work has a separate page.

A published design for binding an IBAN to a wallet

Protofire's IBAN-to-wallet blueprint lists Monerium among its vendors. The blueprint sets out the reference architecture and the regulatory position. Our wallet-linked IBAN accounts page describes the vendor-neutral account model.

From signed account model to orders booked on your ledger

  1. Step 1

    Risk and finance sign the account model before any code

    Before any code is written, your risk owner and finance sign one document. The document names the Monerium plan, the wallet holder and the posting rules. It also names the owner of each stalled profile.
  2. Step 2

    The build runs in Monerium's sandbox first

    Before production credentials exist, onboarding and wallet linking run against Monerium's sandbox. Orders and the webhook receiver run there first too, and so does a change of a Safe's owners.
  3. Step 3

    Booking and the daily match start with the first approved profiles

    Postings start with the first approved profiles. The ledger books an order once, when the order reaches the processed state. A rejected order releases the reserved amount.
  4. Step 4

    Your firm owns the code and runs the integration

    The code, configuration and runbooks are yours. Monerium credentials are stored in your secrets vault. Keys are held in your customers' wallets or in your own custody. Your team runs the integration from the runbooks.

How a Monerium project starts

You send your Monerium plan, or the plan you are weighing, and the onboarding flow you have.You also send the wallets that customers will link and the ledger that orders must reach. The terms in this section apply to each phase, as set out on how we work.

Proposal
In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
Price
Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
Ownership
Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
After launch
Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
Access
Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
Licenses
Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.

How we work shows a worked proposal.

When Monerium's own tools are enough or Monerium does not fit

In four cases, Monerium's own tools are enough or Monerium is the wrong fit.

  • Your app can send customers to Monerium's portal. On the OAuth plan, Monerium runs signup and KYC (OAuth guide). Your build then covers authorization and wallet linking, plus orders and watching onchain events. A firm that moves only its own euros can use the self-service Private plan (plans).
  • You have one plain flow and a backend team. Monerium's SDK and sandbox may be enough for that team.
  • You need SWIFT or a non-euro rail. Monerium runs on SEPA and says SWIFT is not supported (Monerium).
  • Your policy requires an issuer supervised in an EU member state. Monerium is supervised in Iceland, an EEA country outside the EU.

Monerium approves your customers and issues their EURe. Protofire holds no license of its own and signs none of Monerium's agreements for you. Protofire holds no keys and approves no payouts. We give no legal opinions on MiCA or PSD2.

FAQ

What is a Monerium integration?
A Monerium integration connects the IBANs and EURe that Monerium issues to a firm's app, ledger and payment operations. The integration onboards customers into Monerium profiles and links each profile's IBAN to a wallet with a signed proof. It also places signed redeem orders. Protofire builds Monerium integrations, and each order posts to the firm's ledger once it is processed.
Who can build a Monerium integration for a wallet app or a payment firm?
Protofire builds the firm's own side of a Monerium integration. The firm's side covers onboarding, wallet linking and signed orders. It also covers a webhook receiver, ledger postings and a daily match against the chain. Monerium itself approves customers and issues the EURe. Protofire helped build the Gnosis Safe web app and has published an IBAN-to-wallet design.
What happens when our webhook endpoint is down?
Monerium retries each failed delivery up to 10 times over 12 hours, with the same webhook ID (Whitelabel guide). Monerium's API also documents an inactive subscription state (Monerium API). Your monitor reactivates the subscription with the full list of event types. An update without that list falls back to the profile and IBAN defaults. The monitor then rereads each order that is still placed or pending.
Can a Safe or a custody wallet hold a Monerium IBAN?
Yes, a Safe, a Fireblocks vault account or an externally owned account such as MetaMask or Ledger can hold a Monerium IBAN. Monerium's wallet FAQ lists all of them (Monerium). A Dfns wallet appears on that FAQ too. But a Dfns vault cannot link, because its wallets are sealed and move funds only through vault transfers (Dfns). The wallet signs Monerium's ownership message once and then signs each redeem order. Wallet products differ in whether they can sign that message, so the signing path is tested in the sandbox before a customer links.
Can a holder redeem EURe through our app without being a Monerium customer?
No. EURe's white paper conditions redemption on "the holder establishing a customer relationship with Monerium" (white paper). So a user who received EURe from another wallet onboards with Monerium first. The paper adds that Monerium may have to freeze EURe sent to or from blacklisted addresses. The holder then forfeits the right to redeem that EURe, so onchain payouts are screened before signing. Under MiCA, the holder's claim and redemption are at par (Article 49).
What happens to customers' IBANs if our app closes?
A customer's IBAN belongs to the customer's Monerium profile. For example, Gnosis Pay set 20 December 2026 as the end of its consumer card. Its help center told users that their EUR IBAN "keeps working". Monerium closes a profile only when no orders are pending, and it answers 409 to a closure request while any order is open (Monerium API). So open orders finish and are booked first.
What can Protofire do inside our Monerium setup after go-live?
By default, Protofire can read your Monerium setup and nothing more. Starting orders needs a role that your written scope grants. Your firm keeps the signer, admin and approver roles. The key-holder and recovery roles also remain with your firm.

Get a proposal

Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.

Luis MedeirosField CTO, reads every request · LinkedIn

A demo or repository link also works.