Overview

Authorize.net supports six distinct transaction types that control how payment transactions are authorized, captured, refunded, or cancelled. Each transaction type serves a specific purpose in the payment lifecycle, and selecting the correct type helps ensure funds are handled accurately and efficiently.

Transactions can be submitted through the Merchant Interface, the application programming interface (API), or a web site integration. This article describes each transaction type, explains when to use it, and identifies key constraints, limitations, or time limits that apply. Where a transaction type has known processor exclusions or access restrictions, those are clearly identified.

Transaction Types at a Glance

Authorize and Capture

The Authorize and Capture transaction type is the most straightforward option. When you submit this transaction type, Authorize.net automatically sends the transaction to your processor for authorization. If approved, the transaction is placed in your Unsettled Transactions with a status of Captured Pending Settlement and settles at your next batch.

Settlement occurs every 24 hours, within 24 hours of your Transaction Cut-off Time. No additional steps are required after submission.

Best used when: You are ready to collect payment immediately and do not need to delay the funds transfer.

Authorization Only

An Authorization Only transaction sends the transaction to your processor for authorization without immediately capturing the funds. If approved, the transaction is placed in your Unsettled Transactions with a status of Authorized/Pending Capture. The authorization places the funds on hold with the customer's bank. The funds transfer process does not begin until the transaction is captured.

This transaction type is useful when you need to confirm funds availability before fulfilling an order - for example, when merchandise will not ship for several days. Authorize the transaction to hold the funds, then capture it when the order ships.

Time Limit

Authorization Only transactions are held in your Unsettled Transactions for a maximum of 30 days. If the transaction is not captured within 30 days, the status changes to Expired and the funds are not transferred. Monitor open authorizations regularly to avoid expiration.

Prior Authorization Capture

Prior Authorization Capture transactions are used to capture funds for an existing transaction that has a status of Authorized/Pending Capture. This transaction type can be submitted through the Merchant Interface, the API, or a web site integration.

Use this transaction type after an Authorization Only transaction has been approved and you are ready to initiate the funds transfer.

For step-by-step guidance, refer to:

• How to capture a prior authorized transaction? - Classic Experience (1.0) and New Experience (2.0)
• How to search for and perform bulk actions using manage transactions in the Merchant Interface? - New Experience (2.0)

Capture Only

Capture Only transactions are used when you already have an authorization code obtained directly from a card-issuing bank and do not need Authorize.net to obtain one on your behalf. This is common in scenarios where you called the card-issuing bank directly and received a verbal authorization code - typically a five- or six-character alphanumeric code.

Submitting a Capture Only transaction initiates the funds transfer process using the externally obtained authorization code. Submit this transaction type through the Virtual Terminal by selecting Capture Only, or through the API or web site integration.

If you try to perform a capture only transaction without the necessary permission, the transaction will fail and you will receive the error: 67 - Capture Only transactions are not permitted for this processor.

Processor Exclusions

The Capture Only transaction type is not supported for the processor listed here:

• Elavon
• Global

Access Limitation

The Capture Only transaction method is limited as of May 2026 and is not automatically enabled on your account. If you require access to this method, contact support with your inquiry and details around your need for this transaction type. Access is granted on a case-by-case basis. Refer to: How do I submit a Capture Only transaction? - Classic Experience (1.0) and New Experience (2.0)

Credit/Refund

Credit/Refund transactions are used to return funds to a customer's credit card. Process credit requests manually through the Virtual Terminal or through the API or web site integration.

Refund Eligibility and Time Limits

By default, credit requests can only be issued for transactions that were originally processed through the Authorize.net system, and only within 180 days of the original authorization date. After 180 days, the card data associated with the transaction is archived for security purposes, and the system no longer has access to the information needed to process a linked refund directly to the original payment method.

For transactions settled more than 180 days ago, use an alternative refund method or apply for Expanded Credit Capabilities (ECC) to issue the refund payment to your customer.

For step-by-step guidance, refer to:

• How to issue a refund transaction? - Classic Experience (1.0)
• How to issue a refund transaction? - New Experience (2.0)

Void/Cancel

Void requests are used to cancel an existing transaction that has a status of Authorized/Pending Capture or Captured/Pending Settlement. A void effectively cancels the capture request before the funds transfer process begins, meaning no money changes hands on a voided transaction.

Key Constraints

• Settled transactions cannot be voided. If a transaction has already settled, issue a Credit/Refund to reverse the charge.
• Voiding a transaction in Authorize.net does not necessarily release the authorization hold placed by the card-issuing bank. The bank's hold may remain until it expires naturally.

For step-by-step guidance, refer to:

