This page contains sample data you can use for testing your integration in the Klarna playground environment.
Use the sample customer data to test the standard approved and denied payment flows in Klarna payments and Klarna checkout. If you want to test non-standard flows, such as pending payments or presenting only pre-paid payment options, see the Other test scenarios section in this page.
If you want to test different payment methods, direct debit, credit card, and bank transfer, use the sample payment data.
To make a purchase new users in most countries go through an account creation wizard, provide their personal data, and enter a verification code to create their Klarna user account.
To test a new Klarna user account, select a combination of a random phone number and an email matching the required pattern. If the combination was used during sign-up before, you'll be logged into an existing account after providing a one-time password (OTP). In the playground environment, you can use any valid 6-digit number other than 999999 as the OTP.
One user account is only valid in a single market. For example, you can't use the same email address or phone number to test purchases in a playground store in Germany and Sweden.
User account is available in all countries included in the sample customer data list, except for Switzerland and Finland.
If you choose to create a new account rather than using one of the provided sample customer accounts on this page, any Personally Identifiable Information (PII) will be substituted with synthetically generated data. Consequently, you may notice different account values from those you provided. This helps us prevent data leaks in our playground environment.
Use the sample data for private persons to test B2C transactions. The company test data can be used for testing B2B transactions.
The B2C sample data in this article s split into two sub-categories:
Standard flows shows the data for testing standard responses approved and denied transactions.
Custom flows shows the data for testing flows other than the standard approved and denied transactions, for example, launching a dispute.
Below is a list of email addresses associated with standard and custom test flows. When testing, replace the final two asterisks with a 2-letter country code of a Klarna market. For example, to test an approved transaction flow for Sweden, use [email protected].
Standard flows
Email address pattern
Description
customer@email.**
Accept purchase. Message: "None, auth_token (valid 60 minutes) is returned for use in create_order"
customer+denied@email.**
Hard decline. Message: "Your purchase can not be accepted Unfortunately your purchase can not be accepted at this moment. Please choose a different payment method to complete your purchase."
Custom flows
Email address pattern
Description
customer+disputed-return@email.**
Creates a dispute on each capture of the order with the reason return and one open dispute request
customer+disputed-goods_not_received@email.**
Creates a dispute on each capture of the order with the reason goods not received and one open dispute request
customer+disputed-already_paid@email.**
Creates a dispute on each capture of the order with the reason already paid and one open dispute request
customer+disputed-faulty_goods@email.**
Creates a dispute on each capture of the order with the reason faulty goods and one open dispute request
customer+disputed-incorrect_invoice@email.**
Creates a dispute on each capture of the order with the reason incorrect invoice and one open dispute request
customer+disputed-high_risk_order@email.**
Creates a high-risk order (formerly known as stop request) on order level.
customer+disputed-unauthorized_purchase@email.**
Creates a dispute on each capture of the order with the reason unauthorized_purchase and one open dispute request
As we're constantly improving the testing experience, you may not able to test the denied payment flow in some markets, for example, Sweden and Norway. Please contact Klarna merchant support for more information.
The sample customer data lets you test the basic approve and deny transaction flows. However, you can also test some other Payments and Checkout scenarios by adding suffixes to sample usernames.
In the examples below, the email address reflects sample customer data for the United States. Make sure to adjust the address to match the country in which your store operates.
To launch a Payments widget, include a sample email address in your API call. You can modify the address to display the sign-up widget or delay the payment.
To launch a Checkout widget, include a sample email address in your API call.
{status} is the expected status after the time delay, either accept to accept a payment or reject to reject a payment.
{time delay} is the time delay, in minutes, before the decision is made and the status is confirmed. The value must be a two-digit number in the range of 00–99. Note: Only works for US and UK.