_id
. IDs are used to uniquely identify resources or entities within Klarna's systems._reference
. References are used to link Klarna's systems with the partner's systems, allowing for seamless integration and tracking (1)._id
._reference
.This distinction ensures clarity and proper mapping between Klarna's and the partner's systems, facilitating smooth integration and operations.
To ensure accurate correlation, reconciliation, and customer experience, Klarna supports the use of multiple reference types in its APIs. As an Acquiring Partner, correctly handling and mapping these references is essential for integrating with Klarna Payments and ensuring visibility across systems for you, your subpartners, and end-customers.
Klarna provides the following Partner References
Reference Type | Purpose | How to Provide |
payment_request_reference | Reference to the payment session or equivalent on your side | Include in the payment_request_reference field when creating a payment request. API ReferenceAPI |
payment_transaction_reference | Reference to the payment resource or transaction on your side | Include in the payment_transaction_reference when capturing or authorizing the transaction API ReferenceAPI |
purchase_reference | Customer-facing order number, generated by the subpartner | Include in the purchase_reference field as part of supplementary_purchase_data when creating a payment request. API ReferenceAPI |
session_reference | Long-lived integration/session identifier used for internal tracing | Include in the Klarna-Integration-Metadata header as part of the request metadata API ReferenceAPI |
Partner-Correlation-Id | An optional identifier that the partner can use to correlate and to use for troubleshooting. This value will be returned in the response. | Include in the Partner-Correlation-Id header as part of the request API ReferenceAPI |