Skip to main content

​
Introduction

Bridgfy is a multi-tenant SaaS platform for cross-chain asset routing. It automates the movement of EVM-based assets across blockchain networks using a webhook-driven architecture. Access to the platform is managed through Organizations and Teams, making it easy for businesses to integrate cross-chain functionality into their applications. Unlike traditional bridge interfaces where users connect a wallet and sign a transaction, Bridgfy operates as a “fire-and-forget” system. Users or applications configure a Deposit Intent (destination chain, token, and address), and Bridgfy provides a unique deposit address. When funds land in that address, Bridgfy detects them automatically, calculates fees (protocol + gas), and executes the bridge transaction without requiring any further user interaction.

​
Getting Started

To use Bridgfy:
  1. Create an account at the Bridgfy Dashboard
  2. Create or join an Organization to manage your API keys
  3. Generate an API key with your preferred fee settings
  4. Integrate the API into your application
All API keys are scoped to an Organization, allowing teams to collaborate and track usage together.

​
Supported Chains

Bridgfy currently supports the following EVM chains:
ChainChain IDKeyNative TokenSupported Tokens
Base8453baseETHETH, USDC
Ethereum1ethereumETHETH, USDC
Polygon PoS137polygonMATICMATIC, USDC
Arbitrum One42161arbitrumETHETH, USDC
Avalanche C-Chain43114avalancheAVAXAVAX, USDC
Note: Additional tokens can be routed even if not explicitly listed above. Bridgfy operates with an open token policy, accepting any ERC-20 token not on the security blacklist. See Token Support for details.

​
Key Concepts

​
Multi-Tenant Architecture

Bridgfy uses a hierarchical access model: 
User → Organization → API Key → Executions
  • Users authenticate via the Dashboard using Google OAuth or email/password
  • Organizations represent teams or businesses using Bridgfy
  • API Keys belong to Organizations and are used for programmatic API access
  • Executions are tracked per API key for usage monitoring and billing

​
Deposit Intent

A Deposit Intent is a user-scoped configuration that tells Bridgfy “where should funds go?”. It maps a userId to a destination tuple: (targetChainId, targetTokenAddress, targetAddress).
  • Deterministic Address: Based on the intent’s fingerprint, Bridgfy provisions a stable Modular Account address
  • Snapshotting: Fee settings (like protocolFeeBps) are captured from your API key at creation time, ensuring consistent pricing for future deposits

​
Webhook-Driven Flow

Bridgfy uses webhooks to detect incoming deposits automatically:
  1. Deposit Detected: When funds arrive at a deposit address, the system is notified via webhook
  2. Validation: The deposit is verified and matched to the user’s Deposit Intent
  3. Route Resolution: The system requests a quote from routing providers to find the best path
  4. Execution: If a valid route exists and fees are covered, the transaction is submitted to the blockchain automatically

​
Execution Lifecycle

Every attempted route becomes an Execution record with a lifecycle status:
  • PENDING: Route resolved, preparing transaction
  • RUNNING: Transaction submitted to the network
  • SUCCESS: Transaction confirmed on the source chain
  • FAILED: Execution failed (e.g., simulation error, network timeout)
  • Terminal Statuses: Specific error states like TOKEN_BLACKLISTED or FAILED_INSUFFICIENT_AFTER_FEES that indicate non-recoverable failures

​
Glossary

TermDefinition
Modular AccountA smart contract wallet (ERC-6900/4337 style) managed by Bridgfy on behalf of a user
Atomic UnitsThe smallest unit of a token (e.g., “wei” for ETH, micro-units for USDC). All API money fields use stringified atomic integers
Protocol FeeA percentage fee (in bps) taken by the platform before routing. Deducted on the source chain
Gas SponsorshipWhen Bridgfy covers the gas cost. If disabled, the user pays gas from the deposit amount
LI.FIThe underlying bridge aggregator/router provider
Deposit IntentUser-scoped configuration specifying where deposited funds should be routed (destination chain/token/address)
ExecutionA tracked attempt to bridge funds, with lifecycle states (PENDING, RUNNING, SUCCESS, FAILED)

​
Next Steps