Give incoming payments a purpose.
Connect customer wallet provisioning, collection registrations and payment orders. Keep asset identity, expiry and payment status together.
See supported routesOne integration for collections, payment workflows and payouts. Keep customer signing authority, make approvals explicit, and give your team a clear view of every outcome.
Private sandbox · Live transfers are not enabled
Retain one original payment identity.
Apply tenant permissions and limits.
Signing stays at the customer boundary.
Keep pending and unknown results visible.
Bringing stablecoins into a business means connecting more than a wallet. Azums brings the operational pieces into one customer-controlled workspace.
Connect customer wallet provisioning, collection registrations and payment orders. Keep asset identity, expiry and payment status together.
See supported routesSeparate request creation, policy checks, approval and customer signing. Give each teammate the permissions their role actually needs.
Read the API contractsInspect original attempts, retained events and recovery cases. An uncertain result stays uncertain until the backend has evidence.
Discuss sandbox accessExplore the supported sandbox routes. Asset and network identities stay explicit throughout each workflow.
USDC_SOL
The sandbox does not issue real receiving addresses or payable QR codes. Do not send funds.
Explore the current API reference, inspect the server SDK and understand the authorization model before integrating.
GET /v1/auth/me
GET /v1/organizations/{org}/wallets
POST /v1/organizations/{org}/payment-orders
POST /v1/organizations/{org}/payouts
# Tenant permissions + explicit approvals
# Exact asset amounts + original request identityRust owns authentication, permissions and financial state.
Fintechs and payment businesses building stablecoin products. Azums supports business payment workflows.
Customer asset signing stays with the fintech, end user or verified external non-custodial signer. The Azums frontend does not collect customer private keys.
No. The current platform is a fixture-backed sandbox. Real balances, receiving destinations and native payment execution are not yet available. The private pilot is for evaluating the integration.
No. The current scope is official USDT on Solana, native USDC on Solana and Base, and USDC-only cross-chain workflows.
Tell us what you are building, which routes you need, and where your current integration gets difficult.
Discuss a private pilot support@getazums.com