Update a Payment Request
Learn how to update an existing payment request while it's in the SUBMITTED state. This operation allows you to modify payment details, supplementary purchase data, or customer interaction configuration before the customer enters the Klarna Purchase Journey.
Introduction
Update an existing Payment Request while it's still in the
SUBMITTED state. This operation allows you to modify payment details, supplementary purchase data, or customer interaction configuration before the customer enters the Klarna Purchase Journey.Prerequisites
Before updating a Payment Request, ensure the following:
- A valid Partner Account with API credentials
- Backend capability to receive and process Klarna webhooks
- An existing Payment Request in
SUBMITTEDstate - The
payment_request_idof the Payment Request to update
Request
Call updatePaymentRequest
with the
with the payment_request_id and provide the fields you want to update.Sample request
SHELL
1
2
3
4
5
6
7
8
9
10
curl -X PUT https://api-global.test.klarna.com/v2/accounts/{partner_account_id}/payment/requests/{payment_request_id} \
-H 'Authorization: Basic <API key>' \
-H 'Content-Type: application/json' \
-d '{
"amount": 12500,
"supplementary_purchase_data": {
"line_items": [
{
"name": "Updated Product Name",
"quantity": 2,Response
The API returns the updated Payment Request with the same structure as returned by authorizePayment when a step up is triggered, reflecting the changes made.
when a step up is triggered, reflecting the changes made.Sample response
JSON
1
2
3
4
5
6
7
8
9
10
{
"payment_request_id": "krn:payment:eu1:request:10be1d49-7beb-6b24-b9dd-8c14d0528503",
"state": "SUBMITTED",
"state_context": {
"customer_interaction": {
"method": "HANDOVER",
"payment_request_id": "krn:payment:eu1:request:10be1d49-7beb-6b24-b9dd-8c14d0528503",
"payment_request_url": "https://pay.klarna.com/l/ZjW2Xipgh0tjbrBGD7hzJM"
}
},Webhook
Subscribe to the
payment.request.updated webhook event using the guidelines provided here. Klarna sends this event when a Payment Request is successfully updated.Sample payload
JSON
1
2
3
4
5
6
7
8
9
10
{
"metadata": {
"event_type": "payment.request.updated",
"event_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"event_version": "v2",
"occurred_at": "2025-02-24T17:30:00Z",
"correlation_id": "3e2668f9-28d4-577d-a35d-c0b4f02d3b13",
"subject_account_id": "krn:partner:global:account:live:HGBY07TR",
"recipient_account_id": "krn:partner:global:account:live:LWT2XJSE",
"product_instance_id": "krn:partner:product:payment:ad71bc48-8a07-4919-[...]",Use cases
Update Payment Requests before customer interaction begins to handle common checkout scenarios such as cart changes, promotions, or configuration updates.
Update payment amount
Update the amount when cart contents change or promotions are applied.
JSON
1
2
3
4
5
{
"amount": 15000,
"currency": "USD"
}
Update line items
Modify line items to reflect changes in the shopping cart.
JSON
1
2
3
4
5
6
7
8
9
10
{
"amount": 15000,
"supplementary_purchase_data": {
"line_items": [
{
"name": "Premium Product Bundle",
"quantity": 1,
"total_amount": 15000
}
]Update customer interaction configuration
Change return URLs or interaction method before the customer enters the purchase flow.
JSON
1
2
3
4
5
6
7
8
{
"customer_interaction_config": {
"method": "HANDOVER",
"return_url": "https://example.com/new-return-url",
"app_return_url": "merchantapp://new-callback"
}
}
Update Payment Request expiry
Extend or shorten the Payment Request lifetime by updating
customer_interaction_config.interaction_expiry. Use this to align the expiration with a changed Partner checkout session timeout — for example, when a flash-sale window is extended or a hard deadline is brought forward. See Custom Payment Request expiry for accepted formats and constraints.JSON
1
2
3
4
5
6
7
8
9
{
"customer_interaction_config": {
"method": "HANDOVER",
"interaction_expiry": {
"duration": "PT1H"
}
}
}
Related articles
API & SDK references