Merces puts a privacy layer over blockchain payments
TACEO's limited launch on Monad and World Chain aims to let payments settle without publishing private balances. Some of its more ambitious features are still on test networks.
Article
Paying a contractor should not require publishing the rest of your company’s finances.
On a public blockchain, that can be a problem. Once someone connects an address to your business, its visible transfers can reveal who you pay and how much money moves through it.
TACEO’s Merces is meant to keep the payment on a public blockchain while keeping the financial details private. Its September 24 launch covers Monad and World Chain, but with an important qualification: the deployment documentation lists limited users and volume caps, not unrestricted public access.
A payment without opening the whole book
Imagine a small company paying three contractors. Each contractor needs to know they were paid. They do not need to see the company’s remaining balance or what the other two received.
That is the practical problem Merces addresses. Its private accounts hold encrypted balances alongside an existing public wallet. Tokens enter through a deposit, move within the private system and can leave through a withdrawal.
The company’s payment app would integrate this infrastructure. It is not a new bank account that every reader can open today, and “private” does not mean every detail is hidden from every party in every circumstance.
TACEO’s follow-up announcement draws the distinction between what is on mainnet and what is still being tested:
Payments settle on mainnet today.
TACEO (@TACEO_IO) · September 25, 2026
How it checks a payment without exposing the balance
Two technical ideas do different jobs:
- Split the private information. Merces describes balances distributed as secret shares across computing operators. One share alone is not the readable balance. This approach is called multi-party computation.
- Prove that the rules were followed. A zero-knowledge proof lets the blockchain check the specified calculation without revealing the private inputs used to make it.
In plain terms, the system aims to check “this payment is valid” without displaying everyone’s account details. It still depends on the implementation and its security assumptions. A cryptographic proof is not a guarantee that an entire application is safe.
Privacy does not mean removing compliance
The design includes checks before a transfer settles and a way to disclose selected records afterward. TACEO’s documentation names Predicate as the current default screening provider. Identity verification remains the integrating business’s responsibility.
That is a different promise from making all activity permanently invisible. It aims to protect ordinary financial confidentiality while allowing specified checks and disclosures.
What is real today, and what is next?
TACEO says its own team uses an internal payment app, Tapa, with real funds on Monad. That is a useful concrete use claim, but it is still the operator reporting its own use. We have not completed a payment or independently verified that activity.
Its published deployment table supports deposits, withdrawals and transfers with limits on the two production networks. Yield and cross-chain bridging are not marked available there. Test-network demos are not evidence that those features are ready for unrestricted real-money use.
For a builder, the useful next question is specific: can this fit a real payment flow, with acceptable privacy, access, cost and reliability? For everyone else, the story is simpler. Public settlement does not have to mean a public statement of every customer’s finances, but this launch is still early and constrained.
Sources and reporting notes
Checked September 27, 2026. Scope and internal-use claim: TACEO’s September 24 launch article. Live limits take precedence over broad feature language: deployment status. Mechanism: private-account documentation and Merces overview. Disclosure and identity responsibilities: compliance documentation.
These are operator sources, not an independent security audit. We have not verified performance benchmarks, partner production use or user totals, so none is presented as established adoption. The embedded post is the issuer’s explanation, not public consensus.