Use cases
Merces gives a business a private balance on the chain it already uses. What that unlocks depends on what publishing the ledger would otherwise cost you.
| Use case | What a public ledger would expose | |
|---|---|---|
| Payments, payroll & batch | Every recipient, every amount, and the timing of each run — salary bands, vendor lists, cash-flow signals | Read |
| Treasury management | Every buy, sell and rebalance in real time, plus reserve size and strategy | Read |
| Card payments & delegated spend | Every purchase a cardholder makes, as a public spending diary | Read |
| On/off ramp | Conversion size and frequency, the moment funds land | Read |
Two further use cases have their own sections: Private RWAs for tokenized funds, credit and securities, and Agent Solutions for agent-to-agent payments.
Choosing a mode per flow
Most of these use more than one privacy mode, selected per transaction rather than fixed for the deployment. Domestic payroll might run confidential — amounts hidden, parties visible — while cross-border settlement runs private, with parties hidden too.
What they have in common
Every use case below runs on the chain the business already uses, with no migration and no new asset. Compliance is enforced at the boundary and on confidential transfers rather than bolted on afterwards, and every state change leaves a verifiable onchain record that can be audited without decrypting what sits behind it.