Clavem

Move off FastSpring without invalidating the license keys you already sold

How you move FastSpring keys depends on how they were generated. Keys from a pasted list or your own server can be imported as they are, while CocoaFob, AquaticPrime and Software Passport keys are verified offline and need that check kept in your app.

Start with how your keys are made

FastSpring does not have one kind of license key. As of November 2026 its fulfillment docs describe a generated license, a pre-defined list you paste in, a PHP or JavaScript script, a remote server that FastSpring calls with the order, CocoaFob, AquaticPrime and Software Passport. The route to your keys, and what must stay in your app, depends on which you use:

Generator Where the key comes from What to do
Pre-defined list A list you pasted in You already have the keys. Match them to buyers through the orders.
Script or remote server Your own code or server The keys are also in your database. See homegrown license server.
Generated by FastSpring FastSpring Read them from the orders.
CocoaFob, AquaticPrime Your DSA or AquaticPrime keys, from the buyer’s name or email The app verifies them offline. Keep that code.
Software Passport Your Software Passport project settings Keep Software Passport verification in the app.

For the last two rows the “key” is a string or file derived from the buyer’s name or email, checked with a public key inside your app. Importing the string into Clavem lets Clavem track it and answer validate calls, but installed copies of your app will keep verifying it the old way. Leave that verifier in the new build and call Clavem when the offline check fails, or the other way round. Do not remove it until you are sure no one still runs an old build.

Step 1: read the keys from your orders

For remote generation, FastSpring’s docs say the key is saved as part of the order record, and other generators should behave the same way, but confirm that on your own orders. The /orders endpoint lists orders and takes these parameters: begin and end as yyyy-mm-dd, days, limit (default 50), page, products, rebill, returns, scope (all, live or test) and status (completed, cancelled or failed). Use scope=live and status=completed and walk the pages. In each order, customer.email is the buyer and items[].product the product path.

On each item the webhook payload documents a fulfillments object whose entries have type (such as license), display, size and file. The reference does not say which property holds the key text, and it does not show the list response envelope. Pull one real order from your own store, find a key you know, and write the extraction around what you see.

Reshape what you collect into the columns Clavem reads:

key,email,name,created_at,activation_limit
7QX2M-4KD9P-ZR8TB-W3NVH-61CJA,ada@example.com,Ada Lovelace,2024-03-04,2

FastSpring’s device limits are not in the order. If your app enforced a limit, put it in activation_limit, or leave the column out and set the Clavem product’s limit. If a buyer bought a quantity of two with “one key per quantity”, they have two keys, two rows with the same email, which Clavem allows.

Step 2: import and check

Choose Import, CSV or JSON file, pick the Clavem product and read the column preview before sending. The file is sent in batches of 500, bad rows are listed by position and the rest still import, and running it again is safe. FastSpring has no device list, so the keys show as valid with 0 devices until each app activates. See Import existing licenses.

Validate one key by hand:

curl https://clavem.io/v1/licenses/validate -d license_key=7QX2M-4KD9P-ZR8TB-W3NVH-61CJA

Step 3: the app

If your app validated keys against your own server or a FastSpring remote request, replace that call with Clavem’s /v1/licenses/activate once per device and /v1/licenses/validate on launch, as in the API reference. Keys that were verified offline need no network change. Add the Clavem path next to the existing one so both kinds of key work in one build.

Subscribers

FastSpring is the merchant of record, so it and its payment processors hold the saved cards. In a post dated January 2022, which FastSpring still publishes, the process for a seller who leaves has these properties:

  • It covers credit card tokens only. FastSpring says it cannot migrate PayPal tokens.
  • FastSpring provides lists of active subscribers by payment method and processor, signs a letter of intent for each processor and connects you, the new vendor and the processor.
  • The new vendor must be PCI compliant, and the process “usually takes 10 weeks”.
  • You deactivate the subscriptions in FastSpring, in the dashboard or with the /subscriptions API, once they are running elsewhere. Otherwise customers are billed twice.

Treat those as a 2022 description and ask FastSpring what applies now. On the Stripe side, its Data Migrations team executes the import for an outside processor and returns a mapping file, and Stripe says to cancel the previous subscriptions as soon as the Stripe ones are active.

Clavem takes no part in moving cards. It extends a key from Stripe events only when the key was issued by a Stripe purchase, and an imported key has no Stripe subscription. For subscribers, import the key with an expires_at set to the end of their paid period and move it with PATCH /v1/admin/licenses/:id, or ask them to subscribe through a new Stripe link and receive a new key. An empty expires_at means the key never expires.

Leaving a merchant of record also moves tax collection onto you. This is general information, not advice; ask an accountant before you switch.

Rollback

Importing only reads. Keep FastSpring live, keep the old verifier in the app, and keep subscriptions there until each has been moved and checked. Put the host of the License API behind a setting so one release can switch it back, and keep the CSV you imported as an archive.

Questions

Does FastSpring's order data include the license keys?

FastSpring's docs say that, with remote generation, the key is saved as part of the order record, and its order webhook documents a fulfillments object on each item with a type such as license. The reference does not show which property holds the key text, so pull one real order and check.

Can FastSpring subscribers move to Stripe without re-entering their card?

FastSpring has described a process that migrates credit card tokens through its payment processors to a new vendor. It does not migrate PayPal tokens, and its own 2022 post gave about ten weeks. Ask FastSpring for the current process.

Will old keys keep working in my app?

Only if the app can still check them. Offline schemes keep working with the code you already ship. Keys that your server validated need that server, or an import into Clavem and an app update.

Sources

  1. FastSpring, license key fulfillments (checked November 2026)
  2. FastSpring, the orders endpoint (checked November 2026)
  3. FastSpring, the order.completed webhook payload (checked November 2026)
  4. FastSpring, subscription export process (post dated January 2022, read November 2026)
  5. Stripe, import payment data to Stripe (checked November 2026)