Klarna and Stripe present different approaches to checkout, merchant economics and UX. This comparison focuses on UK merchants evaluating Buy Now Pay Later (BNPL) vs card-first gateways, delivering concrete cost models, integration steps, conversion impact tests and a decision matrix for B2C, B2B, marketplaces and SaaS. The analysis includes up-to-date 2025–2026 data, links to authoritative sources and repeatable technical patterns for production rollouts.
Executive comparison: single-view decision matrix
- Business type suitability: BNPL drives AOV and conversion for retail and D2C. Card-first payments (Stripe) remain universal and essential for subscriptions and B2B invoices.
- Merchant fees & cost structure: Stripe typically charges a percentage + fixed fee per card transaction; Klarna fees vary by market and product (pay later, financing, slices) and are often higher per-order but can boost AOV.
- Integration complexity: Stripe offers native Klarna integration via its Payments ecosystem, simplifying technical work. Direct Klarna integrations provide additional merchant control and reporting features.
- Risk & reconciliation: Klarna assumes consumer credit risk in many models; Stripe retains card processing risk and chargeback flows.
Quick recommendation
- Retailers prioritising conversion and capable of margin absorption: test Klarna for consumer purchases.
- SaaS, B2B and subscription merchants: keep Stripe as primary processor; add Klarna where one-off retail purchases exist.
Fees, sample calculations and payout timing
This section shows representative UK-calibrated examples for 2025–2026. Fees change; always confirm current rates with each provider links below.
Source links
Representative fee table (UK, 2025–2026 approximate)
| Provider |
Typical fee model |
Example fee (domestic card / BNPL) |
Payout timing (typical) |
| Stripe (card) |
% + pence per txn |
1.4% + 20p (EU cards), 2.9% + 20p (non-EU) |
2–7 days (depends on account and country) |
| Klarna (merchant) |
% of order + fixed fee; variable by product |
~2.5%–6% + fixed fee (merchant-negotiated) |
Varies: immediate settlement or vendor-funded depending on contract |
Notes: percentages above are representative. Klarna pricing depends on the chosen product (pay later, slice it, financing) and merchant category. Stripe typically publishes standard rates; bespoke volumes may reduce cost.
Example cost calculation (AOV = £100)
- Stripe (EU card 1.4% + £0.20): 1.4% of 100 = £1.40 + £0.20 = £1.60.
- Klarna (assumed 4.0% + £0.00): 4% of 100 = £4.00.
Impact: If Klarna increases conversion by +8% and AOV by +12%, the incremental revenue may offset higher fees. Run an A/B test to measure net margin change.
Technical integration patterns and step-by-step examples
The competitive gap shows merchants need reproducible, stack-agnostic examples. The following patterns cover the most common cases: Stripe-native Klarna integration, and direct Klarna integration for maximum control.
Option A — Klarna via Stripe (recommended for faster rollout)
Benefits: single platform for reconciliation, unified payouts, Stripe dashboard metrics and fraud controls.
Code snippet (Node.js) — create a PaymentIntent for Klarna
// Requires: npm install stripe
const Stripe = require('stripe');
const stripe = new Stripe(process.env.STRIPE_SECRET_KEY);
const paymentIntent = await stripe.paymentIntents.create({
amount: 10000, // pence (100.00 GBP)
currency: 'gbp',
payment_method_types: ['klarna'],
capture_method: 'automatic',
payment_method_options: {
klarna: {product: 'pay_later'}
}
});
Key implementation steps:
- Enable Klarna as a payment method in the Stripe Dashboard.
- Use the Stripe Payment Element or Checkout for hosted flows to reduce PCI scope.
- Ensure shipping and billing address fields are collected; Klarna requires consumer data for authorisation.
Documentation: Stripe: Klarna integration
Option B — Direct Klarna integration (merchant-controlled)
Use direct integration when custom UX, advanced reconciliation or unique product mixes are needed.
Code snippet (Python, simplified) — create Klarna session (server-side)
import requests
merchant_id = 'MERCHANT_ID'
shared_secret = 'SECRET'
url = 'https://api.playground.klarna.com/checkout/v3/orders'
payload = {
'purchase_country': 'GB',
'purchase_currency': 'GBP',
'locale': 'en-GB',
'order_amount': 10000,
'order_tax_amount': 0,
'order_lines': [{
'type': 'physical', 'reference': 'SKU-001', 'name': 'Example Item', 'quantity': 1, 'unit_price': 10000, 'tax_rate': 0
}]
}
resp = requests.post(url, json=payload, auth=(merchant_id, shared_secret))
print(resp.json())
Documentation: Klarna Developers
Reconciliation and reporting
- Stripe: consolidated payouts and reporting via the Dashboard and Sigma queries. Connect Stripe Reports to accounting software.
- Klarna: direct integrations provide clearer BNPL settlement lines; when Klarna runs via Stripe, map Klarna transactions using payment method metadata.
Implement automated reconciliation scripts that match order_id, payment_intent_id and settlement_date. Track fees separately: processor fee, BNPL fee, refunds and disputes.
Risk, disputes and compliance
Chargebacks and fraud
- Stripe: chargeback flow relies on card networks; Stripe offers dispute handling and optional chargeback protection products. Reference: Stripe Disputes.
- Klarna: in many merchant agreements Klarna assumes consumer credit risk, reducing merchant liability on consumer non-payment, but merchant liability for fraud or fulfilment errors often remains.
Regulatory & compliance
- PSD2 and SCA requirements apply to card payments in the UK and EU. Use Stripe’s built-in SCA flows or Klarna’s compliant checkout flows.
- BNPL regulation continues to evolve; consult the FCA for the latest guidance in the UK.
UX and conversion testing: practical A/B plan
A/B test framework for measuring Klarna impact on checkout conversion:
- Baseline: existing Stripe card checkout for 7–14 days.
- Variant A: add Klarna as a visible checkout method (prominent placement for mobile). Monitor conversion, AOV and refund rates.
- Variant B: show Klarna option only on orders above a threshold (e.g., £50) to measure targeted uplift.
Metrics to track:
- Checkout conversion rate
- AOV change
- Refund and return rates
- Chargeback ratio
- Net revenue per visitor (after fees)
Migration and coexistence strategy
- Phase 1: Parallel run — enable Klarna via Stripe and keep Stripe card flows active. Route a percentage of traffic to Klarna using feature flags.
- Phase 2: Reconcile finance flows for both methods and update order management and accounting.
- Phase 3: Expand Klarna availability by product category if metrics meet targets.
Migration risks:
- Unexpected fee structures and holdbacks
- Customer confusion if UX is inconsistent
- Reconciliation mismatches between platforms
Prepare rollback plans that disable Klarna quickly in the Stripe Dashboard and fall back to the card flow.
Case studies and expected ROI
Representative scenarios (anonymised):
- D2C apparel merchant: adding Klarna increased conversion +9% and AOV +11%. Even with a 3.8% merchant fee, net revenue per visitor rose by ~5% after returns and fees.
- Electronics reseller: BNPL increased cart size but introduced more returns; net margin improvement depended on stricter return policy enforcement.
Recommendation: run a 30-day pilot with strict KPI thresholds for continuation.
Implementation checklist (pre-launch)
- Register and verify merchant accounts with Stripe and/or Klarna.
- Confirm pricing and settlement cadence in writing.
- Implement SCA-compliant flows for EU/UK cards.
- Add monitoring: conversions, refunds, disputes and settlement reports.
- Update terms & conditions and privacy policy for BNPL disclosures.
FAQ
How much does Klarna cost compared to Stripe for UK merchants?
Klarna typically charges higher per-order merchant fees than Stripe card processing. Exact figures depend on negotiation, product (pay later vs financing) and volume. Confirm with the provider: Klarna for Merchants and Stripe Pricing.
Can Stripe process Klarna payments directly?
Yes. Stripe supports Klarna as a payment method within the Stripe Payments ecosystem. Use the Stripe Dashboard to enable Klarna and follow Stripe's Klarna docs.
Which merchants benefit most from Klarna?
Merchants in retail and D2C categories with moderate to high AOV and elastic conversion rates usually benefit most. For subscription-first or B2B merchants, Stripe card flows and invoicing remain primary.
Does using Klarna reduce merchant risk?
Klarna often assumes consumer credit risk for BNPL products, reducing bad debt for merchants, but merchant liability for fraud, cancellations and non-compliant fulfilment can remain.
Conclusion
Choosing between Klarna and Stripe is not exclusive. For many UK merchants the optimal approach is a hybrid: keep Stripe as the primary processor and add Klarna where the business expects conversion uplift and higher AOV. Decisions should be data-driven: run controlled A/B tests, model fee vs revenue uplift, and validate reconciliation and payout flows before scaling. The recommended path is to start with Stripe-native Klarna to reduce integration time, then iterate to a direct integration only if the merchant requires deeper reporting, specialised UX or bespoke settlement terms.
