Affirm

What Is Affirm?

Affirm is a buy-now-pay-later (BNPL) provider that lets shoppers split the cost of a purchase into a series of scheduled payments, often with transparent, upfront terms instead of revolving credit-card interest. When a store integrates Affirm, customers see an option at or near the product page and checkout that says something like "As low as $25/mo with Affirm" and can finance an order over a fixed number of installments rather than paying the full amount immediately.

Affirm is widely recognized as one of the largest installment-financing companies operating in the United States and Canada, and it partners with thousands of merchants ranging from large electronics and travel brands to mid-size online retailers. Its core promise to consumers is clarity: it presents the total cost and the per-month payment before a shopper commits, positioning itself as a more straightforward alternative to traditional credit.

From a merchant's perspective, Affirm is a payment and financing option you add to an existing checkout rather than a full payment processor in the way Stripe or a card acquirer is. The retailer still has a primary way of taking card payments; Affirm sits alongside that as an additional method that handles the lending, underwriting, and repayment relationship with the customer. The merchant is typically paid the order value up front (less Affirm's fee), and Affirm assumes responsibility for collecting the installments from the buyer.

It is important to be precise about what Affirm is and is not. It is not a browser extension, and it is not something a shopper installs. It is a financing service that a merchant embeds into the storefront through Affirm's SDK, hosted scripts, and APIs. Because that integration runs in the browser and calls Affirm's own domains, it leaves recognizable fingerprints in a page's source, which is exactly what a server-side analysis tool like StackOptic looks for when it identifies the payment and financing technologies behind a URL.

Understanding where Affirm fits in the broader payments landscape helps clarify its role. Card networks and processors move money; BNPL providers like Affirm add a consumer-credit layer on top of a sale. A store can run a conventional card stack for the bulk of its transactions and still offer Affirm as a way to convert shoppers who would rather spread a larger purchase over time. That combination, a primary processor plus one or more BNPL options, is increasingly common across mid-market and enterprise ecommerce, and it is one reason detecting these services has become a useful signal for sales, competitive, and market research.

How Affirm Works

At a high level, Affirm inserts itself into three moments of the shopping journey: discovery, application, and checkout. During discovery, the merchant displays promotional messaging, the "as low as $X/mo" copy, on product and category pages. This messaging is rendered by Affirm's JavaScript, which reads the price from the page and asks Affirm's service what monthly estimate to show. The shopper sees financing as an option long before they reach the cart, which is part of how BNPL lifts conversion and average order value.

When the customer decides to use Affirm, they launch an application flow, usually a hosted modal or redirect provided by Affirm. They enter a few details, and Affirm performs a real-time eligibility check to decide whether to approve the purchase and on what terms. This underwriting happens on Affirm's side; the merchant does not see or store the applicant's sensitive financial data. If approved, the shopper selects a repayment plan from the options Affirm offers for that order.

At checkout, the approved Affirm plan becomes the payment method for the order. Affirm confirms the transaction back to the merchant through its API, the merchant fulfills the order as normal, and Affirm pays the merchant the agreed amount, typically the order total minus a merchant fee. From that point, the repayment relationship is between Affirm and the consumer: Affirm bills the installments, handles servicing, and manages any missed-payment process, insulating the merchant from the credit risk.

Technically, the integration is built from a few moving parts. Merchants load affirm.js, Affirm's client library, which exposes a global JavaScript object (commonly affirm) used to configure the public API key, render promotional messaging, and open the checkout modal. Server-to-server calls confirm and capture charges through Affirm's REST API. Platform-specific plugins exist for major commerce systems, so a store on a hosted platform can often enable Affirm without writing custom code, while larger merchants integrate directly against the API for full control.

The economics are worth spelling out because they explain why merchants adopt Affirm despite the fee. By absorbing the credit decision and the collection process, Affirm removes both the risk and the operational burden of offering financing in-house. In exchange, the merchant pays a percentage of each financed order. The bet most retailers are making is that the conversions and larger baskets that financing unlocks, particularly for higher-ticket items like furniture, electronics, fitness equipment, and travel, more than offset that fee. Because the value proposition is strongest at higher price points, Affirm tends to show up most often on stores selling considered, big-ticket purchases rather than low-cost impulse goods.

How to Tell if a Website Uses Affirm

