Guidance on enabling Klarna using Cybersource and the different integration path available: Server-side Cybersource APIs or Cybersource Unified Checkout.
To ensure a robust, seamless, and customer-friendly Klarna integration through Cybersource, it is essential to follow a set of best practices. This checklist will help you finalize your Klarna setup using Cybersource APIs and prepare for go-live with full functionality and compliance.
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.
In an advanced integration, you will receive a klarna_network_session_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 a klarna_network_session_token is available, include it in your authorization request to Cybersource as processorInformation.authApprovalToken when calling the Payments API.