This task allows detailed credit card billing information to be requested and received for a credit card vendor.
Transaction Name:
DocProdFareManipulation_3_0
Can any other transactions perform this same task?
No other transaction can perform this task.
Can this task be performed in a sessionless environment?
No, it must be a used in a sessioned environment.
Are the request and response identical on both the Apollo and Galileo systems?
No, this task is currently not supported on the Apollo system.
List any industry-specific knowledge required to understand this task in terms of the specific business process.
Detailed Billing Information (DBI), also known as Extended Billing Data (EBD), is required by some credit card vendors. This information is used along with the credit card number to identify that the user of the card is valid and to track how the card is used.
Explain any special limits or restrictions.
The amount and type of information required for the request can vary depending on what the credit card vendor requires for the given card number. If the credit card vendor is not available, all possible fields may be presented in the request, but are not all required.
Request:
The detailed billing mask task uses the <TicketingMods> element.
Send the <TicketingControl> sub-element with the ‘TK’ transaction type to request a ticket (See the Ticket Issue task). If the host determines that the credit card form of payment requires Extended Billing Data (EBD), the host attempts to contact the credit card vendor to determine what data is required.
A response <TicketingControl> sub-element with a ‘DB’ in the <TransType> and a <DetailedBillingMask> are returned from the host, whether or not the credit card vendor was contacted. This response indicates that additional or detailed billing data is required.
After this data is gathered, initiate the transaction again with the <TicketingMods> element. Send the <TicketingControl> sub-element with the ‘DB’ transaction code and a <DetailedBillingMask> that contains the additional data.
Prerequisite tasks:
Initiate a Ticketing Transaction using the <TicketingMods> element that contains a <TicketingControl> with a ‘TK’ transaction code.
Expected response:
Response when EBD is required and a 'TK' transaction code is used.
Response when a 'DB' transaction code is used and a <DetailedBillingMask> is sent.
<DPOK>
Error and warning responses:
Errors are returned in the <ErrText> sub-element of <TicketNumberData>.
The following error messages are returned from the Galileo system ONLY for the new Detailed Billing Mask task.
Follow-on requests:
After the initial transaction request for the ‘TK’ transaction type, when a EBD is required, the follow on request consists of a <TicketingMods> element. This element must contain a <TicketingControl> subelement with a ‘DB’ transaction code and a completed <DetailedBillingMask>.
|
<TicketingMods> |
Terminal Equivalents: |
Apollo: |
Galileo: TKP |
|
Ordering |
KLR |
Min/Max |
KLR Name |
|
A |
DPTK 2.0 |
1-1 |
<TicketingControl> |
|
B |
DPDB 1.0 |
0-1 |
<DetailedBillingMask> |
|
<Ticketing> |
|
|
Ordering |
KLR |
Min/Max |
KLR Name |
|
A |
DPTK 2.0 |
1-1 |
<TicketingControl> |
|
B |
DPPI 1.0 |
0-1 |
<AssocPsgrs> |
C |
DPDB 1.0 |
0-1 |
<DetailedBillingMask> |
|
D |
TEXT 1.0 |
0-1 |
<TextMsg> |
|
<Ticketing> |
|
|
Ordering |
KLR |
Min/Max |
KLR Name |
|
A |
EROR |
1-1 |
<ErrText> |
|
B |
DPDB 1.0 |
0-1 |
<DetailedBillingMask> |
Note: When complete detailed billing mask data is received, or if no detailed billing mask data is needed, the normal ticket issue takes place.