tl;dr
- Meta transactions let someone else pay the network fee, or let the user pay it in a stablecoin they already hold.
- By default, your Polygon wallets project sponsors every transaction. The cost is billed to you monthly in US dollars.
- You can limit sponsorship to a user’s first few transactions. Testnet transactions, smart sessions, and server wallet transfers are always sponsored.
- When a transaction is not sponsored, the user pays the fee in an accepted stablecoin, so nobody has to buy a gas token first.
Nobody opens a payments app to buy gas. They open it to send money, pay for something, or move a balance. The moment a product asks a new user to hold a network token before they can do any of that, most of them leave.
Meta transactions remove that step. They let someone else pay the network fee, or let the user pay it in the money they already hold. Polygon wallets handle both for you.
What are meta transactions?
On most blockchains, the account that sends a transaction also pays the fee for it. Gas pays for the computation, and the sender has to hold the network’s native token to cover it.
A meta transaction separates the two roles. One party signs the action they want to take. A different party submits it to the network and pays the fee. The user’s intent is still verified onchain; only the payer changes.
A wallet with rules at the account level is the cleanest way to do this. The account runs code onchain that controls the user’s funds and executes whatever the owner has signed. Because it checks the signature, not the sender, a relayer can submit the transaction and cover the gas without ever taking control of the funds.
A shopper paying by card never sees the processing fee the merchant pays. Users expect the same from a financial product: the fee is an implementation detail, not a checkout step.
There are two main types of meta transaction:
- Gasless transactions. Someone other than the user pays the fee, usually the app.
- Gas abstraction. The user pays the fee, but in a token other than the network’s native one, such as a stablecoin.
Polygon wallets support both.
How do they work?
A meta transaction is a regular transaction with another transaction inside it. The user signs the action they want with their key. That signed message goes to a relayer. The relayer wraps it in a second transaction and submits it to the network, paying the fee.
The account’s onchain code does the checking. It validates the signature, confirms it came from the wallet’s owner, and only then executes the action. It does not matter who submitted the transaction, as long as the signature is the owner’s.
With Polygon wallets, you do not build any of this. Sponsorship is configured once on your Polygon Open Money Stack project, and your application code never has to decide per transaction who pays. The user’s signed intent goes through the wallet infrastructure, and the fee is handled according to the rules you set.
Gasless transactions
Gasless transactions are the most common type of meta transaction: the user pays nothing. They can take their first action in your product (fund a balance, send a payment, approve a subscription) without ever acquiring a network token.
By default, your project sponsors every transaction. Gas is billed to you monthly, converted to US dollars at the time of each transaction, so you see a predictable cost line instead of a token balance to manage.
You do not have to sponsor everything. A common pattern is to cover a user’s first few transactions, so onboarding is free, and let later transactions fall through to the user. Some flows are always sponsored: transactions on testnets, transactions run through smart sessions (the pre-authorized permissions that power subscriptions and payouts), and transfers from server wallets.
Gas abstraction
Gas abstraction also relays the fee, but the user still pays it. The difference is what they pay with.
When a transaction is not sponsored, our wallet SDKs tell your app which tokens are accepted for the fee. The user can pay in a stablecoin instead of the network’s native token. They never need to buy POL, ETH, or any other gas token just to use your product.
For a payments business this matters more than it sounds. A customer holding USDC should be able to send USDC and pay the fee out of that same balance. Asking them to go find a second asset first is where conversion drops.
Each Polygon wallet SDK includes a fee-option selector. The simplest configuration picks the first available option, which covers both cases: if the transaction is sponsored, the selector returns nothing and the transaction continues; if it is not, the user pays in an accepted token. Handling both outcomes in your code means a change to your sponsorship rules never requires a code change.
Get started with meta transactions
If you are building a wallet, a checkout, or a payouts product, start with the gas sponsorship guide and the wallet quickstart. To compare platforms that support gas sponsorship, see stablecoin payments with gas sponsorship. For how fee handling fits into a full onboarding flow, read How to simplify user onboarding for a web3 app and What is an embedded wallet? For the pre-authorized flows that are always sponsored, see recurring subscriptions, payouts and checkouts on a non-custodial wallet.
Read the wallet documentation, or talk to a payments specialist about the flow you want to build.

Nuvera is live on Polygon Open Money Stack for cross-border stablecoin settlement

Web3 user onboarding: how to simplify it for your app

SoFiUSD lands on Polygon Chain, bringing America's first bank-issued stablecoin to everyday use

Polygon Trails partners with Foresight to bring 1-click fund flows to prediction markets

Scalable payment infrastructure: scaling payment apps without sacrificing UX

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

Polygon Trails partners with Katana to solve DeFi fragmentation with 1-click liquidity and real yield

Stablecoin infrastructure is fragmented: the structural barriers to scaling crypto payments

What is an embedded wallet? How embedded wallets work

