Litle Point-to-Point Integration

Litle Point-to-Point Integration

Litle Point-to-Point integration allows you to process batch deposit transactions between CWSerenade and Litle using point-to-point communication. Deposit processing remains the same in CWSerenade; however, instead of using the Deposit integration layer job to process the deposit transactions and send the transactions to a CWIntegrate site via the queues defined for the integration layer job, CWSerenade uses the Litle Batch Deposit messages to send the deposit transactions directly to the Litle system for processing.

Supported: The Litle integration supports the following transactions for Visa, Mastercard, American Express, Diners and Discover credit cards.

CWSerenade Transaction	Litle Transaction	Message Generated
Deposit: Debit	Capture	Litle Batch Deposit Request Message Litle Batch Deposit Response Message
Deposit: Credit	Credit	Litle Batch Deposit Request Message Litle Batch Deposit Response Message
Deposit: Debit without Litle approved authorization	Capture Given Auth	Litle Batch Deposit Request Message Litle Batch Deposit Response Message

See Processing Auto Deposits (SDEP) for more information on processing deposits.

The integration also supports:

Process	See:
level II processing (not level III)	Level II and III Discounting
multicurrency	Multi Currency by Offer (E03) and Using Alternate Currency Pricing

Not supported: The Litle Point-to-Point integration does not support:

• authorization transactions (online or batch). To use the Litle Point-to-Point integration and also process authorization transactions, you must create two service bureaus in Defining Authorization Services (WASV) for Litle:

• Create the LTD deposit service to process deposit transactions between CWSerenade and Litle using point-to-point communication.

• Create another Litle service bureau to process all authorization transactions between CWSerenade and Litle using the Litle CWIntegrate site.

See Service Bureau Settings for setup information.

• level III processing

• deferred or installment billing

• card identification (CSV/CSP)

• Verified by Visa and MasterCard Secure Code programs

• address verification (AVS)

• switch cards

• Bill Me Later payments

In this topic:

• Litle Point-to-Point Integration Setup

• Litle Point-to-Point Deposit Process

• Sample Litle Transactions

• Litle Batch Deposit Request Message

• Litle Batch Deposit Response Message

Litle Point-to-Point Integration Setup

Before you can use the Litle Point-to-Point integration, you must complete the required setup.

• Service Bureau Settings

• Interface Properties File

• Work with Pay Types (WPAY)

Required versions: To use the Litle Point-to-Point integration with CWSerenade, you must be on version 8.1 of Litle and version 3.0 or later of CWSerenade.

Service Bureau Settings

• Litle Service Bureau Setup

• .IL Service Bureau Setup

Litle Service Bureau Setup

Use Defining Authorization Services (WASV) to create a service bureau for the Litle service that you will use to process authorizations and deposits via point-to-point communication.

Note: Litle Point-to-Point communication is available for deposit processing only; you will need to create two service bureaus for Litle:

• Create the LTD deposit service to process deposit transactions between CWSerenade and Litle using point-to-point communication.

• Create another Litle service bureau to process all authorization transactions between CWSerenade and Litle using the Litle CWIntegrate site; see Processing Authorizations and Deposits using CWIntegrate and the CWIntegrate Litle Integration with CWSerenade Site Reference.

