# Paymasters: who pays for a smart-account operation?

An ERC-4337 paymaster can agree to cover a user operation’s gas through the EntryPoint, subject to its validation and payment policy. It may sponsor selected actions or charge the user in another way. “Gasless” usually describes the user experience; network execution still has a cost and sponsorship can be refused.

Evidence: [Account Abstraction Using Alt Mempool](https://eips.ethereum.org/EIPS/eip-4337)

Canonical: https://degreesofsatoshi.com/encyclopedia/smart-account-paymasters/
Published: 2026-10-02
Substantively modified: 2026-10-02
Independently verified by an automated reviewer: 2026-10-02T18:12:41.505Z
Data current through: 2026-10-02

AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied.

## Key facts

- **Validation:** The paymaster participates in validating whether it will cover an operation. ([Account Abstraction Using Alt Mempool](https://eips.ethereum.org/EIPS/eip-4337))
- **Funding:** EntryPoint deposits support paying applicable gas charges. ([Account Abstraction Using Alt Mempool](https://eips.ethereum.org/EIPS/eip-4337))
- **Policy:** Sponsorship conditions are implementation-specific. ([Account Abstraction Using Alt Mempool](https://eips.ethereum.org/EIPS/eip-4337))

## Move the payment responsibility, not the computation cost

A user can interact without holding native ETH for the immediate gas charge if a suitable paymaster funds the operation. The paymaster may receive compensation elsewhere or treat the charge as a service expense.

This does not remove gas metering or make every smart-account action free. Identify who pays, which operations qualify and whether another token is charged.

Evidence: [Account Abstraction Using Alt Mempool](https://eips.ethereum.org/EIPS/eip-4337)

## Authorization to execute differs from authorization to sponsor

An account may validly authorize an operation while the paymaster refuses it because of policy, insufficient funding or changed conditions. Conversely, available sponsorship does not give the paymaster unrestricted authority over the account.

The exact powers depend on the account, paymaster and any allowances or additional contracts involved. Review those relationships rather than the marketing label.

Evidence: [Account Abstraction Using Alt Mempool](https://eips.ethereum.org/EIPS/eip-4337)

## Failed work can still create costs

Validation and execution have distinct stages and accounting rules. Paymasters need to handle the specified post-operation flow and potential execution failure.

A user interface should distinguish a sponsorship rejection from a contract execution revert, and show any user-paid token charge before authorization.

Evidence: [Account Abstraction Using Alt Mempool](https://eips.ethereum.org/EIPS/eip-4337)

## Questions

### Can a paymaster guarantee that I will never need ETH again?

No. Coverage depends on the supported account stack, funding and policy for each operation. A service can change or refuse sponsorship.

Evidence: [Account Abstraction Using Alt Mempool](https://eips.ethereum.org/EIPS/eip-4337)

## Claims and scope

### smart-account-paymasters-quick-answer

An ERC-4337 paymaster can agree to cover a user operation’s gas through the EntryPoint, subject to its validation and payment policy. It may sponsor selected actions or charge the user in another way. “Gasless” usually describes the user experience; network execution still has a cost and sponsorship can be refused.

Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null}

### smart-account-paymasters-fact-validation

Validation: The paymaster participates in validating whether it will cover an operation.

Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null}

### smart-account-paymasters-fact-funding

Funding: EntryPoint deposits support paying applicable gas charges.

Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null}

### smart-account-paymasters-fact-policy

Policy: Sponsorship conditions are implementation-specific.

Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null}

## Sources

- [Account Abstraction Using Alt Mempool](https://eips.ethereum.org/EIPS/eip-4337) — Ethereum Improvement Proposals. User operations, bundler transaction submission and paymaster validation. Locator: Specification; Bundlers; Paymasters; Security Considerations. Retrieved: 2026-10-02T17:03:42.486Z.

## Revision history

- 2026-10-02: First publication after primary-source research and independent automated verification.

## Cite this entry

Degrees of Satoshi editorial project. “Paymasters: who pays for a smart-account operation?.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/smart-account-paymasters/