Affirm Installment Guide: Compliance and Operations of a Lending-Based BNPL
The site already carries a cross-platform comparison of Klarna, Afterpay and Affirm in the Buy Now Pay Later Platform Comparison, and that article settles the choice question. This guide does not repeat it, it focuses on one thing: Affirm is a lending product, and that attribute imposes extra duties on the merchant. The same instalment button behaves very differently when it sits on a lending product, because compliant display and marketing boundaries change, and none of that work appears in a rate table.
1. A Lending Product, Not a Deferred Charge
1.1 The legal difference
Deferred-charge buy now pay later splits a payment into instalments and sits closer to a payment arrangement between merchant and buyer. A lending product is different: the buyer receives credit, advanced by a licensed institution, and repays under a contract. Most Affirm products belong to the second group, and some variants involve interest and an annual percentage rate disclosure.
This is not a conceptual nicety. It determines the contract relationship, the regulator and the merchant's duties. In a deferred-charge model the merchant mainly watches settlement and refunds; in a lending model the merchant must also watch whether the display is compliant and the claims are accurate.
1.2 What the merchant actually sees
From the merchant side, three things differ: the checkout page needs richer plan information, including instalment count, per-period amount and whether interest applies; approval is real time and may be declined or produce a different plan; and the order carries a credit state that does not always map one to one onto payment state.
So a lending-style instalment cannot be implemented as a variant of card payment. It needs separate fields and states, and the page has to carry compliance information. For the wider family of products see Instalment Payment Solutions.
2. Merchant Eligibility and US Market Requirements
2.1 Entity and documentation
Affirm is primarily a US market proposition today, so onboarding expects a US-operating entity, a settlement account and a site that explains the business. Review looks at category, price range, refund policy and fulfilment capability. Exact materials and standards belong to the official pages.
Note that even where the entity is not American, selling to US consumers means handling state-level tax and consumer protection rules. The tax side of interstate selling is covered in the VAT and Sales Tax Compliance Guide.
2.2 The effect of state-level rules
Instalment lending in the United States is governed at state level, and rules on rate caps, disclosure and marketing restrictions differ between states. The same product page copy can be compliant in one state and non-compliant in another. Platforms usually compute plans dynamically from the buyer's state, but copy the merchant publishes is still the merchant's responsibility.
The practical rule is to let platform components render every statement involving rates or instalment counts, and never hand-write those numbers. That single rule removes most cross-state publication risk, and the surrounding licensing picture is in the Payment Compliance and Licensing Guide.
3. Integration Paths and Platform Connectivity
3.1 Integration shapes
There are two shapes: native platform integration, where you enable the method and configure placement and eligible products, and a self-built interface, where you handle credit application creation, redirect to approval, webhooks and order state synchronisation.
Both share one requirement: the approval result must return in real time and map onto your order state. Approved, declined and alternative-offer are three different outcomes that need three different responses, not a single success-or-failure branch.
3.2 Combining with a payment provider
Where a team already runs aggregated acquiring through Stripe or Adyen, instalment products are usually folded into the unified state model as one method. The benefit is a single order state spine with instalment fields as extensions.
The cost is configuration granularity: an aggregation layer usually offers less display control than a direct integration, and lending products demand more control over display. Confirm before integrating whether the layer can render compliance text, otherwise you will patch the front end yourself.
4. Product Variants and Buyer Choice
4.1 Interest-free and interest-bearing side by side
A trait of lending-based instalments is that several product variants coexist: some plans are interest-free, some carry interest, and instalment counts vary. What the buyer sees at approval is a plan the platform derives from their profile, not a single option preset by the merchant. Operationally that means a merchant cannot promise every buyer will receive an interest-free plan.
Wording therefore needs room. The correct claim is that interest-free plans exist with stated eligibility, not that interest-free is guaranteed. Interest-bearing plans involve APR disclosure, and that display must be rendered by a compliant component.
4.2 Contrasting the two shapes
One checkout page can legitimately offer both shapes: deferred charge and lending. The former feels lighter with faster approval and usually needs no rate disclosure; the latter covers higher tickets and longer terms at the cost of heavier disclosure. The comparison below summarises what that means for the merchant.
| Dimension | Deferred charge | Lending such as Affirm | Effect on the merchant |
|---|---|---|---|
| Legal relationship | Payment arrangement | Credit from a licensed lender | Different contract and liable party |
| Rate disclosure | Usually none | APR disclosure for interest plans | Display must use compliant components |
| Approval experience | Light and fast | Real time, may decline | Page must handle multiple outcomes |
| Ticket coverage | Lower to mid | Can cover higher tickets | Changes category fit |
| Dispute handling | Standard refund path | Credit state must be closed too | Higher operational complexity |
Where a business serves both Europe and the United States, a common layering is Klarna for Europe, a lending product for high-ticket US scenarios, and Afterpay for short-instalment audiences. This is layering by market and ticket, not substitution.
5. Compliant Display and Disclosure Duties
5.1 Where the duties apply
Display duty is heavier than for deferred charge. Everywhere a plan is presented to a consumer is a compliance scene: the price note on a product page, the plan card at checkout, marketing emails and on-site banners, and paid social creative.
Three rules summarise it: plan information is generated by platform components rather than typed by hand; interest-bearing plans show the APR alongside; and any interest-free claim carries eligibility conditions. These look simple and fail most often in marketing assets, because those are produced by marketing teams rather than payment teams.
| Scene | Requirement | Frequent error |
|---|---|---|
| Product page price note | Plan rendered by compliant component | Hand-typed instalment amount that drifts |
| Checkout plan card | Show count and whether interest applies | Only a minimum amount, no conditions |
| Marketing email | Interest-free claims carry eligibility | Written as interest-free for everyone |
| Paid social creative | Plan data from component or reviewed draft | In-house rate wording |
| Landing page banner | Interest plans show the APR | Instalment count without the rate |
| Support scripts | Wording matches the page | Verbal promises not on the page |
5.2 The boundary of disclosure
The point of disclosure is accuracy, not volume. The APR basis, the mapping between instalment count and per-period amount, and the treatment of missed payments all become the merchant's responsibility once they appear on merchant-owned pages.
A workable split: every number involving rates or counts comes from a platform component, and merchant-owned content describes only the mechanism and eligibility without numeric claims. That satisfies disclosure and avoids cross-state rule gaps at the same time.
6. Fee Structure and What Merchants Carry
6.1 Fee composition
Merchant cost includes the transaction fee, shared funding of promotional campaigns, refund and reverse-flow handling, dispute handling, and integration plus compliance maintenance. Current rates and conditions belong to official policies and local regulation, and stale third-party numbers are a poor basis for budgeting.
Distinguish carefully who funds the interest. In some arrangements the merchant subsidises the interest-free period, in others the buyer bears it. The two shapes change the cost structure materially, so confirm line by line instead of assuming the fee already covers everything.
6.2 The hidden compliance cost
Part of a lending product's cost is compliance operations: creative review, page inspection, support training and cross-state wording upkeep. It does not show in a rate, it is a recurring expense, and it grows linearly with the number of markets.
Selling in one or a few states keeps this small; expanding nationwide requires a creative review process. Include it in the evaluation, otherwise the margin gets eaten by compliance labour only after you scale. General dispute practice is in the Chargeback Reason Codes and Evidence Playbook.
7. Categories and Ticket Sizes That Fit
7.1 Where it fits
Lending-based instalments fit higher-ticket categories where buyers want a longer repayment horizon: furniture, consumer electronics, fitness equipment, auto parts and home improvement services. These share high unit price, long decision cycles and sensitivity to the monthly amount rather than the total.
Fit is strongest for merchants selling into the United States at mid to high ticket, where the item is naturally financeable and return rates are controlled.
7.2 Where it does not fit
Low-ticket fast-moving goods, subscriptions and digital content do not fit: approval and disclosure costs are largely fixed and a low ticket cannot absorb them. Digital delivery also does not match credit product logic; check fit in the Digital Products Payment Guide first.
Businesses aimed at Europe or other markets should not make a lending product the main method either, because coverage is limited. Those needs suit platforms with broader regional reach; short-instalment options such as Sezzle fit differently across markets.
8. Operating Points and Common Misreadings
8.1 Operating points
First, model order state and credit state separately, since their lifecycles differ and merging them breaks refunds and reconciliation. Second, route every rate or count display through a component and keep owned pages to mechanism only. Third, maintain a creative review checklist so every asset with instalment wording passes through it. Fourth, match settlement and refunds each period, watching amounts that shift when credit state changes.
If you later add or replace an instalment product, plan for order and state migration; the path is in the Payment Gateway Migration Guide.
8.2 Support and dispute points
Support is the highest-risk area. Saying a buyer will definitely get an interest-free plan or will definitely be approved becomes misleading the moment it diverges from the page. Give support a fixed script that separates what may be promised from what should be pointed to on the page.
On disputes, lending products add a credit state, so after a refund you must confirm the plan was also closed. Without an automated check, money gets refunded while the plan keeps collecting, and cleanup is expensive.
8.3 Common misreadings
The first misreading is treating Affirm and Klarna as interchangeable. Their legal relationships differ: one is closer to a payment arrangement, the other is credit. What looks interchangeable is only the button on the checkout page; the disclosure duties, approval logic and state models behind it are not.
The second misreading is assuming every marketing claim can say interest-free after integration. Interest-free holds only for specific plans, specific profiles and specific markets, and a merchant cannot generalise one plan's conditions into a blanket promise.
The third misreading is assuming compliance means adding text. Real compliance is accuracy of display, consistency of wording and a traceable review process. Bolting on a disclaimer solves nothing. Beyond instalments, wallets and local methods remain options, and broad-coverage methods such as PayPal are often used to cover the long tail.
More acquiring and payment options are organised under Payment, grouped by instalments, wallets and local payment methods.
Source: 16IDC original. Product capabilities, pricing and eligibility requirements follow www.affirm.com and related official documentation and contract terms.