Abort Checkout Order
Irreversibly abort an incomplete legacy Klarna Checkout order.
Klarna provides merchant APIs for payments, checkout, order management, settlements, customer tokens, and hosted payment pages.
Irreversibly abort an incomplete legacy Klarna Checkout order.
Irreversibly request acceptance of the financial loss for a Klarna dispute. HTTP 202 means Klarna accepted the request for processing; use GET_DISPUTE to verify that the dispute closed and the chargeback was activated.
Acknowledge receipt of a Klarna order so order processing can continue.
Append shipping carrier and tracking information to a Klarna capture.
Append shipping carrier and tracking information to a Klarna order.
Irreversibly cancel a Klarna payment authorization before an order is created from it.
Irreversibly cancel an uncaptured Klarna order that is not closed. Cancellation cannot be undone.
Irreversibly capture all or part of an authorized Klarna order and return the created capture ID.
Create a Klarna card promise for an order. This Merchant Card Service operation requires Virtual Card Number (VCN) entitlement. Creating a new promise irreversibly invalidates the previous promise for the same order.
Create a Klarna settlement for a completed order and issue its encrypted virtual cards. This Merchant Card Service operation requires Virtual Card Number (VCN) entitlement and commits a new settlement, an irreversible effect.
Create a legacy Klarna Checkout V3 order and return its checkout details.
Create a reusable Klarna customer token from a payment authorization token for subscription purchases.
Create a Hosted Payment Page session from an existing Klarna Payments session or Checkout order URL. The returned distribution-module token is sensitive and must not be logged or persisted.
Create a Klarna order from a customer authorization token. When order.auto_capture is true, Klarna also captures payment automatically.
Create a Klarna order using a reusable customer token. Setting auto_capture to true captures the payment automatically.
Create a Klarna Payments session and return its session ID, sensitive client token, and available payment method categories.
Irreversibly disable a Klarna Hosted Payment Page session that has not completed.
Distribute a Klarna Hosted Payment Page link by email, SMS, or a documented token access ID. Warning: choosing email or SMS immediately sends a message to the specified external recipient; confirm the destination before calling.
Download a merchant or customer evidence attachment from a Klarna payment dispute as a bounded file reference.
Download the PDF settlement report for one payout.
Download a CSV report containing one payout and its transactions.
Download a PDF payout summary for a payout date-time range.
Download a CSV summary of Klarna payouts and transactions for an inclusive payout date-time range.
Irreversibly activate Disputes v3 handling for one direct Klarna merchant account. This account onboarding cannot be undone through the API. Partners cannot use this operation to enroll individual merchants; HTTP 204 also means the merchant was already enrolled.
Irreversibly activate Disputes v3 handling for one Klarna partner account. This account onboarding cannot be undone through the API. partner_id identifies the partner account and client_id supplies the merchant OAuth2 client ID in the request body. Merchants cannot use this operation to enroll a partner; HTTP 204 also means the partner was already enrolled.
First call KLARNA_LIST_CAPTURE_DUE_DATE_OPTIONS for this order and capture, then extend the payment due date using one returned option. Fetch the options before this action because some extensions can cost money.
Extend the authorization validity period for an order that is still AUTHORIZED and delayed unexpectedly. Call this before capture or release changes the order state; Klarna does not allow extension after the order expires or is cancelled. For routinely long fulfillment periods, arrange extended authorization during merchant onboarding instead.
Return one Klarna capture by order ID and capture ID.
Retrieve a Klarna card promise and its card specifications. This Merchant Card Service operation requires Virtual Card Number (VCN) entitlement.
Retrieve a Klarna card settlement by settlement ID or by its associated order ID. Select the identifier with lookup_by and provide only its corresponding field. This Merchant Card Service operation requires Virtual Card Number (VCN) entitlement and returns encrypted card material that must be handled securely.
Return a legacy Klarna Checkout order by order ID.
Return a reusable Klarna customer token and its current status.
Return a fully detailed Klarna Disputes v3 record, including associated merchant and customer evidence. The response preserves provider-added fields and accepts all current or future state values.
Return the current details and distribution state of a Klarna Hosted Payment Page session.
Return a Klarna order and its current authorization, capture, refund, shipping, and customer details.
Return the current details of a Klarna Payments session by session ID. The response may contain sensitive client or authorization tokens; do not log or persist them.
Return one Klarna payout by payment reference.
Return Klarna payout totals grouped by currency for an inclusive payout date-time range.
Return one Klarna refund by order ID and refund ID.
Retrieve the asynchronous cancellation status for a Klarna order with a Virtual Credit Card settlement. This operation requires Virtual Card Number (VCN) entitlement and does not itself change the order.
List the due-date extension options available for a Klarna capture.
Return one page of Klarna Disputes v3 records using all documented filters. Repeated-array and CSV query serialization follow the provider contract; use next_cursor to request one additional page.
Return all captures recorded for a Klarna order.
Return one offset-controlled page of Klarna payouts, optionally filtered by payout date range and currency.
Return one offset-controlled page of Klarna settlement transactions, optionally filtered by payout reference or order ID.
Irreversibly create a full or partial Klarna refund and return the created refund ID.
Irreversibly release the uncaptured authorization remaining on a Klarna order. Use only when no further capture is needed; this does not refund captured funds. This may also normalize the order total: in live testing, a partial capture followed by release reduced order_amount to captured_amount.
Request asynchronous cancellation of a reusable Klarna customer token by changing its status to CANCELLED. Once Klarna processes the request, the token can no longer be used for new orders; HTTP 202 confirms acceptance, not that the state change has completed.
Irreversibly request cancellation of a Klarna order associated with a Virtual Credit Card settlement. This operation requires Virtual Card Number (VCN) entitlement. It mutates the order: an existing cancellation returns CANCELLED, while a new request is queued asynchronously and returns PENDING.
Irreversibly resend Klarna customer communication for a capture. Calling this action has an operational side effect: Klarna sends a communication to the customer.
Submit reason-specific merchant evidence for a Klarna dispute request.
Update a legacy Klarna Checkout order and return the resulting order.
Update the authorized amount and order lines on an existing order.
Update the permitted customer address details on an existing order.
Update the merchant reference values stored on a Klarna order.
Update mutable data on an existing Klarna Payments session, including order amounts and lines, customer and billing or shipping addresses, merchant references and URLs, purchase locale and currency, payment options, and session intent. Klarna returns no session data after a successful update.
Upload one merchant evidence attachment to a Klarna payment dispute. Klarna limits attachments to 7 MB.
Upload 1-10 merchant evidence attachments to one Klarna payment dispute, sequentially in input order. Each successful upload creates a separate attachment resource. The batch is not atomic: if a later upload fails, attachments uploaded earlier remain created.
The Klarna integration connects your Dench AI CRM directly to Klarna, so agents can read and act on your Klarna data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
58 actions are available for agents to invoke on your behalf. Every call runs through Klarna's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Klarna and click Connect — you'll authorize access through Klarna's own sign-in flow. No API keys or code required.
Ask an agent to use Klarna in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Klarna integration connects your AI CRM to Klarna, so AI agents can work with your Klarna data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Klarna integration currently exposes 58 actions, including Abort Checkout Order, Accept Dispute Loss, Acknowledge Order, Add Capture Shipping Info, Add Order Shipping Info, and Cancel Authorization. Agents invoke them on your behalf from chat or from automations.
No. You connect Klarna from your Dench workspace using Klarna's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Klarna's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Klarna connection from your workspace settings at any time.