ERC-4337 • Polygon • USDC Paymaster

NoKYC Gas Station

The dApp user pays for gas + our AA infrastructure fee in USDC (compare with Pimlico).
Zero KYC. Production-grade ERC-4337 paymaster on Polygon.

Integrate Now
Live on Polygon
99.9% Uptime
USDC-first
AA INFRASTRUCTURE

No Registration Required

Developers do not need to sign up or create an account. Just point your dapp to https://nokycgas.com and start calling pm_sponsorUserOperation.

How to Integrate

One RPC call. The dApp user pays for gas + AA infrastructure fee in USDC. No KYC. Works with any ERC-4337 wallet or SDK.

POST /
pm_sponsorUserOperation
{
  "jsonrpc": "2.0",
  "method": "pm_sponsorUserOperation",
  "params": [userOp, entryPoint],
  "id": 1
}
✓
Returns paymasterData, gas limits, and accurate USDC estimates
✓
Supports referral addresses and basis points
✓
Approximate cost fields for dApp UX: approximateTotalCostUsdcE6
BUNDLER PROXY (CORS)
Use https://nokycgas.com/bundler/rpc instead of raw bundler port
PRICING
The dApp user pays for gas + our AA infrastructure fee in USDC (default service fee 10%, compare with Pimlico).
Real-time USDC/gas rate and approximate total cost are returned in every sponsor response.
REFERRAL REVENUE

Monetize Every Sponsored UserOp

Integrated dapps can charge for their own service at the same moment users pay gas. Add your referral context to sponsorship requests and your fee is included in the USDC charge flow.

What your users see

  • •One clear total fee in USDC before submission.
  • •Gas + infra + dapp service fee combined in one transparent flow.
  • •Better trust and fewer checkout surprises.

How you integrate it

Pass referral context in params[2] of pm_sponsorUserOperation:

{
  "referralAddress": "0xYourRevenueAddress",
  "referralBps": 200
}

Example above: 200 bps = 2.00% referral fee.

COMPARISON

NoKYC vs Pimlico

Built for teams that want a simple integration plus transparent user-facing economics.

NoKYC Gas Station

  • - Dapp user pays gas + AA infra fee in USDC.
  • - Pricing fields are returned in sponsor response for dapp UX.
  • - One integration flow: paymaster RPC + bundler proxy endpoint.
  • - Fee model and reserve strategy are visible and explicit.
  • - Optimized for clear conversion messaging to end users.

Typical Pimlico Setup

  • - Requires developer registration and direct payment to Pimlico services.
  • - Sponsorship economics are usually abstracted behind provider defaults.
  • - Dapp teams commonly add their own explanation layer for users.
  • - Provider-centric controls and dashboards depend on external product choices.
  • - Great managed option; less opinionated on your public conversion narrative.
LIVE

Current Network Status

Loading live metrics...