Skip to main content
Manage liquidity across fiat currencies, stablecoins, and payment networks from a single infrastructure layer. StableStack helps treasury and finance teams move operational liquidity between markets, currencies, and settlement networks without maintaining separate payment integrations for every corridor.

What You Can Build

  • Stablecoin treasury management
  • Cross-border liquidity movement
  • Fiat to stablecoin conversion
  • Stablecoin to fiat conversion
  • Liquidity rebalancing
  • Funding of local payout operations
  • USD liquidity management
  • Multi-currency settlement
  • Operational wallet management

How the Flow Works

Treasury operations typically follow this pattern: Source liquidity → StableStack → conversion / liquidity routing → destination asset → wallet or payment rail The destination can be another stablecoin, fiat currency, wallet, or bank account depending on the use case.

Common Flows

Fiat to Stablecoin

USD → USDC A business converts fiat liquidity into a supported stablecoin for cross-border movement or operational settlement.

Stablecoin to Fiat

USDT → USD Stablecoin liquidity is converted into USD and routed to a supported bank rail.

Stablecoin to Stablecoin

USDT → USDC A business can move between supported stablecoins when required for liquidity management, network availability, or downstream settlement.

Cross-Border Liquidity Movement

NGN → USDT → USD Local liquidity is converted into a stablecoin, moved through the supported network, and converted into the required settlement currency.

Treasury Rebalancing

StableStack can be used to move liquidity between operational balances. For example: USD balance → USDC → supported blockchain → local payout liquidity This allows a treasury operation to prepare liquidity before customer or supplier payouts are initiated.

Liquidity Routing

StableStack’s liquidity layer sits between the source of funds and the final settlement rail. The objective is to determine an available route based on factors such as:
  • Source currency
  • Destination currency
  • Stablecoin
  • Blockchain network
  • Destination country
  • Payment rail
  • Available liquidity
  • Transaction requirements
Your application does not need to maintain a separate integration for every route.

Example

A financial platform needs to fund NGN payouts from USD liquidity. USD → USDC → StableStack → NGN → NIBSS → beneficiary The application can initiate the transaction while StableStack orchestrates the conversion and payout flow.

Core Flow

1

Set up merchant-level wallets for each reserve

Create separate merchant wallets for different purposes (e.g., a USDC wallet on ERC20 for operational receipts, a USDC wallet on Polygon as a secondary reserve). No customer_id is required for merchant wallets.
2

View all wallets and balances

Get a consolidated view of all merchant wallets and their balances for treasury reporting.
3

Distribute funds to subsidiaries or partners

When disbursing to an entity with a crypto wallet, send directly to their stablecoin address.
4

Off-ramp to a bank account

Convert stablecoin reserves to fiat and pay directly into a bank account — useful for covering local operating expenses or settling invoices.
5

Audit the full transaction history

Query all transactions across your merchant account for reconciliation, audits, or reporting.
Filter by transaction ID or reference ID for precise lookups:

Treasury Architecture Pattern

A typical StableStack treasury setup uses layered wallets:
Each wallet has a dedicated on-chain address. Inbound deposits trigger wallet.transaction.inbound webhooks, giving your treasury system real-time visibility.

Key APIs Used


Relevant Webhook Events


Next Steps