Integrator Tagging

Discover the essentials of integration tagging for enhancing the integration journey with Klarna. Learn about its role in customer experience, performance monitoring, and how to effectively use naming standards for seamless operations.

Integration tagging is a crucial mechanism for improving the integration experience by providing detailed and consistent data to support customer experience, performance tracking, and incident resolution. All operations and interactions with Klarna should be tagged with associated integration Partners to ensure granular monitoring and performance. To provide this level of detail, Klarna requires that Partners provide all available information with each interaction.

Note: Integration tagging is currently under development and is subject to change. It will become available in future releases.

Naming standardization

To enable Acquiring Partners to provide all integrated Partners without additional validation, and avoid unnecessary rejections of requests when a new Partnership is provided, the naming parameters in Klarna’s tagging solution are unvalidated strings, not enums. As such it is required that naming conventions are followed whenever a new application name is provided.

In cases where Klarna recognizes a Partnership under a different name, Klarna agents may reach out to request the value provided be adjusted to remain consistent across multiple integrators.

Conventions when providing integrator names

To maximize the possibility of alignment in naming conventions without maintaining a list of all possible applications, Please ensure that your name parameters follow the below naming conventions:

Base any name used off of the commonly used naming convention for the application - what they call themselves externally towards customers.
Use UPPER_CASE SNAKE_CASE where multiple words are involved in an application name.
Standardize language-specific characters and convert characters with diacritics or accents to their base form for consistent handling. (e.g “Rénault” becomes “Renault”)
Strip out spaces and punctuation
Separate the company name from it’s legal form (e.g. “Klarna Inc.” and “Klarna AB” both become “Klarna”)
Do not include regions or countries within an application name where it doesn’t express fundamental differences in the performance of the product. (e.g. “Klarna US” and “Klarna SE” both become “Klarna”)

Predefined platforms

Below is a list of key platforms with predefined strings. All tagging requests involving these Partners must match their name parameter to the strings below. More information on these Partnerships can be found in the links provided alongside the list. In this context, the term “platform” is used to describe any specific layer within the integration. Acquiring Partners are considered “platform” in this context. Contact Klarna Solutions Engineers if the platforms are not in the list.

