What a bridge actually does
Each blockchain is a separate, self-contained ledger. A token sitting on Ethereum is an entry in Ethereum's state; nothing on Tron or Solana knows it exists. A bridge spans that gap. In the most widely used pattern — often called lock-and-mint — you deposit the asset into a contract or custodian on the source chain, where it is locked, and an equivalent amount is minted on the destination chain as a representation of the original. Send it back, and the representation is burned and the original is released. The locked supply on one side is meant to always back the issued supply on the other.
That representation is usually a wrapped token: a token on the destination chain that stands in for an asset native to a different chain, redeemable for the original through the same bridge. Wrapped bitcoin issued on Ethereum is the classic example — the underlying BTC is held on Bitcoin while a token representing it circulates on Ethereum. The wrapped version is only as good as the bridge holding the backing; if the lock is compromised, the representation loses what stands behind it.
Bridges differ in who is trusted to hold the locked funds and authorize minting. Some rely on a custodian or a small set of validators; others use more decentralized validation. Because a bridge concentrates locked value and the authority to mint, it is a frequent target — several of the largest crypto losses on record have been bridge exploits. Bridging is a real capability, but it adds a trust assumption and a moving part that the underlying chains do not have on their own.
Bridges and crypto payments
For a customer paying an invoice, a bridge is rarely part of the flow they see. They pay with the asset they hold, on the network they hold it on. Bridging matters more to people managing balances across chains — for instance, consolidating funds onto one network — and it is where a same-named asset can become a different on-chain object. "USDC" is not a single thing across every chain: USDC issued natively on Ethereum and a bridged representation of USDC on another chain are not always interchangeable, and confusing the two is a common source of stuck or unrecoverable funds.
The practical takeaway for a merchant is to be precise about which asset on which network you actually accept and hold. A bridged or wrapped form of a token is not automatically the same as the native asset, even when it shares a ticker. Knowing the exact network for every balance avoids sending funds across a bridge by accident or accepting a representation you cannot redeem.
Bridges and halfin
halfin is not a bridge and does not ask you or your customers to bridge anything to get paid. Each supported asset is accepted on the specific networks halfin runs gates for — Bitcoin, Ethereum and its ERC-20 tokens, Base, Arbitrum, Polygon, BNB Smart Chain, Tron, the XRP Ledger, and Solana — and a payment is detected and credited on the chain it arrives on. There is no cross-chain lock-and-mint step in receiving a payment; the asset stays on its own network, and halfin credits the fiat-anchored balance once the chain's confirmation threshold is met.
Balance conversion is the closest adjacent feature, and it is deliberately different from a bridge. Conversion rebalances one asset into another within your halfin balance — it is asset-to-asset treasury movement, not a bridge you operate and not a way to wrap or unwrap tokens across chains, and it is never a fiat off-ramp. Because halfin only supports assets it has gates for, you never need to bridge an unsupported token into a supported one; you accept and settle in the networks and assets halfin already handles.