Affirm leaves several reliable fingerprints in a page's front-end code. Because StackOptic analyzes a URL from the server side, it inspects the same signals you can check manually with browser tools, View Source, or a detection extension.

The affirm.js script. The strongest single signal is a request to Affirm's client library, typically loaded from a cdn1.affirm.com (or similar affirm.com) host as affirm.js. Seeing this script reference in the page source or the Network tab is close to definitive.

Promotional messaging elements. Affirm renders its "as low as" monthly-payment copy into specific HTML containers. Look for elements with classes or attributes such as affirm-as-low-as or data-promo-id, and the affirm-site-modal container that Affirm uses for its informational popups.

The global affirm object. When affirm.js loads, it attaches a global affirm object to the page's JavaScript context. In DevTools, typing affirm in the Console and getting an object back (rather than "undefined") confirms the integration.

Checkout buttons and the hosted modal. Affirm's checkout typically opens a hosted modal served from Affirm's domain. Network requests to affirm.com endpoints during the checkout flow, and an Affirm-branded payment button, are strong secondary signals.

Public API key in configuration. Affirm's client configuration includes a public API key passed to affirm.ui.ready or the config object. Its presence in inline script confirms an active integration (the public key is not sensitive).

Here is how to check each signal yourself:

Method	What to do	What Affirm reveals
View Source	Right-click, "View Page Source" on a product page	The affirm.js script tag, affirm-as-low-as elements, inline config
Browser DevTools	Open the Network tab and filter, then inspect Elements	Requests to cdn1.affirm.com, the affirm modal container, messaging markup
Console check	Type affirm in the DevTools Console	Returns the global Affirm object if the SDK is loaded
Wappalyzer	Run the extension on the live page	Identifies "Affirm" under payment processors / BNPL
BuiltWith	Look up the domain	Current and historical Affirm usage across the site

A practical approach is to open a higher-priced product page (where financing messaging is most likely) and search the source for "affirm". For the broader methodology, see our guides on how to find out what payment processor a website uses and how to find out what technology a website uses.

A few caveats make multi-signal analysis worthwhile. Affirm's promotional messaging is sometimes loaded only on certain product templates or only above a price threshold, so a single page may not show it even though the store offers Affirm elsewhere. The affirm.js script and the global affirm object, by contrast, tend to be present site-wide wherever financing is enabled, which makes them more dependable tells. Occasionally a merchant proxies scripts through its own domain or gates the financing widget behind a price condition, which can hide the most obvious clue on a given page. Combining several signals, the script host, the messaging markup, the global object, and checkout-time requests to Affirm, produces a confident verdict even on a partially obscured integration. Server-side analysis helps here because it fetches the raw HTML directly and can be pointed at the pages most likely to carry the financing widget.

Key Features

• Transparent installment financing. Fixed, scheduled payments with terms shown to the shopper before they commit, positioned against revolving credit-card interest.
• On-site promotional messaging. "As low as $X/mo" copy on product and category pages that surfaces financing early in the journey.
• Real-time eligibility checks. Affirm underwrites each purchase instantly through a hosted application flow, keeping sensitive data off the merchant.
• Merchant paid up front. The retailer receives the order value (less a fee) while Affirm assumes the credit risk and handles collections.
• Platform plugins and APIs. Prebuilt integrations for major commerce platforms plus a REST API for custom checkouts.
• Servicing and support handled by Affirm. Billing, reminders, and missed-payment processes are managed by Affirm, not the store.

Pros and Cons

Pros

• Can lift conversion and average order value, especially for higher-ticket purchases.
• Shifts credit risk and collections to Affirm, simplifying the merchant's operations.
• Transparent terms can improve customer trust compared with hidden financing costs.
• Straightforward to add to many platforms via official plugins.

Cons

• Merchants pay a per-transaction fee that can exceed standard card-processing costs.
• BNPL is most effective for considered, higher-priced goods and adds little for low-cost items.
• Approval is not guaranteed for every shopper, so it is an additional option rather than a universal one.
• Adds another third-party script and vendor relationship to maintain.

Affirm vs Alternatives

Affirm competes with other BNPL and installment providers. The table below compares it with common alternatives a store might detect or consider.