Platform name	Predefined string
24Nettbutikk	`24NETTBUTIKK`
4webs	`4WEBS`
Abicart AB	`ABICART_AB`
ACIWorldwide	`ACIWORLDWIDE`
Addis	`ADDIS`
Adobe Commerce (Magento)	`ADOBE_COMMERCE`
Adyen	`ADYEN`
Aera Payment & Identification	`AERA_PAYMENT_AND_IDENTIFICATION`
Airwallex	`AIRWALLEX`
Alcalink	`ALCALINK`
Alipay	`ALIPAY`
Alphabank	`ALPHABANK`
Altapay	`ALTAPAY`
Antom	`ANTOM`
Apexx	`APEXX`
Aptos	`APTOS`
AQS	`AQS`
Artdinamica	`ARTDINAMICA`
Askås I & R	`ASKAS_I_AND_R`
Aurus	`AURUS`
AutoPay	`AUTOPAY`
AvantiCart	`AVANTICART`
Avensia	`AVENSIA`
Axerve S.p.A	`AXERVE_SPA`
Ayla Diseño y Tecnología	`AYLA_DISENO_Y_TECNOLOGIA`
Bank of America	`BANK_OF_AMERICA`
Banorte	`BANORTE`
Banque Populaire	`BANQUE_POPULAIRE`
BBVA	`BBVA`
BigCommerce	`BIGCOMMERCE`
Billwerk+	`BILLWERKPLUS`
BlackPepper	`BLACKPEPPER`
BlueSnap	`BLUESNAP`
Blugento	`BLUGENTO`
BNPP	`BNPP`
Bold Commerce	`BOLD_COMMERCE`
BPCE	`BPCE`
Braintree	`BRAINTREE`
BrinkCommerce	`BRINKCOMMERCE`
Buckaroo	`BUCKAROO`
Cafe24	`CAFE24`
CardinalCommerce	`CARDINALCOMMERCE`
Cardlink	`CARDLINK`
CCV Group B.V.	`CCV_GROUP_BV`
Cegid	`CEGID`
Centra	`CENTRA`
Checkout	`CHECKOUT`
Citcon	`CITCON`
Citibank	`CITIBANK`
ClearHaus	`CLEARHAUS`
Clearis	`CLEARIS`
CloudCart	`CLOUDCART`
CodaPayment	`CODAPAYMENT`
Commerzia	`COMMERZIA`
Comerzzia	`COMERZZIA`
Comgate	`COMGATE`
CommerceTools	`COMMERCETOOLS`
Computop	`COMPUTOP`
Conecta Software	`CONECTA_SOFTWARE`
Conekta	`CONEKTA`
ContentSpeed (Payten)	`CONTENTSPEED`
Cosin	`COSIN`
Credit Agricole	`CREDIT_AGRICOLE`
Credit Mutuel	`CREDIT_MUTUEL`
Crisp Studio	`CRISP_STUDIO`
CS Cart	`CS_CART`
Cybersource	`CYBERSOURCE`
Danal	`DANAL`
DanDomain	`DANDOMAIN`
DAPP	`DAPP`
DEUNA	`DEUNA`
Deutsche Bank	`DEUTSCHE_BANK`
Digital River	`DIGITAL_RIVER`
Digital Takeout	`DIGITAL_TAKEOUT`
Dintero	`DINTERO`
Dir&Ge	`DIR_AND_GE`
Dlocal	`DLOCAL`
DNA Payments	`DNA_PAYMENTS`
e-shop 360	`E-SHOP_360`
Easypay	`EASYPAY`
Ebanx	`EBANX`
eComm360	`ECOMM360`
eCommerce news	`ECOMMERCE_NEWS`
ecwid	`ECWID`
Egloba	`EGLOBA`
EKMPowershop	`EKMPOWERSHOP`
Elavon	`ELAVON`
Enactor	`ENACTOR`
epay	`EPAY`
EpiServer	`EPISERVER`
Eromnet*	`EROMNET`
eService	`ESERVICE`
eShopWorld	`ESHOPWORLD`
eStudio 34	`ESTUDIO_34`
Eupago	`EUPAGO`
EuPlatesc	`EUPLATESC`
Eurobank	`EUROBANK`
eValent	`EVALENT`
Eximbay	`EXIMBAY`
Extended	`EXTENDED`
FAPS	`FAPS`
FIK	`FIK`
Finqu Oy	`FINQU_OY`
Fintk Consulting	`FINTK_CONSULTING`
First Data	`FIRST_DATA`
FIS	`FIS`
FiServ (Clover, Telecash, AIB)	`FISERV`
FlatPay	`FLATPAY`
Flooid	`FLOOID`
FreedomPay	`FREEDOMPAY`
GetNet	`GETNET`
GK Software	`GK_SOFTWARE`
Global Payments (Evo Payments)	`GLOBAL_PAYMENTS`
GlobalE	`GLOBALE`
GoDaddy	`GODADDY`
Gomag	`GOMAG`
GoPay	`GOPAY`
Hiberus	`HIBERUS`
HiPay SAS	`HIPAY_SAS`
Hobex	`HOBEX`
Holipay	`HOLIPAY`
Hostinger	`HOSTINGER`
I’mweb	`IMWEB`
ICG	`ICG`
Idosell/IAI	`IDOSELL_IAI`
Ifthenpay	`IFTHENPAY`
Ilion	`ILION`
Ingenico	`INGENICO`
Intershop	`INTERSHOP`
Ixopay	`IXOPAY`
J.P. Morgan	`JP_MORGAN`
Jimdo	`JIMDO`
JPM	`JPM`
JTL Shop	`JTL_SHOP`
Jumpseller	`JUMPSELLER`
KG Inicis	`KG_INICIS`
Kodmyran	`KODMYRAN`
Kushki	`KUSHKI`
Kustom	`KUSTOM`
Kvanto	`KVANTO`
Labelgrup	`LABELGRUP`
Legends	`LEGENDS`
Lemonway	`LEMONWAY`
Lightspeed	`LIGHTSPEED`
Línea Gráfica	`LINEA_GRAFICA`
Litium	`LITIUM`
Lloyd	`LLOYD`
LMS-Sport	`LMS-SPORT`
Logpay	`LOGPAY`
Lyra Network	`LYRA_NETWORK`
Maktagg	`MAKTAGG`
Mangopay	`MANGOPAY`
Marketpay	`MARKETPAY`
MerchantPro	`MERCHANTPRO`
Microsoft Dynamics Navision	`MICROSOFT_DYNAMICS_NAVISION`
MobilePay	`MOBILEPAY`
MODDO	`MODDO`
Mollie	`MOLLIE`
Mondido	`MONDIDO`
Monei	`MONEI`
Moneris	`MONERIS`
Monext	`MONEXT`
Multisafepay	`MULTISAFEPAY`
myPOS	`MYPOS`
Mystore	`MYSTORE`
NBG	`NBG`
NCR	`NCR`
Netgiganten.dk	`NETGIGANTENDK`
Nethit Systems	`NETHIT_SYSTEMS`
Netopia	`NETOPIA`
Netsite	`NETSITE`
Nexi Group (Nets, Concardis, Computop, Paytrail)	`NEXI_GROUP`
NHN Commerce	`NHN_COMMERCE`
NHN KCP	`NHN_KCP`
Nice Payments	`NICE_PAYMENTS`
Norce (Jetshop/Storm)	`NORCE`
Nordicway	`NORDICWAY`
Novalnet	`NOVALNET`
Nuvei	`NUVEI`
OC Payment GmbH	`OC_PAYMENT`
Oceanpayment	`OCEANPAYMENT`
Odero (TOKEN)	`ODERO`
Ohdigital	`OHDIGITAL`
Okisam	`OKISAM`
One.com	`ONECOM`
OneBox	`ONEBOX`
Onil	`ONIL`
OnlinePaymentPlatform	`ONLINEPAYMENTPLATFORM`
Openbravo	`OPENBRAVO`
Opencart	`OPENCART`
Openpay	`OPENPAY`
Optimizely	`OPTIMIZELY`
Oracle Commerce Cloud	`ORACLE_COMMERCE_CLOUD`
Orbital Revolution	`ORBITAL_REVOLUTION`
Outpayce (part of Amadeus)	`OUTPAYCE`
OxidESales	`OXIDESALES`
P24	`P24`
Pacypay	`PACYPAY`
Pay.nl	`PAYNL`
Paybyrd	`PAYBYRD`
Payco	`PAYCO`
PayComet	`PAYCOMET`
PayerMax	`PAYERMAX`
PayGreen	`PAYGREEN`
Payletter	`PAYLETTER`
Paylike	`PAYLIKE`
Payline	`PAYLINE`
Payment Sense	`PAYMENT_SENSE`
Paymentwall	`PAYMENTWALL`
PayNow	`PAYNOW`
Payone	`PAYONE`
Payoneer	`PAYONEER`
PayPlug Enterprise SaaS	`PAYPLUG`
Payrexx	`PAYREXX`
PaySafe	`PAYSAFE`
Paytrim	`PAYTRIM`
PayU	`PAYU`
Payxpert	`PAYXPERT`
PensoPay	`PENSOPAY`
PeP	`PEP`
PHC	`PHC`
PingPong	`PINGPONG`
Pireaus Bank	`PIREAUS_BANK`
Planet Payment (DataTrans)	`PLANET_PAYMENT`
Plati.online	`PLATIONLINE`
Polcard	`POLCARD`
PPRO	`PPRO`
Prestashop	`PRESTASHOP`
Primavera	`PRIMAVERA`
Primer	`PRIMER`
ProcessOut	`PROCESSOUT`
Prosa	`PROSA`
Pulse247 Oy (MyCashFlow)	`PULSE247_OY`
PXP Financial	`PXP_FINANCIAL`
Qenta	`QENTA`
Quickbooks	`QUICKBOOKS`
Quickbutik	`QUICKBUTIK`
QuickPay	`QUICKPAY`
Radial	`RADIAL`
Razer Merchant Service	`RAZER_MERCHANT_SERVICE`
Reach	`REACH`
Redicom	`REDICOM`
Redsys	`REDSYS`
Reduncle	`REDUNCLE`
Reduniq	`REDUNIQ`
Rocket Digital	`ROCKET_DIGITAL`
Sabadell	`SABADELL`
Sage	`SAGE`
Salesforce Commerce Cloud	`SALESFORCE_COMMERCE_CLOUD`
SAP (Hybris)	`SAP_HYBRIS`
Scannet	`SCANNET`
Scayle	`SCAYLE`
SDi Digital Group	`SDI_DIGITAL_GROUP`
Seidor	`SEIDOR`
Shift4	`SHIFT4`
Shoper	`SHOPER`
Shopify	`SHOPIFY`
ShopLazza	`SHOPLAZZA`
Shopline	`SHOPLINE`
Shoptet	`SHOPTET`
Shopware	`SHOPWARE`
SIBS	`SIBS`
Simpler	`SIMPLER`
Simply.com	`SIMPLYCOM`
Sipay	`SIPAY`
Six Saferpay	`SIX_SAFERPAY`
Smallpay S.r.l.	`SMALLPAY_SRL`
solteq	`SOLTEQ`
Square	`SQUARE`
Squarespace Commerce	`SQUARESPACE_COMMERCE`
Strato	`STRATO`
Stripe	`STRIPE`
Studioforty9	`STUDIOFORTY9`
SumUp	`SUMUP`
Swedbank Pay	`SWEDBANK_PAY`
TD Bank Merchant Solutions	`TD_BANK_MERCHANT_SOLUTIONS`
Telecash	`TELECASH`
Tencent	`TENCENT`
Thunes	`THUNES`
TiendaNube	`TIENDANUBE`
Tier1	`TIER1`
Toss Payments	`TOSS_PAYMENTS`
Tpay	`TPAY`
Trevenque Sistemas de Inflormación	`TREVENQUE_SISTEMAS_DE_INFLORMACION`
Trilogi	`TRILOGI`
TrustPay	`TRUSTPAY`
Twice Commerce (prev. Rentle Oy)	`TWICE_COMMERCE`
Unzer	`UNZER`
Upstream pay	`UPSTREAM_PAY`
Verifone	`VERIFONE`
Vilkas Group	`VILKAS_GROUP`
Vipps	`VIPPS`
VismaPay	`VISMAPAY`
Visualit	`VISUALIT`
VisualSoft	`VISUALSOFT`
VivaWallet	`VIVAWALLET`
VR Payment	`VR_PAYMENT`
Vtex	`VTEX`
Wallee	`WALLEE`
Way2ecommerce	`WAY2ECOMMERCE`
Weasy.io	`WEASYIO`
Webimpacto	`WEBIMPACTO`
Webmefy	`WEBMEFY`
Wells Fargo	`WELLS_FARGO`
Westpay	`WESTPAY`
Wikinggruppen	`WIKINGGRUPPEN`
Windcave	`WINDCAVE`
Wix	`WIX`
Wizishop	`WIZISHOP`
Woocommerce	`WOOCOMMERCE`
woolman	`WOOLMAN`
WorldFirst	`WORLDFIRST`
Worldline	`WORLDLINE`
Worldpay	`WORLDPAY`
Xsolla	`XSOLLA`
xt commerce	`XT_COMMERCE`
Young Pixel	`YOUNG_PIXEL`
Zettle by Paypal	`ZETTLE`

