Magma Documentation

Magma is a multi-tenant payments platform built for fintechs. From a single operator dashboard you onboard your customers (organizations), fund their accounts, send SWIFT / Wire / ACH payouts on their behalf, and run crypto-to-fiat payments end-to-end. This site is the customer-facing manual for that dashboard, plus the API reference for teams that want to integrate programmatically.

I want to…

• Invite a teammate - add another operator to your fintech.
• Create a customer - onboard a new organization and trigger KYC / KYB.
• Add a recipient - set up a fiat or crypto destination for payouts.
• Top up a customer - show your customer where to wire funds.
• Set up an on-ramp - register a destination wallet so inbound USD wires auto-convert to USDC / USDT.
• Send a fiat payout - debit a customer's balance and pay a SWIFT, Wire, or ACH recipient.
• Send a crypto-to-fiat payout - generate a single-use deposit address that auto-converts and wires the recipient.
• Look up the API - base URL, auth, idempotency, OTP, and a curated endpoint list.

How Magma is structured

Magma sits between you and the payments rails. Three tiers, top to bottom:

Magma (platform)
└── Fintech (you, the paying customer)
    └── Customers / Organizations (your end-clients)

Your operators log into the dashboard, manage customers, and run payments on their behalf. End-customers do not access the dashboard themselves - you operate it for them.

How this wiki works

Source of truth

The repo is the source of truth. The published site is just a rendered view of docs/ on the master branch. Click the pencil icon at the top-right of any page to edit it via pull request.

New here?

Start with Welcome to Magma, then read Roles & permissions so your team knows who can do what.