Update an existing checkout session’s contract, customer details, expiration, currency, redirect URLs, attribution, or custom data.
Common use cases:
Rules and validations:
System behavior:
Related endpoints:
Documentation Index
Fetch the complete documentation index at: https://docs2.zenskar.com/llms.txt
Use this file to discover all available pages before exploring further.
Schema for updating an existing checkout session
This schema defines the fields that can be updated on an existing checkout session. Only open sessions with no payment activity can be updated.
Contract data for checkout session. Updating this will recalculate estimates.
{
"currency": "USD",
"is_plan_based": true,
"plan_id": "123e4567-e89b-12d3-a456-426614174000",
"start_date": "2023-01-01T00:00:00"
}Customer snapshot for guest checkout or to override existing customer details. Cannot change customer_id, only customer details.
When this checkout session expires. Format: ISO 8601 datetime.
Display currency for the checkout session. Must be a valid ISO 4217 currency code (e.g., 'USD', 'EUR'). If provided with contract, must match the contract currency.
URL to redirect customers after successful checkout. Must be a valid, fully-qualified URL.
1 - 2083URL to redirect customers after cancellation. Must be a valid, fully-qualified URL.
1 - 2083URL to redirect customers when payment is pending. Must be a valid, fully-qualified URL.
1 - 2083UTM and attribution data for marketing tracking. Helps track the source of the checkout session.
Arbitrary key-value storage for additional data. Can be used to store metadata or integration-specific information.
Reason for updating the checkout session. Useful for audit and tracking purposes.
customer_request, admin_correction, price_update, contract_update, error_correction, other Optional note explaining the reason for the update in more detail.
500Checkout session successfully updated
Schema for checkout session response
This schema defines the response format for checkout session operations, including all session details, status information, and associated data.
Unique identifier for the checkout session
Current status of the checkout session (open, processing, completed, closed, cancelled)
open, processing, completed, closed, cancelled Current status of the payment (not_started, pending, paid, failed, no_payment_required)
not_started, pending, paid, failed, no_payment_required Contract data associated with this checkout session
Indicates if this was a guest checkout flow
ID of the associated contract, if one has been created
ID of the execution process for this checkout session
Timestamp when the checkout session was confirmed
Timestamp when the payment was received
External payment intent ID from the payment provider
Calculated price estimates for the contract as EstimationResponseSchema (estimation_id, current_invoice, future_invoices, amount_due, credit_notes)
ID of the customer associated with this checkout session
ID of the business entity associated with this checkout session
Customer data snapshot at the time of checkout
Timestamp when this checkout session expires
Timestamp of the last activity on this checkout session
Timestamp when the checkout session was completed
Idempotency key used when creating this checkout session
Correlation ID for cross-service tracking
Display currency for the checkout session
URL to redirect customers after successful checkout
URL to redirect customers after cancellation
URL to redirect customers when payment is pending
UTM and attribution data for marketing tracking
Arbitrary key-value storage for additional data