Monerium SDK

Monerium SDK Documentation

Monerium connects your web3 wallet to any euro bank account with your personal IBAN. All incoming euro payments are automatically minted as EURe tokens to your wallet. Sending EURe to traditional bank accounts is just as easy. With a single signature from your wallet, your EURe is burned and sent as Euros to any bank account.

Table of Contents



Node v16.15 or higher is required.

yarn add @monerium/sdk


Environments - URLs

Environment Web API

Environments - Networks

Environment Chain Network
sandbox ethereum sepolia
polygon mumbai
gnosis chiado
production ethereum mainnet
polygon mainnet
gnosis mainnet

Usage Examples

We recommend starting in the Developer Portal. There you will learn more about client_id's and ways of authenticating.

Initialize and authenticate using Client Credentials

Client Credentials is used when there's no need for user interaction, and the system-to-system interaction requires authentication.

import { MoneriumClient } from '@monerium/sdk';
// Initialize the client with credentials
const monerium = new MoneriumClient({
environment: 'sandbox',
clientId: 'your_client_credentials_uuid', // replace with your client ID
clientSecret: 'your_client_secret', // replace with your client secret

await monerium.getAccess();

// Retrieve authentication data after successful authentication.
await monerium.getAuthContext();

// Access tokens are now available for use.
const { access_token, refresh_token } = monerium.bearerProfile as BearerProfile;


API documentation:

Initialize and authenticate using Authorization Code Flow with PKCE

Authorization Code Flow with PKCE is used for apps where direct user interaction is involved, and the application is running on an environment where the confidentiality of a secret cannot be safely maintained. It allows the application to authorize users without handling their passwords and mitigates the additional risk involved in this sort of delegation.

First you have to navigate the user to the Monerium authentication flow. This can be done by generating a URL and redirecting the user to it. After the user has authenticated, Monerium will redirect back to your specified URI with a code. You can then finalize the authentication process by exchanging the code for access and refresh tokens.

import { MoneriumClient } from '@monerium/sdk';

export function App() {
const [authCtx, setAuthCtx] = useState<AuthContext | null>(null);
const [monerium, setMonerium] = useState<MoneriumClient>();
const [isAuthorized, setIsAuthorized] = useState<boolean>(false);

useEffect(() => {
const sdk = new MoneriumClient({
environment: 'sandbox',
clientId: 'f99e629b-6dca-11ee-8aa6-5273f65ed05b',
redirectUrl: 'http://localhost:4200',
}, []);

useEffect(() => {
const connect = async () => {
if (monerium) {
setIsAuthorized(await monerium.getAccess());


return () => {
if (monerium) {
}, [monerium]);

useEffect(() => {
const fetchData = async () => {
if (monerium && isAuthorized) {
try {
setAuthCtx(await monerium.getAuthContext());
} catch (err) {
console.error('Error fetching data:', err);
}, [monerium, isAuthorized]);

return (
{!isAuthorized && <button onClick={() => monerium?.authorize()}>Connect</button>}

<p>{authCtx?.name || authCtx?.email}</p>


API documentation:

Get account information

// Get all profiles for the authenticated user.
const authCtx: AuthContext = await monerium.getAuthContext();

// Fetching all accounts for a specific profile
const { id: profileId, accounts }: Profile = await monerium.getProfile(authCtx.profiles[0].id);

// Fetching all balances for a specific profile
const balances: Balances = await monerium.getBalances(profileId);


API documentation:

Get token information

Get the contract addresses of EURe tokens.

const tokens: Token[] = await monerium.getTokens();


API documentation:

Link a new address to Monerium

It's important to understand, when interacting with a blockchain, the user needs to provide a signature in their wallet. This signature is used to verify that the user is the owner of the wallet address.

We recommend Viem as an Ethereum interface, see:

import { constants } from '@monerium/sdk';
import { walletClient } from '...' // See Viem documentation

const { LINK_MESSAGE } = constants; // "I hereby declare that I am the address owner."

// Send a signature request to the wallet.
const signature = await walletClient.signMessage({
message: LINK_MESSAGE,

// Link a new address to Monerium and create accounts for ethereum and gnosis.
await monerium.linkAddress(profileId, {
address: '0xUserAddress72413Fa92980B889A1eCE84dD', // user wallet address
accounts: [
} as LinkAddress);


API documentation:

Get and place orders

// Get orders for a specific profile
const orders: Order[] = await monerium.getOrders(profileId);
// Place a redeem order
import { placeOrderMessage } from '@monerium/sdk';
import { walletClient } from '...'; // See Viem documentation

const amount = '100'; // replace with the amount in EUR
const iban = 'EE12341234123412341234'; // replace with requested IBAN

// First you have to form the message that will be signed by the user
const message = placeOrderMessage(amount, iban);

// The message should look like this, with the current date and time in RFC3339 format:
// Send EUR 100 to EE12341234123412341234 at Thu, 29 Dec 2022 14:58:29Z

// Send a signature request to the wallet.
const signature = await walletClient.signMessage({
message: message,

// Place the order
const order = await monerium.placeOrder({
address: '0xUserAddress72413Fa92980B889A1eCE84dD', // user wallet address
counterpart: {
identifier: {
standard: 'iban', // PaymentStandard.iban,
details: {
firstName: 'User',
lastName: 'Userson',
county: 'IS',
memo: 'Powered by Monerium SDK',
chain: 'ethereum',
network: 'sepolia',
// supportingDocumentId, see below


API documentation:

Add supporting documents

When placing orders with payouts above 15,000 EUR, a supporting document is required. The document must be uploaded to Monerium before the order can be placed. Supporting documents can be an invoice or an agreement.

// Upload a supporting document
const supportingDocumentId: SupportingDoc = await uploadSupportingDocument(document);


API documentation:

Subscribe to order events

import { OrderState } from '@monerium/sdk';
const [orderState, setOrderState] = useState<OrderState>();
// Subscribe to order events
monerium.subscribeOrders(OrderState.pending, (notification) => {

monerium.subscribeOrders(OrderState.placed, (notification) => {

monerium.subscribeOrders(OrderState.rejected, (notification) => {
setTimeout(() => {
}, 5000);

monerium.subscribeOrders(OrderState.processed, (notification) => {
setTimeout(() => {
}, 5000);

API Reference

API Documentation


We are using commitlint to enforce that developers format the commit messages according to the Conventional Commits guidelines.

We are using Yarn as a package manager.

# Install dependencies
nx run sdk:init

# Run Vite to build a production release distributable
nx run sdk:build

# Run Vite in watch mode to detect changes to files during development
nx run sdk:build --watch

# Update the docs. This will run the build and update the docs in the static folder.
# Open static/index.html in your browser to view the docs. Refresh the page to see changes.
nx run sdk:docs:watch


For development, a package can be linked into another project. This is often useful to test out new features or when trying to debug an issue in a package that manifests itself in another project. run yarn link inside of the sdk project.

YARN_IGNORE_PATH=1 yarn link

Use yarn link "@monerium/sdk" to link and test into your current project.

cd ../your-project
yarn link "@monerium/sdk"

If you get an error that there is already a package called '@monerium/sdk' registered, but you can't find it and unlinking does nothing, remove it manually with rm -rf ~/.config/yarn/link/@monerium and try again.


Refer to Typedocs syntaxes to use for this documentation.

There is a Github action that will automatically run on the successful release of the SDK. It will generate a static output of the documentation and push it to the gh-pages branch. The documentation is then available at


When changes are merged to the main branch that follows the conventional commits standard, release-please workflow creates a pull request, preparing for the next release. If kept open, the following commits will also be added to the PR. Merging that PR will create a new release, a workflow will publish it on NPM and tag it on Github.


Common questions developers have regarding the SDK.


Support Telegram Github Issues

Release Notes

Generated using TypeDoc