Litle setup using Point-to-Point	Litle setup using CWIntegrate
Service code: Enter LTD.	Service code: Enter a code to identify the Litle service bureau, such as LTL. Do not enter LTD since this code is used for point-to-point communication with Litle.
Application: Enter Deposit.	Application: Enter Authorization.
The following values are supplied by Litle and apply to both integrations: • Merchant ID • Signon • password
Integration layer processes: Leave these fields blank.	Integration layer processes: • Online authorization: Enter the code for the integration layer process used to process online authorizations. • Batch authorization: Enter the code for the integration layer process used to process batch authorizations.
Batch/Online: Enter Batch.	Batch/Online: Enter Online or Batch.
The following values are the same for both integrations: • Request token: Must be unselected. • Send reversal: Must be unselected. • Media type: Enter Communication. • Active production system: Must be selected. • Immediate response: Must be selected. • Immediate deposit: Must be unselected. • Address verification: Select to perform address verification. • Primary authorization service: Must be .IL. • Response check frequency: Enter the number of seconds the system waits before checking for a response to the batch transaction sent to Litle. The system checks for a response up to 20 times. At minimum, set this value to 60. • Response time: Enter the number of seconds the system waits for an authorization response when you are performing online transactions.
Test mode: If selected, the system retains the Litle Batch Deposit Request Message and Litle Batch Deposit Response Message in the inbound and outbound directories; if unselected, the system deletes these messages once processing is complete. Note: For data security, select this field only if you are troubleshooting a transaction; once troubleshooting is complete, immediately delete the files.	Test mode: Leave unselected.
Communication type: Enter Payment Link to indicate messages sent to and from Litle are processed directly.	Communication type: Enter Integration Layer to indicate messages sent to and from Litle are processed via the Litle CWIntegrate site.
API user name: Enter the user name provided by Litle used to establish a secure FTP connection to the Litle system during deposit processing.	API user name: Leave blank.
API password: Enter the password provided by Litle used to establish a secure FTP connection to the Litle system during deposit processing.	API password: Leave blank.
The following options must be defined for both integrations: Paytype codes: Define a cross reference between your pay type code and the pay type code used by Litle; see Defining Vendor Paytype Codes. Response codes: Define the reasons that the service bureau approves or declines a transaction. The codes are assigned to each transaction by the service bureau when approving or declining the request; see Defining Vendor Response Codes.

.IL Service Bureau Setup

To send transactions to Litle using Point-to-Point communication or a CWIntegrate site, create a service bureau using the service code .IL and enter a value in the following fields:

• Application: Enter Auth/Deposit.

• Merchant ID: Enter INTEGRATION LAYER.

• Charge description: Enter CWIntegrate.

• Media type: Enter Communication.

Enter the .IL service bureau in the Primary authorization service field for each Litle service bureau.

Interface Properties File

Use the following settings in the cwdirectcp_interfaces.properties file to communicate with the Litle system using point-to-point communication.

To edit a properties file: You can use a text editor such as WordPad to edit the file, being careful to only change the settings that are configurable.

Note: If you make a change to a properties file, you must select Change in Refresh System Properties (PROP) or stop and restart the Serenade service (or the application server) before the changes take effect.

Location of properties file: Typically, the CWSerenade properties files are saved on the CWSerenade application server at the following location, where C: is the root directory of the server.

C:\Serenade\server\conf\cwdirectcpproperties

Note: Define these settings on each of your CWSerenade application servers.

LTD_PAY_LINK_

SERVICE

The name of the external system. Set this to Litle.

LTD_PAY_LINK_

SERVICE_IP_ADDRESS

The web address used to connect to Litle using point-to-point communication.

LTD_PAY_LINK_

SERVICE_BATCH_PORT

The port number used to connect to Litle using point-to-point communication.

LTD_PAY_LINK_

SERVICE_LOCAL_

SOURCE_DIRECTORY

The directory on the CWSerenade application server where request transactions are placed to send to Litle for processing. The directory entry must use a double forward slash. The recommended directory is C://CWSerenade//Integrations//Litle//Outbound//, where C is the root directory where CWSerenade is installed.

Note: If this directory does not already exist, the system creates it.

LTD_PAY_LINK_

SERVICE_REMOTE_

TARGET_DIRECTORY

The directory on the Litle server where request transactions are placed for Litle to process. The directory is supplied by Litle and should not be changed unless specified by Litle.

Example: inbound

LTD_PAY_LINK_

SERVICE_REMOTE_

SOURCE_DIRECTORY

The directory on the Litle server where response transactions are placed to send to CWSerenade for processing. The directory is supplied by Litle and should not be changed unless specified by Litle.

Example: outbound

