PTechDetailRecord Control

Properties   Methods   Events   Config Settings   Errors  

The PTechDetailRecord control is a tool used to create off-line Credit or Force transactions to be settled by the PTECHMANUALSETTLE control. The PTDetailRecord control may also be used to modify the XML aggregates returned by the PTECHCHARGE control's GetDetailAggregate method.

Syntax

PTechDetailRecord

Remarks

Credit and voice-authorization Capture transactions are off-line transactions. This means that there is no authorization of funds using the PTechCharge control. Instead, you must manually add these transactions to the settlement batch. The PTDetailRecord control can be used to create these transactions, which can then be added to the PTechManualSettle control's DetailRecords property.

To create a Credit, first set the TransactionType to dttCredit, and then set the IndustryType and EntryDataSource Next, set the Card, SettlementAmount, and the current TransactionDate and TransactionTime.

Since this is an off-line transaction, the SequenceNumber may be any value (except 0), and need not reflect the next available sequence number used for authorizations. Finally, set the PTechManualSettle control's DetailRecords array property with the value returned by the GetDetailAggregate method. You've just added a Credit to the settlement.

Voice authorization Capture transactions are similar to credits, with the exception that it requires a Voice Authorization code obtained from your acquiring bank's call center. Generally, the purchase of large high-dollar items (cars, appliances, etc) will require the merchant to call and receive a voice authorization. Once this code is received, it should be set to the ApprovalCode property. The following example shows a Force transaction in a Retail environment.

In addition to creating Credit and Force transactions, the PTechDetailRecord control can be used to adjust the Detail Records returned from the PTechCharge control to reflect changes in the SettlementAmount. The most common reasons to modify these detail records are to add a GratuityAmount (tip) to a charge (itResturant IndustryType), or to add additional charges for the itHotel IndustryType. Note that when the SettlementAmount differs from the original authorized amount, the AmountStatus must be updated to asAmountChanged.

Property List

---

The following is the full list of the properties of the control with short descriptions. Click on the links for further details.

Method List

---

The following is the full list of the methods of the control with short descriptions. Click on the links for further details.

Event List

---

The following is the full list of the events fired by the control with short descriptions. Click on the links for further details.

Config Settings

---

The following is a list of config settings for the control with short descriptions. Click on the links for further details.

AmountStatus Property (PTechDetailRecord Control)

Indicates whether SettlementAmount has been modified from the original authorization.

Syntax

ptechdetailrecordcontrol.AmountStatus[=integer]

Possible Values

asActualAmount(0), 
asAmountChanged(1)

Default Value

0

Remarks

Notes for the Hotel IndustryType:

To obtain the best interchange rate for Visa transactions in the Hotel IndustryType, the check out amount (SettlementAmount) must be within 15% of the original authorization amount. If the SettlementAmount is less than the original authorized amount by more than 15%, you must perform an authorization reversal using the PTechReversal control. This will immediately release funds from the cardholder's open to buy amount. The original transaction must then be settled for the new amount as usual. However, if the SettlementAmount exceeds the original authorized amount by more than 15%, you must submit an incremental authorization to make up the remaining amount. In this case even though there are two separate transactions, they are tied together with the same authorization code. Therefore, only the original authorization (with the newly updated SettlementAmount) is to be sent in the settlement.

Non-Visa transactions do not allow for Incrementals to tie transactions together, nor Reversals to release funds from the cardholder's open to buy amount. There are no restrictions on the difference between the SettlementAmount and the original authorization amount. However, if the merchant suspects that the final transaction amount will be substantially higher than the original authorization amount, the merchant should perform an additional authorization for the difference. This subsequent authorization must be sent to the host as a standard authorization-only transaction, and will not be tied in any way to the original transaction. Both transactions must be present in the settlement.

Notes for the Restaurant IndustryType:

For Visa transactions, to obtain the best interchange rate the SettlementAmount must be within 20% of the authorized amount. The initial authorization must be submitted for the actual transaction amount. It must not be altered to include an additional percentage that accounts for a tip being added before settlement.

The same rule applies to MasterCard transactions, with the exception that MasterCard allows the SettlementAmount to be within 25% of the authorized amount.

There are no rules concerning authorization and settlement amounts for other card types.

