Payments on restricted businesses
Submit the supplementary purchase data Klarna requires for restricted business categories. Specific Merchant Category Codes (MCCs) trigger additional reservation or seller details that must be present on both the Payment Request and the authorize call.
3 min read
Overview
Some business categories (defined by their Merchant Category Code, or MCC) are subject to additional regulatory and compliance requirements. When the Partner's account is configured with one of these MCCs, extra fields must be included inside 
and authorizePayment so Klarna can underwrite, authorize, and report on the transaction in compliance with applicable rules.
supplementary_ on both createPaymentRequest and authorizePayment so Klarna can underwrite, authorize, and report on the transaction in compliance with applicable rules.This page lists the MCCs in scope and the data points Klarna expects for each category. The Partner's checkout, backend, or order management system must be able to populate these fields whenever a transaction falls under one of these categories.
MCC assignment at onboarding
The assigned MCC is set during Klarna onboarding and reflects the goods or services the Partner sells. When operating across multiple categories or unsure which MCC applies to the account, contact Klarna Support. For all supported MCCs, refer to the full list of merchant category codes.
Required supplementary data per MCC
The table below lists the MCCs that require additional
supplementary_ fields and which fields to provide.| Goods and Services | MCCs | Required supplementary_ fields |
|---|---|---|
| Airlines (card network classification) | 3000–3308, 4511 | travel_ |
| Automobile/vehicle rentals (card network classification) | 3351–3441 | travel_ |
| Hotels and motels (card network classification) | 3500–3999 | lodging_ |
| Steamships and cruise lines | 4411, 4457 | travel_ |
| Airlines and air carriers (not elsewhere classified) | 3000–3308, 4511, 4722, 5962 | travel_ |
| Transportation services | 4789 | travel_ |
| Marketplaces | 5262 | marketplace_ |
| Lodging (hotels, motels, and resorts) | 7011, 4722, 5962 | lodging_ |
| Timeshares | 7012 | lodging_ |
| Automobile rentals | 7512 | travel_ |
| Travel agencies and tour operators | 4722, 4723 | travel_, event_ |
| Truck and utility trailer rentals | 7513 | travel_ |
| Theatrical producers (excluding motion pictures) and ticket agencies | 7922 | event_ |
| Bands, orchestras, and miscellaneous entertainers (not elsewhere classified) | 7929 | event_ |
| Amusement parks, circuses, carnivals, and fortune tellers | 7996 | event_ |
| Aquariums, seaquariums, zoos, and dolphinariums | 7998 | event_ |
Integration requirement
When the required fields for the Partner's MCC are missing or malformed, the authorization may be declined or settlement and reporting may be blocked downstream. Validate that both the
createPaymentRequest and authorizePayment requests carry the correct supplementary_ block for every Payment Transaction in scope, and keep the values consistent across the two calls.How to include the data
Add the relevant block to
supplementary_ in the request body of:- createPaymentRequest: so Klarna has the context it needs for risk evaluation and to render the Klarna Purchase Journey correctly.
- authorizePayment: so the resulting Payment Transaction is created with the data needed for authorization, settlement, and reporting.
The schemas of
travel_, lodging_, event_, and marketplace_ are documented in the API reference for each operation. Use the same values on both calls. Significant discrepancies between the Payment Request and the authorize call can cause Klarna to require re-confirmation or to decline the authorization.For general guidance on
supplementary_ (including line items, customer, and shipping) see Supplementary purchase data.Related articles
Jump to section...