What Klarna actually does
Klarna is a Swedish BNPL (Buy Now, Pay Later) and payment company founded in 2005 in Stockholm, that went public on NYSE in September 2025 (ticker: KLAR) at a $15B valuation — closing at $45.82/share (~$17.4B) on its first day. The total offering raised $1.37B, with only $222M going to Klarna itself (existing shareholders sold the majority). By the end of 2025, Klarna had 118M active consumers (+28% YoY) and 966K merchants (+42%), with GMV of $127.9B (+22%) for FY2025. Klarna surpassed 1 million merchants globally in March 2026.
Klarna's core offering is installment payment: consumers pay in 4 equal installments interest-free (for merchants), pay in 30 days with no interest, or access 6–36 month financing at interest. Merchants pay the fee; consumers pay nothing (unless they miss a payment — Klarna charges a $7 late fee after 10 days, which has drawn CFPB scrutiny). Klarna earns from merchant fees, consumer late fees, and interest on financed products.
Klarna uses WebBank as its US sponsor bank and operates on GCP-heavy Kubernetes infrastructure in Java/Kotlin. In November 2025, Klarna launched KlarnaUSD, a stablecoin on Stripe's infrastructure. Klarna's AI shopping app — which helps consumers find and compare products across retailers — has become a significant traffic source that some merchants argue cannibalizes their own organic traffic.
Pay in 4 (Interest-Free Installments)
The core BNPL product: split any purchase into 4 equal payments over 6 weeks, with the first payment due at checkout. Merchants pay 5.99%+$0.30 per transaction. Consumers pay $0 in interest but face $7 late fees after 10 days on any missed installment.
Pay in 30 Days
Buy now, pay the full amount within 30 days with no interest. Merchants pay 5.99%+$0.30. This option works like a deferred invoice for consumers and is popular for fashion and home goods purchases.
Long-Term Financing (6–36 Months)
Consumer-facing financing at interest rates, with merchants paying a lower rate of 3.29%+$0.30. Klarna earns from consumer interest. This product requires state-by-state consumer lending licenses — the most complex regulatory component.
Merchant Dashboard and Settlement
Merchants receive full payment from Klarna immediately after purchase (minus the merchant fee), with settlement reports, dispute management, and API for order status updates via webhooks.
Consumer App and Credit Scoring
Klarna's consumer app shows purchase history, installment schedules, and upcoming payment dates. The credit scoring engine approves or declines consumers in real-time at checkout — a soft credit check that does not affect credit scores for Pay in 4.
AI Shopping App
Klarna's AI-powered shopping app helps consumers discover, compare, and purchase products across 966K+ merchants. Critics argue this diverts traffic that would otherwise go directly to merchant sites — Klarna becomes the destination rather than the merchant.
Klarnapricing & limits
Standard Pay in 4 at 5.99%+$0.30: $6,290/mo for a $100K/mo store — versus $3,200/mo on Stripe at 2.9%+$0.30
Where Klarna falls short
Merchant fees at 5.99% are roughly 2x Stripe's rate
A store doing $100K/mo in BNPL volume pays $6,290/mo to Klarna versus $3,200/mo for standard Stripe Checkout. The $3,090/mo difference ($37,080/yr) is the ongoing cost premium merchants pay for the BNPL conversion lift. r/ecommerce regularly features threads comparing these rates, with merchants questioning whether BNPL conversion improvements justify the 2x fee premium — particularly as competitors like Affirm and Afterpay offer comparable rates.
Consumer late fees driving CFPB scrutiny
Klarna charges consumers a $7 late fee after 10 days on any missed installment payment. The CFPB has issued supervisory guidance on BNPL products, flagging late fees as a consumer harm concern. If the CFPB imposes late fee caps (as it did with credit card late fees in 2024), Klarna's business model would require restructuring. Merchants using Klarna inherit some reputational risk if consumers associate late fees with the merchant's checkout experience.
Soft credit check declines without visibility
Klarna declines some consumers at checkout based on its proprietary risk scoring model without providing merchants any visibility into why. Merchants see a declined BNPL attempt but cannot distinguish between a consumer with poor credit history and a legitimate consumer declined due to a system error. This opacity leads to lost sales with no actionable insight — particularly frustrating when a consumer is declined mid-checkout after adding items to cart.
Klarna AI shopping app cannibalization
Klarna's AI shopping app surfaces competing products alongside merchant listings, effectively turning Klarna into a product comparison marketplace. Merchants who rely on Klarna for checkout may find their checkout traffic partially diverted to Klarna's own shopping destination. This conflict of interest — checkout provider that also operates a competing shopping channel — is a recurring Trustpilot complaint from merchants.
Dispute resolution is slow
Multiple BBB complaints and merchant forums document Klarna dispute resolutions taking 4–8 weeks with limited merchant communication during the process. In traditional payment disputes, merchants typically respond within 7–10 days and receive a decision within 30–45 days. Klarna's process is slower, with less transparency about status, creating cash flow uncertainty for merchants whose funds may be held during the dispute period.
Key features to replicate
The core feature set any Klarna alternative needs — plus what you can improve on.
Checkout Widget and Integration
A JavaScript widget that merchants add to their checkout page to offer installment options. The widget shows consumers 'Pay in 4 × $X.XX' messaging and handles the approval flow inline. Build with a JavaScript SDK that merchants load via a script tag, a secure popup for the authorization flow, and a webhook callback to the merchant's order system when approval is granted.
Credit Risk Scoring Engine
Real-time approval/decline decision at checkout using consumer data: purchase amount, consumer history, credit bureau signals, and device/behavioral signals. This is the hardest component to build — requires integration with a credit bureau (Experian, TransUnion, or Equifax) for a soft pull, a risk model trained on default patterns, and a sponsor bank to issue the underlying credit. Do not attempt to build this without a data science team and a lending license.
Installment Payment Ledger
Track each order's installment schedule: due dates, amounts, payment status, and reminders. Build with an installment_schedules table linked to orders, and a scheduled job that processes automatic payments on due dates. Consumer notifications (push, email, SMS) for upcoming and overdue payments. Late fee calculation and application after the grace period.
Merchant Settlement System
Pay merchants immediately upon purchase approval (minus the fee), then collect from consumers over the installment period. This means the BNPL provider bears the credit risk during the collection period. Settlement reports show gross receipts, fees deducted, net payout, and chargeback offsets. Build with a settlement_batches table and ACH payout integration to merchant bank accounts.
Consumer App and Account Management
Consumer-facing app showing active orders, upcoming payments, payment history, and account management. Build with React Native for iOS/Android, authenticated via phone number OTP. Key features: payment calendar, retry on failed payment, and installment adjustment requests.
Merchant Dashboard
Transaction history, settlement reports, dispute management, and configuration (which BNPL products to offer, minimum/maximum order thresholds). Build with Next.js App Router Server Components for reporting data and Recharts for sales trend visualization.
Webhook-Based Order Notifications
Notify merchant systems of BNPL events: order.authorized, order.captured, order.cancelled, payment.completed, payment.failed, dispute.opened. Build a reliable webhook delivery system with at-least-once semantics, exponential retry, and HMAC signature verification.
KYC and Consumer Credit Compliance
Consumer lending regulations require adverse action notices when declining an application, FCRA compliance for credit bureau queries, ECOA compliance (no discrimination based on protected class), and Truth in Lending Act (TILA) disclosures for financed products. Integrate Persona for identity verification and credit bureau APIs for soft pulls. Regulatory counsel required before launch.
Technical architecture
A Klarna alternative is a lending platform with a merchant checkout integration layer. The business model requires capital (to advance merchant payments before consumer collection), a sponsor bank relationship (WebBank is Klarna's partner), and state-by-state lender licensing. The white-label route via a bank partner eliminates licensing risk but reduces margin.
Merchant SDK / Frontend
JavaScript SDK, React component, iframe checkout
Recommended: JavaScript SDK with a popup overlay for the authorization flow — matches Klarna's and Affirm's implementation. Merchants add one script tag and one function call; the rest happens in your modal.
API / Backend
Node.js + Fastify, Go, Java + Spring
Recommended: Node.js for the merchant-facing API. Go for the real-time credit scoring path where sub-second latency matters for checkout conversion. Separate services for lending operations vs merchant-facing API.
Lending and Credit Infrastructure
White-label via bank partner (Cross River, WebBank), direct NMLS licensing
Recommended: White-label lending via Cross River Bank or a similar BaaS lending partner — they issue the credit under their charter, you build the consumer UX. This eliminates the need for state-by-state lender licenses in the short term.
Credit Risk Scoring
Experian API, TransUnion API, Equifax API, Alloy
Recommended: Alloy for a unified credit decisioning layer — aggregates credit bureau, bank verification, and fraud signals into a single API call. Start with rule-based scoring; add ML model trained on your acceptance/default data after 6+ months of history.
Payment Collection
Stripe (card autopay), Dwolla (ACH), Unit
Recommended: Stripe for card-on-file autopay collection on installment due dates. ACH via Dwolla for bank account debit. Stripe's payment method setup flow handles consumer consent for future charges.
Database
PostgreSQL (Supabase), CockroachDB
Recommended: PostgreSQL for all lending data: applications, installment_schedules, payments, settlements. Strong ACID guarantees required — financial data cannot have race conditions. Redis for real-time scoring cache.
Compliance
Direct NMLS licensing, bank partnership, exempt-from-lending structure
Recommended: Bank partnership (white-label) for fastest time to market. Direct state lender licensing takes 12–24 months. Some BNPL structures (charge-and-split, no interest, no late fees) may qualify for exemption from state lending laws in some jurisdictions — consult payments law counsel.
Complexity estimate
Complexity 10/10 — state-by-state lender licensing, sponsor bank partnership, consumer credit compliance (FCRA, ECOA, TILA), capital requirements, and credit risk modeling make this a 9–15 month regulatory-dominated build via bank partner.
Klarna vs building your own
Open-source Klarna alternatives
Existing projects you can self-host or use as a starting point. Each has trade-offs.
Kill Bill
Stars unverifiedKill Bill is a mature Java-based billing and subscription management platform used by Goldman Sachs and enterprise clients for 13+ years. It has a plugin architecture supporting installment payment schedules, recurring billing, and custom payment plugins. It can implement the billing/installment ledger component of a BNPL system but does not include credit decisioning or merchant checkout integration.
Apache Fineract
Stars unverifiedApache Fineract is a core banking platform originally built for microfinance institutions (Mifos II). It supports loan origination, installment schedules, repayment tracking, and interest calculation. Used by 100+ microfinance institutions worldwide. It provides the lending ledger that forms the backend of a BNPL system.
Lago
9.5KLago is a Ruby-based usage-based billing engine. While primarily designed for subscription billing, its flexible pricing model supports installment schedules and deferred payment logic. It is not a credit product but can handle the merchant billing side of a BNPL system.
Build vs buy: the real math
9–15 months via bank partner
Custom build time
$1M–$3M (agency, via bank partner route)
One-time investment
Variable — depends on GMV volume and negotiated bank partner rates
Breakeven vs Klarna
Klarna charges merchants 5.99%+$0.30 per Pay in 4 transaction. A white-label BNPL via a bank partner can offer merchants 3.5–4.5% — a 25–40% discount on Klarna's rate. For a merchant processing $500K/mo in BNPL volume, this saves $7,450–$12,450/mo ($89K–$149K/yr). The build case is primarily for payment infrastructure companies, large e-commerce platforms, and banks that want to offer BNPL under their own brand rather than send customers to Klarna. For a standalone startup, the capital requirements are the binding constraint: BNPL providers must advance merchant payments before consumer installments are collected, requiring $10–$50M in credit facilities even before the first merchant is live. The regulatory path is also complex: state-by-state consumer lending licenses, CFPB supervisory compliance, FCRA compliance for credit pulls, and TILA disclosures for financed products. The realistic path for most founders is building a white-label merchant tools layer that enables any bank with a BNPL product to offer a better merchant experience — not building a BNPL from scratch.
DIY roadmap: build it yourself
This roadmap covers building a BNPL merchant checkout tool via a white-label bank partner (Cross River, WebBank) rather than obtaining direct consumer lending licenses. Assumes a team of 4–6 engineers and a signed bank partner agreement.
Regulatory and bank partner setup
3–5 months (regulatory timeline dominates)- Engage fintech lending law counsel for BNPL regulatory analysis in target states
- Execute white-label lending agreement with Cross River Bank or similar bank partner
- Integrate Persona or Alloy for consumer identity verification at checkout
- Establish credit bureau API access: TransUnion or Experian soft pull for risk scoring
- Define consumer disclosure templates: TILA disclosures, adverse action notices, terms of service
- Set up FinCEN MSB registration if also handling any fund movement
Credit decisioning and merchant checkout
3–4 months- Build credit scoring rules engine: purchase amount, consumer history, bureau signals → approve/decline
- Implement merchant JavaScript SDK: script tag install, popup authorization flow
- Build authorization API: merchant sends order details → scoring → approve/decline + installment terms
- Implement consumer consent and disclosure: display TILA-compliant terms before final approval
- Build Stripe Setup Intent flow for storing consumer card for future installment charges
- Implement merchant order webhook: order.authorized, order.captured, order.cancelled events
Installment management and collections
2–3 months- Build installment schedule generator: order amount → 4 equal payments + due dates
- Implement scheduled payment collection: Stripe PaymentIntent charged on each due date
- Build failure handling: retry on card failure, SMS/email notification to consumer, bank account fallback
- Implement late fee logic: calculate and charge after grace period (configurable)
- Build consumer account portal: view orders, upcoming payments, payment history
- Add merchant settlement: T+1 ACH payout to merchant bank account minus fee
Merchant dashboard and analytics
2–3 months- Build merchant dashboard: transaction list, settlement history, dispute queue, BNPL rate display
- Add order analytics: approval rate, average order value, installment completion rate
- Implement dispute management: consumer dispute flow, merchant evidence submission, resolution tracking
- Build merchant onboarding: API key provisioning, test mode, webhook configuration
- Add risk management dashboard: decline reasons, fraud flags, consumer default patterns
- Implement reporting exports: CSV settlement reports, tax documentation
Consumer app and launch
2–3 months- Build consumer mobile app: React Native, active orders, payment calendar, account management
- Implement push notifications: payment due reminder (3 days before), payment failed, late fee applied
- Set up fraud monitoring: device fingerprinting, velocity rules, unusual approval patterns
- Execute compliance audit with payments law counsel before launch
- Soft launch with 5–10 partner merchants, monitor default rates and approval rates
- Adjust scoring rules based on first 90 days of data before broad launch
These estimates assume 4–6 experienced engineers. The regulatory setup timeline is non-negotiable — bank partner agreements take 3–6 months to execute. Capital requirements are the real constraint: BNPL providers need $10–$50M in credit facilities to advance merchant payments before collecting from consumers. Do not start engineering until the bank partnership and capital facility are in place.
Features you can't get from Klarna
This is where a custom build pulls ahead — features impossible or impractical on a shared platform.
Merchant-competitive rates by offering ACH-first BNPL
Klarna's 5.99%+$0.30 is driven in part by card network interchange costs (1.7–2.2% of each installment). A BNPL product that defaults to ACH for installment collection (0.8%, $5 cap) versus card can offer merchants 3.5–4.0% rates rather than Klarna's 5.99% — a 33% cost reduction. The tradeoff is slightly higher consumer friction (ACH requires bank account linking), but merchants who enable this option gain a clear price advantage over Klarna.
BNPL with zero late fees as a consumer differentiator
Klarna's $7 late fee is under CFPB scrutiny and is a consumer trust issue. A BNPL product with zero late fees — instead pausing the consumer's account for future purchases on missed payments — positions as consumer-friendly while maintaining merchant protection. This model is already proven by Sezzle and some Zip products. Zero late fees also eliminates the main regulatory compliance risk (CFPB late fee caps).
Vertical BNPL for specific merchant categories
Klarna is horizontal — it serves all merchant categories at the same rate. A vertical BNPL for home improvement (higher average order values of $2,000–$15,000, lower default rates), medical procedures (dental, vision, cosmetic), or professional services can offer lower rates (4–4.5%) and higher approval limits by building category-specific risk models. Affirm's success in the home improvement vertical demonstrates this approach.
B2B BNPL for small business procurement
Klarna is B2C-only. Small businesses that buy supplies, equipment, and services often need net-30 or net-60 payment terms that neither Klarna nor standard payment processors offer. A B2B BNPL product (invoice terms rather than consumer installments) with business credit scoring instead of consumer credit scoring serves a segment where average transaction values are 10x higher and default rates are measurably lower.
Embedded BNPL for marketplace platforms
Klarna is a standalone checkout integration. An embeddable BNPL module that platforms (Shopify apps, WooCommerce plugins, custom marketplace backends) can integrate via a single API gives the platform's merchants BNPL as a feature rather than a third-party service. The platform earns a referral fee on every BNPL transaction. This white-label B2B model is higher LTV per customer and avoids direct consumer acquisition costs.
Who should build a custom Klarna
Payment infrastructure companies and fintech platforms
A company already processing payments for a merchant base can add BNPL as a feature by white-labeling a bank partner's lending product with their own checkout SDK. This converts payment processing customers into BNPL customers at a fraction of Klarna's customer acquisition cost, with existing merchant relationships as the distribution advantage.
Large e-commerce platforms needing in-house BNPL
Platforms processing $100M+/mo in BNPL volume are paying Klarna $5.99M/mo in fees. Building a white-label BNPL at 3.5–4% saves $2–2.5M/mo at that volume. The build cost of $1–3M pays back in under 2 months at scale. Platforms that own their merchant relationships can also negotiate better bank partner terms based on their portfolio's historical default data.
Banks wanting to offer white-label BNPL
Major banks (JPMorgan Chase, Capital One, Wells Fargo) have launched BNPL products to compete with Klarna. Regional and community banks that want to offer BNPL to their merchant customers can license a white-label BNPL merchant checkout tool rather than building one from scratch — charging merchants 3.5–4.5% and earning the spread versus their own credit cost.
Vertical market BNPL specialists
Home improvement, medical, legal, and education are BNPL verticals with higher average order values ($2,000–$20,000) and different risk profiles than general retail. A vertical BNPL specialist can build category-specific risk models, serve merchants Klarna ignores (dental practices, roofing contractors), and charge premium rates ($3–4%) relative to Klarna's general retail rate.
International payment companies entering US BNPL
International BNPL players (Zip from Australia, Paidy from Japan) have entered the US by partnering with US banks for the lending compliance layer and building their consumer UX on top. A non-US BNPL company with an existing consumer base or merchant network can use this playbook to enter the US market without the full cost of direct licensing.
Skip the DIY — let RapidDev build it
Everything above is doable — but it takes months of full-time work. We build custom Klarna alternatives using AI-accelerated development, delivering in weeks what used to take quarters.
Discovery call (free)
30 minWe map your exact requirements: which Klarna features you need, what custom features to add, your users, integrations, and compliance needs. You get a detailed scope document and fixed-price quote within 48 hours.
AI-accelerated build
9–15 months via bank partnerOur engineers use Claude Code, Lovable, and custom AI tooling to build 3–5x faster than traditional development. You see progress in a staging environment every week — not a black box for months.
Launch + handoff
1 weekWe deploy to your infrastructure, transfer the GitHub repo, set up CI/CD, and walk your team through the codebase. You own 100% of the source code — no vendor lock-in, no recurring platform fees.
What you get
Timeline
9–15 months via bank partner
Investment
$1M–$3M (agency, via bank partner route)
vs Klarna
ROI in Variable — depends on GMV volume and negotiated bank partner rates
30-min call. Fixed-price quote within 48 hours. No commitment.
Frequently asked questions
How much does it cost to build a Klarna alternative?
A white-label BNPL product via a bank partner (Cross River, WebBank) costs $1M–$3M with a 9–15 month timeline. This includes bank partner agreement negotiation, KYC/AML compliance program, credit scoring integration, merchant SDK, consumer app, and engineering. Capital requirements are separate: you need $10–$50M in credit facilities to advance merchant payments before collecting from consumers. Building a fully licensed BNPL from scratch costs $5–20M and takes 24–36 months.
How long does it take to build a Klarna alternative?
9–15 months via a bank partner route. The regulatory and bank partnership timeline (3–5 months) dominates over engineering (4–6 months). The capital facility negotiation typically takes 2–3 months separately. A realistic launch timeline from decision to first merchant live: 12–15 months.
Are there open-source Klarna alternatives?
No mature open-source BNPL platform exists — the lending license and capital requirements make it impractical. Kill Bill (Apache 2.0) handles billing/installment ledger logic. Apache Fineract (Apache 2.0) handles loan origination and repayment tracking. Both require substantial integration work and neither includes credit decisioning, merchant checkout integration, or consumer app.
What licenses are required to build a BNPL product in the US?
Consumer lending licenses are required in each state where you extend credit to consumers — typically 40–49 states each requiring a separate NMLS license application ($1,000–$10,000 per state plus surety bonds). FCRA compliance for credit bureau soft pulls. ECOA compliance (Equal Credit Opportunity Act — no discriminatory approval criteria). TILA disclosures for financed products (interest rates, APR, payment schedule). The fastest path is using a bank partner (WebBank, Cross River) who already holds these licenses.
Why does Klarna charge 5.99% when Stripe is 2.9%?
Klarna charges 5.99% because it advances the full payment to the merchant immediately while collecting from consumers over 6 weeks. The additional ~3% covers: credit risk (some consumers default on installments), cost of capital (funding the advance), consumer acquisition cost, and margin. Stripe's 2.9% covers payment processing only — no credit risk, no capital advance. The merchant is paying a premium for Klarna's 'pay us later, get paid now' service.
Can RapidDev build a custom BNPL platform?
Yes. RapidDev has built complex fintech platforms including payment infrastructure and lending products. A BNPL build requires the right regulatory counsel and bank partner relationship before engineering begins. RapidDev can build the technology stack on top of a bank partner API. Visit rapidevelopers.com/contact for a scope assessment and realistic cost estimate.
What is Klarna's KlarnaUSD stablecoin and does it matter?
Klarna launched KlarnaUSD in November 2025 as a US dollar-pegged stablecoin on Stripe's stablecoin infrastructure. It is currently a pilot product and has not been integrated into Klarna's main checkout flow. Its relevance to a Klarna alternative is minimal in 2026 — the core merchant pain points are fee levels and credit approval transparency, not cryptocurrency settlement.
Is BNPL still growing or has the market peaked?
Klarna's FY2025 results show GMV growing 22% YoY to $127.9B and merchant count growing 42% to 966K — the market is still growing. However, regulatory pressure (CFPB oversight, potential late fee caps), rising consumer credit risk in the post-zero-rate environment, and increasing competition (Affirm, Afterpay, PayPal Pay Later, Apple Pay Later, bank-native BNPL) are compressing margins. The opportunity window for a differentiated BNPL entrant is real but narrowing.
We'll build your Klarna
- Delivered in 9–15 months via bank partner
- You own 100% of the code
- No per-seat fees, ever
30-min call. No commitment.