Can AI agents automate Klarna Payments?

Klarna Payments is automatable today through the merchant payments API, up to the shopper authorization step. This record is Klarna Payments for merchants. It is not Adyen, Stripe, Mollie, or Vipps MobilePay, and it is not the Klarna consumer app. A merchant opens a session with POST {apiURL}/payments/v1/sessions. Authentication is HTTP Basic with a username linked to the merchant ID and a password. Required session fields include purchase_country, purchase_currency, order_amount, and order_lines. Intent values distinguish a one-time buy from recurring tokenization. A session stays open for 48 hours or until an order is placed. The success response returns session_id and a client_token for the JavaScript SDK or the mobile SDK. One-time orders are POST {apiUrl}/payments/v1/authorizations/{authorizationToken}/order. Recurring orders start from a customer token. The shopper authorization that produces the token happens in the Klarna widget, so an agent cannot finish that step from the API alone. Order management after the purchase is a separate API using the same HTTP Basic credentials. A first-party MCP server was not established. Connector catalogs were not opened. A Klarna CLI was not established. Computer-use viability is unassessed. API scores 7 because the session and order calls are documented and authenticated, while the shopper step and the partial product boundary keep it below a broader payments platform.

Best path today: api · Overall automatability: 7/10