Introducing Batched Transactions on Portal

One signature, many actions

A batched transaction groups several calls together and executes them as one atomic unit. Either everything in the batch succeeds, or nothing does. That removes a whole class of half-finished states, like an approval that goes through while the swap behind it fails.

‍

For your users, the experience is simple: one confirmation instead of a sequence of them. For your product, it means flows that used to take several screens can happen in a single step. Approve and swap. Claim and stake. Pay an invoice and settle a fee. The actions that naturally belong together now ship together.

Gas paid in stablecoins

Native gas tokens are one of the most persistent points of friction in onchain UX. A user holds USDC and wants to send USDC, but the transaction won't go through until they also hold the chain's gas token. That is a confusing detour, and for payments products it can be a dealbreaker.

‍

Batched transactions on Portal let gas be paid in ERC20 stablecoins. Your application can sponsor gas for a user and be repaid in stablecoins as part of the same batch, so the cost is settled in the asset everyone is already using. Users transact with the token in their wallet. They never have to think about gas at all.

One-tap yield

Earning yield looks like one action to a user. Move idle balance into a position that earns. Under the hood, it rarely is that simple. The token they hold isn't always the token the protocol wants, so first there's a swap. Then the protocol needs an approval before it can touch those funds. Only then can the deposit go through. Three transactions, three confirmations, three moments where a user can hesitate, get confused, or walk away, all to do the one thing they actually asked for.

‍

This is exactly the friction holding back the neobanks and fintechs racing to put yield in front of their users. An "earn 5%" button shouldn't open into a three-step gauntlet of wallet prompts.

‍

With batched transactions on Portal, the swap, the approval, and the deposit collapse into a single signature. The user holds USDC, taps once, and lands in the position. The routing to the right token, the approval, and the entry all execute atomically. Either they're earning, or nothing happened and their balance is untouched. No half-finished state where the approval cleared but the deposit failed, and no native gas token to source along the way. What feels like one action to your user finally is one action.

Built on MPC and account abstraction

This is the combination Portal has been building toward. MPC gives every user a self custodial wallet with no seed phrase and no single point of compromise. Account abstraction gives that wallet the programmability to batch calls and abstract gas. Together they let you offer a wallet that is both genuinely user owned and genuinely easy to use.

‍

Under the hood, the flow is straightforward to integrate. You build a user operation that describes the batch, sign it through Portal's MPC signer, and broadcast it onchain. The signing keys stay split across parties the entire time, so the security model is exactly the same as every other transaction on Portal.

What you can build

• One-tap yield. Swap, approve, and enter a position in a single confirmation, so "earn" is one tap instead of three.
• Payments that settle in one step. Pay a merchant and cover the network fee in stablecoins, all in a single confirmation.
• Trading flows without the approval dance. Approve and execute a swap together so users aren't bounced between two prompts.
• Sponsored onboarding. Let new users take their first onchain action immediately, with gas handled in the background and reconciled in stablecoins.
• Any multi step action. Wherever your product chains calls together today, batch them into one transaction your user signs once.

Get started

Batched transactions are available through the Portal API, with SDK support rolling out. If you're building payments, trading, or any flow where users do more than one thing at a time, this is the cleanest way to ship it.

‍

Reach out to the Portal team to get access, and check the docs for the build and broadcast user operation endpoints.