LTD_PAY_LINK_

SERVICE_LOCAL_

TARGET_DIRECTORY

The directory on the CWSerenade application server where response transactions are placed for CWSerenade to process. The directory entry must use a double forward slash. The recommended directory is C://CWSerenade//Integrations//Litle//Inbound//, where C is the root directory where CWSerenade is installed.

Note: If this directory does not already exist, the system creates it.

Work with Pay Types (WPAY)

Use Working with Pay Types (WPAY) to define the authorization and deposit service used for each Litle pay type.

• The authorization service must be the Litle service bureau set up for communication via the CWIntegrate site.

• The deposit service must be LTD to communicate with Litle via point-to-point communication.

Litle Point-to-Point Deposit Process

CWSerenade performs the following steps when you process deposits for Litle using point-to-point communication.

For more information: See Processing Auto Deposits (SDEP) for more information on the deposit process.

1.	CWSerenade looks at the Communication type field for the LTD service bureau to determine how transactions are processed between CWSerenade and Litle. • Integration Layer = CWIntegrate integration. The system sends deposit transactions to Litle via the CWIntegrate Litle site using queues defined for the Deposit integration layer job. You must define communication protocols within the CWIntegrate Litle site to translate and transmit data between CWSerenade and Litle. See Processing Authorizations and Deposits using CWIntegrate. • Payment Link = Point-to-point integration. The system sends deposit transactions directly to Litle.
2.	If the Communication type field for the LTD service bureau is Payment Link, CWSerenade: • Creates the Litle Batch Deposit Request Message using information in the Credit Card Deposit Transaction table and other tables. • Writes the Litle Batch Deposit Request in the CWSerenade Trace Log if its Logging Level is set to DEBUG. CWSerenade masks the card number in the log based on the setting of the Display Partial Credit Card Number in Logs (J16) system control value. • If the Display Partial Credit Card Number in Logs (J16) system control value is selected, the system displays the last four digits of the credit card number in the log; for example ************1443. If the credit card number is 4 digits or less, the entire credit card number is masked. • If the Display Partial Credit Card Number in Logs (J16)* system control value is unselected, the system replaces the credit card number in the log with the word *REMOVED. • Updates the status of the records in the Credit Card Deposit Transaction table to SENT status. • Places the request in the outbound directory on the CWSerenade application server (this is the directory defined for the LTD_PAY_LINK_SERVICE_LOCAL_SOURCE_DIRECTORY setting in the Interface Properties File). CWSerenade names the file as follows, where 001 is the CWSerenade company code, 123456 is the LTD merchant ID, and 999 is the next number in the Batch Auth File Trace Number number assignment wheel: LTD_001_123456_999.prg. Note: Spaces are not allowed in the file name and the prg file extension must be in lower case.
3.	The SFTP process monitors the outbound directory on the CWSerenade application server for new deposit requests to process and uses the Litle settings in the Interface Properties File and the settings in Defining Authorization Services (WASV) for the LTD service bureau to send the deposit request directly to Litle using secure FTP communication protocol.
4.	The SFTP process places the deposit request in the inbound directory on the Litle server (this is the directory defined for the LTD_PAY_LINK_SERVICE_REMOTE_TARGET_DIRECTORY setting in the Interface Properties File). The SFTP process changes the file extension from prg to asc.
5.	Litle monitors the inbound directory on the Litle server for new deposit requests with a file extension of asc to process every thirty seconds. When a new request is found, Litle processes it and generates a Litle Batch Deposit Response Message. Litle names the file as follows, using the same CWSerenade company code, LTD merchant ID, and Batch Auth File Trace number that was assigned to the associated Litle Batch Deposit Request message: LTD_001_123456_999.prg.
6.	Litle places the Batch Deposit Response message in the outbound directory on the Litle server (this is the directory defined for the LTD_PAY_LINK_SERVICE_REMOTE_SOURCE_DIRECTORY setting in the Interface Properties File) and changes the file extension from prg to asc when the file is ready to transfer.
7.	The SFTP process monitors the outbound directory on the Litle server for new deposit responses to process every 15 seconds. When a new response is found and its file extension is asc, the SFTP process retrieves the response and places it in the inbound directory on the CWSerenade application server (this is the directory defined for the LTD_PAY_LINK_SERVICE_LOCAL_TARGET_DIRECTORY setting in the Interface Properties File).
8.	CWSerenade monitors the inbound directory on the CWSerenade application server for a new Litle Batch Deposit Response Message to process. The system checks for a response using the number of seconds defined in the Response check frequency setting for the LTD service bureau. The system checks for a response to the batch deposit request up to 20 times. If a response is not received: If a Litle Batch Deposit Response is not received within the maximum wait time, CWSerenade creates a record in the Request for Response table; see Working with Required Responses (WREQ) for processing details.
9.	CWSerenade processes the response: • Writes the Litle Batch Deposit Response Message in the CWSerenade Trace Log if its Logging Level is set to DEBUG. CWSerenade masks the card number in the log based on the setting of the Display Partial Credit Card Number in Logs (J16) system control value. • If the Display Partial Credit Card Number in Logs (J16) system control value is selected, the system displays the last four digits of the credit card number in the log; for example ************1443. If the credit card number is 4 digits or less, the entire credit card number is masked. • If the Display Partial Credit Card Number in Logs (J16)* system control value is unselected, the system replaces the credit card number in the log with the word *REMOVED. • Matches the Litle Batch Deposit Response message to a send deposit record in the CC Deposit Transaction table. When a match is found, the system updates the status of the Credit Card Deposit Transaction record to RCVD and with the values in the deposit response. • Deletes the Litle Batch Deposit Request Message and Litle Batch Deposit Response Message from the inbound and outbound directories (defined in the Interface Properties File), unless the Test mode setting for the LTD service bureau in Defining Authorization Services (WASV) is selected. Note: For data security, select the Test mode field only if you are troubleshooting a transaction; once troubleshooting is complete, immediately delete the files. • Completes the AUTO_DEP job and submits the DEP_UPDATE job to the QSYSNOMAX queue to process the remaining updates, such as generating reports and performing general ledger postings. See Batch Deposit Updates.

