PTechDetailRecord Class

Properties   Methods   Events   Config Settings   Errors  

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

Syntax

class dpaymentssdk.PTechDetailRecord

Remarks

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

To create a Credit, first set the transaction_type to dttCredit, and then set the industry_type and entry_data_source Next, set the card, settlement_amount, and the current transaction_date and transaction_time.

Since this is an off-line transaction, the sequence_number may be any value (except 0), and need not reflect the next available sequence number used for authorizations. Finally, set the PTechManualSettle class's detail_records array property with the value returned by the get_detail_aggregate 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 approval_code property. The following example shows a Force transaction in a Retail environment.

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

Property List

---

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

Method List

---

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

Event List

---

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

Config Settings

---

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

amount_status Property

Indicates whether SettlementAmount has been modified from the original authorization.

Syntax

def get_amount_status() -> int: ...
def set_amount_status(value: int) -> None: ...

amount_status = property(get_amount_status, set_amount_status)

Default Value

0

Remarks

Notes for the Hotel industry_type:

To obtain the best interchange rate for Visa transactions in the Hotel industry_type, the check out amount (settlement_amount) must be within 15% of the original authorization amount. If the settlement_amount is less than the original authorized amount by more than 15%, you must perform an authorization reversal using the PTechReversal class. 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 settlement_amount 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 settlement_amount) 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 settlement_amount 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 industry_type:

For Visa transactions, to obtain the best interchange rate the settlement_amount 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 settlement_amount 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.

approval_code Property

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

Syntax

def get_approval_code() -> str: ...
def set_approval_code(value: str) -> None: ...

approval_code = property(get_approval_code, set_approval_code)

Default Value

""

Remarks

If this is a Forced transaction, approval_code 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.

auth_source Property

Indicates the source of the authorization code stored in ApprovalCode .

Syntax

def get_auth_source() -> str: ...
def set_auth_source(value: str) -> None: ...

auth_source = property(get_auth_source, set_auth_source)

Default Value

""

Remarks

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

Valid source codes:

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

card_exp_month Property

Expiration month of the credit card specified by CardNumber .

Syntax

def get_card_exp_month() -> int: ...
def set_card_exp_month(value: int) -> None: ...

card_exp_month = property(get_card_exp_month, set_card_exp_month)

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.

card_exp_year Property

Expiration year of the credit card specified by CardNumber .

Syntax

def get_card_exp_year() -> int: ...
def set_card_exp_year(value: int) -> None: ...

card_exp_year = property(get_card_exp_year, set_card_exp_year)

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.

card_number Property

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

Syntax

def get_card_number() -> str: ...
def set_card_number(value: str) -> None: ...

card_number = property(get_card_number, set_card_number)

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.

card_type Property

Type of the credit card.

Syntax

def get_card_type() -> str: ...
def set_card_type(value: str) -> None: ...

card_type = property(get_card_type, set_card_type)

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.

cvv_result Property

Contains the returned CVV result code if it was requested.

Syntax

def get_cvv_result() -> str: ...
def set_cvv_result(value: str) -> None: ...

cvv_result = property(get_cvv_result, set_cvv_result)

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.

eci Property

Electronic Commerce Indicator from the original authorization request.

Syntax

def get_eci() -> str: ...
def set_eci(value: str) -> None: ...

eci = property(get_eci, set_eci)

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.

entry_data_source Property

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

Syntax

def get_entry_data_source() -> int: ...
def set_entry_data_source(value: int) -> None: ...

entry_data_source = property(get_entry_data_source, set_entry_data_source)

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

goods_indicator Property

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

Syntax

def get_goods_indicator() -> int: ...
def set_goods_indicator(value: int) -> None: ...

goods_indicator = property(get_goods_indicator, set_goods_indicator)

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 industry_type is set to itECommerce.

gratuity_amount Property

Gratuity amount for settling restaurant industry transactions.

Syntax

def get_gratuity_amount() -> str: ...
def set_gratuity_amount(value: str) -> None: ...

gratuity_amount = property(get_gratuity_amount, set_gratuity_amount)

Default Value

""

