Skip to main content

Getting Started

Welcome to Monerium! This guide will help you integrate the Monerium API to offer your users IBANs directly connected to their blockchain addresses. Enable seamless money transfers between bank accounts and blockchains over the SEPA network.

Overview​

Before you begin, determine which integration type fits your needs:

Choose Your Integration Type

Building a user-facing app? → OAuth - Users authenticate with their Monerium accounts

Automating your own account? → Personal - Run scripts and backend jobs on your account

Managing accounts for your users? → White-label - Full platform control, Monerium abstracted away

Setup​

1. Create Your Account​

Head over to our Sandbox and sign up for a developer account.

2. Create an App​

Once signed up, go to the developer portal and create a new app. You'll need to select an app type based on your use case.

App Types​

Choose the authentication flow that matches your integration needs:

🔐 OAuth (User-facing Apps)​

Authentication: Authorization Code Flow with PKCE (Proof Key for Code Exchange)

How it works: Your app acts on behalf of Monerium users with their explicit consent. Users sign in with their Monerium credentials and grant your app permission to access their accounts.

Credentials you'll receive:

  • client_id - Unique identifier for OAuth flows

Best for:

  • Web applications
  • Mobile apps
  • Any app where users authenticate and control their own data

Pricing: Free

Next steps: OAuth Implementation Guide →

🤖 Personal (Own Account)​

Authentication: Client Credentials Flow

How it works: Your app performs automated actions directly on your own Monerium account, such as processing payments or checking balances.

Credentials you'll receive:

  • client_id - Unique identifier
  • client_secret - Secret key for authentication (keep secure!)

Best for:

  • Backend scripts
  • Scheduled jobs
  • Internal tooling and automation

Pricing: Free

Next steps: Client Credentials Guide →

🏢 White-label (Managed Users)​

Authentication: Client Credentials Flow

How it works: Your platform manages users and their payment accounts directly. Monerium is fully abstracted away from your end users—they never see or interact with Monerium.

Credentials you'll receive:

  • client_id - Unique identifier
  • client_secret - Secret key for authentication (keep secure!)

Best for:

  • Payment platforms
  • Fintech applications
  • Services requiring full control over user payment flows

Pricing: €5,000/month

Enterprise Solution

This is an enterprise solution for platforms that want to offer IBAN accounts under their own brand. Contact us to discuss your requirements.

Next steps: Client Credentials Guide →

Implementation Guides​

OAuth - Authorization Code Flow with PKCE (Proof Key for Code Exchange)​

For user-facing applications using OAuth with PKCE:

  1. Redirect users to the Monerium authorization endpoint
  2. Handle the returned authorization code
  3. Exchange the code for an access token
  4. Use the access token to make API calls

📖 Read the OAuth guide →

Client Credentials​

For server-to-server authentication (Personal and White-label):

  1. Securely store your client_id and client_secret
  2. Request an access token from the authorization server
  3. Use the access token to make API calls

📖 Read the Client Credentials guide →

Additional Resources​

Key OAuth Concepts​

  • OAuth 2.0 - The foundational framework for authorization. RFC 6749
  • PKCE - Security enhancement for public clients. RFC 7636
  • Client Credentials Grant - Server-to-server authentication flow. RFC 6749 §4.4
  • Bearer Authentication - Method for transmitting access tokens. RFC 6750

API Documentation​

Explore the complete API reference:

📖 View API Documentation →

Need Help?​

Join our Discord server to get help from the community and the Monerium team.