Data Panda brings your Klarna data together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your team uses every day.
Klarna is a Swedish fintech founded in 2005 in Stockholm by Sebastian Siemiatkowski, Niklas Adalberth and Victor Jacobsson. It started as a way for small Swedish webshops to let a customer pay after delivery, grew across Europe through the 2010s, launched in the United States in 2015 and went public on the New York Stock Exchange in September 2025 under the ticker KLAR at a valuation around 17 billion dollars. The group serves roughly 114 million active consumers and around 850 thousand merchants across 26 markets. In Sweden, Klarna holds a banking licence and is supervised by Finansinspektionen, the Swedish Financial Supervisory Authority.
Klarna is a different payment rail than a card processor. A Visa or Mastercard charge clears within days against the shopper's own bank; a Klarna checkout means Klarna pays the merchant up front and collects from the consumer later, through Pay in 30, Pay in 4 or longer financing. That is why Klarna's merchant fee sits higher than a card fee and why the payout on the bank is a single netted line with a 2 to 3 business-day delay after capture. Our connector exposes the two tables Peliqan pulls: Settlement Payouts and Settlement Transactions. It is a narrow slice, purpose-built for reconciling the BNPL payout against the order, the invoice and the card-side totals next to it. Consumer-app behaviour and Klarna Card lifestyle data sit outside this scope.
Klarna, Stripe and the local methods on one timeline, with the fee drift made visible.
Let the ledger and the webshop react to the Klarna settlement as it lands.
Use Klarna history to predict the return and the dispute before they hit the payout.
Internal tools around the BNPL payout data that otherwise lives in the Klarna merchant portal.
A list of concrete reports, automations and AI features we have built on Klarna data. Pick the one that matches your situation.
Does the Klarna payout on the bank match the orders behind it?
Each Klarna payout is broken down to the Settlement Transactions that produced it: captures, refunds, fees and dispute adjustments. The gap finance used to chase between the Klarna Merchant Portal export and the bank statement becomes one reconciled view, with the adjustment that caused any mismatch already tagged.
What is the real cost of BNPL on our checkout compared to card?
Klarna fee per order next to the Stripe fee on the same cart, by country and by average order value. The question of whether the extra Klarna fee pays for itself in conversion and average order value stops being a hunch and becomes a number you can defend against the card baseline.
How does BNPL change our return and dispute rate?
Return and dispute share on Klarna orders next to card orders, per product category and country. Some categories that look profitable on gross BNPL revenue turn out to ship more returns and more disputes, and the warehouse makes that visible before the quarterly review flags it.
Every Klarna payout broken down to its captures, fees, refunds and dispute adjustments, next to the bank line and the journal booking. Month-end reconciliation between the Klarna portal, the ledger and the bank statement stops being a separate loop on top of the card reconciliation.
For account owners and ecommerce leads, Klarna share of the basket next to card share, per country and per product line. The call on where to push BNPL and where to let the card rail carry the checkout draws on the same warehouse view as finance uses for reconciliation.
Return and dispute rate per product and country, split between BNPL and card rails. The operational choices about which product to keep on Klarna, which to cap at card only and which to renegotiate on fees stop being based on a single Klarna dashboard export.
Every Shopify order paid through Klarna is matched to the Settlement Transaction that captured it, and each Klarna payout is traced back to the orders it paid out for. Returns and disputes flow back to the original Shopify order so the margin view reflects BNPL refunds instead of waiting for the next Klarna export.
Klarna payouts land in Exact Online as bank journal entries, with Klarna fees split out and the underlying captures matched to the invoices they settle. The 2 to 3 day gap between order capture and payout is reconciled on the ledger side without finance chasing a portal export.
BigCommerce orders paid via Klarna line up with the Settlement Transactions that captured and refunded them, and each Klarna payout links back to the BigCommerce order it funded. Return and dispute rates per product category become visible in the same BigCommerce sales view, not in a separate Klarna report.
Klarna Settlement Transactions are joined with Stripe charges on order id and customer, so the fee per order on the BNPL rail sits next to the fee on the card rail for the same cart. Finance and ecommerce see the real cost of BNPL conversion instead of averaging the fees across a quarter.
These are the 2 tables we currently pull from Klarna into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.
Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.
You keep the reporting tool you already have. We connect it to the warehouse where your Klarna data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
The connector exposes two tables from the Klarna Merchant Portal: Settlement Payouts and Settlement Transactions. That covers payout reconciliation, fee analysis, return and dispute tracking, and the join back to the order that produced each capture. It does not cover consumer-app behaviour, Klarna Card activity or the resolution-centre case trail beyond the dispute flag on the transaction.
Yes. Klarna Bank AB holds a Swedish banking licence and is supervised by Finansinspektionen, the Swedish Financial Supervisory Authority. In other markets Klarna works under local consumer-credit and payment regulations, including FCA oversight in the United Kingdom. That regulatory status is why Klarna can front the money to the merchant and collect from the consumer on Pay in 30 or Pay in 4 terms.
Klarna typically settles payouts 2 to 3 business days after the order is captured, with the exact delay set in your merchant contract. That delay gives Klarna a window to register returns and adjustments before money moves, and it is why reconciliation between the Klarna payout line on the bank and the order in the webshop always needs a time-aware join rather than a same-day match.
We review your Klarna setup and the systems around it. Together we pick the first thing worth building.