Remarks

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

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

hotel_arrival_date Property

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

Syntax

def get_hotel_arrival_date() -> str: ...
def set_hotel_arrival_date(value: str) -> None: ...

hotel_arrival_date = property(get_hotel_arrival_date, set_hotel_arrival_date)

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.

hotel_charge_descriptor Property

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

Syntax

def get_hotel_charge_descriptor() -> int: ...
def set_hotel_charge_descriptor(value: int) -> None: ...

hotel_charge_descriptor = property(get_hotel_charge_descriptor, set_hotel_charge_descriptor)

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)

hotel_departure_date Property

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

Syntax

def get_hotel_departure_date() -> str: ...
def set_hotel_departure_date(value: str) -> None: ...

hotel_departure_date = property(get_hotel_departure_date, set_hotel_departure_date)

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.

hotel_duration Property

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

Syntax

def get_hotel_duration() -> int: ...
def set_hotel_duration(value: int) -> None: ...

hotel_duration = property(get_hotel_duration, set_hotel_duration)

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.

hotel_extra_charge_amount Property

Total amount of extra charges incurred by the customer.

Syntax

def get_hotel_extra_charge_amount() -> str: ...
def set_hotel_extra_charge_amount(value: str) -> None: ...

hotel_extra_charge_amount = property(get_hotel_extra_charge_amount, set_hotel_extra_charge_amount)

Default Value

"0.00"

Remarks

Total amount of extra charges incurred by the customer. Use the hotel_extra_charges_code 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"

hotel_extra_charges_code Property

List of extra charges added to the cost of lodging.

Syntax

def get_hotel_extra_charges_code() -> str: ...
def set_hotel_extra_charges_code(value: str) -> None: ...

hotel_extra_charges_code = property(get_hotel_extra_charges_code, set_hotel_extra_charges_code)

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:

hotel_preferred_customer Property

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

Syntax

def get_hotel_preferred_customer() -> bool: ...
def set_hotel_preferred_customer(value: bool) -> None: ...

hotel_preferred_customer = property(get_hotel_preferred_customer, set_hotel_preferred_customer)

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 class for phone or internet reservations.

hotel_sale_code Property

Provides additional details about the type of this transaction.

Syntax

def get_hotel_sale_code() -> int: ...
def set_hotel_sale_code(value: int) -> None: ...

hotel_sale_code = property(get_hotel_sale_code, set_hotel_sale_code)

Default Value

1

Remarks

Provides additional details about the type of this transaction.

industry_type Property

Determines the merchant's industry type.

Syntax

def get_industry_type() -> int: ...
def set_industry_type(value: int) -> None: ...

industry_type = property(get_industry_type, set_industry_type)

Default Value

0

Remarks

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

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

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

invoice_number Property

Invoice Number from the original authorization request.

Syntax

def get_invoice_number() -> str: ...
def set_invoice_number(value: str) -> None: ...

invoice_number = property(get_invoice_number, set_invoice_number)

Default Value

""

Remarks

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

level_2_purchase_id Property

Purchase Identifier for use when sending Level II data.

Syntax

def get_level_2_purchase_id() -> str: ...
def set_level_2_purchase_id(value: str) -> None: ...

level_2_purchase_id = property(get_level_2_purchase_id, set_level_2_purchase_id)

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 level_2_purchase_id, level_2_sales_tax, and level_2_ship_to_zip 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.

level_2_sales_tax Property

Sales Tax for use when sending Level II data.

Syntax

def get_level_2_sales_tax() -> str: ...
def set_level_2_sales_tax(value: str) -> None: ...

level_2_sales_tax = property(get_level_2_sales_tax, set_level_2_sales_tax)

Default Value

""

Remarks

Sales Tax for use when sending Level II data. This property contains the portion of the transaction_amount 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 level_2_purchase_id, level_2_sales_tax, and level_2_ship_to_zip 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.

level_2_ship_to_zip Property

Destination ZipCode for use when sending Level II data.

Syntax

def get_level_2_ship_to_zip() -> str: ...
def set_level_2_ship_to_zip(value: str) -> None: ...

