Skip to content
Book a demoStart free
Connectors

Klarna connector

Set up the Klarna connector in Kaivo: authentication, configuration, the 2 BigQuery tables it syncs, and answers to common questions.

Klarna connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your Klarna data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your payment and finance data instead of moving it.

Sync your Klarna payments data into BigQuery with Kaivo to analyse transactions and payouts alongside the rest of your finance data.

CategoryFinance & Payments
AuthenticationUsername and password
SetupSelf-service
  1. Sign up for Kaivo and create a workspace.
  2. Connect your Klarna account.
  3. Choose which tables to sync.
  4. Wait for the initial sync to finish.
  5. Query your data in BigQuery or your favourite AI or BI tool.

Connect with your Klarna login. You provide:

Field Description
Password
The password associated with your Klarna Merchant ID, used to authorize API access.

|

When you set up the connector, you provide:

Field Description
Region
The API region for your Klarna account. Supported values: ‘eu’ (Europe), ‘na’ (North America), ‘oc’ (Oceania).

| | Username |

Your Klarna Merchant ID (eid) combined with a random string, used for API authentication.

|

Kaivo syncs 2 tables from Klarna into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.

payouts (22 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
totals__commission_amount INT64 The total amount of commissions, in minor units
totals__repay_amount INT64 The total amount of money that has been repaid by the merchant from the debt to Klarna, in minor units
totals__sale_amount INT64 The total amount of sales, in minor units
totals__holdback_amount INT64 The total amount of money withheld by Klarna, in minor units
totals__tax_amount INT64 The total amount of tax, in minor units
totals__settlement_amount INT64 The total amount of the settlement in question, in minor units
totals__fee_correction_amount INT64 The total amount of fee correction, in minor units
totals__reversal_amount INT64 The total amount of reversals, in minor units
totals__release_amount INT64 The total amount of money released from holdback by Klarna, in minor units
totals__return_amount INT64 The total amount of returns, in minor units
totals__fee_amount INT64 The total amount of fees, in minor units
totals__charge_amount INT64 The total amount of charges, in minor units. The additional field detailed_type contains the purpose of the charge
totals__credit_amount INT64 The total amount of credits, in minor units. The additional field detailed_type contains the purpose of the credit
payment_reference STRING The reference id of the payout
payout_date TIMESTAMP ISO 8601 formatted date-time string
currency_code STRING ISO 4217 Currency Code. Like USD, EUR, AUD or GBP.
currency_code_of_registration_country STRING ISO 4217 Currency Code of the country you are registered in.
merchant_settlement_type STRING Whether the amounts are net or gross
merchant_id STRING The merchant id
transactions STRING Link to the transactions that are part of this payout
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
transactions (29 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
amount INT64 Total amount of the specific transaction, in minor units
merchant_id STRING Unique identifier of the merchant associated with the transaction
shipping_address_country STRING Country of the shipping address for the transaction
capture_id STRING The Klarna assigned id reference of a specific capture
merchant_reference1 STRING Merchant assigned reference, typically a reference to an order management system id
sale_date TIMESTAMP ISO 8601 formatted date-time string
type STRING The type of transaction.
capture_date TIMESTAMP ISO 8601 formatted date-time string
payment_reference STRING Reference to the specific payout the transaction is part of, if available.
order_id STRING The Klarna assigned order id reference
payout STRING Link to the payout that this transaction is part of
refund_id STRING The Klarna assigned id reference of a specific refund
short_order_id STRING The Klarna assigned short order id reference
merchant_reference2 STRING Merchant assigned reference, typically a reference to an order management system id
currency_code STRING ISO 4217 Currency Code. Like USD, EUR, AUD or GBP.
purchase_country STRING ISO Alpha-2 Country Code
vat_rate INT64 VAT (Value added tax) rate on Klarna fees
vat_amount INT64 VAT (Value added tax) amount on Klarna fees, in minor units
shipping_country STRING ISO Alpha-2 Country Code
initial_payment_method_type STRING Payment method the consumer chose during checkout
initial_number_of_installments INT64 Number of installments the consumer chose during checkout in case of installment payments
initial_payment_method_monthly_downpayments INT64 Number of monthly downpayments that were chosen during the checkout in case of installment payments.
merchant_capture_reference STRING Your internal reference to the capture, that has been submitted during capturing an order via API
merchant_refund_reference STRING Your internal reference to the refund, that has been submitted during refunding an order via API
detailed_type STRING Detailed description of the transaction type
tax_in_currency_of_registration_country INT64 The tax amount on the respective fee, converted into the currency of your registration country. In case you are a German merchant selling in another currency then EUR or a Swedish merchant selling in another currency then SEK, we convert the VAT amount on the Klarna fees into the currency of the country you are registered in, based on the exchange rate of the capture date.
currency_code_of_registration_country STRING ISO 4217 Currency Code of the country you are registered in.
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Klarna supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.

How long does the initial sync take for Klarna?

Section titled “How long does the initial sync take for Klarna?”

It depends on how much history is in your Klarna account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.

Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.

What happens when Klarna’s schema changes?

Section titled “What happens when Klarna’s schema changes?”

New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in Klarna, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.

How do I handle GDPR or data deletion requests?

Section titled “How do I handle GDPR or data deletion requests?”

Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Klarna instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Klarna connector in Kaivo and all of its synced data is deleted with it.

Use transactions to track sales and fees over time.

Join payouts with transactions to reconcile sales against bank deposits.

Use transactions to understand how fees affect your margins.

Once Klarna data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with Klarna data.

Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →

Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →

Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →

The premium analytics standard, with native BigQuery integration. Setup guide →

Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →

Connect via Power Query’s BigQuery connector. Setup guide →

Open-source BI tool with strong BigQuery support. Setup guide →

See our pricing page for Klarna connector pricing and plan details.