Skip to content
Banking/open banking

klarna.com:payments

Klarna Payments API V1 sandbox and mock API

The payments API is used to create a session to offer Klarna's payment methods as part of your checkout. As soon as the purchase is completed the order should be read and handled using the [`Order Management API`](https://docs.klarna.com/api/ordermanagement). Read more on [Klarna payments](https://docs.klarna.com/klarna-payments/). Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
6
Collections
-
Event types
-
Start this simulation
example request
curl https://your-klarna-payments.slurry.io/payments/v1/sessions/123 \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.0.0.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

All 6.

  • DELETE/payments/v1/authorizations/{authorizationToken}
  • POST/payments/v1/authorizations/{authorizationToken}/customer-token
  • POST/payments/v1/authorizations/{authorizationToken}/order
  • POST/payments/v1/sessions
  • GET/payments/v1/sessions/{session_id}
  • POST/payments/v1/sessions/{session_id}