Sample Litle Transactions

See Litle Batch Deposit Request Message and Litle Batch Deposit Response Message for mapping details.

• Capture Transaction

• Credit Transaction

• Capture Given Authorization Transaction

• Capture, Credit and Capture Given Authorization Transaction

Capture Transaction

Request:

<user>MICROS</user>

<password>certXZ7v</password>

</authentication>

<taxExempt>false</taxExempt>

</enhancedData>

</capture>

</batchRequest>

</litleRequest>

Response:

<message>Approved</message>

</captureResponse>

</batchResponse>

</litleResponse>

Credit Transaction

Request:

<user>MICROS</user>

<password>certXZ7v</password>

</authentication>

<orderSource>telephone</orderSource>

<card>

</card>

<taxExempt>false</taxExempt>

</enhancedData>

</credit>

</batchRequest>

</litleRequest>

Response:

<message>Approved</message>

</creditResponse>

</batchResponse>

</litleResponse>

Capture Given Authorization Transaction

Request:

<user>MICROS</user>

<password>certXZ7v</password>

</authentication>

</authInformation>

<orderSource>telephone</orderSource>

<card>

</card>

<taxExempt>false</taxExempt>

</enhancedData>

</captureGivenAuth>

</batchRequest>

</litleRequest>

Response:

<message>Approved</message>

</captureGivenAuthResponse>

</batchResponse>

</litleResponse>

Capture, Credit and Capture Given Authorization Transaction

Request:

<user>MICROS</user>

<password>certXZ7v</password>

</authentication>

<orderSource>telephone</orderSource>

<card>

</card>

<taxExempt>false</taxExempt>

</enhancedData>

</credit>

<taxExempt>false</taxExempt>

