One ecosystem. One set of APIs.
Banking, cards, acquiring, custody, issuance and trading, each behind the API of the ecosystem company that holds the licence for it. Chain-level SDKs and docs live on blockmaze.org. Sandbox credentials come after the first call.
The APIs
What you can call, and who you contract with.
01 — Identity. KYC and KYB, liveness, screening, reliance between ecosystem entities.
02 — Accounts and payments. Accounts, IBANs, transfers, FX, payouts, webhooks.
03 — Cards. Card creation, controls, tokenisation, disputes.
04 — Acquiring. Merchant onboarding, checkout, settlement.
05 — Custody and register. Holdings, transfers, corporate actions, attestations.
06 — Issuance. Offerings catalogue, eligibility, subscriptions, allocations, documents.
07 — Trading. Orders, positions, market data for tokenised stocks, gold, treasuries and listed offerings.
08 — Chain. Nodes, token standards, smart contracts, explorer.
How access works
Keys follow a conversation, not a sign-up form.
The sandbox is free. Production keys are issued under the partner agreement.
- 01
Apply
What you want to build, your company, your licences if any.
- 02
The call
Which APIs, which model, which entity. If you only need the chain, you go to blockmaze.org.
- 03
Sandbox
Keys, test accounts, test cards and test offerings. Everything mocked that touches money.
- 04
Certification
Your flows reviewed: onboarding, eligibility, settlement, error handling.
- 05
Production
Live keys, rate limits set, named coverage.
What you get in the sandbox
Enough to build the whole product before anyone signs.
- Reference docs and SDKsREST with OpenAPI specs; SDKs for TypeScript, Python, Java and Kotlin; webhooks for every state change.
- Test everything that touches moneyTest KYC outcomes, test accounts with balances, test cards, test offerings with every status, test trades.
- Compliance in the loopEligibility by country and appropriateness are enforced in the sandbox exactly as in production, so you never ship a flow that production will refuse.
- A personA named engineer on our side for the build, from the first key.
Rules of the road
What the APIs will and won’t let you do.
Every user is verified before they transact
Identity is a precondition, enforced by the API. There is no anonymous path.
Eligibility is ours to enforce
Which offerings a user can see and buy is decided by country and category inside the API, not by your front end.
Marketing copy about offerings is approved
What you show about an offering comes from the catalogue; your own copy is reviewed before it goes live.
Who you contract with
Each API belongs to the entity that holds its licence. One agreement can cover several; the agreement says which.
FAQ
What developers ask first.
Not yet. The call takes twenty minutes and saves you building against the wrong entity.
The sandbox is free. Production pricing is set under the partner agreement.
On blockmaze.org: node software, token standards, contract libraries and the explorer API.
Yes, with identity built in; see the Wallets page. Custodial models carry different regulatory treatment.
Build it in the sandbox first.
Apply, take the call, get keys.