At a glance
Total count of successful Klarna BNPL orders in the period. Klarna order-volume divided by this gives Klarna AOV (typically 30 to 45% above card AOV).
| What it counts | COUNT(orders) where status = CAPTURED. Pay in 4, Pay in 30, Slice it all count as one transaction each. |
| API endpoint | /ordermanagement/v1/orders. |
| Currency | Currency-neutral (count). |
| Refunds | Excluded. |
| Failed / declined Klarna orders | Excluded. |
| Cancelled-by-merchant | Excluded. |
| Klarna underwriting decision | Counted only if Klarna approved AND captured. |
| Pay in 4 vs Pay in 30 vs Slice it | Each = one transaction. |
| Time window | 30D vsP. |
| Alert trigger | drop >15% vsP. |
| Roles | owner, finance, operations |
Calculation
Calculated automatically from your Klarna data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
“Helle Mode” (German DTC fashion), 30 days ending 02 May 26.| Klarna product | Order count | Volume | AOV |
|---|---|---|---|
| Pay in 30 days (DE) | 4,820 | EUR 612,400 | EUR 127 |
| Pay in 4 (DE) | 1,840 | EUR 248,300 | EUR 135 |
| Slice it | 320 | EUR 184,200 | EUR 575 |
| Pay in 30 days (UK) | 480 | GBP 51,800 | GBP 108 |
| Total | 7,460 |
- 7,460 Klarna orders is roughly 35% of total order count for Helle Mode, consistent with a German fashion brand at maturity of Klarna integration.
- Pay in 30 days dominates with 65% of order count. German consumer preference; Pay in 4 grows but slower.
- Slice it at 4.3% of count contributes 17.6% of volume. Higher AOV justifies the friction (consumer credit check).
- A 15% drop in count triggers alert. Common causes: Klarna approval rate dropped (issuer-side risk model tightening); checkout-page Klarna placement changed; competitive BNPL added (Afterpay).
Sibling cards merchants should reference together
| Card | Why pair it |
|---|---|
kla_total_volume | The dollar-volume view. |
kla_avg_transaction | AOV. |
kla_decline_rate | What fraction of attempts failed. |
kla_top_payment_methods | Pay in 4 vs Pay in 30 vs Slice it split. |
Stripe stripe_total_transactions | Cross-rail count comparison. |
Reconciling against the vendor’s own dashboard
Where to look: Klarna Merchant Portal at portal.klarna.com → Orders → All orders with status filter “Captured”. Why our number may differ:| Reason | Direction | Why |
|---|---|---|
| Time zone | Boundary days off | CEST vs UTC. |
| Authorised vs captured | Theirs higher | Authorised-but-not-captured included in some Portal views. |
| Refresh lag | Ours lower for “today” | API sync lag. |
| Comparison | Expected | Why |
|---|---|---|
kla_total_transactions ↔ commerce-platform Klarna order count | Approximately equal | Both count same orders. |
Known limitations / merchant FAQs
Are authorised-but-not-captured orders counted? No. Once captured, they count. Klarna order with multiple line items, one transaction or many? One. The Klarna order is the unit. Cancelled-by-merchant Klarna orders, counted? No. Klarna refunds, do original orders still count? Yes. Refund is separate event inkla_refund_volume.
Slice it vs Pay in 4, distinguishable here?
No, this is a single count. Use kla_top_payment_methods.
Klarna in-app purchases counted?
Yes if they redirect to merchant checkout and complete via Klarna Payments.
Klarna NYSE listing 2025, operational change?
None. Public-listed Klarna AB continues operations as before.