Skip to main content
Paymasters enable gasless transactions by sponsoring transaction fees on behalf of your users, so they can begin using your application before acquiring SOL.

What is a Paymaster?

A paymaster is a Solana wallet managed by Swig that:
  • Holds SOL for sponsoring transaction fees
  • Signs transactions as the fee payer
  • Tracks usage for billing and limits
  • Enforces limits to prevent abuse
When a user submits a transaction through your application, the paymaster covers the transaction fee, allowing users to transact without holding SOL.

How It Works

Subscription Requirements

Paymasters are available on paid tiers only:
FREE tier accounts cannot create paymasters. Upgrade to PRO or higher to access paymaster features.

Key Concepts

Paymaster Limits

Each paymaster has configurable limits:

Monthly Limits

Your subscription tier determines your monthly sponsorship limit:
  • Measured in USD value
  • Resets at the start of each billing period
  • Overage billing applies if exceeded

Paymaster Balance

Each paymaster needs SOL to sponsor transactions:
  • Fund the paymaster after creation
  • Monitor balance to prevent failed transactions
  • Low balance alerts available for Enterprise

Use Cases

User Onboarding

Remove friction for new users:
  • Users can begin transacting immediately
  • Immediate access to your application
  • Higher conversion rates

In-App Transactions

Seamless in-app experiences:
  • Token transfers
  • NFT minting
  • DeFi interactions
  • Game actions

Subscription Services

Automate recurring transactions:
  • Payment processing
  • Subscription renewals
  • Scheduled operations

Paymaster vs Direct SDK

Getting Started

Create a Paymaster

Set up your first paymaster

Manage Paymasters

Configure settings and monitor usage

Transaction History

View sponsored transactions and analytics

Security

Access Control

  • Paymasters are scoped to your project
  • API keys authenticate requests
  • Per-paymaster limits prevent abuse

Allow Other Instructions

By default, paymasters only sponsor Swig-related instructions. You can enable allowOtherIxs to sponsor any instruction, but use caution:
Enabling allowOtherIxs allows sponsoring any transaction type. This increases flexibility but also potential for abuse.

Monitoring

  • Track all sponsored transactions
  • View real-time usage metrics
  • Set up alerts for anomalies

Best Practices

Start with Limits

Begin with conservative limits:
  • Low single transaction limit
  • Moderate monthly threshold
  • Increase as you understand usage patterns

Monitor Usage

Regularly review:
  • Transaction volume
  • SOL spending
  • Error rates

Maintain Balance

Keep paymaster funded:
  • Monitor balance regularly
  • Set up low balance alerts (Enterprise)
  • Automate top-ups if possible

Separate Environments

Use different paymasters for:
  • Development (devnet)
  • Staging
  • Production (mainnet)

Next Steps