> For the complete documentation index, see [llms.txt](https://developers.bead.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.bead.xyz/faqs-and-troubleshooting/payments-faqs/why-is-my-klarna-payment-still-processing.md).

# Why is my Klarna payment still processing?

This page explains how a Klarna payment moves through its statuses, including the less common cases: a payment that stays in `processing`, an approval that arrives late, and two checkouts open for the same order. For the full status list, see [Payment Statuses](https://developers.bead.xyz/payments/payment-statuses.md).

#### What does `processing` mean for a Klarna payment?

For Klarna, `processing` means the customer chose Klarna on the hosted payment page and Bead has sent them to Klarna to complete checkout. Bead is waiting for Klarna's result.

It does not mean Klarna approved the purchase. When Klarna approves, Bead captures the payment right away and it moves to `completed`, usually within seconds.

#### Why can a Klarna payment stay in `processing` for a long time?

If the customer closes Klarna or leaves without finishing, Klarna does not send a result. The payment stays in `processing` until Bead closes it automatically.

This is expected. It usually means the customer did not complete the Klarna checkout. It does not mean the payment is stuck or that funds are on the way.

#### When does Bead close it?

Bead closes unfinished payments automatically 24 hours after the payment was created, on a periodic check shortly after that point.

* A Klarna payment that was in `processing` closes as `expired`. Bead sends a payment webhook with `statusCode: "expired"`.
* A payment where the customer never chose a payment method closes as `abandoned`, also with a payment webhook.

There is no separate status or reason code for a Klarna decline versus a customer who left. Both surface as `expired`.

#### What if Klarna approves after the payment has closed?

Bead voids the approval. It is not captured and does not settle, and the payment stays `expired`.

#### What if the customer has two Klarna checkouts open for the same order?

Bead treats each payment you create as its own payment. It does not combine or deduplicate payments that share a `reference`. If the customer completes Klarna on two payments, both are captured and both settle, and one will need a refund.

Bead does not currently offer an API to cancel an open payment. To avoid duplicates:

* Create one payment per order, and send the customer back to the same hosted payment URL while that payment is still open.
* Avoid creating a second payment for an order while the first is still `created` or `processing`. A customer may still be completing Klarna on it.
* Expect any payment the customer did not finish to close on its own as `expired` or `abandoned`.

#### When should I fulfill the order?

Fulfill only when the payment reaches `completed`, confirmed by webhook or by `GET /Payments/{paymentId}/tracking`. A payment in `processing` is not a reliable signal that the payment will complete or that funds will settle.

#### Related pages

* [Payment Statuses](https://developers.bead.xyz/payments/payment-statuses.md)
* [Payment Webhooks](https://developers.bead.xyz/payments/payment-webhooks.md)
* [Why is my payment still Created or In Progress?](https://developers.bead.xyz/faqs-and-troubleshooting/payments-faqs/why-is-my-payment-still-created-or-in-progress.md)
* [Expired Payment Handling](https://developers.bead.xyz/reference-guide/payment-scenarios/expired-payment-handling.md)
* [Does Bead support a refund API for crypto, wallet, and BNPL payments?](https://developers.bead.xyz/faqs-and-troubleshooting/payments-faqs/does-bead-support-a-refund-api-for-crypto-wallet-and-bnpl-payments.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.bead.xyz/faqs-and-troubleshooting/payments-faqs/why-is-my-klarna-payment-still-processing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
