How to Tell If a Website Uses FastSpring

FastSpring is a merchant-of-record ecommerce platform built for selling software, SaaS and digital goods globally — handling payments, worldwide tax and compliance on the seller's behalf. To tell whether a site uses it, the quickest answer is to open the Network tab and look for the Store Builder Library from sbl.onfastspring.com and the global fastspring object. This guide covers every reliable signal, the merchant-of-record model behind them, the peer platforms to distinguish it from, and what a FastSpring integration tells you about the business and how it sells internationally.

What is FastSpring?

FastSpring, founded in 2005, is a commerce platform specialising in digital and software products with a distinctive merchant-of-record (MoR) model. As the merchant of record, FastSpring is the legal seller in each transaction: it processes the payment, calculates and remits sales tax, VAT and GST across jurisdictions worldwide, handles invoicing, fraud and chargebacks, and then pays the software company. This removes an enormous compliance burden — managing global tax registration and remittance is famously painful — which is why FastSpring is popular with software vendors, SaaS companies and digital-goods sellers that want to sell internationally without building and operating billing and tax in-house.

For detection, the key context is that FastSpring is chosen specifically to offload the hard parts of global selling. Finding it therefore signals a software or digital business that sells across borders and prioritised frictionless, compliant checkout over owning its billing stack. The integration can be embedded into the merchant's own site (popup or inline checkout) or run as a FastSpring-hosted store, both of which leave clear traces on the onfastspring.com domain.

How FastSpring integrates and sells

FastSpring's modern integration uses the Store Builder Library (SBL), loaded from https://sbl.onfastspring.com/sbl/<version>/fastspring-builder.min.js. The SBL exposes a global fastspring object (and a fastspring.builder API) that manages the cart and launches checkout. Buttons and elements on the merchant's page are wired up with data-fsc-* attributes (FastSpring Contextual) — for example data-fsc-item-path-value, data-fsc-action="Add,Checkout" — which the SBL reads to add products and trigger the purchase flow. The checkout itself is a popup/overlay served by FastSpring or a redirect to a FastSpring-hosted store, both on onfastspring.com.

Because FastSpring is the merchant of record, the entire payment, tax and invoicing process happens within FastSpring's hosted checkout, not on the merchant's own server — so, as with other hosted checkouts, you will not find a separate payment processor's fields on the merchant page. Detection focuses on the sbl.onfastspring.com library, the fastspring global, the data-fsc-* attributes, and the onfastspring.com checkout. Knowing these makes FastSpring straightforward to identify.

How to tell if a website uses FastSpring

Confirm at least two of the following, ideally on a pricing or buy page.

1. Check the Network tab. Filter for fastspring or onfastspring. The Store Builder Library from sbl.onfastspring.com is the clearest signal, alongside any onfastspring.com checkout traffic.

2. Use the console. Type fastspring and press Enter. A returned object (with a builder API) confirms the SBL is loaded.

3. Inspect buy buttons. Search the source for data-fsc- attributes such as data-fsc-item-path-value or data-fsc-action, which wire up FastSpring's cart and checkout.

4. Trigger the checkout. Clicking a buy button opens a FastSpring popup/overlay or redirects to an onfastspring.com store — a clear confirmation, often showing localised pricing and tax.

5. Look for the storefront domain. Hosted FastSpring stores are served on <store>.onfastspring.com, which identifies the FastSpring account.

What the FastSpring signals look like

<script src="https://sbl.onfastspring.com/sbl/1.0.x/fastspring-builder.min.js"
        type="text/javascript" id="fsc-api" data-storefront="example.onfastspring.com/popup-example"></script>
window.fastspring = { builder: { add: ƒ, checkout: ƒ, … } }
<button data-fsc-item-path-value="pro-plan" data-fsc-action="Add,Checkout">Buy</button>
// Checkout popup served from onfastspring.com

The combination of the sbl.onfastspring.com library, the global fastspring object, and data-fsc-* attributes (or an onfastspring.com checkout) is conclusive.

FastSpring versus other billing tools — avoiding false positives