level_2_ship_to_zip = property(get_level_2_ship_to_zip, set_level_2_ship_to_zip)

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 level_2_purchase_id, level_2_sales_tax, and level_2_ship_to_zip 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.

network_id Property

The Authorizing network Id from the original authorization response.

Syntax

def get_network_id() -> str: ...
def set_network_id(value: str) -> None: ...

network_id = property(get_network_id, set_network_id)

Default Value

""

Remarks

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

sequence_number Property

Sequence number of the transaction.

Syntax

def get_sequence_number() -> int: ...
def set_sequence_number(value: int) -> None: ...

sequence_number = property(get_sequence_number, set_sequence_number)

Default Value

1

Remarks

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

server_number Property

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

Syntax

def get_server_number() -> str: ...
def set_server_number(value: str) -> None: ...

server_number = property(get_server_number, set_server_number)

Default Value

""

Remarks

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

settlement_amount Property

The amount that the customer will be charged.

Syntax

def get_settlement_amount() -> str: ...
def set_settlement_amount(value: str) -> None: ...

settlement_amount = property(get_settlement_amount, set_settlement_amount)

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 gratuity_amount amount, the settlement_amount must reflect the total of the original authorized amount plus the gratuity_amount (this is only applicable to the itResturant industry_type).

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 industry_type:

To obtain the best interchange rate for Visa transactions in the Hotel industry_type, the check out amount (settlement_amount) must be within 15% of the original authorization amount. If the settlement_amount is less than the original authorized amount by more than 15%, you must perform an authorization reversal using the PTechReversal class. 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 settlement_amount 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 settlement_amount) 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 settlement_amount 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 industry_type:

For Visa transactions, to obtain the best interchange rate the settlement_amount 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 settlement_amount 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.

transaction_date Property

Local Transaction Date from the original authorization response.

Syntax

def get_transaction_date() -> str: ...
def set_transaction_date(value: str) -> None: ...

transaction_date = property(get_transaction_date, set_transaction_date)

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.

transaction_time Property

Local transaction time from the original authorization response.

Syntax

def get_transaction_time() -> str: ...
def set_transaction_time(value: str) -> None: ...

transaction_time = property(get_transaction_time, set_transaction_time)

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.

transaction_type Property

Indicates transaction type for this detail record.

Syntax

def get_transaction_type() -> int: ...
def set_transaction_type(value: int) -> None: ...

transaction_type = property(get_transaction_type, set_transaction_type)

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 class must be removed from the batch. Voided transactions must not be settled.

config Method

Sets or retrieves a configuration setting.

Syntax

def config(configuration_string: str) -> str: ...

Remarks

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

These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the class, 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.

get_detail_aggregate Method

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

Syntax

def get_detail_aggregate() -> str: ...

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 class'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 class 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();

parse_aggregate Method

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

Syntax

def parse_aggregate(aggregate: str) -> None: ...

Remarks

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

reset Method

Clears all properties to their default values.

Syntax

def reset() -> None: ...

Remarks

This method clears all properties to their default values.

on_error Event

Information about errors during data delivery.

Syntax

class PTechDetailRecordErrorEventParams(object):
  @property
  def error_code() -> int: ...

  @property
  def description() -> str: ...

# In class PTechDetailRecord:
@property
def on_error() -> Callable[[PTechDetailRecordErrorEventParams], None]: ...
@on_error.setter
def on_error(event_hook: Callable[[PTechDetailRecordErrorEventParams], None]) -> None: ...

Remarks

The on_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.

PTechDetailRecord Config Settings

The class 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 class, access to these internal properties is provided through the config method.

PTechDetailRecord Config Settings

Base Config Settings

PTechDetailRecord Errors

PTechDetailRecord Errors

	501   Property length is invalid
	502   Property is set with invalid data.
	504   Luhn digit check failed.
	505   Card date invalid.
	506   Card expired.
	517   Response length mismatch.
	546   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 response_code property will contain "E", the error code will be contained in the response_approval_code property, and the description in response_text

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 class.

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

