Software Conversions

It is suggested that customers changing to a different transaction processor at the time of conversion work with their Integration Analyst to determine how the information stored in their database corresponds to the information required below.

Prior to processing these conversion records, the software must be configured as if it were running front desk transactions in a production mode. When these transactions are processed, they are edited and validated as if they were regular transactions. However, the process stops short of actually sending the transaction to Fusebox and the processor. The conversion occurs by populating the fields in the database based on the information provided for those fields and on how the system is configured.


If the user is changing to a different transaction processor, the conversion program should not try to carry over the CPS fields.

API FieldField NameRequiredDescription
0001Transaction TypeYMust be 01 (Auth Only)
0002Transaction AmountYTransaction amount (total amount authorized). Minimum of four digits, decimal point included.
0003Account NumberYContains either the unformatted track swipe or the manually-entered account number.
0004Expiration DateYRequired only if full magnetic stripe data is not provided in API Field 0003.
0006Authorization CodeYOriginal approval code returned from the card issuer.
0007Reference NumberYUnique number supplied by the POS to identify the transaction.
0012Force FlagYMust be 1.
0015PS2000 DataNMost Third Party Processor Interface sets do not return this field. The information once contained in this field is now returned in API fields 0034, 0035, and 0036.
0016PS2000 AmountNMost Third Party Processor Interface sets do not return this field.
0032Original Auth DateYDate the original transaction took place.
0033Original Auth TimeYTime the original transaction took place.
0034Authorization Characteristics IndicatorCCode representing the Card Association authorizing the transaction. Information received as part of the original authorization response.
0035CPS Validation CodeCComputed value assigned by the card association (Visa/MasterCard) and returned as part of the original authorization response.
0036CPS Transaction IdentifierCUnique tracking number assigned by the card issuing bank and returned as part of the original authorization response.
0037AuthorizerCCode that identifies the authorizing agency.
0038Merit Reason CodeCCode assigned by processor to track rating.
0039Merit POS Entry ModeCCode assigned by processor to identify how data was entered.
0040Merit CVC Error IndicatorCCode returned by issuing bank to indicate the result of the CVC check.
0041Merit Mag Stripe QualifierCCode returned by issuing bank to indicate the quality of the track data received.
0042Merit Authentication CodeCCode assigned by issuing bank to transaction.
0109Terminal IDYReferences a terminal defined in the PBUI configuration file.


If using dial backup, PBUI uses the eighth position when creating the backup terminal ID, so the terminal ID size is limited to 7 characters.

0110Cashier IDNCan contain any code or name up to 7 characters to identify the person creating the transaction.
0115Transaction QualifierYMust be 010 for credit
0125CPS Retrieval Reference No.CAssigned for chargeback retrieval purposes.
0126CPS Acquiring ICACAcquiring bank or third party processor ID
0127CPS Miscellaneous Data (Requested Payment Service)CAny additional, non-standard, data that the processor
0128CPS Original Auth AmountCOriginal authorization. The only dollar amount associated with this transaction.
0129CPS Preferred Customer IndicatorCIndicates if this customer qualifies for the preferred plan.
0130CPS Total Authorized AmountCTotal amount authorized up to this point in the lifecycle of this transaction. Includes decimal point.
0131Total Number of Incremental Auths SentCTotal number of incremental authorizations up to this point in the lifecycle of this transaction.
0300Charge DescriptionYDefault is 001 = Lodging
0301Folio NumberYFolio number.
0302Room RateYPer day charge for room. Include decimal. If room rate $1,000 or more, enter 999.99.
0303Arrival DateYDate when customer checks in to the property.
0304Departure DateYDate when guest expects to checkout.
0305Program CodeY01 = default

02 = No Show

03 = Advanced Deposit

04 = Charge

05 = Express Service

06 = Assured Reservation
0307Duration of StayYThe number of days for the charge.
0308Ticket / ROC NumberYRecord of charge, reference number assigned to the charge. Usually the same as API field 0007.
0309Employee NumberYIdentifies the person who checked in or out of the property.
0310Room NumberYIdentification of the room incurring primary charges.
0311Extra Charges AmountYDollar amount (including decimal point) for any extra charges incurred by the guest.
0312Lodging Extra Charges Reason CodesYReason(s) for extra charges. Enter multiple reasons back to back. This field should only contain a value if the Extra Charges Amount (Field 311) contains a valid amount.

0 = N/A

2 = restaurant

3 = gift shop

4 = mini bar

5 = telephone

6 = other

7 = laundry
0313Guest NameYName of guest.
0723Recurring Payments StatusCFlag indicating status of recurring payment (Card on File transaction). Valid values are:

F - First Payment

S – Subsequent scheduled recurring payment (i.e., regular payment)

U – Unscheduled recurring payment/purchase
0738Recurring Compliance DataCContains compliance data that merchants should retain and then return unaltered in the next card on file transaction.
1002Cardholder NameNCardholder name parsed from Track I, if provided in input API.
1008Unique ID RequestYRequests Unique ID in Input Request

Masked Account Number In Output Response
1011Host Reference NumberNReference number assigned by the host processor to track this transaction. Only required if the processor provided one.
1015AVS Result CodeNCode indicating level of success of address verification portion of authorization.
8002Location NameYGateway UI based reporting, settlement and other database functions.
8006Chain CodeYA six position code assigned at the chain level used for key management.