This information was accurate at the time this document was written. Please see the Processing and Interchange Guidelines (provided by Paymentech) for updates as well as additional information on interchange rate qualification.

Data Type

Integer

ApprovalCode Property (PTechDetailRecord Control)

The Approval code returned in the response to the authorization linked to this transaction.

Syntax

ptechdetailrecordcontrol.ApprovalCode[=string]

Default Value

""

Remarks

If this is a Forced transaction, ApprovalCode should contain the voice auth code received from the call center. If this is a Credit (Refund) transaction it should remain empty or be space filled.

Data Type

String

AuthSource Property (PTechDetailRecord Control)

Indicates the source of the authorization code stored in ApprovalCode .

Syntax

ptechdetailrecordcontrol.AuthSource[=string]

Default Value

""

Remarks

This field contains a one character code indicating the source of the ApprovalCode. The received code must be stored and submitted in the batch settlement.

Valid source codes:

* Currently in use by Japan Acquirer Services (JAS).

Data Type

String

CardExpMonth Property (PTechDetailRecord Control)

Expiration month of the credit card specified by CardNumber .

Syntax

ptechdetailrecordcontrol.CardExpMonth[=integer]

Default Value

1

Remarks

This property contains the expiration date of the customer's credit card. This property must be in the range 1 - 12.

Data Type

Integer

CardExpYear Property (PTechDetailRecord Control)

Expiration year of the credit card specified by CardNumber .

Syntax

ptechdetailrecordcontrol.CardExpYear[=integer]

Default Value

1

Remarks

This property contains the expiration date of the customer's credit card. This property must be in the range 1 - 12.

Data Type

Integer

CardNumber Property (PTechDetailRecord Control)

Customer's credit card number from the original authorization request.

Syntax

ptechdetailrecordcontrol.CardNumber[=string]

Default Value

""

Remarks

This field contains the customer's credit card number used in the original authorization request. This alphanumeric field can be a maximum of 22 characters long, excluding whitespace and dashes which are stripped out when the property is set.

Data Type

String

CardType Property (PTechDetailRecord Control)

Type of the credit card.

Syntax

ptechdetailrecordcontrol.CardType[=string]

Default Value

""

Remarks

Paymentech determines the type of credit card used for each authorization, and returns that value to the merchant in the response. The following is a list of card mnemonics and their meanings.

Data Type

String

CVVResult Property (PTechDetailRecord Control)

Contains the returned CVV result code if it was requested.

Syntax

ptechdetailrecordcontrol.CVVResult[=string]

Default Value

""

Remarks

If a CVV value was sent in the authorization request, then this one character property will contain the host returned Card Verification Value result code.

Data Type

String

ECI Property (PTechDetailRecord Control)

Electronic Commerce Indicator from the original authorization request.

Syntax

ptechdetailrecordcontrol.ECI[=string]

Default Value

""

Remarks

This field should be identical to the ECI property from the original authorization request. This property is used only for eCommerce and Direct Marketing (card not present) transactions, and is ignored for all Card Present (Retail) transactions.

Data Type

String

EntryDataSource Property (PTechDetailRecord Control)

Should reflect the Entry Data Source sent in the original authorization request.

Syntax

ptechdetailrecordcontrol.EntryDataSource[=integer]

Possible Values

edsTrack1(0), 
edsTrack2(1), 
edsManualEntryTrack1Capable(2), 
edsManualEntryTrack2Capable(3), 
edsManualEntryNoCardReader(4), 
edsTrack1Contactless(5), 
edsTrack2Contactless(6), 
edsManualEntryContactlessCapable(7), 
edsIVR(8), 
edsKiosk(9)

Default Value

0

Remarks

If sending an off-line credit or capture this property should reflect the way in which the card was presented for the credit or capture.

The following data sources are supported - edsTrack1, edsTrack2, edsManualEntryTrack1Capable, edsManualEntryTrack2Capable, edsManualEntryNoCardReader, edsTrack1Contactless, edsTrack2Contactless, edsManualEntryContactlessCapable

This property is not available at design time.

Data Type

Integer

GoodsIndicator Property (PTechDetailRecord Control)

Indicates the type of goods being sold by an e-Commerce merchant.

Syntax

ptechdetailrecordcontrol.GoodsIndicator[=integer]

