Klarna MCP. Manage the entire payment lifecycle from chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Klarna. Manage the entire payment lifecycle—from checkout session creation to final fulfillment updates—via the Klarna REST API. This MCP server lets your AI client handle complex e-commerce transactions in natural language.
You can create sessions, place orders, capture payments, process refunds, and update shipping details all without touching the Klarna portal.
What your AI agents can do
Cancel authorized order
Cancels an order that was authorized for payment but has not yet been captured.
Capture klarna order
Triggers the final payment processing to convert an authorized order into a captured, paid order.
Create klarna order
Places a formal order using an authorization token, starting the transaction record.
Initializes a transaction by creating a payment session and obtaining the necessary client token for your checkout widget.
Uses authorization tokens to place a formal order, and then triggers the payment capture to complete the transaction.
Processes full or partial refunds, or cancels authorized orders that haven't been captured yet.
Modifies the logistics details, including tracking numbers, for an order after it has been placed.
Retrieves comprehensive details and financial totals for any existing Klarna order ID.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Klarna MCP Server: 8 Tools for Payment Operations
Use these tools to manage the complete payment lifecycle, from initializing a session to updating shipping and processing refunds.
019d75c1cancel authorized order
Cancels an order that was authorized for payment but has not yet been captured.
019d75c1capture klarna order
Triggers the final payment processing to convert an authorized order into a captured, paid order.
019d75c1create klarna order
Places a formal order using an authorization token, starting the transaction record.
019d75c1create payment session
Initializes a checkout session, requiring the order amount, currency, and item lines.
019d75c1get order details
Retrieves full details, status, and financial data for any specific Klarna order ID.
019d75c1get payment session
Gets the status and details for a payment session using its unique identifier.
019d75c1refund klarna order
Processes a refund against a previously captured order.
019d75c1update order shipping
Changes the shipping address or adds tracking numbers to an existing order record.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Klarna, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
You'll use the Klarna MCP Server to manage everything about payments and orders through the Klarna REST API. This lets your AI client handle complex e-commerce transactions just by talking to it. You can set up the entire payment lifecycle—from the initial checkout session right through to updating shipping details and processing refunds, all without ever touching the Klarna portal.
Creating Payment Sessions: Your agent starts by running create_payment_session to initialize a transaction. This call requires the order amount, currency, and item lines, and it gives your client the necessary token for your checkout widget.
Placing and Capturing Orders: After the customer approves payment, your agent uses create_klarna_order with an authorization token to place a formal order and start the transaction record. It then calls capture_klarna_order to finalize the payment, converting the authorized order into a fully captured, paid order.
Managing Refunds and Cancellations: Need to handle money issues? Your agent can process full or partial refunds by calling refund_klarna_order against a previously captured order. If the order was authorized but hasn't been paid for yet, it can cancel it using cancel_authorized_order.
Updating Shipping Information: If the customer changes their mind about where they want the stuff shipped, your agent runs update_order_shipping to modify the address or add tracking numbers to an existing order record.
Auditing Order Status: When you need to know what's going on, your agent pulls the full picture. You can get complete details, status, and financial data for any specific Klarna order ID using get_order_details, or check the status of a payment session with get_payment_session using its unique identifier.
How Klarna MCP Works
- 1 Subscribe to the Klarna MCP Server and provide your API credentials (Username, Shared Secret, Region Domain).
- 2 Instruct your AI client to perform a payment action, like 'Check the status of order 98765-XYZ' or 'Refund order 123'.
- 3 The agent invokes the relevant tool, which makes the necessary API calls and returns the current state and results directly to your client.
The bottom line is: your AI agent handles the multi-step payment logic by talking to Klarna's APIs, keeping you out of the web portal.
Who Is Klarna MCP For?
This server is for e-commerce operations teams and financial controllers. If your job involves monitoring order statuses, processing payments, or auditing transactions across different systems, this tool saves hours of manual dashboard clicking. It lets you manage the full payment lifecycle directly from your natural language client.
Uses the server to check order status, update shipping details, and initiate refunds without logging into the merchant portal.
Audits payment sessions and transaction totals quickly, retrieving specific financial metadata for reconciliation reports.
Integrates Klarna's complex, two-phase payment logic (authorization then capture) into custom applications using reliable API calls.
What Changes When You Connect
- Streamline financial audits. Use
get_order_detailsto instantly pull payment session statuses and total financial metadata for reconciliation, bypassing the need to log into the Klarna portal. - Control the payment flow. Use
create_payment_sessionto initialize a checkout session and get the client token required for your frontend widget, keeping the checkout process fast. - Handle post-sale logistics. Use
update_order_shippingto change shipping information and add tracking numbers to an order without needing a dedicated fulfillment system call. - Fix payment issues instantly. If a payment failed, use
get_order_detailsto check the specific status. If it was authorized but not paid, usecapture_klarna_orderto finalize the payment. - Manage reversals. If a customer cancels, use
cancel_authorized_orderto void the payment attempt, or userefund_klarna_orderfor a full refund on a captured order.
Real-World Use Cases
Processing a complex, multi-stage order
A developer needs to process a $300 order. They first call create_payment_session to get the client token. After the customer completes checkout, they use the resulting authorization token to call create_klarna_order, and finally, they call capture_klarna_order to complete the payment. This sequence runs entirely via the AI agent.
Auditing a batch of disputed orders
A financial controller needs to reconcile payments for 15 orders. Instead of logging into the portal, they ask their agent to run get_order_details for a list of IDs. The agent compiles the status, total amount, and metadata for all of them in a single output.
Handling a shipment address change
The operations team receives a customer request to change the shipping address for order 'XYZ-123'. They simply tell their agent, which calls update_order_shipping with the new details and tracking number, keeping the order record current.
Voiding a failed payment attempt
A customer's payment fails, leaving an authorized but uncaptured order. The team tells the agent to check the status using get_order_details, and then calls cancel_authorized_order to fully void the transaction.
The Tradeoffs
Assuming one API call is enough
Just calling capture_klarna_order for an order ID without first checking if it's authorized or if the order exists.
→
Always check the state first. Use get_order_details to confirm the current status. Only then, if necessary, call capture_klarna_order.
Mixing up order and session IDs
Trying to refund an order ID using the credentials from a payment session ID, leading to an API error.
→
Remember the difference: use get_payment_session when you have a session ID. Use get_order_details when you have a full order ID.
Forgetting to capture funds
Placing an order using create_klarna_order and assuming the money is taken. The payment remains 'AUTHORIZED' and uncaptured.
→
After placing the order, you must explicitly call capture_klarna_order to trigger the actual payment from the customer.
When It Fits, When It Doesn't
Use this server if your core business logic requires managing the entire payment lifecycle: authorization, capture, refund, and shipping updates. It's ideal for developers building complex e-commerce backends or for ops staff who need a single source of truth for payments. Don't use this if you only need to validate a single, static order ID—use a simple lookup tool instead. If your payment system relies heavily on asynchronous webhooks for state changes, you still need to use the tools like get_order_details to reconcile the state within your agent's workflow.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Klarna. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 8 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Manual payment reconciliation shouldn't require jumping between five different dashboards.
Right now, figuring out why a payment failed means logging into the merchant portal, finding the order, checking the status tab, opening the financial reports, and cross-referencing it with the shipping system. It's a minimum of five tabs and three copy-pastes.
With the Klarna MCP Server, your agent pulls all that data in one go. You ask it to 'What's the status of order 98765-XYZ?', and it returns the status, financial totals, and metadata without you leaving your chat window.
Klarna MCP Server: Manage Payments and Orders
You stop manually creating sessions, placing orders, and then manually triggering captures. You just tell your agent, 'Process the payment for this cart.' The agent handles the entire, multi-step API sequence for you.
This means your workflow doesn't just check status; it actively manages the state—it can capture, refund, or cancel the order based on your natural language command.
Common Questions About Klarna MCP
How do I use the `create_payment_session` tool? +
You start by telling your agent the order amount, currency, and item lines. The tool returns a session ID and a client token. You must use this token in your frontend widget to proceed with checkout.
What is the difference between `create_klarna_order` and `capture_klarna_order`? +
create_klarna_order uses an authorization token to place the order record. capture_klarna_order takes that existing order and processes the payment, moving the status from 'AUTHORIZED' to 'CAPTURED'.
How do I get the status of a specific order with `get_order_details`? +
You provide the specific Klarna order ID. The tool returns a full data object containing the current status, financial totals, and any metadata attached to that order.
Can I refund an order with `refund_klarna_order`? +
Yes, you provide the order ID, and the tool processes the refund. It handles partial or full refunds on captured orders.
Does `update_order_shipping` handle tracking numbers? +
Yes, it updates the logistics details for an existing order, allowing you to add tracking numbers and change the shipping address.
What do I need to do before using the `create_klarna_order` tool? +
You must first obtain an authorization token. This token is required to place a formal order via create_klarna_order. You typically get this token when setting up the initial payment session.
Can I use `cancel_authorized_order` if the order has already been captured? +
No, you cannot cancel a captured order. The cancel_authorized_order tool only works on orders that have been authorized but not yet captured. You'll need a refund tool for captured payments.
How do I use `get_payment_session` to check the status of my checkout process? +
This tool retrieves details for an existing payment session. It confirms the status, available funds, and any associated client tokens for your checkout widget.
How do I determine my Klarna Region Domain? +
Use api.klarna.com for Europe, api-na.klarna.com for North America, or api.playground.klarna.com for testing/sandbox environments.
What is the difference between authorizing and capturing an order? +
Authorizing only reserves the funds. You must use the capture_klarna_order tool (typically when shipping) to actually move the money from the customer to your account.
Can I process partial refunds? +
Yes, the refund_klarna_order tool accepts a JSON object where you can specify the exact amount and the specific items being refunded.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
PayPal
Manage e-commerce payments via PayPal — orchestrate orders, process captures securely, issue refunds natively, and structure active subscriptions using AI.
Maxio (SaaS Billing & FinOps)
Manage SaaS billing via Maxio — audit customer contracts, track ARR/MRR metrics, and create invoices.
Recurly
Equip your AI to directly manage subscriptions, billing accounts, and invoices within your Recurly ecosystem without shifting interfaces.
You might also like
Crawlbase
Scrape and crawl via Crawlbase — perform HTML extraction, handle JS-rendered pages, bypass CAPTCHAs, and scrape social profiles directly from any AI agent.
Corescan (Core DAO Blockchain Explorer)
Explore the Core DAO blockchain — check balances, track transactions, inspect smart contracts, and monitor network stats directly via AI.
BoxLock
Secure package deliveries with smart lockbox technology that verifies carriers and prevents porch theft at the door.