PTechDetailRecord Component
Properties Methods Events Config Settings Errors
The PTechDetailRecord component is a tool used to create off-line Credit or Force transactions to be settled by the component. The PTDetailRecord component may also be used to modify the XML aggregates returned by the component's method.
Syntax
DPayments.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 component. Instead, you must manually add these transactions to the settlement batch. The PTDetailRecord component can be used to create these transactions, which can then be added to the PTechManualSettle component'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 component'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 component can be used to adjust the Detail Records returned from the PTechCharge component 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 component with short descriptions. Click on the links for further details.
AmountStatus | Indicates whether SettlementAmount has been modified from the original authorization. |
ApprovalCode | The Approval code returned in the response to the authorization linked to this transaction. |
AuthSource | Indicates the source of the authorization code stored in ApprovalCode . |
CardExpMonth | Expiration month of the credit card specified by CardNumber . |
CardExpYear | Expiration year of the credit card specified by CardNumber . |
CardNumber | Customer's credit card number from the original authorization request. |
CardType | Type of the credit card. |
CVVResult | Contains the returned CVV result code if it was requested. |
ECI | Electronic Commerce Indicator from the original authorization request. |
EntryDataSource | Should reflect the Entry Data Source sent in the original authorization request. |
GoodsIndicator | Indicates the type of goods being sold by an e-Commerce merchant |
GratuityAmount | Gratuity amount for settling restaurant industry transactions. |
Hotel | Contains additional information required for the Hotel/Lodging industry. |
IndustryType | Determines the merchant's industry type. |
InvoiceNumber | Invoice Number from the original authorization request. |
Level2Data | Supplies extra information for Commercial or Purchasing cards. |
NetworkId | The Authorizing network Id from the original authorization response. |
SequenceNumber | Sequence number of the transaction. |
ServerNumber | Used for restaurant transactions: Id number of the server (waiter/waitress) making the transaction. |
SettlementAmount | The amount that the customer will be charged. |
TransactionDate | Local Transaction Date from the original authorization response. |
TransactionTime | Local transaction time from the original authorization response. |
TransactionType | Indicates transaction type for this detail record |
Method List
The following is the full list of the methods of the component with short descriptions. Click on the links for further details.
Config | Sets or retrieves a configuration setting. |
GetDetailAggregate | Returns an aggregate containing details of this transaction, which is then used for settlement. |
ParseAggregate | Parses the aggregate returned from another component's GetDetailAggregate method. |
Reset | Clears all properties to their default values. |
Event List
The following is the full list of the events fired by the component with short descriptions. Click on the links for further details.
Error | Information about errors during data delivery. |
Config Settings
The following is a list of config settings for the component with short descriptions. Click on the links for further details.
SystemInformation | System Information field for Batch Inquiry and Release transactions. |
BuildInfo | Information about the product's build. |
GUIAvailable | Whether or not a message loop is available for processing events. |
LicenseInfo | Information about the current license. |
MaskSensitive | Whether sensitive data is masked in log messages. |
UseInternalSecurityAPI | Whether or not to use the system security libraries or an internal implementation. |
AmountStatus Property (PTechDetailRecord Component)
Indicates whether SettlementAmount has been modified from the original authorization.
Syntax
public PtechdetailrecordAmountStatus AmountStatus { get; set; }
enum PtechdetailrecordAmountStatus { asActualAmount, asAmountChanged }
Public Property AmountStatus As PtechdetailrecordAmountStatus
Enum PtechdetailrecordAmountStatus asActualAmount asAmountChanged End Enum
Default Value
0
Remarks
asActualAmount (0) | The SettlementAmount is the exact amount authorized in the original transaction. |
asAmountChanged (1) | The SettlementAmount is different from the amount originally authorized. This may be due to the addition of a GratuityAmount, or the settlement of a lesser amount. |
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 component. 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.
ApprovalCode Property (PTechDetailRecord Component)
The Approval code returned in the response to the authorization linked to this transaction.
Syntax
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.
AuthSource Property (PTechDetailRecord Component)
Indicates the source of the authorization code stored in ApprovalCode .
Syntax
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:
Code | Description |
1 | STIP (Stand-In Processing): time-out response. |
2 | STIP: amount below issuer limit. |
3 | STIP: issuer in Suppress Inquiry mode. |
4 | STIP: issuer unavailable. |
5 | Issuer generated response. |
6 | Off-line approval: POS device generated. |
7 | Acquirer approval: Base I unavailable. |
8 | Acquirer approval of a referral. |
9 | Use for non-authorized transactions; such as credit card credits. |
D | Referral: authorization code manually keyed. |
E | Off-line approval: authorization code manually keyed. |
F | CAFIS Interface Off-Line Post-Auth.* |
G | Issuer Approval: Post-Auth.* |
CardExpMonth Property (PTechDetailRecord Component)
Expiration month of the credit card specified by CardNumber .
Syntax
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.
CardExpYear Property (PTechDetailRecord Component)
Expiration year of the credit card specified by CardNumber .
Syntax
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.
CardNumber Property (PTechDetailRecord Component)
Customer's credit card number from the original authorization request.
Syntax
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.
CardType Property (PTechDetailRecord Component)
Type of the credit card.
Syntax
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.
VI | Visa |
MC | MasterCard |
AX | American Exp. |
DS | Discover |
JC | JCB |
DB | Debit |
EB | EBT |
SV | Stored Value |
CK | Check Authorization |
IG | In Good Taste |
PL | Retail PL |
CC | Club Card |
SC | Smarte Carte |
TH | TCH Light Fleet |
TS | TCRS Consumer Card |
IR | Irving Oil PL |
RA | RAI |
DY | Disney Rewards |
SR | Sears PL |
BE | Best |
EN | Enmark |
GC | FleetCor / GasCard |
VY | Voyager |
FO | Fleet One |
SH | Shell |
GT | Gate |
WX | WEX |
MM | MotoMart |
?? | Included in Batch Totals by Card Type responses when the host has summarized more than 14 card types within the batch (includes all other card types in the batch over 14). |
99 | Supported in Enhanced Batch Inquiry requests when "all" details or totals are being requested. |
CVVResult Property (PTechDetailRecord Component)
Contains the returned CVV result code if it was requested.
Syntax
Default Value
""
Remarks
If a CVV value was sent in the authorization request, then this one character field will contain the host returned Card Verification Value result code.
M | CVV2 match. |
N | CVV2 no match. |
P | Not processed. |
S | Merchant has indicated that CVV2 is not present on card. |
U | Issuer not certified and/or has not provided Visa encryption keys. |
ECI Property (PTechDetailRecord Component)
Electronic Commerce Indicator from the original authorization request.
Syntax
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.
EntryDataSource Property (PTechDetailRecord Component)
Should reflect the Entry Data Source sent in the original authorization request.
Syntax
public PtechdetailrecordEntryDataSources EntryDataSource { get; set; }
enum PtechdetailrecordEntryDataSources { edsTrack1, edsTrack2, edsManualEntryTrack1Capable, edsManualEntryTrack2Capable, edsManualEntryNoCardReader, edsTrack1Contactless, edsTrack2Contactless, edsManualEntryContactlessCapable, edsIVR, edsKiosk }
Public Property EntryDataSource As PtechdetailrecordEntryDataSources
Enum PtechdetailrecordEntryDataSources edsTrack1 edsTrack2 edsManualEntryTrack1Capable edsManualEntryTrack2Capable edsManualEntryNoCardReader edsTrack1Contactless edsTrack2Contactless edsManualEntryContactlessCapable edsIVR edsKiosk End Enum
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.
edsTrack1 (0) | Full Magnetic stripe read and transmit, Track 1. |
edsTrack2 (1) | Full magnetic stripe read and transmit, Track 2. |
edsManualEntryTrack1Capable (2) | Manually keyed, Track 1 capable. |
edsManualEntryTrack2Capable (3) | Manually keyed, Track 2 capable. |
edsManualEntryNoCardReader (4) | Manually keyed, terminal has no card reading capability (use this for e-commerce and MOTO transactions). |
edsTrack1Contactless (5) | Full magnetic stripe read (Track 1 only), Chip Card capable terminal (Visa, Mastercard, and JCB Transactions only). |
edsTrack2Contactless (6) | Full magnetic stripe read (Track 2 only), Chip Card capable terminal (Visa, Mastercard, and JCB Transactions only). |
edsManualEntryContactlessCapable (7) | Manually keyed, Chip Card read capable terminal (Visa, MasterCard, and JCB transactions only). |
edsIVR (8) | Interactive Voice Response processing. This is applicable to Mail Order/Telephone Order (MOTO) transactions. (CardNumber, CardExpMonth, and CardExpYear are sent). |
edsKiosk (9) | Automated kiosk transaction. Track1 or Track2 data must be sent. The transaction cannot be manually entered. |
The following data sources are supported - edsTrack1, edsTrack2, edsManualEntryTrack1Capable, edsManualEntryTrack2Capable, edsManualEntryNoCardReader, edsTrack1Contactless, edsTrack2Contactless, edsManualEntryContactlessCapable
This property is not available at design time.
GoodsIndicator Property (PTechDetailRecord Component)
Indicates the type of goods being sold by an e-Commerce merchant
Syntax
public PtechdetailrecordGoodsIndicators GoodsIndicator { get; set; }
enum PtechdetailrecordGoodsIndicators { giPhysicalGoods, giDigitalGoods }
Public Property GoodsIndicator As PtechdetailrecordGoodsIndicators
Enum PtechdetailrecordGoodsIndicators giPhysicalGoods giDigitalGoods End Enum
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.
GratuityAmount Property (PTechDetailRecord Component)
Gratuity amount for settling restaurant industry transactions.
Syntax
Default Value
""
Remarks
This field contains the gratuity (tip) amount of the transaction being settled. This amount is only sent when the PTechCharge component'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".
Hotel Property (PTechDetailRecord Component)
Contains additional information required for the Hotel/Lodging industry.
Syntax
public PTechHotelInfo Hotel { get; set; }
Public Property Hotel As PTechHotelInfo
Remarks
This property will be sent in both authorizations and detail records when the IndustryType is set to Hotel. At minimum, you should pass the expected Duration, ArrivalDate, expected DepartureDate, and SaleCode. You may pass the ExtraChargeAmount and ExtraChargesCode in the authorization, but those are normally not known until settlement. To process a reservation or any other transaction where the customer and his card are not physically present, set the PreferredCustomer field to True;. This will indicate to Paymentech that the transaction is a card-not-present authorization (PreferredCustomer must be set to False for normal card-present transaction processing).
Please refer to the PTechHotelInfo type for a complete list of fields.IndustryType Property (PTechDetailRecord Component)
Determines the merchant's industry type.
Syntax
public PtechdetailrecordIndustryTypes IndustryType { get; set; }
enum PtechdetailrecordIndustryTypes { pitRetail, pitDirectMarketing, pitECommerce, pitRestaurant, pitHotel }
Public Property IndustryType As PtechdetailrecordIndustryTypes
Enum PtechdetailrecordIndustryTypes pitRetail pitDirectMarketing pitECommerce pitRestaurant pitHotel End Enum
Default Value
0
Remarks
This property sets the merchant's industry type. Valid values are shown in the table below:
Industry Type | Description |
pitRetail (0) | Retail environments are classified as those environments where the card and cardholder are physically present at the time of purchase. |
pitDirectMarketing (1) | Mail Order or Phone Order (MOPO) environments are classified as those environments where the card and/or cardholder are not physically present at the time of purchase and the transaction is performed through the mail or over the telephone. |
pitECommerce (2) | Electronic Commerce environments are classified as those environments where the card and/or cardholder are not physically present at the time of purchase and the transaction is performed over the Internet. |
pitRestaurant (3) | Restaurant environments are similar to retail environments, where the card and cardholder are physically present at the time of purchase.* A gratuity may be added at the time of authorization, or before settlement. Note that the itRestaurant industry type requires merchants to use Paymentech's Terminal Capture System (TCS) to process transactions, and batches must be manually settled using the PTechManualSettle component. |
pitHotel (4) | Hotel/Lodging environments allow for both card-present and card-not-present transactions* (for instance, a phoned-in reservation or a charge for a no-show). Additional hotel (PTechHotelInfo) information must be submitted in the authorization and capture. Additional charges may be added on to the initial authorization using the PTechDetailRecord component before the transaction is settled with the PTechManualSettle component. Note that the itHotel industry type requires merchants to use Paymentech's Terminal Capture System (TCS) to process transactions, and batches must be manually settled using the PTechManualSettle component. |
* Restaurant orders taken over the phone should be processed as itDirectMarketing transactions. Hotel transactions should always be processed in the itHotel IndustryType. Setting the PTechHotelInfo.PreferredCustomer field to True.
InvoiceNumber Property (PTechDetailRecord Component)
Invoice Number from the original authorization request.
Syntax
Default Value
""
Remarks
This property should be identical to the InvoiceNumber from the original authorization request.
Level2Data Property (PTechDetailRecord Component)
Supplies extra information for Commercial or Purchasing cards.
Syntax
public PTechLevel2 Level2Data { get; set; }
Public Property Level2Data As PTechLevel2
Remarks
This property can be used to send additional Level II data that may qualify the merchant for a lower Interchange rate for this transaction. However, it is only valid for use with business or government Purchasing or Commercial Cards. This property is only valid for Sale and AuthOnly transactions. The PTechLevel2 type contains the following fields:
PurchaseId | Merchant-generated number that uniquely identifies this transaction. |
SalesTax | Sales tax charged to the customer. |
ShipToZip | Destination zip code for eCommerce/MOTO transactions, or zip code of the retail establishment. |
NetworkId Property (PTechDetailRecord Component)
The Authorizing network Id from the original authorization response.
Syntax
Default Value
""
Remarks
This property should be identical to the NetworkId returned from Paymentech in the authorization response.
SequenceNumber Property (PTechDetailRecord Component)
Sequence number of the transaction.
Syntax
Default Value
1
Remarks
This should be identical to the sequence number sent in the original authorization.
ServerNumber Property (PTechDetailRecord Component)
Used for restaurant transactions: Id number of the server (waiter/waitress) making the transaction.
Syntax
Default Value
""
Remarks
Each server should have his or her own unique Id number.
SettlementAmount Property (PTechDetailRecord Component)
The amount that the customer will be charged.
Syntax
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 component. 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.
TransactionDate Property (PTechDetailRecord Component)
Local Transaction Date from the original authorization response.
Syntax
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.
TransactionTime Property (PTechDetailRecord Component)
Local transaction time from the original authorization response.
Syntax
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.
TransactionType Property (PTechDetailRecord Component)
Indicates transaction type for this detail record
Syntax
public PtechdetailrecordTransactionTypes TransactionType { get; set; }
enum PtechdetailrecordTransactionTypes { dttSale, dttCapture, dttHotelNoShow, dttCredit }
Public Property TransactionType As PtechdetailrecordTransactionTypes
Enum PtechdetailrecordTransactionTypes dttSale dttCapture dttHotelNoShow dttCredit End Enum
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.
dttSale (1) | If the original transaction was a Sale (and not an Auth-only), the TransactionType will be set to dttSale after calling ParseAggregate. You should not then modify this value. |
dttCapture (3) | If the original transaction was an Auth-Only, the TransactionType will be set to dttCapture after calling ParseAggregate. This value may also be used to process voice authorization (Force) transactions. Simply fill out all of the detail record properties manually, and set the ApprovalCode property with the authorization code you received from the call center. |
dttHotelNoShow (4) | This is used only for the Hotel IndustryType, when a customer fails to show for his reservation. |
dttCredit (6) | This is a purely off-line TransactionType. It is used to credit a transaction from a previously settled batch. In this case the ApprovalCode is irrelevant, and all of the detail record properties must be filled manually. The SettlementAmount indicates the amount to be returned to the cardholder. |
Note that transactions Voided with the PTechCharge component must be removed from the batch. Voided transactions must not be settled.
Config Method (PTechDetailRecord Component)
Sets or retrieves a configuration setting.
Syntax
Remarks
Config is a generic method available in every component. It is used to set and retrieve configuration settings for the component.
These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, 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 Component)
Returns an aggregate containing details of this transaction, which is then used for settlement.
Syntax
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 component'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 component to do so.
Note: This method may only be called after a successful authorization. If the authorization was not successful the method throws an exception.
An example of how this method is used is shown below:
PTechCharge.Sale();
PTechManualSettle.DetailRecord[0] = PTechCharge.GetDetailAggregate();
ParseAggregate Method (PTechDetailRecord Component)
Parses the aggregate returned from another component's GetDetailAggregate method.
Syntax
Remarks
This method takes the XML aggregate returned from the PTechCharge component, parses it, and then fills all the properties of the PTechDetailRecord component. While normally you can pass the results of the GetDetailAggregate method call directly to the PTechManualSettle component, sometimes it is necessary to adjust the contents of the XML aggregate first.
Reset Method (PTechDetailRecord Component)
Clears all properties to their default values.
Syntax
public void Reset();
Public Sub Reset()
Remarks
This method clears all properties to their default values.
Error Event (PTechDetailRecord Component)
Information about errors during data delivery.
Syntax
public event OnErrorHandler OnError; public delegate void OnErrorHandler(object sender, PtechdetailrecordErrorEventArgs e); public class PtechdetailrecordErrorEventArgs : EventArgs { public int ErrorCode { get; } public string Description { get; } }
Public Event OnError As OnErrorHandler Public Delegate Sub OnErrorHandler(sender As Object, e As PtechdetailrecordErrorEventArgs) Public Class PtechdetailrecordErrorEventArgs Inherits EventArgs Public ReadOnly Property ErrorCode As Integer Public ReadOnly Property Description As String End Class
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.
PTechHotelInfo Type
Contains additional information required for the Hotel/Lodging industry.
Remarks
This type is used in both authorizations and detail records when processing transactions in the hotel/lodging industry type. At minimum, you should pass the expected Duration of stay, ArrivalDate, expected DepartureDate, and SaleCode. You may pass the ExtraChargeAmount and ExtraChargesCode in the authorization, but those are normally not known until settlement. To process a reservation or any other transaction where the customer and his card are not physically present, set the PreferredCustomer field to True;. This will indicate to Paymentech that the transaction is a card-not-present authorization (PreferredCustomer must be set to False for normal card-present transaction processing).
Fields
ArrivalDate
string
Default Value: "010101"
Date the customer checked in, or the expected arrival date when authorizing a reservation. This field must contain an actual valid date.
ChargeDescriptor
PTHotelChargeDescs
Default Value: 1
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)
DepartureDate
string
Default Value: "010101"
Date the customer checked out, or the expected check-out date when authorizing a reservation. This field must contain an actual valid date.
Duration
int
Default Value: 1
The number of days the customer stayed in the hotel, or the expected duration of stay when authorizing a reservation. This field must be between 1 and 99 days.
ExtraChargeAmount
string
Default Value: "0.00"
Total amount of extra charges incurred by the customer. Use the ExtraChargesCode 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"
ExtraChargesCode
string
Default Value: "000000"
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 field. 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:
0 | None. If there are no extra charges, this field should contain six zeros- "000000". |
2 | Restaurant. |
3 | Gift shop. |
4 | Mini bar. |
5 | Telephone charges. |
6 | Other charges not listed. |
7 | Laundry service. |
PreferredCustomer
bool
Default Value: False
Set this field 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 field is only applicable for Visa and MasterCard transactions. Other card types must use the PTechECommerce component for phone or internet reservations.
SaleCode
PTHotelSaleCodes
Default Value: 1
Provides additional details about the type of this transaction.
Constructors
public PTechHotelInfo();
Public PTechHotelInfo()
PTechLevel2 Type
Level II Purchase or Commercial Card information.
Remarks
This type allows the merchant to specify additional fields for Commercial Cards or Purchasing Cards for business or government transaction. Supplying the PurchaseId, SalesTax, and ShipToZip for these credit cards can qualify the merchant for a lower Interchange rate.
Fields
PurchaseId
string
Default Value: ""
Purchase Identifier for use when sending Level II data. This property contains a Purchase Identifier (Purchase Order Number or Order Number). The PurchaseId, SalesTax, and ShipToZip 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.
SalesTax
string
Default Value: ""
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 PurchaseId, SalesTax, and ShipToZip 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.
ShipToZip
string
Default Value: ""
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 PurchaseId, SalesTax, and ShipToZip 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.
Constructors
public PTechLevel2(string purchaseId, string salesTax, string shipToZip);
Public PTechLevel2(ByVal PurchaseId As String, ByVal SalesTax As String, ByVal ShipToZip As String)
public PTechLevel2();
Public PTechLevel2()
Config Settings (PTechDetailRecord Component)
The component 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 component, access to these internal properties is provided through the Config method.PTechDetailRecord Config Settings
The component will construct the System Information data based on the following specifications:
- Application Name - 7 characters
- Release Date - 6 characters (MMDDYY)
- EPROM / Version Number - 10 characters
Base Config Settings
In some non-GUI applications, an invalid message loop may be discovered that will result in errant behavior. In these cases, setting GUIAvailable to false will ensure that the component does not attempt to process external events.
- Product: The product the license is for.
- Product Key: The key the license was generated from.
- License Source: Where the license was found (e.g., RuntimeLicense, License File).
- License Type: The type of license installed (e.g., Royalty Free, Single Server).
- Last Valid Build: The last valid build number for which the license will work.
This setting only works on these components: AS3Receiver, AS3Sender, Atom, Client(3DS), FTP, FTPServer, IMAP, OFTPClient, SSHClient, SCP, Server(3DS), Sexec, SFTP, SFTPServer, SSHServer, TCPClient, TCPServer.
Setting this configuration setting to true tells the component to use the internal implementation instead of using the system security libraries.
On Windows, this setting is set to false by default. On Linux/macOS, this setting is set to true by default.
If using the .NET Standard Library, this setting will be true on all platforms. The .NET Standard library does not support using the system security libraries.
Note: This setting is static. The value set is applicable to all components used in the application.
When this value is set, the product's system dynamic link library (DLL) is no longer required as a reference, as all unmanaged code is stored in that file.
Trappable Errors (PTechDetailRecord Component)
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. |
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 Code field will contain "E", the error code will be contained in the ApprovalCode field, and the description in Text
Paymentech Issuer Errors
ApprovalCode | Text | Description |
200 | Auth Declined | Cardholder's bank did not approve transaction. |
201 | Call Voice Oper | Authorizer needs more information for approval. |
202 | Hold - Call | Card issuer does not want that card used. Call for further instructions. |
203 | Call Voice Oper | Authorizer didn't respond within allotted time. |
204 | Invalid Card No | Account #/mag stripe is invalid. |
205 | Invalid Exp. Date | Expiration date is either incorrect format or prior to today. |
206 | Invalid ICA No | Invalid International Control Account number. |
207 | Invalid ABA No | Invalid American Banking Association number. |
208 | Invalid PIN No | The Personal ID Number for a debit transaction is incorrect. |
209 | Invalid Bank MID | The Bank Merchant ID is incorrect. |
210 | Invalid Term No | The merchant ID is not valid or active. |
211 | Invalid Amount | Amount is either: equal to 0, has no decimal, has decimal in wrong place, or has multiple decimals. |
213 | Invalid Tran Fmt | The transaction format isn't valid, typically invalid SIC code |
214 | Call Voice Oper | Authorization center cannot be reached. |
215 | Lost/Stolen Card | Card has been reported lost or stolen. |
216 | Invalid PIN | Personal ID code is incorrect. |
217 | Over Credit Flr | Amount requested exceeds credit limit. |
218 | Request Denied | Transaction is not valid for this authorizer. |
220 | Not Online to XX | Fatal communications error. |
221 | Auth Down-Retry | Debit authorizer temporarily unavailable. |
222 | Auth Declined | Vehicle not found in positive file. |
223 | Invalid Pin No | Driver # not found in positive file. |
224 | Auth Declined | Card is on private label negative file. |
225 | Card Not Allowed | Merchant does not accept this card. |
226 | PL Setup Reqd | Merchant not set up for Private Label. |
227 | BIN Not Allowed | Merchant cannot accept this Private Label BIN range. |
228 | Card Not Allowed | Merchant cannot accept this card. |
229 | Inv Merc Rstrct Code | Restriction code field contains invalid data. |
230 | Prod Restricted | Merchant attempted a product code not permitted by this merchant. |
231 | Prod Not On File | Merchant attempted a product code that does not exist on host. |
232 | Auth Declined | Invalid card type for Prior Auth sale. |
233 | Auth Declined | Terminal Type not supported. |
234 | Auth Declined | T&E card used for Sale when merchant only allows Auth Only. |
235 | *Request Denied* | Prior Auth selected with no Auth code provided. |
238 | Invalid Driver Number | The Driver Number entered is invalid. |
247 | PIN Not Selected | EBT recipient has not selected a PIN for this card. |
248 | Unmatch Vch Info | Voucher submitted does not match one previously issued. |
248 | CVC2/CID ERROR | CVC2 or CID entered was not valid for the card number. |
249 | Tran Not Defined | This type of transaction is not allowed for this type of card. |
257 | Block Act Not Alwd | The merchant.is not allowed to process Stored Value Block Activations |
258 | Incorrect Act Amt | The activation amount requested does not match the predenominated amount for the card. |
292 | Auth Down - Retry | Authorizer is not responding. |
293 | Auth Busy - Retry | Authorizer not available at this time. |
294 | Auth Busy - Retry | Authorizer not available at this time. |
297 | Auth Error - Retry | Authorizer not available at this time. |
298 | Err - Pls Retry | Debit authorizer experienced an error. |
299 | Err - Pls Retry | Debit authorizer experienced an error. |
Paymentech Format Errors
ApprovalCode | Text | Description |
300 | Invalid Term ID | The length of the merchant ID is incorrect or contains invalid data. |
301 | Invalid Function | Tran code is incorrect or wrong length. |
302 | Invalid Card | Mag stripe contains invalid data or account # is greater than 19 digits |
303 | Invalid Exp. Date | Card has expired, month was not 01-12 or year was not 00-99. |
304 | Invalid Action Code | Action code is longer than 1 digit. |
305 | Amt Entry Error | Amount less than .01 or greater than 99999.99 or contained non- numeric data. |
306 | Invalid PIN | Incorrect PIN block length. |
307 | Invalid Card | Invalid card type or account number. |
308 | Auth # Not Entered | Auth code was not entered on a Prior Auth, Incremental or Rev. |
309 | Invalid Down Pay Ind | Insurance down payment indicator is invalid. |
310 | Policy # Wrong Len | Insurance policy number is incorrect length. |
311 | Invalid Ind Code | Industry type must be RE or DM. |
312 | Invalid Function | Tran code is invalid or contains alpha data. |
313 | Entry Mode Invalid | POS Entry mode is less than 01 or greater than 04. |
314 | Invalid Industry Data | The Industry Specific field contains invalid data. |
315 | Inv Fleet Data | The Fleet Card field contains invalid data. |
316 | Invalid Sys Info | The System Information field contains invalid data. |
317 | Invalid Format | Payment Service indicator or Transaction ID is invalid. |
318 | Inv Transaction Class | Transaction class not "F" for financial transaction. |
319 | Inv PIN Capability | Pin capability code field contains invalid data. |
320 | Inv/Missing Retr Ref | Retrieval Reference # is missing or contains alpha data. |
321 | Inv MSDI | Market Specific Data field contains invalid data. |
322 | Invalid Duration | Market specific data field Duration is 00, blank or missing. |
323 | Inv Pref Cust Ind | Preferred Customer indicator contains invalid data. |
324 | Inv MO/TO Number | Mail/Telephone Order number is invalid (InvoiceNumber must have a value). |
325 | Inv Sale/Chg Des/Folio | Hotel Sale Code, Charge Descriptor or Folio contains invalid data. |
326 | Inv Mult Clr Seq No | Multiple Clearing sequence number is invalid. |
327 | Inv Purch Card Data | Purchasing card field contains invalid data. |
328 | Inv Input/Use VRU | Insurance transaction not from VRU. |
329 | Invalid EC Data 329 | Invalid Electronic Commerce Data. |
330 | INV Function or Multiple FS or Unknown TKN | Indicates system problem, notify Paymentech Network Services or Multiple field separators received without required data or A token of unknown definition was received |
331 | INV TKN Value | Invalid token value was received. |
332 | CVD Data Error | Error with the cardholder verification data received; invalid value or not allowable for this card for this transaction. |
333 | TKN Data Error | Indicates system problem, notify Paymentech Network Services. |
359 | Invalid Sequence Number | The SequenceNumber must be a number between 0 and 2400. |
Paymentech Host / Setup Errors
ApprovalCode | Text | Description |
400 | Invalid Term ID | Merchant ID not found in merchant file. |
401 | Invalid Term ID | Merchant ID not found in terminal file. |
402 | Term Not Active | Active flag for merchant set to "N". |
403 | Invalid Act Code | Merchant not set up for cash advance function. |
404 | Void Not Allowed | The transaction requested for voiding is not an EFT transaction. |
405 | Ref Num Not Found | Transaction requested for reversal not found. |
406 | Proc Error 7 | The host can't clear all transaction records for the requested Batch Release. |
407 | Too Many Batches | There are 999 open batches for this merchant. |
408 | Release Batch | Current batch has 999 records. Release batch before continuing. |
409 | Invalid Function | Debit transaction requested but debit flag is set to "N". |
410 | Invalid Term ID | The Terminal ID portion of the merchant ID is incorrect. |
411 | Invalid Term ID | The maximum retries for this merchant have been exceeded. |
412 | Proc Error 13 | Unable to read reference number file. |
413 | Proc Error 14 | 413 |
414 | Proc Error 15 | 414 |
415 | Invalid Function | 415 |
416 | Invalid Function | Merchant is Authorization Only and a debit record was sent. |
417 | Invalid Function | Private label flag is "N" but a private label account number was sent. |
418 | Please Try Again | Incorrect debit working key. |
419 | Invalid Function | Manually entered transactions are not allowed for this terminal ID. |
420 | Amount Too Large | Maximum sale amount exceeded. |
421 | Amount Too Large | Maximum return amount exceeded. |
422 | Invalid Term ID | Host couldn't read terminal file within specified time. |
423 | Proc Error 24 | Host couldn't read reference number file within specified time. |
424 | Invalid Term ID | Transaction open flag has been set to "Y" within prior 3 minutes. |
425 | Invalid Function | Cash management not allowed for this merchant ID. |
426 | Rev Not Allowed | Host found no batch number matching the one sent. |
427 | Rev Not Allowed | Host found no transactions meeting the specifications sent. |
428 | Dscv Not Allowed | Merchant not set up for Discover transactions. |
429 | Rev Not Allowed | The batch containing the transaction to void has been released. |
430 | Dscv Not Allowed | Merchant not set up for Discover. |
431 | DC Not Allowed | Merchant not set up for Diners Club. |
432 | CB Not Allowed | Merchant not set up for Carte Blanche. |
433 | Invalid Key | No AMEX subscriber number, process control ID or product code set up |
434 | Invalid Key | Future use. |
435 | Failed-Plz Call | Debit transaction being sent to an authorizer not set up on host file. |
436 | Failed-Plz Call | Debit security key does not exist on the security management file. |
437 | Failed-Plz Call | Failure occurred during encryption/decryption of PIN. |
438 | Failed-Plz Call | Error occurred while generating a debit working key. |
439 | Failed-Plz Call | The DB (debit) sponsor institution on the merchant file is not set up on sponsor file. |
440 | Failed-Plz Call | The network set up on the sponsoring bank file for this institution is not set up on the host's network file. |
441 | Failed-Plz Call | The host is unable to communicate with decryption device. |
442 | JCB Not Allowed | JCB CD flag on merchant record not set up for JCB transactions. |
443 | JCB Not Allowed | JCB subscriber number not set up for JCB transactions. |
444 | Bank Not On File | Debit BIN not set up for this merchant in routing table. |
445 | No Sponsor Inst | No valid sponsorship was found on Merchant record. |
446 | Failed Plz Call | Future use. |
447 | WX Not Allowed | Merchant not set up to accept WEX. |
448 | Amount Too Large | Amount exceeds maximum limit. |
449 | Reenter Odometer | Odometer was 000000 or contained non-numeric data. |
450 | Duplicate Tran | No ACK reversal was followed by a duplicate request |
451 | Tran Not Allowed | Requested transaction type is not allowed for this card/merchant. |
452 | Bat Already Rels | Batch has already been released. |
453 | Invalid Rtng Ind | Invalid Routing Indicator field. |
454 | AX Not Allowed | AMEX not allowed. |
999 | Invalid Merchant | Merchant number not on file. |
Paymentech Debit / EBT Specific Errors
ApprovalCode | Text | Description |
602 | Call Voice Op | Auth center cannot be reached. |
692 | Auth Down-Retry | Debit authorizer temporarily unavailable. |
693 | Auth Busy-Retry | Queue for debit authorizer too long. |
694 | Auth Busy-Retry | Debit authorizer not responding in time. |
Paymentech Batch Management Errors (use the ErrorCode configuration setting to retrieve this information from the PTechHostSettle component.
ErrorCode | Text | Description |
105 | Invalid Term ID | Merchant ID on a Batch Inquiry or Release is incorrect. |
106 | Term Not Active | Active flag for the merchant ID is set to N. |
107 | No Transactions | A Batch Inquiry or Release was requested but no open batch exists. |
108 | Bat Already Rels | A second batch release was attempted. |
109 | Batch Not Found | Requested batch does not exist. |
The component may also return one of the following error codes, which are inherited from other components.
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 URLScheme is invalid. | |
155 Range operation is not supported by server. | |
156 Invalid cookie index (out of range). | |
301 Interrupted. | |
302 Can't open AttachedFile. |
The component may also return one of the following error codes, which are inherited from other components.
TCPClient Errors
100 You cannot change the RemotePort at this time. A connection is in progress. | |
101 You cannot change the RemoteHost (Server) at this time. A connection is in progress. | |
102 The RemoteHost 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 LocalPort at this time. A connection is in progress. | |
107 You cannot change the LocalHost at this time. A connection is in progress. | |
112 You cannot change MaxLineLength at this time. A connection is in progress. | |
116 RemotePort cannot be zero. Please specify a valid service port number. | |
117 You cannot change the UseConnection option while the component 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. | |
303 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). |