Possible Values

giPhysicalGoods(0), 
giDigitalGoods(1)

Default Value

0

Remarks

If the merchant is selling physical goods (goods that are shipped or are otherwise tangible) this property must be set to giPhysicalGoods. If the merchant is selling Digital goods, such a membership, or any software or file that is delivered electronically, this field must be set to giDigitalGoods. This property is only valid when the IndustryType is set to itECommerce.

Data Type

Integer

GratuityAmount Property (PTechDetailRecord Control)

Gratuity amount for settling restaurant industry transactions.

Syntax

ptechdetailrecordcontrol.GratuityAmount[=string]

Default Value

""

Remarks

This field contains the gratuity (tip) amount of the transaction being settled. This amount is only sent when the PTechCharge control's IndustryType is set to "itRestaurant". If a transaction includes a GratuityAmount amount, the SettlementAmount must reflect the total of the original Authorized Amount plus the GratuityAmount.

This must be formatted as a dollar amount with a real decimal point, excluding the dollar sign. For instance "12.00".

Data Type

String

HotelArrivalDate Property (PTechDetailRecord Control)

Date the customer checked in, or the expected arrival date when authorizing a reservation.

Syntax

ptechdetailrecordcontrol.HotelArrivalDate[=string]

Default Value

"010101"

Remarks

Date the customer checked in, or the expected arrival date when authorizing a reservation. This property must contain an actual valid date.

Data Type

String

HotelChargeDescriptor Property (PTechDetailRecord Control)

Provides additional information about what this transaction was used for at the hotel.

Syntax

ptechdetailrecordcontrol.HotelChargeDescriptor[=integer]

Possible Values

cdHealthClub(0), 
cdLodging(1), 
cdRestaurant(2), 
cdGiftShop(3), 
cdHairSalon(4), 
cdConventionFees(5), 
cdTennisClub(6), 
cdGolfShop(7)

Default Value

1

Remarks

Provides additional information about what this transaction was used for at the hotel. If used to pay for actual hotel accommodations, this should be set to cdLodging. If this transaction was used for any hotel-provided services, it should be set to the corresponding description listed below. Available descriptors include:

• cdHealthClub (0)
• cdLodging (1)
• cdRestaurant (2)
• cdGiftShop (3)
• cdHairSalon (4)
• cdConventionFees (5)
• cdTennisClub (6)
• cdGolfShop (7)

Data Type

Integer

HotelDepartureDate Property (PTechDetailRecord Control)

Date the customer checked out, or the expected check-out date when authorizing a reservation.

Syntax

ptechdetailrecordcontrol.HotelDepartureDate[=string]

Default Value

"010101"

Remarks

Date the customer checked out, or the expected check-out date when authorizing a reservation. This property must contain an actual valid date.

Data Type

String

HotelDuration Property (PTechDetailRecord Control)

The number of days the customer stayed in the hotel, or the expected duration of stay when authorizing a reservation.

Syntax

ptechdetailrecordcontrol.HotelDuration[=integer]

Default Value

1

Remarks

The number of days the customer stayed in the hotel, or the expected duration of stay when authorizing a reservation. This property must be between 1 and 99 days.

Data Type

Integer

HotelExtraChargeAmount Property (PTechDetailRecord Control)

Total amount of extra charges incurred by the customer.

Syntax

ptechdetailrecordcontrol.HotelExtraChargeAmount[=string]

Default Value

"0.00"

Remarks

Total amount of extra charges incurred by the customer. Use the HotelExtraChargesCode to indicate the types of charges that have been added on to this transaction.

This must be formatted as a dollar amount with a real decimal point, excluding the dollar sign. For instance "12.00"

Data Type

String

HotelExtraChargesCode Property (PTechDetailRecord Control)

List of extra charges added to the cost of lodging.

Syntax

ptechdetailrecordcontrol.HotelExtraChargesCode[=string]

Default Value

"000000"

Remarks

List of extra charges added to the cost of lodging. You may include a list of extra charges for hotel transactions. Simply add the code below to this property. Multiple codes may be specified by concatenating them together. Only six extra charges may be added. For instance "240000" indicates the customer dined at the hotel restaurant and drank from the mini bar in his room. Available codes include:

Data Type

String

