Skip to main content

How the Bridge Extension works and managed currencies

Syncing Rehive activity with Bridge custody and transaction flows

Helghardt Avenant avatar
Written by Helghardt Avenant
Updated yesterday

The Bridge Extension enables a direct integration between Rehive and Bridge, mapping all wallet and transaction activity 1:1 to Bridge’s infrastructure. This means your app’s balances, transactions, deposits, and withdrawals on Rehive are not simulated - they are reflected in real-time on Bridge wallets.


🔌 What the Bridge Extension does

At its core, the Bridge Extension:

  • Mirrors Rehive users as Bridge customers

  • Mirrors Rehive accounts as Bridge wallets (store-of-value)

  • Handles KYC using Bridge’s built-in identity flow

  • Enables fiat on/off ramps via virtual accounts

  • Supports crypto deposits and withdrawals via liquidation addresses

  • Initiates and syncs transactions between Rehive and Bridge

This integration ensures all Rehive-led actions are verified, executed, and traceable directly on the Bridge platform.

📖 For full details on supported functionality and configuration, visit:
👉 Bridge Extension Documentation


🧠 What is a “managed currency”?

The Bridge Extension is implemented as a currency manager, meaning it actively controls the transaction lifecycle of any Bridge-linked currency in Rehive. It listens for Rehive transaction events, triggers matching actions on Bridge, and only marks transactions as Complete once confirmed by Bridge.

This ensures full transactional integrity between Rehive and Bridge systems.

📖 Learn more about how Rehive handles managed currencies here:
👉 Currency Manager


✅ Summary

Using the Bridge Extension means your app's financial backend is directly powered by Bridge wallets and rails. Every deposit, withdrawal, and balance is managed through Bridge’s infrastructure, giving you the benefit of real custody and compliance - fully synced with Rehive’s user experience layer.

Did this answer your question?