PTechHotel Control

Properties   Methods   Events   Configuration Settings   Errors  

The PTECHHOTEL component is used to authorize credit card transactions for the Hotel IndustryType with the Paymentech NetConnect system on the Tampa platform. This component creates a simple interface for processing transactions in the Hotel environment. It allows for simple, direct, secure communication to the Paymentech TLS/SSL gateway through a standard Internet connection. This component can be integrated into web pages or stand-alone Point Of Sale applications. Because all TLS/SSL communications are handled inside the component, any application or web page can be deployed without the need for expensive dedicated TLS/SSL servers.

Syntax

PTechHotel

Remarks

Setting up the control and authorizing a transaction is easy. First, set the MerchantNumber, TerminalNumber, ClientNumber, UserId, and Password with the information given to you when you signed up for Paymentech service. You should also set your IndustryType and PINCapability at this time.

After the merchant information is setup, you may enter transaction data. When the Credit Card's CardEntryDataSource is Manually Entered, the merchant should fill the CardNumber, CardExpMonth, and CardExpYear properties. Address Verification Service (AVS) data may be sent in card-present retail transactions by filling the CustomerAddress and CustomerZip properties. For any other CardEntryDataSource , the CardMagneticStripe property should be filled. In addition, the TransactionAmount should be set with the total amount for the transaction, including any taxes.

Now you should set the Hotel properties with extra information about the transaction. At minimum you should set the HotelArrivalDate (or reservation date), estimated HotelDuration of stay, HotelDepartureDate (planned or actual), and HotelSaleCode. If the transaction is card-not-present (ie: phone or online reservation) and the customer supplies a Visa, MasterCard, or American Express card for payment, you must also set the HotelPreferredCustomer to True. This indicates a card-not-present transaction for these two card types. Other card types must use the PTechECommerce control for card-not-present transactions.

Now simply call the Sale or AuthOnly method to send the authorization to the Paymentech Server.

The status of the authorization request will be stored in the ResponseCode property, with human-readable text appearing in the ResponseText property. There are several other Response properties which will contain data that should be logged.

Hotel transactions only operate in Terminal Capture mode. This means you cannot rely on Paymentech to automatically handle the settlement for you. Instead, you must save the XML aggregate returned from the GetDetailAggregate method, for each and every authorization. At the end of the day, you must then use the PTechManualSettle control to send all of these aggregates for processing. The reason Paymentech cannot handle the batch automatically for the PTechHotel control is because Hotel transactions by nature will usually have additional charges tacked on to the originally authorized amount. It may also be several days between check-in (authorization) and departure (when you can then settle the card). The XML aggregates for each transaction may be manipulated using the PTechDetailRecord control. This will allow you to add or remove additional days to the stay, tack on charges for room service or telephone calls, and more.

Note that when processing transactions in Terminal Capture mode, credits and captures are processed off-line using the PTechDetailRecord and PTechManualSettle controls.