</enhancedData>

</capture>

<authCode>authka</authCode>

</authInformation>

<orderSource>telephone</orderSource>

<card>

</card>

<taxExempt>false</taxExempt>

</enhancedData>

</captureGivenAuth>

</batchRequest>

</litleRequest>

Response:

<message>Approved</message>

</captureResponse>

<message>Approved</message>

</captureGivenAuthResponse>

<message>Approved</message>

</creditResponse>

</batchResponse>

</litleResponse>

Litle Batch Deposit Request Message

CWSerenade generates the Litle Batch Deposit Request message when you run deposits for the Litle Point-to-Point Deposit Process. The message includes one or more of the following types of transactions:

• Capture: used to debit the customer’s card. CWSerenade flags a transaction as a Capture transaction if the transaction type is *PURCH and the deposit is associated with an authorization history record that contains a Litle transaction ID.

• Credit: used to transfer previously authorized funds from the customer to you after order fulfillment. CWSerenade flags a transaction as a Credit transaction if the transaction type is *RETURN.

• Capture Given Auth: used to debit the customer’s card. CWSerenade flags a transaction as a Capture Given Auth transaction if the transaction type is *PURCH and the deposit is NOT associated with an authorization history record that contains a Litle transaction ID, indicating the authorization was not authorized by Litle (for example, the authorization occurred over the phone or on the web).

Sample transactions: See Sample Litle Transactions.

Special characters: Certain special characters cannot be passed in an attribute of an XML message except through the use of replacement text strings. CWSerenade replaces the following special characters with the text strings listed below.

Special Character	Description	Replacement Text String
’	single quote	'
"	double quote	"
>	greater than	>
<	less than	<
&	ampersand	&

The elements and attributes of the Litle Batch Deposit Request message that are used by CWSerenade are described below. See the Litle & Co. XML Reference Guide for more information on the additional values in this message.

