$HEADLESS SYSTEMS
03 / Scorecard / Payments

Klarna

C
Headless Index
56/100
JAIRF
71/100
AI-Aware
Verified
MAY 21, 2026
Methodology v1 · JAIRF v1.0.0

Powered by JAIRF v1.0.0 by Jentic · open methodology at /the-headless-index/methodology

Editorial verdict
Klarna is partially headless and partly UI-led. The Headless Index thesis-fit score of 56/100 puts it mid-table on the index, and JAIRF v1.0.0 puts it at 71/100 (Level 2, AI-Aware). In practice, vendors at this tier are partly machine-consumable: the core flows are reachable through code but several adjacent surfaces still expect a human at a dashboard, and the rest of this verdict explains where Klarna lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Klarna exposes the Payments API, Checkout API, Customer Token API, and the Klarna Network for merchant routing. SDKs and integration patterns vary by region (US, EU, AU each have nuances). The merchant portal handles much of the configuration that other acquirers expose programmatically.[1] Schema observability is the related test: can an agent introspect the contract from cold, or does it have to read prose documentation to do so? REST documentation is detailed at docs.klarna.com per region. A unified OpenAPI URL is not the headline artifact, and the regional split makes schema discovery a per-product exercise.[2] An agent can drive parts of this product, but not all of it: integrators should plan for human-in-the-loop checkpoints where the headless surface stops short. On headless operability: Order creation, capture, refund, and customer-token operations are programmable. Region-specific configuration (BNPL terms, dispute handling) is dashboard-led, which is unusual relative to the broader payments category.[3] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: No first-party Klarna MCP server. The product is BNPL-specialised and has not yet invested in agent-integration tooling.[4] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Klarna webhooks deliver order lifecycle events with HMAC signing. Catalog is appropriate for the BNPL use case; some regional variants ship different event payloads. Net assessment: integrators can build agent flows against Klarna, but the rough edge to plan around is MCP posture[5]. Expect to wrap missing pieces in bespoke glue or accept human-in-the-loop checkpoints. Workable but requires scaffolding.
Verdict by Headless Index pipeline (auto)
// AI-drafted from the evidence layer. Editorial review pending.
Scores

Scorecard detail

Headless Index · 5 sub-criteria
API-first design intent16/20
scored

Klarna exposes the Payments API, Checkout API, Customer Token API, and the Klarna Network for merchant routing. SDKs and integration patterns vary by region (US, EU, AU each have nuances). The merchant portal handles much of the configuration that other acquirers expose programmatically.

signals (5)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +OpenAPI specPublished, 0 operations
  • ·GraphQL endpointDiscovered at https://www.klarna.com/graphql, introspection disabled or scoped
  • +SDKs maintained6 (java, kotlin, swift); top by stars: klarna/react-native-klarna-inapp-sdk (26 stars)
  • +SDK recency3 of 6 SDK repos pushed within 30 days (most recent SDK commit: 2026-05-19)
cite (1)
  • github.sdks@2026-05-19
Headless operation12/20
scored

Order creation, capture, refund, and customer-token operations are programmable. Region-specific configuration (BNPL terms, dispute handling) is dashboard-led, which is unusual relative to the broader payments category.

signals (9)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • −API operations exposedOpenAPI present but operations could not be counted
  • ·Docs pages crawled0 pages (crawler: none)
  • ·Auth schemes documentedAuth documentation page not reached by crawler
  • ·Setup / quickstart docsNot reached by crawler
  • ·Billing docsNot reached by crawler
  • ·Teams / org docsNot reached by crawler
  • ·CLI docsNot reached by crawler
  • ·Schema / data model docsNot reached by crawler
cite (1)
  • github.sdks@2026-05-19
MCP & agent posture4/20
scored

No first-party Klarna MCP server. The product is BNPL-specialised and has not yet invested in agent-integration tooling.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • −Official MCP serverNone found in vendor's GitHub org or the official MCP registry
  • −Community MCP serversNone found
  • −Agent-friendly SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)
cite (1)
  • github.sdks@2026-05-19
Schema observability12/20
scored

REST documentation is detailed at docs.klarna.com per region. A unified OpenAPI URL is not the headline artifact, and the regional split makes schema discovery a per-product exercise.

signals (3)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +OpenAPIPublished at https://api.apis.guru/v2/specs/klarna.com/openai/v0/openapi.yaml (OpenAPI undefined, 0 operations)
  • ·GraphQL introspectionGraphQL endpoint at https://www.klarna.com/graphql but introspection is disabled, scoped, or behind authentication
cite (1)
  • github.sdks@2026-05-19
Webhooks & events12/20
scored

Klarna webhooks deliver order lifecycle events with HMAC signing. Catalog is appropriate for the BNPL use case; some regional variants ship different event payloads.

signals (2)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • ·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.
cite (1)
  • github.sdks@2026-05-19
JAIRF · 6 dimensions
FCFoundational Compliance
85/100

Structural validity, standards conformance, and parsability of the OpenAPI specification.

DXJDeveloper Experience & Tooling Compatibility
60/100

Documentation clarity, example coverage, response completeness, and ingestion health.

ARAXAI-Readiness & Agent Experience
55/100

Semantic clarity, intent expression, datatype specificity, and error standardization.

AUAgent Usability
100/100

Operational composability, complexity comfort, navigation affordances, and safety patterns.

SECSecurity
40/100

Authentication strength, transport security, secret hygiene, and OWASP risk posture.

AIDAI Discoverability
80/100

Descriptive richness, intent phrasing, workflow context, and registry signals.

Band rationale:C band: scores 40-75 range

04 / Embed

Show Klarna's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Klarna mini badge preview
Get embed code
Peers in Payments
SpreedlyC
Headless Index 56/100
dLocalC
Headless Index 56/100
AdyenC
Headless Index 56/100
See full Payments ranking →