Finance — entry 027 of 47
Klarna
Klarna Payments is a buy-now-pay-later and checkout API that merchants embed to offer pay-in-full, pay-in-30-days, and interest-free installment options alongside card and bank payments. Integration follows a session-based flow — create a payment session, render the Klarna widget, then authorize and place the order — over region-specific endpoints (api.klarna.com for Europe, api-na.klarna.com for North America, api-oc.klarna.com for Oceania) secured with HTTP Basic Auth and returning JSON only. Klarna does not publish merchant fees; pricing is a per-transaction rate set per contract, and a live Origin-header probe found no Access-Control-Allow-Origin header on either GET or OPTIONS requests to the live API host.
GreatAPIs Score
Auth quickstart
- Sign up with the provider to get an API key.
- Send it on every request as a header
Authorization: <key> - The exact header isn't documented — Authorization is a common default; confirm in the provider's docs.
Your key is stored only in this browser (localStorage) and sent directly to the API — never to greatapis.
Endpoints
orders3
DELETE/payments/v1/authorizations/{authorizationToken}Cancel an existing authorization
| Name | In | Required | Type |
|---|---|---|---|
authorizationToken | path | yes | string |
| Status | Description | Schema |
|---|---|---|
204 | The authorization was cancelled successfully. | — |
403 | You were not authorized to execute this operation. | — |
404 | The authorization does not exist. | — |
POST/payments/v1/authorizations/{authorizationToken}/customer-tokenGenerate a consumer token
| Name | In | Required | Type |
|---|---|---|---|
authorizationToken | path | yes | string |
application/json — customer_token_creation_request
| Status | Description | Schema |
|---|---|---|
200 | Token was successfully created. | customer_token_creation_response |
400 | We were unable to create a customer token with the provided data. Some field constraint was violated. | ErrorV2 |
403 | You were not authorized to execute this operation. | — |
404 | The authorization does not exist. | — |
409 | The data in the request does not match the session for the authorization. | — |
POST/payments/v1/authorizations/{authorizationToken}/orderCreate a new order
| Name | In | Required | Type |
|---|---|---|---|
authorizationToken | path | yes | string |
application/json — create_order_request
| Status | Description | Schema |
|---|---|---|
200 | Order was successfully created. | order |
400 | We were unable to create an order with the provided data. Some field constraint was violated. | — |
403 | You were not authorized to execute this operation. | — |
404 | The authorization does not exist. | — |
409 | The data in the request does not match the session for the authorization. | — |
sessions3
POST/payments/v1/sessionsCreate a new payment session
application/json — session_create (required)
| Status | Description | Schema |
|---|---|---|
200 | successful operation | merchant_session |
400 | We were unable to create a session with the provided data. Some field constraint was violated. | — |
403 | You were not authorized to execute this operation. | — |
GET/payments/v1/sessions/{session_id}Read an existing payment session
| Name | In | Required | Type |
|---|---|---|---|
session_id | path | yes | string |
| Status | Description | Schema |
|---|---|---|
200 | successful operation | session_read |
403 | You were not authorized to execute this operation. | — |
404 | The session does not exist. | — |
POST/payments/v1/sessions/{session_id}Update an existing payment session
| Name | In | Required | Type |
|---|---|---|---|
session_id | path | yes | string |
application/json — session (required)
| Status | Description | Schema |
|---|---|---|
204 | The session was updated successfully. | — |
400 | We were unable to update the session with the provided data. Some field constraint was violated. | — |
403 | You were not authorized to execute this operation. | — |
404 | The session does not exist. | — |
Try it
Developer reference
https://api.klarna.com- POST/payments/v1/sessions
- GET/payments/v1/sessions/{session_id}
- POST/payments/v1/sessions/{session_id}
- POST/payments/v1/authorizations/{authorizationToken}/order
- DELETE/payments/v1/authorizations/{authorizationToken}