> ## Documentation Index
> Fetch the complete documentation index at: https://docs.metalntwx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Interoperability

> How Metal coordinates payments and asset movement across networks

Financial assets and payment systems already span many networks.
Interoperability allows an action completed on one network to cause a
corresponding action on another. A payment or policy decision made on Metal
could, for example, authorize the release of an asset held elsewhere. Metal
could also act on an outcome produced by another network.

> [!WARNING]
>
> Connections between the Metal Testnet and other public networks are under
> development.

## Why Metal needs interoperability

No single network contains every asset, customer, or financial service. An
institution may want to use Metal's payment controls and settlement while
continuing to work with assets and systems on other networks. Interoperability
lets these systems work together. Institutions can connect Metal to existing
financial activity without requiring every participant and asset to move onto
the same network.

## How Metal approaches interoperability

Cross-network actions follow decisions that have become final. The party that
carries a decision between networks can deliver it, but cannot change its
recipient, amount, or intended outcome.

![A finalized Metal decision is relayed with a proof and verified before a contract acts on the destination network.](https://mintcdn.com/nexus-ed339086/CdWwGT0bcT9zD-Uw/images/start/cross-network-action.svg?fit=max\&auto=format\&n=CdWwGT0bcT9zD-Uw\&q=85\&s=4de8337f380e5c7ce7bbe5dc7e390dc3)

> [card] [Light Clients and Messages](https://docs.metalntwx.com/learn/interop/overview.md)
>
> Continue to the interoperability section for the architecture and message
> flow.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.