Sponsor fees - Rhinestone

Choose sponsorship per intent. You can cover all supported fee categories, cover selected categories, or prepare the transaction as user-paid.

Sponsorable fees

Fee	Sponsorable	When it applies
Gas	Yes	Executing and settling the transaction.
Bridge fee	Yes	Moving assets between chains.
Swap fee	Yes	Swapping assets along the route.
Protocol fee	Yes	A Rhinestone protocol fee configured for the intent. It accrues to Rhinestone.
App fee	No	Revenue charged by your application remains user-paid.

Rhinestone applies your configured sponsorship surcharge to surcharge-bearing costs advanced through the relayer flow. Externally settled provider subsidies and sponsored protocol fees do not incur that surcharge. See Pricing for the rates on each plan.

A sponsored request does not silently become user-paid when billing, a policy, or a budget rejects it. Prepare a new unsponsored transaction only after your application has shown the revised quote and the user has accepted it.

Embedded wallet
Custom signer

Complete the shared sponsorship setup, then start with the embedded-wallet example in Send a transaction. It defines wallet, the source and target tokens, and the real transfer calls used below.Embedded wallets select funding with sponsorshipMode:

Mode	Behavior	Required tokens
`required`	Sponsorship must succeed. This is the default and fails closed.	App access token and extension token.
`preferred`	Try sponsorship, then obtain a new self-funded quote if sponsorship fails.	App access token; extension token while sponsorship is attempted.
`disabled`	Request a self-funded quote.	App access token only; the wallet does not fetch an extension token.

const result = await wallet.sendIntent({
  accountAddress,
  targetChain: arbitrum.id,
  sourceChainId: base.id,
  sourceAssets: [usdcOnBase],
  tokenRequests: [{ token: usdcOnArbitrum, amount }],
  calls: [...calls],
  sponsorshipMode: "required",
  experimental_clear_signing: true,
  closeOn: "completed",
});

This example enables the experimental clear-signing review. Use preferred only when the user-paid fallback is part of the flow you present to the user. The wallet re-quotes before changing the funding mode; it does not reuse the sponsored quote. Set sponsorshipMode: "disabled" to request a user-paid quote directly.Configure sponsorship on WalletClient even for user-paid intents. The application access token authenticates the app and project for every user intent; only the extension token requests sponsorship. See Set up for the shared client configuration and Policies and security before exposing grants to a client.Embedded wallets do not expose controls for individual fee categories. They support the intent-level modes above; use the custom signer SDK when your product needs to choose gas, bridge, swap, or protocol-fee sponsorship separately.

Try sponsored and user-paid transfers

Send 0.1 mUSD on Base Sepolia, switching between required sponsorship and disabled user-paid mode. Sign in and mint mock tokens if needed. The user-paid flow needs enough source assets for the transfer and fees; both modes still authenticate your application with an access token.This demo does not exercise preferred fallback or per-category sponsorship. Use Check status for a pending intent rather than sending it again.

Use the backend-held SDK instance from the custom signer tab in Set up. Start with the custom signer example in Send a transaction, which defines the source and target chains, tokens, and real transfer calls.Set sponsored: true when preparing that transaction to request sponsorship for gas, bridge, swap, and protocol fees:

const prepared = await account.prepareTransaction({
  sourceChains: [base],
  sourceAssets: [usdcOnBase],
  targetChain: arbitrum,
  tokenRequests: [{ address: usdcOnArbitrum, amount }],
  calls: [...calls],
  sponsored: true,
});

Use the object form to select categories. Set gas, bridging, and swaps explicitly; protocolFees is optional and defaults to false:

const prepared = await account.prepareTransaction({
  sourceChains: [base],
  sourceAssets: [usdcOnBase],
  targetChain: arbitrum,
  tokenRequests: [{ address: usdcOnArbitrum, amount }],
  calls: [...calls],
  sponsored: {
    gas: true,
    bridging: true,
    swaps: false,
    protocolFees: false,
  },
});

For a user-paid quote, omit sponsored or set it to false. The user’s source assets cover the applicable fees. Inspect the selected quote’s fee breakdown before signing; the total cost alone does not identify who pays each category.

Sponsorship is available for same-chain and crosschain intents. Mainnet charges accrue to your organization’s sponsorship account. Testnet sponsorship does not accrue billed usage or consume the mainnet limits described in Policies and security.

​Sponsorable fees

​Try sponsored and user-paid transfers

Sponsorable fees

Try sponsored and user-paid transfers