Search...
Log inGet started
Airwallex logo
Home
Core API
Payments
Transactional FX
Payouts
Issuing
Back to home
OverviewChoose your payments solutionGet started with payments
Supported currencies
Online payments
Invoice integrations
Payment methods
Payment Methods OverviewGlobal
CardsAirwallex Pay
Apple Pay
Google Pay™
Klarna
Desktop/Mobile Website Browser - KlarnaRecurring Payments - KlarnaExtra Merchant Data (EMD) - Klarna
Afterpay / Clearpay
PayPal
Skrill
EU & UK
APAC
NORTH AMERICA & LATAM

Extra Merchant Data (EMD) - Klarna

Klarna requires additional information regarding the customer and the purchase in order to make a correct risk assessment for certain businesses, including Intangible Goods, Online Education, and Marketplace. You can see additional details via Klarna's guide here . This information, called ‘Extra Merchant Data’ (EMD), may consist of data about the customer performing the transaction, the product/services associated with the transaction, or the seller and their affiliates. Klarna’s requirements are documented here.

If your businesses are in the relevant verticals, we typically require an EMD package for your integration and approval from Klarna before go-live. Please contact your Account Manager for EMD integration details.

Intangible Goods and Online Education

  • Required EMD:
    • customer.merchant_customer_id and customer.additional_info
    • order.product.effective_start_at and order.product.effective_end_at
    • For intangible goods merchants, the seller.name is required
  • Sample request body for creating payment intent:
JSON

Marketplace

  • Required EMD:
    • customer.merchant_customer_id and customer.additional_info
    • order.sellers and the seller information provided in order.sellers should match with order.products.seller
  • Sample request body for creating payment intent:
JSON

Airlines

  • Required EMD:
    • customer
    • order.itineraries and order.travelers. Note that all the traveler’s identifiers provided in order.itineraries should match with order.travelers.
  • Sample request body for creating payment intent:
JSON