For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overcapture

Capture amounts greater than the originally authorized amount in manual capture payments

Overview

In card payments, Over Capture occurs when a merchant captures (settles) an amount greater than the originally authorized amount.

This is particularly useful in scenarios such as:

  • Additional charges (e.g., shipping, handling, gratuities).

  • Price adjustments made after initial authorization.

  • Reducing the risk of under-capturing when final order values differ.

Enabling Over Capture

1. Profile-level Configuration (via Dashboard)

  • Navigate to: Developer → Payment Settings → Always Enable Over Capture

  • Toggle Enable/Disable as required.

2. Per-request Configuration (via API)

Use the boolean field enable_overcapture in your payment request.

This can be passed in:

POST /payments

POST /payments/:id/update


Example: API Request

Example: API Response

Field Semantics

enable_overcapture Indicates merchant intent.

Value
Meaning

true

Over-capture requested

false

Over-capture not requested


is_overcapture_enabled Indicates connector capability acceptance.

Value
Meaning

true

Connector supports and enabled over-capture

false

Connector does not support over-capture


Monitoring & Settlement

  • After authorization, merchants can view the amount_capturable field (under More Payment Details) to see the maximum amount that can be captured.

  • Once the payment is captured (or overcaptured), the final amount will be reflected in the amount_received field.

Merchant Action

  • Use Dashboard settings for global enablement

  • Use API overrides for payment-specific enablement

  • Monitor capturable and received amounts to track final settlements

Last updated

Was this helpful?