For Stablecoin Processors
Settlement infrastructure that never misses
When you process payments, a dropped transaction is a failed settlement. Pimlico executes your onchain transactions reliably, at low latency, on 100+ chains.
Trusted by the best teams in stablecoin payments
Built for payments
What payment-grade execution requires
Every chain that matters
One integration covers 100+ chains, so expanding to a new corridor never means new infrastructure.
Gas in stablecoins
Run your whole operation in stablecoins, fees included
A payments company shouldn't hold a volatile gas treasury on every chain it settles on. With Pimlico, transaction fees are paid in USDC, USDT, or 300+ other tokens, so your users pay fees from the balance they already hold and your books stay in stablecoins end to end.
// Same client, plus one line — token approvals are injected for you
const smartAccountClient = createSmartAccountClient({
// ...same setup as before, plus:
userOperation: {
prepareUserOperation: prepareUserOperationForErc20Paymaster(pimlicoClient),
},
})
const txHash = await smartAccountClient.sendTransaction({
to: "0x...",
value: parseEther("0.1"),
paymasterContext: {
token: usdc, // any of 300+ supported ERC20 tokens
},
})Quotes locked for 30 seconds
The fee you show at checkout is the fee that settles. Every quote holds long enough for the payer to confirm, with no gas volatility mid-payment.
Failed payments cost nothing
Token collection is atomic with execution. A payment that reverts takes no fee, with no pre-funding and no trust assumptions to make.
Approvals your security review will pass
Per-transaction, exact-amount approvals on non-upgradable contracts audited by OpenZeppelin and Quantstamp: the same contracts the issuer of USDC runs on.
Boosted Sponsorships
Faster checkout, settled by invoice
For latency-sensitive checkout flows, Boosted Sponsorships make user operations 34–43% faster by stripping sponsorship out of the hot path, and gas settles by monthly invoice: the billing model your finance team already expects. Access is granted on request.
Your checkout submits a payment
No paymaster data to fetch and no extra signature round-trips.
Pimlico sponsors off-chain
Three RPC calls disappear from the hot path entirely.
Gas settled monthly
One invoice instead of per-operation on-chain deductions.
The onboarding ramp
Sponsor the first transfer, stablecoins after
The adoption pattern that works: sponsor an account's first transfers so nothing blocks activation, then let fees come out of the stablecoins that land. One client and one policy engine cover both, so the switch is a config change, not a migration.
A new account starts transacting
Its first transfers are sponsored under your policy. No balance needed at all.
Stablecoins land
Deposits arrive in the account, and there is still no native token to buy.
The same client switches to ERC-20 gas
Fees come out of the USDC, USDT, or 300+ other tokens the account already holds.
Security & transparency
Every payment accounted for
Moving other people's money means being able to answer "where is this payment?" at any moment. Every operation is traceable in the dashboard from received to included on-chain, with millisecond timestamps and transaction hashes at each step.
Spend is tracked live and itemized by policy, chain, and time, with custom alerts that fire before a budget or limit is hit, not after settlement stops.
Track user operation
Received
2026-06-11 20:01:13.054
Added to Mempool
2026-06-11 20:01:13.054 (+0ms)
Submitted
2026-06-11 20:01:13.341 (+287ms)
Tx Hash: 0x223b701f...Included Onchain
2026-06-11 20:01:13.590 (+249ms)
Tx Hash: 0x223b701f...Risk controls
Your risk engine approves every sponsorship
You already run KYC and fraud checks on every payment, so point the same risk engine at gas sponsorship. Pimlico calls your endpoint before sponsoring, and your server approves or rejects each request in real time: a flagged account never gets a sponsored transfer.
// Pimlico calls your endpoint before sponsoring. You decide.
export async function POST(req: Request) {
const { data } = await req.json()
const { userOperation, chainId, sponsorshipPolicyId } = data.object
// Your rules: KYC status, fraud signals, allowlists — anything
const user = await lookupUser(userOperation.sender)
return Response.json({
sponsor: user.verified && !user.flagged,
})
}Sanctions screening built in
OFAC screening enforced on every transaction at the infrastructure layer, with nothing for your team to bolt on.
Ship with confidence
Test everything before it touches mainnet
Payment flows don't get to fail in production. Rehearse, validate, and debug the full pipeline before real money moves.
Free test environments
Every testnet across 100+ chains, with no surcharge on sponsored gas, so the full settlement flow is rehearsed end to end before production.
Open source
No black box between your checkout and the chain
Alto, the open-source bundler, is the same code Pimlico runs in production, hardened by 250M+ real transactions. Your team can audit exactly what executes your settlements, and you keep an exit path if you ever need one.
We also co-authored the standards this industry builds on: ERC-4337, ERC-7677, and ERC-7679.
In production
Who already settles on Pimlico
Coverage
Every corridor, one integration
Expanding to a new market never means new infrastructure: one API covers 100+ chains.
A few of the networks Pimlico settles on
Ethereum
Base
Arbitrum
Optimism
Polygon
BNB Chain
AvalancheWorks with your stack
Plug in the custody you already use
Treasury and payout signing through institutional key management, embedded wallets at checkout: Pimlico sits below your signing layer, so whichever setup you run, it already works.
Key management
Embedded wallets for checkout
Smart accounts
Any viem-compatible signer works as an owner. If it can sign, it works.
Frequently asked questions
Can we put an SLA on settlement?
Yes. Inclusion averages under 2 seconds on L2s, with gas escalation, resubmission, and re-org recovery handled automatically. Enterprise plans add custom uptime SLAs, 24/7 monitoring by a dedicated team, and phone support.
Which stablecoins can pay for gas?
USDC, USDT, and 300+ other ERC-20 tokens. Your users pay fees in the balance they already hold, and you run your treasury in stablecoins with no native-token inventory to manage across chains.
How does billing work?
Pimlico fronts the gas on-chain and bills you the actual cost plus a 10% surcharge on mainnet, with no surcharge on testnets. Boosted Sponsorships settle by monthly invoice instead, and Enterprise plans get lower pre-negotiated rates.
How do you handle compliance?
OFAC sanctions screening is enforced on every transaction at the infrastructure layer. Pimlico is SOC 2 Type 1 certified, and the paymaster contracts are audited by OpenZeppelin and Quantstamp.
What happens during a volume spike?
User operations execute in parallel, with up to 100 concurrent operations per account using 2D nonces. Bursts never queue behind themselves, so a spike in payment volume does not back up your settlement pipeline.