HotelPreferredCustomer Property (PTechDetailRecord Control)

Set this property to True to process a hotel transaction as card-not-present.

Syntax

ptechdetailrecordcontrol.HotelPreferredCustomer[=boolean]

Default Value

False

Remarks

Set this property to True to process a hotel transaction as card-not-present. This can be used for phoned-in reservations, no-show charges, or any transaction that takes place without the customer's physical card present. This property is only applicable for Visa and MasterCard transactions. Other card types must use the PTechECommerce control for phone or internet reservations.

Data Type

Boolean

HotelSaleCode Property (PTechDetailRecord Control)

Provides additional details about the type of this transaction.

Syntax

ptechdetailrecordcontrol.HotelSaleCode[=integer]

Possible Values

scNotSet(0), 
scSale(1), 
scNoShow(2), 
scDeposit(3), 
scDelayedCharge(4), 
scExpressService(5), 
scAssuredReservation(6)

Default Value

1

Remarks

Provides additional details about the type of this transaction.

Data Type

Integer

IndustryType Property (PTechDetailRecord Control)

Determines the merchant's industry type.

Syntax

ptechdetailrecordcontrol.IndustryType[=integer]

Possible Values

pitRetail(0), 
pitDirectMarketing(1), 
pitECommerce(2), 
pitRestaurant(3), 
pitHotel(4)

Default Value

0

Remarks

This property sets the merchant's industry type. Valid values are shown in the table below:

Note: Setting the IndustryType has the side effect of changing the CardEntryDataSource to the default value for the selected industry type. In addition, setting the IndustryType to itDirectMarketing or itECommerce will also reset the PINCapability to ppNoPIN.

* Restaurant orders taken over the phone should be processed as itDirectMarketing transactions. Hotel transactions should always be processed in the itHotel IndustryType. Setting the HotelPreferredCustomer property to True.

Data Type

Integer

InvoiceNumber Property (PTechDetailRecord Control)

Invoice Number from the original authorization request.

Syntax

ptechdetailrecordcontrol.InvoiceNumber[=string]

Default Value

""

Remarks

This property should be identical to the InvoiceNumber from the original authorization request.

Data Type

String

Level2PurchaseId Property (PTechDetailRecord Control)

Purchase Identifier for use when sending Level II data.

Syntax

ptechdetailrecordcontrol.Level2PurchaseId[=string]

Default Value

""

Remarks

Purchase Identifier for use when sending Level II data. This property contains a Purchase Identifier (Purchase Order Number or Order Number). The Level2PurchaseId, Level2SalesTax, and Level2ShipToZip properties are used to transmit Level II purchasing card data to the host. If any of these properties contain a value, Level II purchasing data will be sent with the authorization request. If they are all empty, Level II data will not be sent. The maximum length for this property is 17 characters.

Data Type

String

Level2SalesTax Property (PTechDetailRecord Control)

Sales Tax for use when sending Level II data.

Syntax

ptechdetailrecordcontrol.Level2SalesTax[=string]

Default Value

""

Remarks

Sales Tax for use when sending Level II data. This property contains the portion of the TransactionAmount which is sales tax. This amount is presented in US Dollars with a decimal point in the proper position, and has a maximum length of 9 characters. Set this property to "EXEMPT" if the transaction is not taxable. Set it to "0.00" if there is no tax provided.

The Level2PurchaseId, Level2SalesTax, and Level2ShipToZip properties are used to transmit Level II purchasing card data to the host. If any of these properties contain a value, Level II purchasing data will be sent with the authorization request. If they are all empty, Level II data will not be sent.

Data Type

String

Level2ShipToZip Property (PTechDetailRecord Control)

Destination ZipCode for use when sending Level II data.

Syntax

ptechdetailrecordcontrol.Level2ShipToZip[=string]

Default Value

""

Remarks

Destination ZipCode for use when sending Level II data. This property contains the zip code where the purchased goods are to be shipped. If this is a face-to-face transaction in a retail environment where the customer immediately receives the goods, this property should be the Zip code of the merchant location where the item was purchased.

The Level2PurchaseId, Level2SalesTax, and Level2ShipToZip properties are used to transmit Level II purchasing card data to the host. If any of these properties contain a value, Level II purchasing data will be sent with the authorization request. If they are all empty, Level II data will not be sent.

