Overcapture
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 flag can be set in the following API calls:
/payments/create with
confirm = false/payments/update
/payments/create call with
confirm = true
⚠️ Note:
The request-level
enable_overcapturewill override the profile-level setting.Over Capture is only applicable for manual capture payments i.e.
capture_method = manual.
Example: API Request
Example: API Response
enable_overcapturetrue→ Overcapture was requested for this payment.false→ Overcapture was not requested.
is_overcapture_enabledtrue→ Connector enabled Overcapture for this payment.false→ Overcapture is not applicable for this PSP/payment.
Monitoring & Settlement
After authorization, merchants can view the
amount_capturablefield (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_receivedfield.
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?

