Klarna is a "Buy Now, Pay Later" payment method allowing your customer to pay in installments.
Make yourself familiar with our API principles to ensure a resilient integration.
Product overview
Klarna allows your customer to:
- defer payment by 30 days
- spread the cost over a period of up to 36 months (with financing)
- pay the full amount immediately with "Pay Now" for card, local domestic or local bank transfer payments
- spread the cost over three (four in some markets) equal interest-free installments
Klarna manages the relationship and collection of future installment payments directly with your customer. You receive full funding upfront and are protected from the risk of unpaid installments.
For recurring integrations, please see Klarna (recurring).
Follow the link for the latest guidelines from Klarna.
| Payment type | Countries | Recurring | Reversals | Partial reversals | Disputes | Auth only | Auth and settlement (sale) |
|---|---|---|---|---|---|---|---|
| Pay Now, Pay in Parts, Pay Later, Financing | CH, CZ, DK, AT, BE, FI, FR, DE, GR, IE, IT, NL, PT, SK, ES, GB, NO, PL, AU, CA, HU, MX, NZ, RO, SE, US | ❌ |
|
| Handled directly via Klarna. We deduct the funds if the dispute is lost. | ✅ | ✅ |
Klarna sets transaction limits, which are regularly updated and dependent upon the merchant, payment option, and your customer's purchase history.
As a general guideline, limits typically range from 0,00 EUR to 10.000,00 EUR.
Refunds are completed through Klarna, arriving in your customer's account within 365 days. You can submit multiple partial refunds for one payment.
| Currency | Currency codes |
|---|---|
| Czech Koruna | CZK |
| Danish Krone | DKK |
| Euro | EUR |
| Norwegian Krone | NOK |
| Polish Złoty | PLN |
| Pound Sterling | GBP |
| Swedish Krona | SEK |
| Swiss Franc | CHF |
The simplest integration option.
Your customer is redirected from your site to Klarna’s hosted payment page to complete their payment.
You create a Klarna order using our APMs API, which returns a URL for the Klarna payment page that you redirect your customer to. After the transaction is completed, your customer is automatically redirected back to your site. You receive the payment confirmation asynchronously from us.
On completion of the payment journey, your customer receives a payment receipt from Klarna.

- Your customer chooses Klarna as their payment method.
- They log into Klarna (or create an account).
- Your customer chooses how they would like to pay (options differ per market).
- They set their funding source.
- Your customer confirms the payment.
- Klarna confirms that the payment is successful and returns your customer to your checkout confirmation page.
Requires additional development effort but provides an optimized customer experience, as the entire payment process takes place within your site using Klarna’s Web SDK.
With this fully integrated checkout flow, you can dynamically display Klarna’s branding, payment descriptors, and personalized messaging on your checkout pages.
You can present the Klarna payment page in a pop-up box over your website, allowing your customer to complete payment without a full-page redirect (although this is still possible if you wish).
Klarna provides two options for integration:
Option 1: Klarna Web SDK + our APMs API
You embed Klarna’s Web SDK directly into your checkout page. You create the request with our APMs API and the response is used to initialize the Klarna SDK, which then displays the payment interface on your site. You receive the payment confirmation asynchronously from us.Option 2: Klarna Web SDK + Klarna API/webhooks + our APMs API
You embed Klarna’s Web SDK in your checkout page and integrate with Klarna’s API and webhooks. You create and manage the Klarna session directly with Klarna through server-side calls. As a final step, you provide the “Klarna Network Session Token” as theproviderTokento the APMs API to complete the payment.