Data Type

String

NetworkId Property (PTechDetailRecord Control)

The Authorizing network Id from the original authorization response.

Syntax

ptechdetailrecordcontrol.NetworkId[=string]

Default Value

""

Remarks

This property should be identical to the NetworkId returned from Paymentech in the authorization response.

Data Type

String

SequenceNumber Property (PTechDetailRecord Control)

Sequence number of the transaction.

Syntax

ptechdetailrecordcontrol.SequenceNumber[=integer]

Default Value

1

Remarks

This should be identical to the sequence number sent in the original authorization.

Data Type

Integer

ServerNumber Property (PTechDetailRecord Control)

Used for restaurant transactions: Id number of the server (waiter/waitress) making the transaction.

Syntax

ptechdetailrecordcontrol.ServerNumber[=string]

Default Value

""

Remarks

Each server should have his or her own unique Id number.

Data Type

String

SettlementAmount Property (PTechDetailRecord Control)

The amount that the customer will be charged.

Syntax

ptechdetailrecordcontrol.SettlementAmount[=string]

Default Value

"0.00"

Remarks

This field contains the final settlement amount of the transaction. In most cases, this is the TransactionAmount from the original authorization request. However, you may settle a lesser amount (ie: Partial shipment or backordered stock). This field must always be greater than zero.

Note: If a transaction includes a GratuityAmount amount, the SettlementAmount must reflect the total of the original authorized amount plus the GratuityAmount (this is only applicable to the itResturant IndustryType).

This must be formatted as a dollar amount with a real decimal point, excluding the dollar sign. For instance "12.00".

Notes for the Hotel IndustryType:

To obtain the best interchange rate for Visa transactions in the Hotel IndustryType, the check out amount (SettlementAmount) must be within 15% of the original authorization amount. If the SettlementAmount is less than the original authorized amount by more than 15%, you must perform an authorization reversal using the PTechReversal control. This will immediately release funds from the cardholder's open to buy amount. The original transaction must then be settled for the new amount as usual. However, if the SettlementAmount exceeds the original authorized amount by more than 15%, you must submit an incremental authorization to make up the remaining amount. In this case even though there are two separate transactions, they are tied together with the same authorization code. Therefore, only the original authorization (with the newly updated SettlementAmount) is to be sent in the settlement.

Non-Visa transactions do not allow for Incrementals to tie transactions together, nor Reversals to release funds from the cardholder's open to buy amount. There are no restrictions on the difference between the SettlementAmount and the original authorization amount. However, if the merchant suspects that the final transaction amount will be substantially higher than the original authorization amount, the merchant should perform an additional authorization for the difference. This subsequent authorization must be sent to the host as a standard authorization-only transaction, and will not be tied in any way to the original transaction. Both transactions must be present in the settlement.

Notes for the Restaurant IndustryType:

For Visa transactions, to obtain the best interchange rate the SettlementAmount must be within 20% of the authorized amount. The initial authorization must be submitted for the actual transaction amount. It must not be altered to include an additional percentage that accounts for a tip being added before settlement.

The same rule applies to MasterCard transactions, with the exception that MasterCard allows the SettlementAmount to be within 25% of the authorized amount.

There are no rules concerning authorization and settlement amounts for other card types.

This information was accurate at the time this document was written. Please see the Processing and Interchange Guidelines (provided by Paymentech) for updates as well as additional information on interchange rate qualification.

Data Type

String

TransactionDate Property (PTechDetailRecord Control)

Local Transaction Date from the original authorization response.

Syntax

ptechdetailrecordcontrol.TransactionDate[=string]

Default Value

"010101"

Remarks

This six digit field contains a local transaction date associated with the transaction being settled. If the transaction was authorized on-line, this field must contain the value returned in the original authorization response message. If the transaction was processed off-line, this field must contain a Point of Sale (POS) device generated date. This field must appear in MMDDYY format.

Data Type

String

TransactionTime Property (PTechDetailRecord Control)

Local transaction time from the original authorization response.

Syntax

ptechdetailrecordcontrol.TransactionTime[=string]

Default Value

"000000"

Remarks

This six digit field contains a local transaction time associated with the transaction being settled. If the transaction was authorized on-line, this field must contain the value returned in the original authorization response message. If the transaction was processed off-line, this field must contain a Point of Sale (POS) device generated time. This field must appear in HHMMSS format.

