Clavem

Selling and licensing a Figma plugin

Figma Community can sell a paid plugin for you for a flat 15% fee, with a Payments API that tells the plugin whether the user has paid. Use it if you are eligible and it covers your buyers. Sell with Stripe and Clavem when you need team invoices, a key shared with other products, or are not eligible.

Figma can sell it for you

Most plugin ecosystems leave payment to you. Figma does not. Its help center says eligible creators can sell files, plugins and widgets directly in Community. For plugins and widgets:

  • Figma collects “a flat 15% fee to cover transactional and operational costs”.
  • A Stripe account is required, and payouts are supported for a listed set of countries.
  • Prices are in whole US dollars with a minimum of 2.00. Plugins can use a one-time payment or a monthly subscription; widgets are one-time.
  • A paid plugin with a subscription includes a seven-day free trial by default, and the Payments API lets you build a custom trial.
  • A plugin or widget can move some functionality behind a paywall, but it “must still contain free features in addition to paid”.
  • Paid resources can only be published from individual accounts that have been approved to sell, not from team or organization profiles, and Figma does not support split payouts.

Inside the plugin, figma.payments.status reports PAID or UNPAID (it needs "payments" in the manifest permissions). You write no license server and no checkout page. For a solo author who qualifies, that is the simplest route, and it should be your first look.

Figma’s help center also says that it is not approving new creators to sell paid files at this time. Its wording for plugins and widgets still talks about eligible and approved creators, so confirm your eligibility in the publishing flow before you plan around it.

When to sell with Stripe and Clavem

Situation Figma payments Stripe and Clavem
Solo author, eligible, individual buyers Good fit Possible, more setup
Buyers are teams who want an invoice and a seat count Limited to what Community offers Quantity pricing, one key per seat, Stripe invoices
You also sell a Sketch plugin, a web app or a desktop app Figma only One key for all your products, if you want
Your country is not on Figma’s payout list, or you publish from an organization profile Not available Works wherever Stripe does
You want a trial longer or shorter than Figma’s Seven days for subscriptions; custom through the Payments API Any length
You want to keep the whole fee No You pay Stripe’s fee and Clavem’s flat plan

Selling outside Community means you handle VAT and sales tax through Stripe. Clavem is not a merchant of record.

Technical notes for plugins

Network access. Add networkAccess to manifest.json, with allowedDomains listing https://clavem.io. Figma’s docs also let you add a reasoning string that explains why a domain is needed, which reviewers read.

Null origin. Figma’s docs say plugin iframes have a null origin, so a plugin “will only be able to call APIs with Access-Control-Allow-Origin: *”. The Clavem License API answers with Access-Control-Allow-Origin: *, and its preflight response allows the content-type header, so a JSON fetch from the plugin UI works. A form-encoded body avoids the preflight altogether.

Storage. figma.clientStorage keeps data on the user’s local machine and does not synchronize it across users. Figma’s own docs call it private for stability, not security. Store the key, the instance id and the token there, and expect a determined user to see them.

No machine id. A plugin has no hardware identifier. Generate a random id on first run, keep it in clientStorage, and send it as fingerprint with an instance_name such as Figma plugin (a3f9). Because storage is local to the client, a person who uses the plugin on two computers, or in the desktop app and a browser, may take more than one device slot.

Outages. Keep the signed token, so a brief outage of the License API does not lock paying users out of the plugin.

Setting Suggested value Why
License type Annual subscription, or one-time for a utility Matches what Figma Community offers, so buyers know it
Device limit 5 Browser, desktop app and a second computer all count
Trial 7 to 14 days in the plugin Same range as Figma’s built-in trial
Updates Figma delivers plugin updates Clavem only gates the paid features

Doing this with Clavem

Create a product, connect Stripe, map the price. In the plugin UI, a field takes the key, activate runs once, and validate runs when the plugin opens. Keep the paid code paths behind licensed. The Figma plugin guide has the code, and the offline guide shows how to verify the token.

Guides to follow

Questions

Can a Figma plugin call my own license server?

Yes, if the manifest lists the domain in networkAccess.allowedDomains and the server answers with Access-Control-Allow-Origin set to a star. Plugin iframes have a null origin, so only servers that allow any origin work. The Clavem License API does.

Does Figma Community let me sell plugins from a team account?

Figma's help center says paid resources cannot be published from team or organization profiles; they must come from individual accounts approved to sell on Community.

Sources

  1. Figma Help, About selling Community resources (checked November 2026)
  2. Figma Developer Docs, figma.payments (checked November 2026)
  3. Figma Developer Docs, making network requests (checked November 2026)
  4. Figma Developer Docs, plugin manifest (checked November 2026)
  5. Figma Developer Docs, clientStorage (checked November 2026)