Name	Comments
litleRequest Contains header information for the Batch Deposit Request. Each litleRequest can contain one or more batchRequests.
version	8.1 defaults.
xmlns	http://www.litle.com/schema defaults.
id	Blank filled for the Litle Point-to-Point integration.
numBatchRequests	The number of batch requests included in the transaction. Each batch request can contain up to 10,000 transactions. Example: If you run deposits for 14,000 transactions, the system sends two batch IDs to Litle, with batch ID 1 containing 10,000 transactions and batch ID 2 containing 4,000 transactions: • batchRequest Id=1 • deposit 1 • deposit 2, etc. • deposit 10,000 • batchRequest Id=2 • deposit 10,001 • deposit 10,002, etc. • deposit 14,000
authentication Contains merchant authentication information.
user	The user ID used to authenticate that the message is from a valid source. From the ASV Signon field for the LTD service in the Authorization Service table.
password	The user’s password. From the ASV Password field for the LTD service in the Authorization Service table.
batchRequest Each batchRequest can contain multiple credit, capture, and captureGivenAuth transactions.
id	The batch ID to identify the batch request in the Litle system, starting with number 1. Each batch request can contain up to 10,000 transactions. Example: If you run deposits for 14,000 transactions, the system sends two batch IDs to Litle, with batch ID 1 containing 10,000 transactions and batch ID 2 containing 4,000 transactions: • batchRequest Id=1 • deposit 1 • deposit 2, etc. • deposit 10,000 • batchRequest Id=2 • deposit 10,001 • deposit 10,002, etc. • deposit 14,000
numCaptures	The total count of capture transactions in the batch request.
captureAmount	The total dollar amount of capture transactions in the batch request. The decimal point is implied; for example 2500 represents $25.00. From the Total $ amt in the CC Deposit Transaction table.
numCaptureGivenAuths	The total count of captureGivenAuth transactions in the batch request.
captureGivenAuthAmount	The total dollar amount of captureGivenAuth transactions in the batch request. The decimal point is implied; for example 2500 represents $25.00. From the Total $ amt in the CC Deposit Transaction table.
numSales	The total count of Sales transactions in the batch request. 0 defaults for the Litle Point-to-Point integration.
saleAmount	The total dollar amount of Sales transactions in the batch request. 0 defaults for the Litle Point-to-Point integration.
numCredits	The total count of credit transactions in the batch request.
creditAmount	The total dollar amount of credit transactions in the batch request. The decimal point is implied; for example 2500 represents $25.00. From the Total $ amt in the CC Deposit Transaction table.
merchantId	The account number assigned by Litle to identify transmissions; this is the merchant ID specified for the LTD service bureau. From the: • Merchant # in the CC Paytype Cross Ref table. • Merchant ID override in the Merchant ID Override table. • ASV Merchant ID in the Authorization Service table.
credit Contains one or more credit transactions. CWSerenade flags a transaction as a Credit transaction if the transaction type is *RETURN.
id	The CWSerenade company code + order number + order payment method sequence number defined for the Credit transaction. From the CMP Company + Order # + OPM Seq # in the CC Deposit Transaction table.
reportGroup	The account number assigned by Litle to identify transmissions; this is the merchant ID specified for the LTD service bureau. From the: • Merchant # in the CC Paytype Cross Ref table. • Merchant ID override in the Merchant ID Override table. • ASV Merchant ID in the Authorization Service table.
orderId	The CWSerenade company code + order number + order payment method sequence number defined for the Credit transaction. From the CMP Company + Order # + OPM Seq # in the CC Deposit Transaction table.
amount	The amount of the credit transaction. The decimal point is implied; for example 1087 represents $10.87. From the Total $ amt field in the CC Deposit Transaction table.
orderSource	ecommerce defaults if the order is an ecommerce (web) order. telephone defaults if the order is not an ecommerce (web) order. From the Ecomm Indic in the Order Payment Method table. If this value is blank, from the E-Commerce Indicator (Future use 1) in the Order Header table.
card Included for each credit transaction.
type	The vendor pay type code defined for the credit card pay type. This is the code Litle uses to identify the method of payment. From the CPC vendor paytype/code in the CC Paytype Cross Ref table.
number	The credit card number. From the Credit card # in the CC Deposit Transaction table.
expDate	The month and year when the card expires, in MMYY format. From the OPM Expiration date in the Order Payment Method table.
enhanceData Included only if the credit transaction qualifies for level II discounting; see Level II and III Discounting.
customerReference	The CWSerenade purchase order number; if a purchase order number is not specified on the order, this is the CWSerenade order number. From the: • Purchase order # in the Order Ship To table. • Order # in the CC Deposit Transaction table.
salesTax	The amount of sales tax included in the transaction amount. The decimal is implied; for example 150 represents $1.50. From the Total tax $ amt in the CC Deposit Transaction table.
taxExempt	Defines whether the transaction is exempt from sales tax. true = The transaction is exempt from sales tax. false (or not included) = The transaction is not exempt from sales tax.
capture Contains one or more capture transactions. CWSerenade flags a transaction as a Capture transaction if the transaction type is *PURCH and the deposit is associated with an authorization history record that contains a Litle transaction ID.
id	The CWSerenade company code + order number + order payment method sequence number defined for the Capture transaction. From the CMP Company + Order # + OPM Seq # in the CC Deposit Transaction table.
reportGroup	The account number assigned by Litle to identify transmissions; this is the merchant ID specified for the LTD service bureau. From the: • Merchant # in the CC Paytype Cross Ref table. • Merchant ID override in the Merchant ID Override table. • ASV Merchant ID in the Authorization Service table.
partial	true defaults.
litleTxnId	The authorization request transaction ID defined for the associated authorization transaction. From the AUH Transaction ID field in the Authorization History table.
amount	The amount of the debit transaction. The decimal point is implied; for example 1087 represents $10.87. From the Total $ amt in the CC Deposit Transaction table.
enhanceData Included only if the capture transaction qualifies for level II discounting; see Level II and III Discounting.
customerReference	The CWSerenade purchase order number; if a purchase order number is not specified on the order, this is the CWSerenade order number. From the: • Purchase order # in the Order Ship To table. • Order # in the CC Deposit Transaction table.
salesTax	The amount of sales tax included in the transaction amount. The decimal is implied; for example 150 represents $1.50. From the Total tax $ amt in the CC Deposit Transaction table.
taxExempt	Defines whether the transaction is exempt from sales tax. true = The transaction is exempt from sales tax. false (or not included) = The transaction is not exempt from sales tax.
captureGivenAuth Contains one or more captureGivenAuth transactions. CWSerenade flags a transaction as a CaptureGivenAuth transaction if the transaction type is *PURCH and the deposit is NOT associated with an authorization history record that contains a Litle transaction ID (for example, the authorization occurred over the phone or on the web).
id	The CWSerenade company code + order number + order payment method sequence number defined for the CaptureGivenAuth transaction. From the CMP Company + Order # + OPM Seq # in the CC Deposit Transaction table.
reportGroup	The account number assigned by Litle to identify transmissions; this is the merchant ID specified for the LTD service bureau. From the: • Merchant # in the CC Paytype Cross Ref table. • Merchant ID override in the Merchant ID Override table. • ASV Merchant ID in the Authorization Service table.
orderId	The CWSerenade company code + order number + order payment method sequence number defined for the CaptureGivenAuth transaction. From the CMP Company + Order # + OPM Seq # in the CC Deposit Transaction table.
authInformation Included for each captureGivenAuth transaction.
authDate	The date of the associated authorization transaction, in YYYY-MM-DD format. From the AUH Auth Date in the Authorization History table.
authCode	The authorization number for the associated authorization transaction. From the AUH Auth # in the Authorization History table.
authAmount	The amount of the associated authorization transaction. The decimal point is implied; for example 1087 represents $10.87. From the AUH Amount Authorized in the Authorization History table.
amount	The amount of the debit transaction. The decimal point is implied; for example 1087 represents $10.87. From the Total $ amt in the CC Deposit Transaction table.
orderSource	ecommerce defaults if the order is an ecommerce (web) order. telephone defaults if the order is not an ecommerce (web) order. From the Ecomm Indic in the Order Payment Method table. If this value is blank, from the E-Commerce Indicator (Future use 1) in the Order Header table.
card Included for each captureGivenAuth transaction.
type	The vendor pay type code defined for the credit card pay type. This is the code Litle uses to identify the method of payment. From the CPC vendor paytype/code in the CC Paytype Cross Ref table.
number	The credit card number. From the Credit card # in the CC Deposit Transaction table.
expDate	The month and year when the card expires, in MMYY format. From the OPM Expiration date in the Order Payment Method table.
enhanceData Included only if the captureGivenAuth transaction qualifies for level II discounting; see Level II and III Discounting.
customerReference	The CWSerenade purchase order number; if a purchase order number is not specified on the order, this is the CWSerenade order number. From the: • Purchase order # in the Order Ship To table. • Order # in the CC Deposit Transaction table.
salesTax	The amount of sales tax included in the transaction amount. The decimal is implied; for example 150 represents $1.50. From the Total tax $ amt in the CC Deposit Transaction table.
taxExempt	Defines whether the transaction is exempt from sales tax. true = The transaction is exempt from sales tax. false (or not included) = The transaction is not exempt from sales tax.