• How do I void transactions? - Classic Experience (1.0)
• How to void transactions? - New Experience (2.0)
• How to search for and perform bulk actions using manage transactions in the Merchant Interface? - New Experience (2.0)

Frequently Asked Questions

• What is the difference between Authorize and Capture and Authorization Only?
  • Authorize and Capture automatically queues the transaction for settlement after authorization. Authorization Only places a hold on the customer's funds but does not initiate the funds transfer until you separately capture the transaction. Use Authorization Only when you need to confirm funds availability before fulfilling an order.
• What happens if I do not capture an Authorization Only transaction within 30 days?
  • If an Authorization Only transaction is not captured within 30 days, the transaction status changes to Expired and the funds are not transferred. You would need to submit a new transaction to collect payment.
• Can I issue a refund for a transaction that was processed more than 180 days ago?
  • Standard linked refunds are only available within 180 days of the original authorization. After 180 days, card data is archived and a direct linked refund is no longer possible. You may apply for Expanded Credit Capabilities (ECC) or use an alternative refund method to return funds to your customer.
• Can I void a transaction that has already settled?
  • No. Settled transactions cannot be voided. If a transaction has already settled, issue a Credit/Refund to reverse the charge. Voids can only be applied to transactions with a status of Authorized/Pending Capture or Captured/Pending Settlement.
• Does voiding a transaction release the authorization hold on the customer's card?
  • Not necessarily. Voiding a transaction in Authorize.net cancels the capture request and prevents funds from being transferred. However, the authorization hold placed by the card-issuing bank may remain until it expires naturally. The timing of the hold release is determined by the card-issuing bank, not Authorize.net.
• When should I use a Capture Only transaction instead of Authorize and Capture?
  • Use a Capture Only transaction when you have already obtained an authorization code directly from the card-issuing bank — for example, through a phone call — and do not need Authorize.net to obtain a new authorization. You will need the five- or six-character alphanumeric authorization code to submit this transaction type.
• What is Expanded Credit Capabilities (ECC) and when do I need it?
  • Expanded Credit Capabilities (ECC) is an optional feature that allows you to issue refunds for transactions settled more than 180 days ago. After 180 days, card data is archived and standard linked refunds are no longer available. Apply for ECC to regain the ability to issue refunds beyond this window.
• How do I void multiple transactions at once?
  • Navigate to the Unsettled Transactions screen in the Merchant Interface and use the Group Void filter near the top of the screen to select and void multiple transactions simultaneously.
• Is the Capture Only transaction type available for all processors?
  • No. The Capture Only transaction type is not supported for Elavon. Additionally, this method is limited as of May 2026 and is not automatically enabled. If you require access, contact support with your inquiry and the details around your need for this transaction type.
• How do I request access to the Capture Only transaction method?
  • Contact support directly with your inquiry and a description of your need for the Capture Only transaction method. Access is not automatically enabled and is reviewed on a case-by-case basis.

Additional Resources

• How to capture a prior authorized transaction? - Classic Experience (1.0) and New Experience (2.0)
• How do I submit a Capture Only transaction? - Classic Experience (1.0) and New Experience (2.0)
• How to issue a refund transaction? - Classic Experience (1.0)
• How to issue a refund transaction? - New Experience (2.0)
• How do I void transactions? - Classic Experience (1.0)
• How to void transactions? - New Experience (2.0)
• How to apply for Expanded Credit Capabilities (ECC)
• How to search for and perform bulk actions using manage transactions in the Merchant Interface? - New Experience (2.0)

Glossary

• API (Application Programming Interface): A set of protocols and tools that allows software applications to communicate with each other. Used to submit transactions programmatically to Authorize.net.
• ECC (Expanded Credit Capabilities): An optional Authorize.net feature that enables merchants to issue refunds for transactions settled more than 180 days after the original authorization date.
• Authorized/Pending Capture: A transaction status indicating that authorization has been obtained from the card-issuing bank, but the funds have not yet been captured for settlement.
• Captured Pending Settlement: A transaction status indicating that the transaction has been captured and is queued to settle at the next batch.
• Group Void: A filter feature in the Unsettled Transactions screen that allows merchants to void multiple transactions simultaneously.
• Transaction Cut-off Time: The daily time threshold after which transactions are batched and submitted for settlement. Settlement occurs within 24 hours of this time.
• Unsettled Transactions: A section of the Merchant Interface that displays transactions that have been authorized or captured but have not yet been submitted for settlement.
• Virtual Terminal: A web-based interface within the Merchant Interface that allows merchants to manually submit transactions without a physical point-of-sale device.