Match the host to keep merchant-of-record and billing platforms distinct. FastSpring uses onfastspring.com and the fastspring global; Paddle (another popular MoR for software) uses cdn.paddle.com, a Paddle global and paddle.com checkout; Lemon Squeezy uses lemonsqueezy.com; Stripe is a payment processor (not a merchant of record) using js.stripe.com. The MoR distinction matters: FastSpring and Paddle take on tax and compliance, while Stripe leaves those to the merchant — so finding FastSpring tells you something specific about why the company chose it. The data-fsc-* attribute prefix and the onfastspring.com domain are unique to FastSpring, so confusion is unlikely once you see them.

How reliable is each FastSpring signal?

The sbl.onfastspring.com Store Builder Library and the global fastspring object are definitive. The data-fsc-* attributes on buy buttons are equally strong and characteristic. An onfastspring.com checkout popup or hosted store is conclusive. The localised pricing and tax shown in the checkout corroborate the merchant-of-record model. The weakest case is a pricing page that loads the SBL only when a buy button is clicked, so interact with the purchase flow if the library is not present on load. As a rule, the SBL host or the fastspring global settles it.

What a FastSpring integration reveals about a business

Finding FastSpring signals a software, SaaS or digital-goods company selling internationally that deliberately chose to offload payments, global tax and compliance to a merchant of record. That decision says a lot: the business sells across borders (otherwise MoR tax handling would be overkill), values speed and compliance over owning its billing stack, and is likely a focused software vendor rather than a physical-goods retailer. The products and pricing in the FastSpring checkout reveal whether it sells one-off licences, subscriptions, or both. If you sell to software companies — developer tools, growth, analytics, or billing-adjacent services — a FastSpring integration marks a global-selling software business. The MoR choice also tells you the company prioritised reducing operational and legal overhead, which is useful context for positioning.

FastSpring in a software-selling stack

FastSpring sits within a software or SaaS go-to-market stack. The site is typically a product marketing site (often on a modern framework or a SaaS-oriented CMS), with FastSpring handling the buy flow, subscriptions and global tax. Around it you will commonly find product analytics, a CRM, an email/marketing-automation platform, and sometimes a separate licensing or entitlement system that FastSpring's webhooks feed. Because FastSpring is the merchant of record, you will not find a separate payment processor or tax tool doing that job. For an auditor, the valuable details are whether the integration is embedded (SBL with data-fsc-*) or a hosted onfastspring.com store, whether pricing is subscription or one-off, and the surrounding SaaS tooling; together these reveal a global-selling software business and how it goes to market.

A quick FastSpring confirmation walkthrough

Open the site's pricing or buy page with developer tools on the Network panel and filter for fastspring or onfastspring. Look for the Store Builder Library from sbl.onfastspring.com. Switch to the Console and type fastspring to confirm the object and its builder API. Search the source for data-fsc- attributes on buy buttons. Click a buy button to confirm a FastSpring popup or an onfastspring.com redirect, noting the localised pricing and tax. Two signals confirm FastSpring and show whether the integration is embedded or hosted.

A quick FastSpring detection checklist

• Filter the Network tab for onfastspring; the sbl.onfastspring.com library is conclusive.
• Type fastspring in the console to confirm the SBL object and builder API.
• Search the source for data-fsc-* attributes on buy buttons.
• Trigger checkout to confirm an onfastspring.com popup or hosted store.
• Note localised pricing/tax, reflecting the merchant-of-record model.
• Distinguish FastSpring from Paddle (cdn.paddle.com) and Lemon Squeezy.

Detecting FastSpring at scale

Checking one site is quick, but finding every software company on FastSpring across a list — to prospect global-selling SaaS and software vendors — calls for automation. StackOptic detects FastSpring and thousands of other technologies from a real browser, including embedded SBL and hosted-store integrations. Because the merchant-of-record choice is itself a strong qualifier — it tells you the company sells internationally and prioritised compliance over building billing in-house — a scan that flags FastSpring (and its peer Paddle) is an efficient way to build a list of global-selling software vendors with a specific operational profile. That profile is far more actionable for outreach than simply knowing a company takes payments, since it implies cross-border revenue, a focus on product over infrastructure, and a likely appetite for tools that further reduce operational overhead. For related reading, see our guide to finding out what payment processor a website uses and the full FastSpring technology profile.