Purple-to-blue gradient cover with the Polygon logo at top left, the headline "MPC wallets: what they protect, and what a payments product still needs" in white, a three-line list icon at top right, and a glossy blue-and-orange hexagonal block holding coins at right
Wallets

November 6, 2026

MPC wallets: what they protect, and what a payments product still needs

tl;dr

  • MPC protects how a private key is stored. It does not set spend limits, scheduled payments, or recovery rules. Those live in the account itself.
  • A wallet with rules at the account level enforces limits, permissions, and recovery onchain.
  • The two are not exclusive. Polygon’s embedded wallets keep signing keys in hardware enclaves and enforce the rules in the account.
  • Account-level rules (pre-authorized payments, spend limits, recovery through linked sign-in methods) are what payments products need as they grow. Starting with them avoids a later migration of users from one wallet model to another.

If you are choosing wallet infrastructure for a financial product, the decision you make now is one you will live with for years. Two designs dominate the conversation: multi-party computation (MPC) wallets, and wallets that enforce rules at the account level. They answer different questions. MPC is about how a key is protected. Account-level rules are about what the account can do. For a payments product, the second question usually decides what you can grow on.

What MPC wallets protect

Most MPC wallets are still externally owned accounts (EOAs), standard accounts controlled by a single private key. What MPC changes is how that key is handled: it is split into shares held by different parties, and a threshold of them has to cooperate to sign. That is a real improvement on a single key in a single place. But the account itself is the same first-generation primitive: one key (however it is assembled), one signature per transaction by default, and no rules of its own.

What a wallet with account-level rules adds

In this design the account has logic onchain: it is either a contract account, or an EOA that delegates to contract code (EIP-7702). That code verifies signatures, but it can also enforce rules: which signers are valid, what they are allowed to do, how much, until when, and what happens if a key is lost. Features that have to be built around a plain EOA are part of the account.

The two choices are not mutually exclusive. Key protection and account design sit at different layers, and a wallet can have both. Polygon’s wallets do: signing keys are held in hardware-isolated enclaves, and the account enforces the rules.

The gap shows up most when a product grows. Teams that start on an MPC EOA can find they need capabilities the account does not provide (pre-authorized recurring payments, spend limits enforced onchain, recovery that does not depend on a single device) and face a re-architecture to get there. Migrating users from one wallet model to another is slow, expensive, and risky. Starting with account-level rules avoids that migration.

MPC wallets vs wallets with account-level rules

MPC improves how a key is stored, and a threshold of parties has to agree before a transaction is signed. But in an EOA the address is derived from the key. Many MPC schemes can refresh the shares, yet the address stays tied to the underlying key, so replacing the key typically means moving to a new address. A wallet with account-level rules keeps its address while its signer set changes onchain.

Capability MPC wallet (typically an EOA) Wallet with account-level rules
Account type Standard externally owned account; the address is derived from the key Account with onchain logic: a contract account, or an EOA delegated to contract code (EIP-7702)
Key management Private key split into shares; a threshold signs Any signer scheme the account allows: weighted multi-signer, session keys, recovery keys
Gas sponsorship and paying fees in stablecoins Added through a separate relayer or paymaster service Part of the account model: a relayer can submit signed actions, and the fee can be sponsored or paid in a stablecoin
Batched transactions (approve + pay in one step) One transaction per signature by default Supported by the account
Pre-authorized actions (subscriptions, payouts, agent budgets) Not part of the account Scoped, time-limited permissions enforced onchain
Spend limits and policy at the wallet layer Typically enforced off-chain by the provider Session limits enforced by the contract, with optional policy checks before a transaction is submitted
Key rotation and signer changes Address is tied to the key, so a new key typically means a new address Signer set updated onchain; the wallet address stays the same
Recovery Depends on how the provider handles shares Built in: linked sign-in methods, with timed recovery as a last resort
Upgradability Adding account-level capabilities usually means moving to a new account model Configuration (signers, session rules, recovery) can be updated without changing the address

Why this matters for payments

Consider what a modern payments product needs from a wallet:

  • A customer approves a subscription once, and it runs every month without a new signature.
  • A business sets a budget and an expiry for an automated payout run, or for an AI agent that pays suppliers.
  • A user who signed in with Google or an email code loses their phone, signs in with another linked method, and reaches the same wallet, with no seed phrase to find.
  • The product pays the network fee for a user’s first transactions, then lets later fees be paid in USDC.

Every one of these is an onchain permission or a wallet-level rule. They belong in the account, not in a service wrapped around it. That is what a wallet with rules at the account level gives you.

Our recommendation

Choose a wallet with rules at the account level. It gives you the key protection an MPC wallet offers, plus the rules your product will need next. If you have already built on an MPC EOA, moving later is non-trivial, so the earlier you decide, the cheaper the decision.

We built Polygon’s embedded wallets to enforce these rules in the account. They are non-custodial. Users sign in with an email code or social login (Google, Apple, or a custom OIDC provider), and several sign-in methods can be linked to the same wallet. Your project can sponsor gas, smart sessions let users pre-authorize payments within limits and an expiry they approve, and recovery runs through the linked methods, with timed recovery as a last resort. Signing keys are held in hardware-isolated enclaves, and Polygon cannot unilaterally move user funds (see how keys are secured and how recovery works). They are part of the Polygon Open Money Stack, so the same integration covers fiat ramps, settlement, and customer-approved yield.

To go deeper: Custodial vs non-custodial wallets covers the custody decision, and What is an embedded wallet? covers the user-experience side. The webinar Wallets: Choosing Your Architecture goes through the trade-offs, security, and UX. For fee handling, see Gasless transactions and gas abstraction.

Read the wallet documentation, or talk to a payments specialist about the wallet model that fits your product.

More Blogs