- Your customer reviews all available payment methods on your checkout page. Klarna is presented with dynamic text.
- They select Klarna and are presented with an illustration of a possible split. The Pay button is dynamically updated to “Pay with Klarna”.
- Your customer logs into Klarna (or creates an account). They choose how they would like to pay (options differ per market).
- Your customer sets their funding source.
- They confirm the payment.
- Klarna confirms that the payment is successful and returns your customer to your checkout confirmation page.
Depending on your business type or the goods you sell, you may need to provide additional transaction details, such as order line items, subscription information, or mandatory industry-specific attributes.
Providing “supplementary purchase data” with Klarna offers greater context for each transaction, increasing their underwriting accuracy and strengthening their fraud assessment. The more information you share, the better your customers' experience and the greater the chances of increased acceptance rates and enhanced fraud prevention.
You have the option to provide supplementary purchase data in two formats:
- Option 1: You can pass specific data fields individually as structured elements within the payment request.
- Option 2: Klarna data - You can include all necessary information encapsulated as a JSON string within the
passthroughDatafield, using Klarna’s “Klarna Network Data for Acquiring Partners" schema.
You can also combine the two options, e.g. sending “line items” as structured data while using “Klarna network data” for specific details like event information.
You can see examples of the types of industry-specific transaction details that we support below. The "Guest" example demonstrates option 1, while the industry-specific examples demonstrate the use of Klarna data outlined in option 2.
Please note that if the same object is provided in both formats, Klarna prioritizes using “Klarna network data” for risk assessment purposes, while the structured “line items” are displayed to your customer during the Klarna purchase flow.
Use our API reference and set your headers.
POST https://try.access.worldpay.com/apmPayments
- Test (Try)https://try.access.worldpay.com/apmPayments
- Livehttps://access.worldpay.com/apmPayments
- Payload
- curl
- Python
- Java
- Node.js
- Go
- PHP
- Ruby
- C#
{ "transactionReference": "Memory265-13/08/1876", "orderReference": "apm-order-12345", "merchant": { "entity": "default" }, "instruction": { "method": "klarna_network", "value": { "amount": 2110, "currency": "GBP" }, "narrative": { "line1": "MindPalace" }, "providerToken": "krn:network:eu1:live:session-token:eyJhbGciOiJFUzI1NiIsImtpZCI6ImNkYzM2MDFhLTBlODQtNDdjZi05ZGMwLWJjNzAxZjNkNDE2OCJ9.ewogICJwYXltZW50X3JlcXVlc3RzIiA6IFsgewogICAgImlkIiA6ICJrcm46cGF5bWVudDpldTE6cmVxdWVzdDo1MGI3NDhkZS05ZDIwLTljZWEtODVhMi1hNjZiNzFhY2JiMDMiLAogICAgInN0YXRlIiA6ICJDT01QTEVURUQiLAogICAgImFtb3VudCIgOiAxNTAwLAogICAgImN1cnJlbmN5IiA6ICJFVVIiLAogICAgImxhc3RfbW9kaWZpZWRfYXQiIDogIjIwMjYtMDQtMTNUMDc6NDk6MTYuNDYxMDQ1NTcxWiIKICB9IF0sCiAgImV4cCIgOiAxNzc2MDcwMTg2Cn0.q1xa-C_yToTpsaHyxBNfg0acp0zg6w_zpMiJOeVC3xnomwVA3SFtF0Y8Pw9J6mEBVUCOeEOh7674IzoBIvtbjQ", "paymentInstrument": { "type": "direct", "country": "GB", "billingAddress": { "firstName": "James", "lastName": "Moriarty", "phone": "00000000000", "address1": "Marylebone", "address2": "Westminster", "postalCode": "NW1 6XE", "city": "London", "state": "Greater London", "countryCode": "GB" } }, "settlement": { "auto": true }, "resultUrls": { "cancel": "https://worldpay.com/cancel", "failure": "https://worldpay.com/failure", "pending": "https://worldpay.com/pending", "success": "https://worldpay.com/success" }, "shipping": { "method": "physicalToDoor", "timeFrame": "express", "courier": { "name": "DHL", "preference": "leaveAtDoor", "signature": true, "tracked": true, "identification": true }, "firstName": "Mike", "lastName": "Shipping", "phone": "0123456789", "email": "mike.shipping@email.com", "address": { "address1": "Worldpay", "address2": "270-289 The Science Park", "postalCode": "CB4 0WE", "city": "Cambridgeshire", "state": "Cambridgeshire", "countryCode": "GB" } }, "order": { "items": [ { "productCode": "DH12-HK", "name": "Panaphonics DH12-HK & Accessories", "quantity": 1, "unitCost": 12000, "totalTaxAmount": 12000, "totalAmount": 2000, "productUrl": "http://www.merchanturl.com/products/f2ytrdmn", "imageUrl": "http://www.merchanturl.com/products/f2ytrdmn_small.jpg" }, { "productCode": "PPSD256", "name": "Panaphonics SD Card 256GB", "quantity": 2, "unitCost": 2400, "totalTaxAmount": 800, "totalAmount": 4800, "productUrl": "http://www.merchanturl.com/products/f2a8d7e34", "imageUrl": "http://www.merchanturl.com/products/f2a8d7e34_small.jpg" } ] } } }
For Bizum transaction please follow this extra regex [a-zA-Z0-9]{4,12}
A reference that you can apply to one or more payments according to your business needs. You may reuse the same reference across multiple payments, for example where:
- the total amount for a single order is split across multiple payments
- you use a single reference for each payment in a recurring agreement or split shipment scenario
Used to route the request in Access Worldpay, created as part of on-boarding.
Object that contains the payment type and details.
Type of payment method
- ach
- alipay_cn
- alipay_hk
- alipay_uni
- bancomat
- bancontact
- bizum
- blik
- eft
- euteller
- ideal
- klarna
- klarna_recurring
- konbini
- multibanco
- mybank
- open_banking
- paypal
- paysafecard
- pix
- przelewy
- safetypay
- sepa
- swish
- trustly
- wechatpay
The value of the payment.
The amount in the lowest denomination of the currency e.g. pennies for GBP, cents for USD.
The supported ISO 4217 currency codes.
The description shown on your customer's bank statement for the payment.
The type of instrument.
URL of the session in which customer fields can be saved via Components SDK.
Note: This field is required when making requests where the type is checkout.
Account type.
Account number of direct debit account.
Routing number of direct debit account.
Check number of the direct debit account.
Company name if a corporate account.
City.
The supported ISO 3166-1 alpha-2 country codes.
Postal code.
State code of the billing address in ISO 3166-2 format.
Your customer's first name.
Your customer's last name.
Your unique reference for the customer so that the 'pay faster next time' function can be used during checkout. This allows your customer's chosen bank to be stored for their next payment.
The customer's e-mail address.
We suggest you provide the cancelURL,failureURL, pendingURL and successURL attribute to redirect your customer to, once you have received the payment result.
{
"paymentInstrument": {
"method": "klarna_network",
"type": "direct"
},
"paymentId": "eyJrIjoiYXBtLXNlcnZpY2UtZGVmYXVsdCIsImxpbmtWZXJzaW9uIjoiNi4wLjAifQ==.BnnxxcMle38OazhwbF8J+4rtJi8CAq:Y3zUOn1dw6VWfvx:PHL5L0S+5ara5vz6ouV5yBmVUQCiSwQjs+1x5qJIJxAKWMWc2Mlb1doricEYlzsZIRIGCflvnYu1Ns8g1S0+66n6wCELiB9OHfX7cdCRSkT0a4UjAkBr16y36rhHD8i3MfeowBaRA60gR5WdTem66NOYspir3PJsMwGsI7JUSNUzNfcyYf:9A8ONjOcqG6UxedN+MVzWk3lOYs4HS580KRMMNREpmBeBMSEX5ykio0WGxZ:7eYQxnPFsTnA:7:SEfTDcAZofBDiAWAe+s8H9:TD3hQpRcoIM3I9mxkgdPhXDL2OFpFf7pNzE4GPA9QEPQrIYQg:q3eZ7ziTPGD:iOAJXRIEuMq+GdkYs3SWlTzbiGM76:BcqQDY0BAUI9GaFhKLR:b0g9SIKK71Rk9YpTLeiVSfZMnt+9116oW2VHgWW6AoAt202XuJ0AU7aToTM6HDqlAkiOs66Po3TBIlIqmMW0DQb44taw0DeEnQ==",
"lastEvent": "pending",
"_links": {
"self": {
"href": "https://try.access.worldpay.com/apmPayments/eyJrIjoiYXBtLXNlcnZpY2UtZGVmYXVsdCIsImxpbmtWZXJzaW9uIjoiNi4wLjAifQ==.BnnxxcMle38OazhwbF8J+4rtJi8CAq:Y3zUOn1dw6VWfvx:PHL5L0S+5ara5vz6ouV5yBmVUQCiSwQjs+1x5qJIJxAKWMWc2Mlb1doricEYlzsZIRIGCflvnYu1Ns8g1S0+66n6wCELiB9OHfX7cdCRSkT0a4UjAkBr16y36rhHD8i3MfeowBaRA60gR5WdTem66NOYspir3PJsMwGsI7JUSNUzNfcyYf:9A8ONjOcqG6UxedN+MVzWk3lOYs4HS580KRMMNREpmBeBMSEX5ykio0WGxZ:7eYQxnPFsTnA:7:SEfTDcAZofBDiAWAe+s8H9:TD3hQpRcoIM3I9mxkgdPhXDL2OFpFf7pNzE4GPA9QEPQrIYQg:q3eZ7ziTPGD:iOAJXRIEuMq+GdkYs3SWlTzbiGM76:BcqQDY0BAUI9GaFhKLR:b0g9SIKK71Rk9YpTLeiVSfZMnt+9116oW2VHgWW6AoAt202XuJ0AU7aToTM6HDqlAkiOs66Po3TBIlIqmMW0DQb44taw0DeEnQ=="
}
},
"_actions": {},
"redirect": "https://secure-test.worldpay.com/jsp/test/shopper/APMSTSimulator.jsp?customerRef=3501456267&paymentMethod=KLARNA_NETWORK",
"commandId": "cmdF3buj-w58hiyu4I-QZqZi0"
}The identifier of the payment resource.
Links to resources related to the request.
The URL to redirect your customer to, or a QR code in Base64 to show to your customer, in order to complete the transaction.
An action ID generated by us identifying a single merchant interaction
For Pix payments - display to your customer for them to copy and paste in the Pix app.
For Swish payments - use this value and add in the custom URL scheme: swish://paymentrequest?token={token}&callbackurl={callbackURL} as the token value. This will prompt the app to open where the customer can complete their payment.
Check out our API reference for more responses or error codes.
To simulate payment outcomes and trigger webhooks in our Try environment you can send a request prompting our simulator.
You receive a redirect link to our simulator where you can choose different payment outcomes:
| Simulator outcome option | Payment status | Description |
|---|---|---|
| Authorised | authorized | Payment authorized successfully. |
| Refused | refused | Unsuccessful payment - failure response from the provider. |
| Error | error | Error in processing the payment or the session timed out. |
| Shopper Cancelled | cancelled | Your customer cancelled the transaction. |
You can also send requests to settlement or reversal endpoints to test the following statuses:
sentForSettlementsentForRefund
Next steps