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
This is the most common type of credit card transaction and is the default payment gateway transaction type. The amount is sent for authorization, and if approved, is automatically submitted for settlement.
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.
The unique field requirement for an Authorization Only is:
<INPUT TYPE=HIDDEN NAME=”x_type” VALUE=”AUTH_ONLY”>
Merchants can submit Authorization Only transactions if they want to verify the availability of funds on the customer’s credit card before finalizing the transaction. This transaction type can also be submitted in the event that the merchant does not currently have an item in stock or wants to review orders before shipping goods.
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.
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.
The payment gateway accepts this transaction type and initiates settlement if the following conditions are met:
The original Authorization Only transaction was submitted within the previous 30 days (Authorization Only transactions expire on the payment gateway after 30 days).
The transaction is submitted with the valid Transaction ID (x_trans_id) of an original, successfully authorized Authorization Only transaction.
The original transaction is not yet captured or expired, and contains no errors.
The amount being requested for capture is less than or equal to the original authorized amount. You can only submit a single Prior Authorization and Capture transaction against an Authorization Only.
The unique field requirements for a Prior Authorization and Capture are:
<INPUT TYPE=HIDDEN NAME=”x_type” VALUE=”PRIOR_AUTH_CAPTURE”>
<INPUT TYPE=HIDDEN NAME=”x_trans_id” VALUE=”Transaction ID here”>
For this transaction type, the amount field (x_amount) is only required if a Prior Authorization and Capture is submitted for an amount that is less than the amount of the original Authorization Only transaction. If no amount is submitted, the payment gateway will initiate settlement for the amount of the original authorized 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.
This transaction type is used to refund a customer for a transaction that was originally processed and successfully settled through the payment gateway.
The payment gateway accepts Credits if the following conditions are met:
The transaction is submitted with the valid Transaction ID (x_trans_id) of an original, successfully settled transaction.
The amount being requested for refund is less than or equal to the original settled amount.
The sum amount of multiple Credit transactions submitted against the original transaction is less than or equal to the original settled amount.
The last four digits only of the credit card number (x_card_num) used for the original, successfully settled transaction are submitted. An expiration date is not required.
The transaction is submitted within 120 days of the settlement date of the original transaction.
The unique field requirements for a Credit are:
<INPUT TYPE=HIDDEN NAME=”x_type” VALUE=”CREDIT”>
<INPUT TYPE=HIDDEN NAME=”x_trans_id” VALUE=”Transaction ID here”>
<INPUT TYPE=HIDDEN NAME=”x_card_num” VALUE=”Only the last four digits of the credit card number here”>
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.
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.
The payment gateway accepts Voids if the following conditions are met:
The transaction is submitted with the valid Transaction ID (x_trans_id) of an original, successfully authorized transaction.
The original transaction is not already settled or expired, and contains no errors.
The unique field requirements for a Void are:
<INPUT TYPE=HIDDEN NAME=”x_type” VALUE=”VOID”>
<INPUT TYPE=HIDDEN NAME=”x_trans_id” VALUE=”Transaction ID here”>
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.