TransactionType Property
Specifies the type of transaction to process.
Data Type
EnumerationPossible Values
Sale (0)Auth Only (1)
Capture (2)
Refund (3)
Credit (4)
Void (5)
Force (6)
AVSOnly (7)
Default Value
0Remarks
Changing the TransactionType can allow for additional functionality depending on the specified Gateway. A list of valid transaction types and their descriptions follows.
| Code | Description |
| Sale | Sale (or Auth-Capture) is the default transaction method; a transaction is sent for approval, the transaction is approved, the merchant is notified of the approval, and the transaction automatically settles at the end of the business day without any further action by the merchant. |
| AuthOnly | Auth-Only stands for Authorization-Only and means obtaining an authorization for a certain amount on a customer's credit card without actually charging the card. |
| Capture | A Prior-Auth-Capture transaction is used to capture funds authorized previously using an Auth-Only transaction. Prior-Auth-Capture is an operation on an already existing transaction. Prior-Auth-Capture should only be used on Auth-Only transactions. |
| Refund | Refunds are based on a previous transaction that has already been captured or settled. Refunds require the original TransactionId be specified. |
| Credit | Credits are not processed in real time, but are submitted at settlement time with other transactions. Credits are not based on a previous transaction and provide a way to simply credit funds to a card. |
| Void | Voiding a transaction prevents a charge to a credit card or bank account from occurring. Voids are performed on existing transactions that have not yet been settled. |
| Force | A voice authorization transaction may be performed after obtaining an approval code from the cardholder's issuing bank. This offline process establishes the transaction as a settleable item. |
| AVSOnly | An AVS Only transaction checks only AVS data such as Address and Zip, and returns the result in the ResponseAVS property. No funds are authorized in an AVS Only transaction. |
Not all gateways support all transaction types. If a gateway supports Capture, Credit, or Void transactions, the TransactionId property must be set to the value of the ResponseTransactionId from the original authorization.
Please see the chart below for the list of TransactionTypes supported by each Gateway.
| Authorize.Net | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid |
| DPI | ttSale, ttAuthOnly |
| Eprocessing | ttSale |
| GoRealTime | ttSale |
| IBill | ttSale, ttAuthOnly, ttCapture, ttCredit |
| Intellipay | ttSale, ttAuthOnly, avs only |
| IOnGate | ttSale |
| ITransact | ttSale |
| NetBilling | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid, ttAvsOnly |
| PayFlowPro | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid, ttForce |
| PayReady | ttSale, ttAuthOnly |
| ViaKlix | ttSale, ttCredit, ttForce |
| USAePay | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid |
| PlugNPay | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid, ttForce |
| Planet Payment | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid |
| MPCS | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid |
| RTWare | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid |
| ECX | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid |
| BankOfAmerica | ttSale, ttAuthOnly |
| Innovative | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid |
| MerchantAnywhere | ttSale |
| Skipjack | ttSale |
| ECHOnline | ttSale, ttAuthOnly, ttCapture, ttCredit, ttAvsOnly |
| 3DSI | ttSale, ttAuthOnly, ttCapture, ttForce |
| TrustCommerce | ttSale, ttAuthOnly, ttCapture, ttCredit |
| PSIGate | ttSale, ttAuthOnly, ttCapture |
| PayFuse | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid |
| PayFlowLink | ttSale, ttAuthOnly, ttCapture |
| Orbital | ttSale, ttAuthOnly, ttCapture, ttCredit, ttForce |
| LinkPoint | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid, ttForce |
| Moneris | ttSale (ttAuthOnly supported through the merchant interface) |
| USight | ttSale |
| FastTransact | ttSale, ttAuthOnly, ttCapture, ttCredit |
| NetworkMerchants | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid |
| Ogone | ttSale, ttAuthOnly, ttCredit |
| EFSNet | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid, ttForce, ttAVSOnly |
| PRIGate | ttSale |
| Protx | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid |
| Optimal | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid, ttAVSOnly |
| MerchantPartners | ttSale, ttAuthOnly, ttCredit, ttVoid |
| CyberCash | ttSale, ttAuthOnly, ttCapture |
| FirstData | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid, ttForce |
| YourPay | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid, ttForce |
| ACHPayments | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid, ttForce |
| PaymentsGateway | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid, ttForce |
| CyberSource | ttSale, ttAuthOnly, ttCapture, ttCredit, ttForce (Add auth_type=verbal with SpecialFields for Force transactions) |
| Eway | ttSale, ttAuthOnly. Please see note below. |
| GoEMerchant | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid |
| PayStream | ttSale, ttAuthOnly, ttCapture, ttCredit |
| TransFirst | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid |
| Chase | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid, ttForce |
| PSIGateXML | ttSale, ttAuthOnly, ttCapture, ttCredit, ttVoid, ttForce |
| NexCommerce | ttSale |
| WorldPay | ttSale, ttAuthOnly |
Note: The EWay gateway does note support TransactionTypes like the other gateways do. Instead, eWay defines different GatewayURLs for each of the actions they support. The following table shows all of the supported actions for the eWay Gateway.
| GatewayURL | Description |
| https://www.eway.com.au/gateway/xmlpayment.asp | Sale transactions without CVVData. |
| https://www.eway.com.au/gateway_cvn/xmlpayment.asp | Sale transactions with CVVData. |
| https://www.eway.com.au/gateway/xmlstored.asp | Authorization Only transactions without CVVData. |
| https://www.eway.com.au/gateway/xmltest/TestPage.asp | Test transactions without CVVData. |
| https://www.eway.com.au/gateway_cvn/xmltest/TestPage.asp | Test transactions with CVVData |