Questions worth answering precisely.

No. Stableflow never takes custody of funds and does not pool user assets. Transfers are executed by the underlying rail involved in the route — an intent solver, CCTP, an OFT layer or a native transfer.

A mixer pools funds from many users and is designed to make tracking impossible. Confidential routing does not pool anything: each transfer is executed individually and the destination settles as a normal public transaction. It hides the origin and the route, not the fact that money arrived.

No. A payout or payment only needs a destination address. There is nothing for the recipient to claim, sign or install.

No. You provide the destination address and receive a single-use deposit address. Wallet connection is only required on routes that cannot generate a deposit address, such as some direct on-chain routes.

28 today, spanning EVM chains, Solana, NEAR, Tron, Aptos, TON, Sui and Zcash. Coverage grows as new rails are integrated.

USDT, USDC, USDT0 and frxUSD are first-class, and any token deployed on a supported network can be routed where a rail exists for it.

The quote you see already includes the cost of the route. Integrators can additionally configure an application fee, which is shared with the underlying settlement provider.

Failed and expired payout rows keep all of their data and can be paid again from the history view without rebuilding the batch.

Not yet. A native Zcash origin is currently limited to a single recipient per payout; batches from other chains settle normally.

Yes. Typed packages for core quoting and execution, bridge routing, Hyperliquid deposits and wallet adapters across seven ecosystems.