This topic describes the credit card transaction types supported by the payment gateway and their specific field requirements. It’s a good idea to talk to your merchant about how their business plans to submit transactions so that you can properly integrate their payment gateway account to support their business processes.
For example, are they submitting transactions mainly through an e-commerce Web site? Do they need to integrate a custom application to allow call center representatives to enter mail order/telephone order (MOTO) transactions? Would they like the ability to verify the availability of funds on a customer’s credit card account at the time of purchase and then charge the credit card at the time they ship the order?
The payment gateway supports the following credit card transaction types.
Note: Some of the field requirements listed in this section for each credit card transaction type are in addition to the minimum field requirements already set forth above for ALL transactions submitted to the payment gateway. For a list of all fields that are required for each credit card transaction type, please see the “Appendix A Fields by Transaction Type” topic.
Prior Authorization and Capture
Authorization with Auto Capture (Auth_Capture) is the default transaction type in the Virtual Terminal. If no x_type variable is submitted to us with a Web site transaction request, the type defaults to Auth_Capture. This type of transaction is completely automatic: the transaction is submitted to your processor for authorization and, if approved, is placed in your Unsettled Transactions already set to Capture. The transaction will settle out with your next batch settlement (settlement occurs every 24 hours, within 24 hours of the time specified in your Settings menu, under Transaction Cutoff Time)
The unique field requirement for an Authorization and Capture is:
<INPUT TYPE=HIDDEN NAME=”x_type” VALUE=”AUTH_CAPTURE”>
This transaction type is sent for authorization only. The transaction will not be sent for settlement until the credit card transaction type Prior Authorization and Capture (see definition below) is submitted or the transaction is submitted for capture manually in the Merchant Interface. For more information about capturing Authorization Only transactions in the Merchant Interface, see the Merchant Integration Guide at http://www.authorize.net/support/merchant/.
If action for the Authorization Only transaction is not taken on the payment gateway within 30 days, the authorization expires and is no longer available for capture. A new Authorization Only transaction would then have to be submitted to obtain a new authorization code.
This transaction type is sent for authorization only. When an Authorization Only (Auth_Only) transaction is submitted, it is sent to your processor for authorization. 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, but until the transaction is captured, the funds transfer process does not take place. This can be useful in situations where you need to make a sale, but won't be able to ship merchandise for several days; you can authorize the transaction to ensure the availability of funds, then, once you have shipped, you can capture the transaction to obtain the funds.
Authorization Only transactions are kept in your Unsettled Transactions for only 30 days. After that, its transaction status changes to Expired, and the funds will NOT be transferred. To capture a transaction, you can manually log on to your Authorize.Net interface and go to your Unsettled Transactions. From there, you can use the Group Capture filter to capture multiple transactions at once, or click on the individual Transaction ID of the transaction you would like to capture, and the next screen will provide a Capture button. From a website or billing application, you can submit the x_Type variable, with a value of Prior_Auth_Capture, to capture the transaction.
The unique field requirement for an Authorization Only is:
<INPUT TYPE=HIDDEN NAME=”x_type” VALUE=”AUTH_ONLY”>
Note: For SIM merchants, the hosted payment form can be configured to submit either Authorization and Capture or Authorization Only transactions. Please check with the merchant regarding their preferences regarding which of these credit card transaction types should be used for their Web site.
Prior Authorization and Capture
This transaction type is used to complete an Authorization Only transaction that was successfully authorized through the payment gateway. It can only be submitted from a Web site or billing application.
Note: An Authorization Only and a Prior Authorization and Capture together are considered one complete transaction. Once the Prior Authorization and Capture is submitted, the transaction will be sent for settlement.
If this transaction type is required, it is recommended that the merchant process the transactions by logging on to the merchant interface directly, or by using a desktop application that uses AIM.
Capture_Only transactions are used when you already have an authorization from a bank. To use this type of transaction, you need an authorization code from the card issuer (usually a five- or six- digit number). For example, if you called Visa directly and obtained an authorization over the phone, you would need to submit a Capture_Only transaction to start the funds transfer process. You can manually submit a Capture_Only transaction from your Virtual Terminal by selencting Capture Only, or from a Web site or billing application by including the following variables with your transaction request:
• x_Type (Capture_Only)
• x_Auth_Code (the five- or six-digit code provided by the card issuer)
This transaction type is used to refund a customer for a transaction that was originally processed and successfully settled through the payment gateway. Credits can be manually processed through the Virtual Terminal, or can be submitted from a Web site or billing application
If this transaction type is required, it is recommended that the merchant process the transactions by logging on to the merchant interface directly, or by using a desktop application that uses AIM.
This transaction type is used to cancel an original transaction that is not yet settled and prevents it from being sent for settlement. A Void can be submitted against any other transaction type.
This transaction type is used to cancel an existing transaction that has a status of Authorized/Pending Capture or Captured/Pending Settlement. Settled transactions cannot be voided (issue a Credit to reverse such charges). Void requests effectively cancel the Capture request that would have started the funds transfer process; no money changes hands on a transaction that has been voided. However, keep in mind that this does not void the authorization provided by the card-issuing bank. Transactions can be manually voided from the Unsettled Transactions screen of the merchant interface. From there, you can use the Group Void filter toward to the top of your screen to void multiple transactions at once, or click on the individual Transaction ID of the transaction you would like to void, and the next screen will provide a Void button. They can also be submitted from a Web site or billing application.
Note: If you are not sure if a transaction is settled, you can attempt to submit a Void first. If the Void transaction generates an error, the original transaction is likely settled and you can submit a Credit for the transaction.
If this transaction type is required, it is recommended that the merchant process the transactions by logging on to the merchant interface directly, or by using a desktop application that uses AIM.