This guide details the crucial final authorization step in Klarna payment integration, focusing on transaction creation with a payment_token. Essential for completing purchases and handling transactions effectively.
{{#lst:Final authorization|Integration overview 1}}
This step is required only if the purchase was part of the payment authorization process. You can ignore this step for pure tokenization flows.
Final authorization functions the same across all integration methods. If it has already been implemented—for example, with a server-only integration for one-time payments—it can be reused without modification.
The acquiring partner must use the klarna_network_session_token to perform a second call to Klarna's Payment Authorize API
/v2/accounts/{partner_account_id}/payment/authorize| Parameter | Required | Description |
|---|---|---|
partner_account_id | Yes | Unique account identifier assigned by Klarna to the onboarded merchant |
The klarna_network_session_token must be passed in the Klarna-Network-Session-Token HTTP header​.
curl https://api-global.test.klarna.com/v2/accounts/{partner_account_id}/payment/authorize \
-H 'Authorization: Basic <API key>' \
-H 'Content-Type: application/json' \
-H 'Klarna-Network-Session-Token: krn:payment:eu1:klarna-network-session-token:...' \
-d '{
"currency": "USD",
"request_payment_transaction": {
"amount": 11800,
"payment_transaction_reference": "acquiring-partner-transaction-reference-1234"
}
}'
Upon successful authorization, the response body includes the payment_transaction_id, which you'll use for payment transaction management actions​.
/v2/accounts/{partner_account_id}/payment/authorize| Parameter | Required | Description |
|---|
{
"payment_transaction_response": {
"result": "APPROVED",
"payment_transaction": {
"payment_transaction_id": "krn:payment:eu1:transaction:6debe89e-98c0-[...]",
"payment_transaction_reference": "acquiring-partner-transaction-reference-1234",
"amount": 11800,
"currency": "USD",
"payment_funding": {...},
"payment_pricing": {...},
"expires_at": "2025-10-30T19:26:02.772Z"
}