Data requirements

The X-Klarna-Integration-Metadata header object encapsulates information about all known integration pathways involved in a given request.

Integrator object

integrator provides details of the client responsible for the request, and Acquiring Partners are required to pass this object with every request.

Name: The name of the integrator sending the request to Klarna. Values are not validated, but Klarna may request the value provided be adjusted to remain consistent across multiple integrators. See predefined platforms for a list of accepted strings for defined platforms.
Module name: The name of the software module sending the request to Klarna. This allows Klarna to recognize different modules under the same integrator. Values are not validated.
Module version: The version of the integration indicated by the module_name parameter.
Session reference: A long-lived, unique identifier assigned by the application associated with an overall transaction or session. This identifier is stored within Klarna’s logs, empowering agents to investigate issues with downstream applications.

Originators array

originators is an array of objects representing all applications or platforms involved in providing information included within the request. This metadata provides a detailed view of the specific software platforms, programs or modules leveraged by the Partner.

Name: The name of the platform providing data passed towards Klarna in the request. Values are not validated, but Klarna may request the value provided be adjusted to remain consistent across multiple integrators. See predefined platforms for a list of accepted strings for defined Partners.
Module name: The name of the software module providing the data passed in the request to Klarna.
Module version: An optional parameter indicating the version of the integration indicated by the module_name parameter.
Session reference: An optional parameter containing a long-lived, unique identifier assigned by the application associated with an overall transaction or session. This identifier is stored within Klarna’s logs, empowering agents to investigate issues with downstream applications.