Litle Batch Deposit Response Message

Litle generates the Litle Batch Deposit Response message when it processes a Litle Batch Deposit Request Message received from CWSerenade. The message includes one or more of the following types of transactions:

• Capture Given Auth: used to debit the customer’s card. CWSerenade flags a transaction as a Capture Given Auth transaction if the transaction type is *PURCH and the deposit is NOT associated with an authorization history record that contains a Litle transaction ID (for example, the authorization occurred over the phone or on the web).

Sample transactions: See Sample Litle Transactions.

The elements and attributes of the Litle Batch Deposit Response message that are received by CWSerenade are described below. See the Litle & Co. XML Reference Guide for more information on the additional values in this message.

Name	Comments
litleResponse Contains header information for the Batch Deposit Response. Each litleResponse can contain one or more batchResponses.
version	The Litle XML schema version against which the XML is validated. 8.1 defaults.
xmlns	http://www.litle.com/schema defaults.
id	Blank filled for the Litle Point-to-Point integration.
response	Indicates whether the XML syntax passed validation. 0 = XML validation succeeded. 1 = XML validation failed.
message	XML validation message. Valid Format = XML validation succeeded. Any other value explains why XML validation failed to help you troubleshoot the problem.
littleSessionId	The session ID specified by Litle.
batchResponse Each batchResponse can contain multiple captureResponse, captureGivenAuthResponse, and creditResponse transactions.
id	The batch id from the associated Litle Batch Deposit Request Message.
litleBatchId	The batch ID to identify the batch in the Litle system.
merchantId	The merchantId from the associated Litle Batch Deposit Request Message.
captureResponse Included for each capture in the associated Litle Batch Deposit Request Message.
id	The id from the associated Litle Batch Deposit Request Message.
reportGroup	The reportGroup from the associated Litle Batch Deposit Request Message.
litleTxnId	The Litle transaction ID defined for the Capture transaction.
orderId	The CWSerenade company code + order number + order payment method sequence number defined for the Capture transaction. Updates the CMP Company, Order #, and OPM Seq # in the CC Deposit History table.
response	Defines whether the Capture transaction was approved (000) or declined. Updates the CDH Response code in the CC Deposit History table. If approved, CWSerenade updates the CDH Status in the CC Deposit History table to C Confirmed.
responseTime	The date and time of the response, in YYYY-MM-DDTHH:MM:SS format. Updates the CDH Deposit date in the CC Deposit History table.
message	A description of the response code returned for the transaction.
captureGivenAuthResponse Included for each captureGivenAuth in the associated Litle Batch Deposit Request Message.
id	The id from the associated Litle Batch Deposit Request Message.
reportGroup	The reportGroup from the associated Litle Batch Deposit Request Message.
litleTxnId	The Litle transaction ID defined for the CaptureGivenAuth transaction.
orderId	The CWSerenade company code + order number + order payment method sequence number defined for the Capture transaction. Updates the CMP Company, Order #, and OPM Seq # in the CC Deposit History table.
response	Defines whether the CaptureGivenAuth transaction was approved (000) or declined. Updates the CDH Response code in the CC Deposit History table. If approved, CWSerenade updates the CDH Status in the CC Deposit History table to C Confirmed.
responseTime	The date and time of the response, in YYYY-MM-DDTHH:MM:SS format. Updates the CDH Deposit date in the CC Deposit History table.
message	A description of the response code returned for the transaction.
creditResponse Included for each credit in the associated Litle Batch Deposit Request Message.
id	The id from the associated Litle Batch Deposit Request Message.
reportGroup	The reportGroup from the associated Litle Batch Deposit Request Message.
litleTxnId	The Litle transaction ID defined for the Credit transaction.
orderId	The CWSerenade company code + order number + order payment method sequence number defined for the Credit transaction. Updates the CMP Company, Order #, and OPM Seq # in the CC Deposit History table.
response	Defines whether the Credit transaction was approved (000) or declined. Updates the CDH Response code in the CC Deposit History table. If approved, CWSerenade updates the CDH Status in the CC Deposit History table to C Confirmed.
responseTime	The date and time of the response, in YYYY-MM-DDTHH:MM:SS format. Updates the CDH Deposit date in the CC Deposit History table.
message	A description of the response code returned for the transaction.

Cybersource Message Layouts

Contents

SCVs

Search

Glossary

Reports

Database

Solutions

XML

Index

Purging Tables

SO04_16LTD Serenade 5.0 March 2015