Provider	Model	Typical positioning	Notable trait
Affirm	Installment financing with clear terms	Higher-ticket US/Canada purchases	Emphasis on transparent, no-hidden-fee messaging
Afterpay	Pay-in-four short-term installments	Fashion, beauty, mid-priced retail	Owned by Block; "Clearpay" in some regions
Klarna	Mix of pay-in-four and longer financing	Broad retail across many markets	Wide international footprint
PayPal Pay Later	BNPL bundled with PayPal checkout	Stores already using PayPal	Rides existing PayPal adoption
Card installments	Bank-issued installment plans	Issuer-driven, post-purchase	Handled by the cardholder's bank, not the merchant

If a checkout offers a different short-term plan, the same fingerprinting approach identifies it; compare Affirm with Afterpay to see how a pay-in-four provider differs from longer-term installment financing. For the underlying techniques, our guide on how to read a website's HTTP headers is a useful companion when you want to confirm the broader stack around a payment integration.

Use Cases

Affirm is most at home on stores selling considered, higher-priced products where spreading the cost meaningfully changes a buyer's decision. Furniture, mattresses, electronics, fitness equipment, jewelry, and travel are classic categories, because the monthly-payment framing makes a large total feel attainable and reduces cart abandonment at the final step.

It also fits direct-to-consumer brands that want to compete with larger retailers on financing options, marketplaces aggregating higher-ticket goods, and service businesses offering pay-over-time for expensive bookings. For competitive and market research, detecting Affirm on a site indicates a merchant that sells higher-value items and has invested in conversion optimization, which is meaningful context for vendors, analysts, and agencies profiling a market.

Consider a few concrete scenarios. A direct-to-consumer furniture brand might add Affirm specifically to convert shoppers hesitating over a four-figure sofa, displaying the monthly estimate on every product page. A consumer-electronics retailer might offer Affirm to compete with big-box financing promotions during peak shopping seasons. A travel company might enable pay-over-time so customers can book a trip now and pay it down before they depart. In each case, the common thread is a high enough price point that financing materially influences whether the sale happens.

From a sales-intelligence standpoint, spotting Affirm is a qualifying signal in its own right. It suggests a merchant operating at a price point where financing matters, one that is willing to pay for conversion lift and likely sophisticated about checkout optimization. A vendor selling ecommerce tools, a competitor benchmarking financing options, or an analyst sizing the BNPL-enabled segment of a market can all use that signal, and surfacing it automatically across many domains, rather than inspecting each checkout by hand, is exactly where automated technology detection earns its value. For lead qualification specifically, our overview of technographics and using tech-stack data to qualify leads explains how a detected provider like Affirm feeds into account scoring.

Frequently Asked Questions

Is Affirm a payment processor?

Not in the traditional sense. Affirm is a buy-now-pay-later financing provider that sits alongside a merchant's primary card processing as an additional payment method. The store still uses a processor or acquirer to take card payments; Affirm handles the lending, underwriting, and repayment for shoppers who choose to finance. It is best categorized as a payment and financing option rather than a general-purpose processor.

How can I tell for free if a store offers Affirm?

Yes, you can confirm it at no cost. Open a product page, ideally a higher-priced one, and use View Source or the DevTools Network tab to look for the affirm.js script loaded from an affirm.com host, affirm-as-low-as messaging elements, or a global affirm object in the Console. Free tools like Wappalyzer and BuiltWith also report Affirm when it is present, and StackOptic detects it server-side from a single URL.

Does the merchant take on the credit risk with Affirm?

Generally no. One of Affirm's core value propositions to merchants is that it assumes the credit risk and handles collections. The merchant is typically paid the order amount up front, minus Affirm's fee, while Affirm bills the customer over the agreed installments and manages any missed payments. This is a key difference from offering store-issued financing directly.

Why do I see Affirm messaging on some pages but not others?

Affirm's promotional "as low as" messaging is often configured to appear only on certain templates or above a price threshold, since financing is most relevant for higher-ticket items. As a result, a low-priced product page might not show the widget even though the store supports Affirm. The affirm.js script and the global object are usually present site-wide where financing is enabled, so they are more reliable signals than the on-page messaging alone.

Is Affirm the same as a credit card?

No. A credit card is revolving credit from an issuing bank that you can reuse and that typically charges compounding interest on carried balances. Affirm provides a fixed installment plan for a specific purchase, with the total cost and per-payment amount shown up front. The two can coexist, a shopper might pay with a card normally but choose Affirm for a large purchase they want to spread over time.

Want to identify Affirm and the rest of a site's payment and technology stack automatically? Run any URL through StackOptic at https://stackoptic.com.