4.3 ww.dll API Reference : General use : Tags in <sale>
 
Tags in <sale>
 
The <sale> tag is used to process a sale with the processsale function. The indentation indicates the nesting of the tags.
 
<sale>
This contains all the information for a sale.
 
<res_hdr>
Holds fields for the resrvatn table.
 
Note: reserv_no should not be filled in.
 
<guest_no>
If provided, first_name, last_name, are filled in. The following fields should have a pri_key passed for the value.
 
<accomodat>
<base_lodge>
<mktg_code>
<wrap_code>
<pickup_loc>
<srce_code>
<user_code1>
<user_code2>
<user_code3>
<res_status>
<settlement>
 
In order to specify ProtoBase server location in the settlement string to the E-Commerce Pages, add a <Server>… </server> tag inside the settlement string with the IP address and port of the ProtoBase server to use. This overrides the [Server] > ProtoBase .INI setting in the ww_system.INI file. Sales Host then uses the same IP address and port to finish processing the credit card, thus overriding the [Server] > ProtoBase setting in the Sales32c_system.INI file.
 
<device type>
Specifies the type of charge used. When <card_no> is present, it is assumed to be 15 (ProtoBase) unless otherwise indicated.
 
<devicetype>
Process via:
Currently supported?
5
DirectNet
No
11
Folio Charge Server
No
14
Tender Retail
No
15
ProtoBase
Note: When a call is made from ww.dll to ProtoBase for a credit card authorization, the tag <proc_online></proc_online> is returned in the XML. If the tag contains a 1 it means that ProtoBase was able to communicate with the bank and if it contains a 0 it means that ProtoBase was unable to communicate with the bank. Online transactions from the E-Commerce pages send tran type 22 to the ProtoBase server.
Yes
16
Debitware
Yes
17
Ingenico Australia
Yes
18
Payment Express
Yes
<devicetype>
Typically holds a <swipe> tag plus any other fields for credit card processing, but can also hold a payment nickname (e.g., CASH). Can hold either just the description of the payment type to be used for the web payment, or the following tags are required for processing via ProtoBase.
 
<pmtn>
Used to specify multiple forms of payment.
 
Example:
<pmt1>...info...</pmt1><pmt2>...info...</pmt2>
 
Payments can be made with one or more credit cards, one or more In-House Cards items or a combination of credit cards and In-House Cards items. For sales that are paid for with a combination of credit cards and In-House Cards items, the In-House Cards payment must come first so that it can be unwound correctly if the credit card is declined.
 
<card_no>
Fifteen or sixteen digit card number
 
<exp_date>
Four digit expiration date in MMYY format
 
<card_addr>
Billing address
 
<card_addr2>
Billing address 2
 
<card_zip>
Billing zip code
 
<ship_zip>
Shipping zip code
 
<card_city>
City
 
<card_cntry>
Country
 
<card_fname>
First name
 
<card_lname>
Last name
 
<card_state>
State
 
<card_cvv2>
Three digit code on the back of the card
 
<auth_no>
Authorization number received from ProtoBase
 
<batch_no>
Batch number received from ProtoBase
 
<BatchSeq>
Batch sequence
 
<host_code>
Host code
 
<merit_cd>
Merit cd
 
<org_date>
Org date
 
<org_time>
Org time
 
<pb_code>
PB code
 
<pr_info>
PR info – encrypted
 
<swipe>
Swipe – encrypted
 
The following fields can be provided, but if they are not included, the item sections of the sale are totaled on <finalprice> and <tax> to obtain these numbers.
 
<amount>
Total amount (including tax)
 
<tax>
Tax only