Skip to main content
Use mode: 'eoa' for users with standard Ethereum wallets like MetaMask, Rabby, Trust Wallet, or any WalletConnect-compatible wallet.

How EOA Mode Works

EOA mode uses Fusion execution—a system that lets regular wallets access Biconomy’s gas abstraction without needing a smart account.
1

User specifies funding tokens

You tell the API which tokens the user will spend
2

API returns permit or approval payload

Depending on token support, user either signs a gasless permit or sends an approval tx
3

User signs

One signature per funding token
4

MEE executes

Biconomy handles the rest

Basic Request

Required Parameters

Understanding fundingTokens

This is the key difference from other modes. You must specify exactly which tokens the user is spending:
The amount should cover both the operation AND any fees. If you’re paying fees in the same token, include enough for both.

Multiple Funding Tokens

If your operation involves multiple input tokens, list them all:
Each funding token requires a separate signature. 2 tokens = 2 signatures.

Fee Token Rules

When using EOA mode, the feeToken must match one of your fundingTokens:

Quote Response

The API returns different quoteType values based on token capabilities:

Signing the Payload

Most modern tokens (USDC, DAI) support permit—user signs typed data:

Complete Example

Important: Withdraw Funds

In EOA mode, swapped tokens land in a temporary Nexus account. Add a withdrawal instruction to send them back to the user’s EOA:
Without the withdrawal instruction, tokens stay in the Nexus account and user won’t see them in their wallet!

Next Steps

Sign Payload

Detailed signing guide

Execute

Submit and track your transaction