web
You’re offline. This is a read only version of the page.
close

What can we help you with?


000001621


112

04/16/2026 14:08 PM

2.0

Introduction

This article explains the maximum timeframes for capturing payment authorizations within the Cybersource platform and provides best practice guidance to help you minimize interchange costs, avoid declined or expired authorizations, and maintain compliance with your Merchant Service Provider (MSP), acquirer, or processor requirements.

Interchange is the default transfer price between issuing and acquiring banks, applied on each transaction. It is bi-directional, flowing from acquirers to issuers on payment transactions and reversed on credits, chargebacks, and ATM (Automated Teller Machine) transactions. The amount of the interchange fee is determined by card associations through a pricing mechanism set in response to market forces. The size of the interchange fee often varies based on transaction type and the order data passed in by the merchant.

Capturing payment authorizations promptly helps ensure compliance with card network rules, reduces the risk of declines, and can lower interchange costs. While the Cybersource platform supports extended timeframes for capturing authorizations, the best practice is to capture within seven days of the original authorization date. This aligns with typical issuer and acquirer expectations and helps avoid potential fees or penalties.

Applicability: This article applies to merchants using the Cybersource platform for payment processing. Capture timeframes described here reflect system-level limits. Your MSP, acquirer, or processor may enforce stricter limits. Always confirm their requirements before relying on the system's maximum timeframes. This article does not apply to non-Cybersource integrations or other Visa payment platforms.

Best Practice Recommendation

  • Capture authorizations within 7 days of the original authorization date whenever possible.
  • Delaying capture beyond 7 days may increase interchange fees and the risk of declined or expired authorizations.
  • Consult your MSP, acquirer, or processor for their specific authorization capture rules.

Capture Methods and Time Limits

Authorization Capture Time Limits by Method

Capture MethodSystem Time LimitNotes
API or Batch CaptureUp to 60 days from the original authorization dateIncludes REST API, Simple Order API, SCMP API, SOAP Toolkit, and offline batch upload. Attempting to capture after 60 days will result in an error.
Business Center CaptureUp to 180 days from the original authorization dateCapture is available via the Transaction Search Detail page or the "Auths Ready to Settle" search option (if enabled). Records are purged after 6 months. Your MSP or acquirer may not honor captures beyond their own limits.

Common Error

If a capture request is submitted after the system time limit, the following error may occur:

102: "The request data was either invalid or missing: auth_request_id"

Key Takeaways

  • Always aim to capture within 7 days for optimal compliance and cost efficiency.
  • System limits allow up to 60 days for API/batch captures and 180 days for Business Center captures, but your MSP or acquirer may have shorter limits.
  • Confirm your MSP or acquirer's policies to avoid declines, penalties, or non-compliance issues.

Potential Client Questions

  • What is the maximum time I have to capture an authorization in Cybersource?
    • The maximum time depends on the capture method used. API and batch capture methods allow up to 60 days from the original authorization date. The Business Center allows up to 180 days. However, your MSP, acquirer, or processor may enforce shorter limits, so always confirm with them directly.
  • What happens if I try to capture an authorization after the system time limit?
    • If you attempt to capture after the system's allowed timeframe, you will receive an error. For API and batch captures, this is typically Reason Code 102: "The request data was either invalid or missing: auth_request_id."
  • Why is it recommended to capture within 7 days if the system allows up to 60 or 180 days?
    • Capturing within 7 days aligns with typical issuer and acquirer expectations and helps reduce the risk of declined or expired authorizations. Delaying beyond 7 days may also result in higher interchange fees, even if the system technically allows a longer window.
  • What is interchange and why does it matter for capture timing?
    • Interchange is the default transfer price between issuing and acquiring banks applied on each transaction. The size of the interchange fee can vary based on transaction type and order data. Capturing promptly can help ensure you qualify for lower interchange rates and avoid additional costs.
  • Does my MSP or acquirer have to follow the same time limits as Cybersource?
    • No. Your MSP, acquirer, or processor may enforce stricter capture timeframes than the Cybersource system allows. Always confirm their specific requirements to avoid non-compliance, penalties, or declined captures.
  • Can I capture an authorization through the Business Center if I missed the API capture window?
    • Yes, the Business Center supports capture up to 180 days from the original authorization date, which is longer than the 60-day API/batch limit. However, your MSP or acquirer may not honor captures beyond their own defined limits, so confirm with them before relying on this option.


Was this article helpful?


Articles Recommended for You