Customer data requirements per market

We care for two reasons really. The first is that we offer credit to consumers, this means that we need to have enough data to do a proper assessment of risk and fraud. This is only possible if we have consumer data of high quality and in a standardized format. The second reason is due to us also being a part of the order management-process.

Our API can handle both billing and shipping addresses separately. If no shipping address has been entered, we will duplicate the billing address and use that as shipping address in our customer data.

Please note that our risk assessment might differ if the billing and shipping are different addresses, as the fraud risk might be seen as higher.

Also note that if the customer of the billing and shipping address is different, this might also be seen as being a larger risk for fraud.

Klarna Payments can receive customer data for a purchase throughout the session. From create_session and up to the authorize call. Any customer data added throughout the session will be be merged and taken into account for the risk assessments that takes place at both load and authorize.

Any customer data in a later call will take precedence over customer data entered in a previous call. If new customer data is amended in subsequent call, this will be merged to the previously entered data.

If any mandatory customer data field (see section below for mandatory fields per market) is still missing at point of authorize, Klarna Payments will respond with an error message. You must collect these and attempt a new authorize to complete the purchase.

Different markets have different standards when it comes to required input. This is mainly due to the internal standards in a country. E.g. are national identification numbers commonly used in Nordics, while not in other countries. In other countries, titles are important.

You need to provide customer details in the fields marked as Mandatory and Optional below for a good customer experience. If you e.g. provide vital aspects of the address in field street_address2 in markets where not marked as Optional this will not be used in all customer-centric systems.