Data Type

String

TransactionType Property (PTechDetailRecord Control)

Indicates transaction type for this detail record.

Syntax

ptechdetailrecordcontrol.TransactionType[=integer]

Possible Values

dttSale(1), 
dttCapture(3), 
dttHotelNoShow(4), 
dttCredit(6)

Default Value

1

Remarks

This property indicates the type of transaction that is being settled.

Note that only credit card transactions are supported here. EBT, Stored Value, Debit, and Canadian Debit cards must be processed with the Host Capture System, and cannot be manually settled.

Note that transactions Voided with the PTechCharge control must be removed from the batch. Voided transactions must not be settled.

Data Type

Integer

Config Method (PTechDetailRecord Control)

Sets or retrieves a configuration setting.

Syntax

ptechdetailrecordcontrol.Config ConfigurationString

Remarks

Config is a generic method available in every control. It is used to set and retrieve configuration settings for the control.

These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the control, access to these internal properties is provided through the Config method.

To set a configuration setting named PROPERTY, you must call Config("PROPERTY=VALUE"), where VALUE is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).

To read (query) the value of a configuration setting, you must call Config("PROPERTY"). The value will be returned as a string.

GetDetailAggregate Method (PTechDetailRecord Control)

Returns an aggregate containing details of this transaction, which is then used for settlement.

Syntax

ptechdetailrecordcontrol.GetDetailAggregate 

Remarks

This method returns an aggregate containing all of the required data to send a transaction to settlement. This aggregate must be passed to the PTechManualSettle control's DetailAggregate array property in order to settle the transaction. If you wish to view or change any part of the aggregate (such as adding a gratuity or additional info for an Installment payment), you may use the PTechDetailRecord control to do so.

Note: This method may only be called after a successful authorization. If the authorization was not successful the method fails with an error.

An example of how this method is used is shown below:

PTechCharge.Sale(); PTechManualSettle.DetailRecord[0] = PTechCharge.GetDetailAggregate();

ParseAggregate Method (PTechDetailRecord Control)

Parses the aggregate returned from another control's GetDetailAggregate method.

Syntax

ptechdetailrecordcontrol.ParseAggregate Aggregate

Remarks

This method takes the XML aggregate returned from the PTechCharge control, parses it, and then fills all the properties of the PTechDetailRecord control. While normally you can pass the results of the GetDetailAggregate method call directly to the PTechManualSettle control, sometimes it is necessary to adjust the contents of the XML aggregate first.

Reset Method (PTechDetailRecord Control)

Clears all properties to their default values.

Syntax

ptechdetailrecordcontrol.Reset 

Remarks

This method clears all properties to their default values.

Error Event (PTechDetailRecord Control)

Information about errors during data delivery.

Syntax

Sub ptechdetailrecordcontrol_Error(ErrorCode As Integer, Description As String)

Remarks

The Error event is fired in case of exceptional conditions during message processing.

ErrorCode contains an error code and Description contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the Error Codes section.

Config Settings (PTechDetailRecord Control)

The control accepts one or more of the following configuration settings. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the control, access to these internal properties is provided through the Config method.

PTechDetailRecord Config Settings

Base Config Settings

Trappable Errors (PTechDetailRecord Control)

PTechDetailRecord Errors

	20502    Property length is invalid
	20503    Property is set with invalid data.
	20505    Luhn digit check failed.
	20506    Card date invalid.
	20507    Card expired.
	20518    Response length mismatch.
	20547    Missing property for current method call.

Paymentech Server Errors:

The following is a list of error codes which may be returned by the Paymentech Server. In the case of a server-side error condition, the ResponseCode property will contain "E", the error code will be contained in the ResponseApprovalCode property, and the description in ResponseText

Paymentech Issuer Errors

Paymentech Format Errors

Paymentech Host / Setup Errors

Paymentech Debit / EBT Specific Errors