HTTP Errors

	118   Firewall Error. Error description contains detailed message.
	143   Busy executing current method.
	151   HTTP protocol error. The error message has the server response.
	152   No server specified in url
	153   Specified url_scheme is invalid.
	155   Range operation is not supported by server.
	156   Invalid cookie index (out of range).
	301   Interrupted.
	302   Can't open attached_file.

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

TCPClient Errors

	100   You cannot change the remote_port at this time. A connection is in progress.
	101   You cannot change the remote_host (Server) at this time. A connection is in progress.
	102   The remote_host address is invalid (0.0.0.0).
	104   Already connected. If you want to reconnect, close the current connection first.
	106   You cannot change the local_port at this time. A connection is in progress.
	107   You cannot change the local_host at this time. A connection is in progress.
	112   You cannot change MaxLineLength at this time. A connection is in progress.
	116   remote_port cannot be zero. Please specify a valid service port number.
	117   You cannot change the UseConnection option while the class is active.
	135   Operation would block.
	201   Timeout.
	211   Action impossible in control's present state.
	212   Action impossible while not connected.
	213   Action impossible while listening.
	301   Timeout.
	302   Could not open file.
	434   Unable to convert string to selected CodePage.
	1105   Already connecting. If you want to reconnect, close the current connection first.
	1117   You need to connect first.
	1119   You cannot change the LocalHost at this time. A connection is in progress.
	1120   Connection dropped by remote host.

SSL Errors

	270   Cannot load specified security library.
	271   Cannot open certificate store.
	272   Cannot find specified certificate.
	273   Cannot acquire security credentials.
	274   Cannot find certificate chain.
	275   Cannot verify certificate chain.
	276   Error during handshake.
	280   Error verifying certificate.
	281   Could not find client certificate.
	282   Could not find server certificate.
	283   Error encrypting data.
	284   Error decrypting data.

TCP/IP Errors

	10004   [10004] Interrupted system call.
	10009   [10009] Bad file number.
	10013   [10013] Access denied.
	10014   [10014] Bad address.
	10022   [10022] Invalid argument.
	10024   [10024] Too many open files.
	10035   [10035] Operation would block.
	10036   [10036] Operation now in progress.
	10037   [10037] Operation already in progress.
	10038   [10038] Socket operation on non-socket.
	10039   [10039] Destination address required.
	10040   [10040] Message too long.
	10041   [10041] Protocol wrong type for socket.
	10042   [10042] Bad protocol option.
	10043   [10043] Protocol not supported.
	10044   [10044] Socket type not supported.
	10045   [10045] Operation not supported on socket.
	10046   [10046] Protocol family not supported.
	10047   [10047] Address family not supported by protocol family.
	10048   [10048] Address already in use.
	10049   [10049] Can't assign requested address.
	10050   [10050] Network is down.
	10051   [10051] Network is unreachable.
	10052   [10052] Net dropped connection or reset.
	10053   [10053] Software caused connection abort.
	10054   [10054] Connection reset by peer.
	10055   [10055] No buffer space available.
	10056   [10056] Socket is already connected.
	10057   [10057] Socket is not connected.
	10058   [10058] Can't send after socket shutdown.
	10059   [10059] Too many references, can't splice.
	10060   [10060] Connection timed out.
	10061   [10061] Connection refused.
	10062   [10062] Too many levels of symbolic links.
	10063   [10063] File name too long.
	10064   [10064] Host is down.
	10065   [10065] No route to host.
	10066   [10066] Directory not empty
	10067   [10067] Too many processes.
	10068   [10068] Too many users.
	10069   [10069] Disc Quota Exceeded.
	10070   [10070] Stale NFS file handle.
	10071   [10071] Too many levels of remote in path.
	10091   [10091] Network subsystem is unavailable.
	10092   [10092] WINSOCK DLL Version out of range.
	10093   [10093] Winsock not loaded yet.
	11001   [11001] Host not found.
	11002   [11002] Non-authoritative 'Host not found' (try again or check DNS setup).
	11003   [11003] Non-recoverable errors: FORMERR, REFUSED, NOTIMP.
	11004   [11004] Valid name, no data record (check DNS setup).