Implementation pathways

WebSDK

When initializing the Klarna WebSDK, integrators can include the integrator context within the configuration object to ensure the integration metadata is correctly registered:

JAVASCRIPT

1 2 3 4 5 6 7 8 9 10

  clientId: 'your_client_id_here',
  integrationMetadata: {
    integrator: {
      name: "AcquiringPartner",
      moduleName: "SubIntegration",
      moduleVersion: "2.0",
      sessionReference: "xxx",
    },
    originators: [{
      name: "ecommerceCompany",

Update integration metadata after initialization:

JAVASCRIPT

1 2 3 4 5 6 7 8 9 10

await Klarna.Config.IntegrationMetadata.setIntegratorSessionReference("new-session-ref");

await Klarna.Config.IntegrationMetadata.setOriginators([{
  name: "ecommerceCompany",
  sessionReference: "5555-474",
  moduleName: "ecommercePlugin",
  moduleVersion: "1.0",
}, {
  name: "anotherMerchant",
  sessionReference: "9999-123",

The originator metadata array will be bound to a specific instance and should be limited to no more than 6 objects, retaining the final 6 items in case of any conflict.

APIs

The Klarna-Integratation-Metadata header object will allow for the passing of integration tagging information in all server-side requests. Although this field is technically optional, Acquiring Partners must send this information in every request towards Klarna, indicating both the version of their integration which triggers the request within the integrator object, in addition to any services which provide relevant data passed within the request in the originators array.

JAVASCRIPT

1 2 3 4 5 6 7 8 9 10

  "integrator": {
    "name": "AcquiringPartner",
    "session_reference": "xxx",
    "module_name": "subIntegrationPath",
    "module_version": "1.0"
  },
  "originators": [{
    "name": "ecommerceCompany",
    "session_reference": "xxx",
    "module_name": "subIntegrationPath",

Plugins and platforms

For any plugin or platform managed by an Acquiring Partner, Partner tagging information should be included by default without additional effort from the Partner. Any plugin provisioning data directly towards Klarna should include information on the specific integration within the integrator object, and any plugin passing information via an Acquiring Partner must be included within the originators array - with the Acquiring Partner passed as the integrator. As Partners are required to provide this information across all integration paths, the result allows monitoring of performance across multiple integrations.