Paymentech Batch Management Errors (use the ErrorCode configuration setting to retrieve this information from the PTechHostSettle control.

The control may also return one of the following error codes, which are inherited from other controls.

HTTP Errors

	20119    Firewall Error. Error description contains detailed message.
	20144    Busy executing current method.
	20152    HTTP protocol error. The error message has the server response.
	20153    No server specified in URL
	20154    Specified URLScheme is invalid.
	20156    Range operation is not supported by server.
	20157    Invalid cookie index (out of range).
	20302    Interrupted.
	20303    Can't open AttachedFile.

The control may also return one of the following error codes, which are inherited from other controls.

TCPClient Errors

	20101    You cannot change the RemotePort at this time. A connection is in progress.
	20102    You cannot change the RemoteHost (Server) at this time. A connection is in progress.
	20103    The RemoteHost address is invalid (0.0.0.0).
	20105    Already connected. If you want to reconnect, close the current connection first.
	20107    You cannot change the LocalPort at this time. A connection is in progress.
	20108    You cannot change the LocalHost at this time. A connection is in progress.
	20113    You cannot change MaxLineLength at this time. A connection is in progress.
	20117    RemotePort cannot be zero. Please specify a valid service port number.
	20118    You cannot change the UseConnection option while the control is active.
	20136    Operation would block.
	20202    Timeout.
	20212    Action impossible in control's present state.
	20213    Action impossible while not connected.
	20214    Action impossible while listening.
	20302    Timeout.
	20303    Could not open file.
	20435    Unable to convert string to selected CodePage.
	21106    Already connecting. If you want to reconnect, close the current connection first.
	21118    You need to connect first.
	21120    You cannot change the LocalHost at this time. A connection is in progress.
	21121    Connection dropped by remote host.

SSL Errors

	20271    Cannot load specified security library.
	20272    Cannot open certificate store.
	20273    Cannot find specified certificate.
	20274    Cannot acquire security credentials.
	20275    Cannot find certificate chain.
	20276    Cannot verify certificate chain.
	20277    Error during handshake.
	20281    Error verifying certificate.
	20282    Could not find client certificate.
	20283    Could not find server certificate.
	20284    Error encrypting data.
	20285    Error decrypting data.

TCP/IP Errors

	25005    [10004] Interrupted system call.
	25010    [10009] Bad file number.
	25014    [10013] Access denied.
	25015    [10014] Bad address.
	25023    [10022] Invalid argument.
	25025    [10024] Too many open files.
	25036    [10035] Operation would block.
	25037    [10036] Operation now in progress.
	25038    [10037] Operation already in progress.
	25039    [10038] Socket operation on non-socket.
	25040    [10039] Destination address required.
	25041    [10040] Message too long.
	25042    [10041] Protocol wrong type for socket.
	25043    [10042] Bad protocol option.
	25044    [10043] Protocol not supported.
	25045    [10044] Socket type not supported.
	25046    [10045] Operation not supported on socket.
	25047    [10046] Protocol family not supported.
	25048    [10047] Address family not supported by protocol family.
	25049    [10048] Address already in use.
	25050    [10049] Can't assign requested address.
	25051    [10050] Network is down.
	25052    [10051] Network is unreachable.
	25053    [10052] Net dropped connection or reset.
	25054    [10053] Software caused connection abort.
	25055    [10054] Connection reset by peer.
	25056    [10055] No buffer space available.
	25057    [10056] Socket is already connected.
	25058    [10057] Socket is not connected.
	25059    [10058] Can't send after socket shutdown.
	25060    [10059] Too many references, can't splice.
	25061    [10060] Connection timed out.
	25062    [10061] Connection refused.
	25063    [10062] Too many levels of symbolic links.
	25064    [10063] File name too long.
	25065    [10064] Host is down.
	25066    [10065] No route to host.
	25067    [10066] Directory not empty
	25068    [10067] Too many processes.
	25069    [10068] Too many users.
	25070    [10069] Disc Quota Exceeded.
	25071    [10070] Stale NFS file handle.
	25072    [10071] Too many levels of remote in path.
	25092    [10091] Network subsystem is unavailable.
	25093    [10092] WINSOCK DLL Version out of range.
	25094    [10093] Winsock not loaded yet.
	26002    [11001] Host not found.
	26003    [11002] Non-authoritative 'Host not found' (try again or check DNS setup).
	26004    [11003] Non-recoverable errors: FORMERR, REFUSED, NOTIMP.
	26005    [11004] Valid name, no data record (check DNS setup).