EIP-7702 lets a regular Ethereum address (an EOA, the kind MetaMask hands you when you create a wallet) temporarily borrow the powers of a smart contract. For one transaction, or for a longer window if you choose, your address can batch calls, sponsor its own gas, recover from a lost key, or auto-route a payment, then snap back to a normal EOA. It shipped with the Pectra upgrade in May 2025 and changed what stablecoin payments can look like without forcing anyone to migrate funds.
​

This article walks through what EIP-7702 actually does, how it differs from ERC-4337, and the six stablecoin payment patterns it unlocks: batched USDC transfers, gasless payments via paymaster, social recovery, auto-swap on receive, merchant pull payments, and subscription debits. We close with the delegation phishing risk and how live wallets like MetaMask Smart Account, Ambire, and Daimo are handling it.
​

An Externally Owned Account is the wallet you control with a private key. It can sign transactions, but it cannot run code. A smart contract account can run code, but historically you had to deploy a new contract and move funds into it, which most users never bothered to do.
​

EIP-7702 introduces a new transaction type (0x04) that carries an authorization list. Each authorization signs over a contract address. When the transaction executes, the EOA's code field temporarily points at that contract. Any call to the EOA during the transaction runs the contract's logic, with the EOA's storage and balance. When the transaction ends, the delegation either persists (until revoked) or clears, depending on how the wallet sets it up.
​

The practical effect: your existing address keeps the same balance, the same history, the same ENS name, but now it can do things only smart contracts could do before. No migration, no new address to share with anyone.
​

ERC-4337 (account abstraction, live since March 2023) lets users operate a separate smart contract wallet through a parallel mempool of UserOperations and a bundler. It works, but it requires deploying a new contract account and moving assets to it. The bundler infrastructure is also separate from normal Ethereum transaction flow.
​

EIP-7702 takes a different path. It upgrades the EOA itself rather than asking users to switch to a new account type. There is no new contract to deploy per user. There is no parallel mempool. The same transaction format goes through the regular Ethereum network. ERC-4337 contracts can be reused as the delegate target, so a wallet vendor can write one verified implementation and have every user delegate to it.
​

The two specs are complementary. EIP-7702 is the on-ramp; ERC-4337 is the destination architecture for users who want a fully separate smart account. For stablecoin payments specifically, 7702 removes the migration step that kept smart wallet adoption in the single digits.
​

A normal EOA can send one USDC transfer per transaction. To pay five contractors, you sign five times and pay five base fees. With 7702 delegation to a batch executor contract, your wallet signs once and the contract loops through five transfer calls atomically. If any one fails, the whole batch reverts, so you never half-pay a payroll run. Daimo and Ambire both ship this as a default in their 7702 wallets.
​

Without 7702, a user holding only USDC has to acquire ETH before they can move that USDC. With a 7702 delegation to a paymaster-aware contract, the wallet can attach a paymaster that pays gas in ETH on the user's behalf and either eats the cost (sponsorship) or charges the user a USDC fee inside the same transaction. The recipient sees a clean USDC transfer; the user never touches ETH.
​

Lose your seed phrase on an EOA and the balance is gone. With 7702, the EOA can delegate to a recovery module that lets a quorum of guardians (other addresses you trust, hardware keys, or a passkey on a second device) replace the signing key after a timelock. The funds never move. Anyone who already has your address pinned for invoicing keeps using it. This is the feature that makes a stablecoin wallet acceptable to a small business that cannot lose payroll to a lost laptop.
​

A delegate contract can run logic on inbound transfers. If a customer sends ETH or another token to your address, the delegate can route it through a DEX and settle the position in USDC, all in the same transaction the inbound transfer triggered. The address looks like a stablecoin-only inbox to the rest of the world while accepting any asset.
​

EOAs cannot grant scoped permissions; once you approve a token spend, the spender can pull up to the limit at any time. A 7702 delegate can enforce session keys with caps, expirations, and per-merchant allowances. A coffee shop can pull up to $50 in USDC per day from your address for the next 30 days, after which the permission self-expires. No gas-spending approve transaction every visit.
​

Same primitive, longer window. A SaaS vendor or streaming service receives a signed authorization to pull a fixed USDC amount on a fixed cadence. The user can revoke at any time by clearing the delegation or by re-delegating to a contract that voids the session. This is the closest crypto has come to ACH-style recurring billing without a custodial intermediary.
​

MetaMask Smart Account, announced in early 2025 and rolling out alongside Pectra, uses 7702 to let any MetaMask user opt into batched and gasless transactions on their existing address. Ambire has been a 7702 advocate since the EIP was drafted and ships batch transactions, paymaster sponsorship, and recovery as a single user setting. Daimo, which started as a USDC-first payments wallet, uses 7702 delegation to issue passkey-controlled session keys for everyday spending while keeping a hardware key as the recovery anchor.
​

On the infrastructure side, Pimlico, Biconomy, and Alchemy have all shipped paymaster and bundler endpoints that accept 7702 transactions, and Safe published a 7702-compatible module for users who want to delegate to a Safe implementation without redeploying.
​

The dominant risk is that a user signs a 7702 authorization to a malicious contract, granting it the ability to drain or misroute funds whenever it is called. This is a step up in damage from a normal token approval, because the malicious contract effectively becomes the wallet's logic. The mitigations are wallet-side: every reputable 7702 wallet whitelists a known set of audited delegate contracts and shows an explicit warning when a dapp asks the user to delegate elsewhere. Users should treat a delegation prompt the way they would treat a seed phrase prompt, not the way they treat a token approval.
​

A 7702 delegation can persist across transactions until the user revokes it. That is a feature for wallet vendors who want batching to stay on, but it means a delegation set during a phishing attack also persists. Wallets should expose a clear "active delegations" panel; revocation is a single transaction that authorizes the zero address.
​

Stablecoin payments care about three things EOAs handle badly: predictable fees (solved by paymasters), recoverability (solved by social recovery modules), and recurring authorizations (solved by session keys). 7702 lets a payment app deliver all three on the wallet a user already has, instead of asking them to migrate. For merchants and payroll operators routing payments through Eco Routes, the practical upshot is that more end-user wallets can accept and send stablecoin payments without holding ETH for gas.
​

Yes. It shipped as part of the Pectra upgrade on Ethereum mainnet in May 2025, alongside EIPs that raised the validator stake cap and added blob throughput.
​

Most major L2s (Optimism, Base, Arbitrum) have shipped Pectra-compatible upgrades or are scheduled to. Coverage is wider on L2s for stablecoin payments because that is where the volume sits.
​

No. They cover different audiences. 7702 upgrades EOAs in place; 4337 is for users who want a fully separate smart account, often with custodial features. The same delegate contract architecture serves both.
​

Yes. Sign a new 7702 authorization pointing at the zero address, or to a different contract. The old delegation clears at the next transaction.
​

This article draws on the EIP-7702 specification at eips.ethereum.org/EIPS/eip-7702, Vitalik Buterin's 2024 post outlining the EOA-upgrade rationale, the Pectra release notes on ethereum.org, and public documentation from MetaMask, Ambire, Daimo, Pimlico, and Safe describing their 7702 implementations as of May 2025.
​