Skip to main content
POST
/
v2
/
order
/
{order_uuid}
/
upcharge
Upcharge amount by order
curl --request POST \
  --url https://sandbox.gateway.sezzle.com/v2/order/{order_uuid}/upcharge \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "intent": "AUTH",
  "upcharge_amount": {
    "amount_in_cents": 5000,
    "currency": "USD"
  }
}
'
{
  "uuid": "6c9db5d4-d09a-4224-860a-b5438ac32ca8"
}

Documentation Index

Fetch the complete documentation index at: https://docs.sezzle.com/llms.txt

Use this file to discover all available pages before exploring further.

This API is in development and not yet available for production use. Details on this page are subject to change.

​
Overview

The upcharge endpoint allows you to charge an additional amount on an existing authorized order. This is useful when the final order total exceeds the originally authorized amount (e.g., due to weight-based pricing adjustments, added services, or shipping cost changes).

​
Key behavior

  • A new, separate order is created for the upcharge amount only. The original order is not released or modified.
  • The upcharge amount is charged to the shopper as a single payment (Pay In Full).
  • The cumulative total of all upcharges on a given order must not exceed 15% of the original authorized amount.
  • The upcharge currency must match the original order’s currency.
  • The returned UUID is the new upcharge order’s UUID and can be used with other Order API endpoints (e.g., capture, refund).
  • The two orders remain associated — you can query the relationship via the Get Order endpoint:
    • On the upcharge order, the response includes is_upcharge: true and parent_order_uuid referencing the original order.
    • On the original order, the response includes an upcharges array listing each upcharge order’s UUID and amount.

​
Validation requirements

  • The original order must have an approved authorization.
  • intent must be either AUTH or CAPTURE.
  • upcharge_amount must include a valid amount_in_cents and currency.

​
Example

For an original order of 100.00 USD:
  • Maximum cumulative upcharge allowed: 15.00 USD (15% of 100.00)
  • A single upcharge of 10.00 succeeds, leaving 5.00 of remaining upcharge capacity.
  • A subsequent upcharge of 6.00 would be rejected (cumulative 16.00 exceeds the 15% limit).

Authorizations

​
Authorization
string
header
required

The authentication token generated from providing API Keys to Sezzle Gateway

Headers

​
Sezzle-Request-Id
string

Unique client-generated ID to enforce idempotency

Path Parameters

​
order_uuid
string
required

The Order UUID to upcharge (order.uuid from session response)

Body

application/json
​
intent
enum<string>
required

If your checkout flow requires the user to confirm their checkout on your site after being approved by Sezzle, use AUTH as your intent. If you prefer the checkout be captured immediately, use CAPTURE. Submit a capture request via the API or your Merchant Dashboard before the authorization expires. The authorization expiration window can be set from 30 minutes up to 7 days in your Merchant Dashboard Settings.

Available options:
AUTH,
CAPTURE
​
upcharge_amount
object
required

The amount to upcharge. The cumulative total of all upcharges on a given order must not exceed 15% of the original order amount. Currency must match the original order.

Response

Successful Operation

​
uuid
string

The UUID of the new upcharge order. This UUID can be used with other Order API endpoints (e.g., capture, refund).