J.P.Morgan

Integration checklist

Guidance on enabling Klarna using J.P. Morgan Payments APIs and the different integration path available: Online Payments or Checkout (Hosted Payment Page or Drop-in Component).

Integration Checklist

To ensure a robust, seamless, and customer-friendly Klarna integration through J.P. Morgan Payments, it is essential to follow a set of best practices. This checklist will help you finalize your Klarna setup using J.P. Morgan Payments APIs and prepare for go-live with full functionality and compliance.

Set up branding in the Klarna Partner Portal

Upload your logo and brand name - ensure the assets meet Klarna’s format and resolution requirements.

  • Benefit: Klarna will reflect your brand across touchpoints with the consumer, improving recognition and trust.

Include line items in the payload

Add all available order details to the line items in your API requests to J.P. Morgan Payments.

For Online Payments API include retailAddenda.level3.lineItems. See documentation.

For Checkout API include cart.lineItems. See documentation.

  • Benefit: Enables enhanced fraud detection, enriched post purchase experience with detailed receipts.

Share the customer facing reference

Ensure consistency across your systems and communications with customer by sharing your customer-facing order ID.

For Online Payments API include merchantOrderNumber. See documentation.

For Checkout API include purchaseOrderNumber. See documentation.

  • Benefit: The information is displayed across all touch points between the customer and Klarna, including Klarna app and emails. It is also a key data point to support your reconciliation process and dispute management.

Forward the interoperability token

In an advanced integration, you will receive an interoperability_token from Klarna when the customer interacts with services powered by WebSDK, such as Klarna On-site Messaging, Sign in with Klarna, or Express Checkout.

If interoperability_token is available, include it in your API requests to J.P. Morgan Payments. This should be included as follows:

JSON
{
    "paymentMetadataList": [
        {
    "metadataAttribute"="Interoperability-Token",
    "metadataAttributeValue"="<actual token>"
        }
        ]
}
  • Benefit: Links customer context across touch points for a smoother experience.