CWIntegrate Authorization and Deposit Setup
Purpose: Before you can process authorizations and deposits using CWIntegrate, you must perform the necessary setup. Information requiring creation and set up includes:
• Integration Layer Process Settings for Authorization/Deposit
For more information: See Authorization/Deposit Setup for more information on the setup required to perform authorizations.
To send transactions to the service bureau, you need to create it in Defining Authorization Services (WASV), making sure to define:
• Online authorization integration layer process: Enter the code for the integration layer process that sends online authorization requests to the service bureau.
• Batch authorization integration layer process: Enter the code for the integration layer process that sends batch authorization requests to the service bureau.
• Deposit: Enter the code for the integration layer process that sends batch deposit requests to the service bureau.
• SVC activation integration layer process: Enter the code for the integration layer process that sends stored value card activation requests to the service bureau.
• SVC balance inquiry integration layer process: Enter the code for the integration layer process that sends stored value card balance inquiry requests to the service bureau.
• Batch/online: Enter C to indicate the service bureau processes both batch messages and online messages.
• Immediate response: Select this field to indicate that the service bureau immediately sends a response back for each authorization request.
• Immediate deposit: Unselect this field to indicate that service bureau sends a detailed response back to CWSerenade.
• Primary authorization service: Enter.IL to indicate request XML messages sent to and from the service bureau are processed through the CWIntegrate site.
Integration service bureau: To send transactions to the service bureau using CWIntegrate, create a service bureau using the service code.IL and enter a value in the following fields:
• Application: ATDP (authorization and deposit)
• Merchant ID: INTEGRATION LAYER
• Charge description: CWIntegrate
• Media type: C (communications)
Integration Layer Process Settings for Authorization/Deposit
Set up an integration layer process for each type of transaction you wish to send to the service bureau. The delivered integration layer processes that send transactions to a service bureau are:
• Batch authorizations
• Online authorizations
• Batch deposit/settlement
• Interactive stored value card balance inquiry
• Batch stored value card activation
• Batch stored value card authorization reversal
For each integration layer process, make sure you define:
• an outbound queue manager and queue to send the request to the service bureau via the CWIntegrate site.
• an inbound queue manager and queue to receive the response from the service bureau via the CWIntegrate site.
Note: You can only define one outbound and inbound queue for each integration layer process. If you create multiple queues, the system sends and receives data in the queue whose Sequence number is 1; all other queues are ignored.
For more information: See Working with Integration Layer Processes (IJCT) for more information on setting up an integration layer process.
The Batch Auth File Trace Number number assignment value assigns the next available number to the merchantFileTrace value in the Authorization Request XML Message (CWAuthorizationRequest) and Deposit Request XML Message (CWDepositRequest) sent to the service bureau. CWSerenade updates the Reference ID field in the Integration Process Control table with this value.
Important:
• The Batch Auth File Trace Number can be up to 7 positions for the Paymentech service bureau; however, this number cannot be greater than 3 positions for other service bureaus. Enter 999 in the End number field for this number assignment value to ensure that this number does not exceed 3 positions.
• If you are using more than one CWSerenade company, make sure that the Batch Auth File Trace Number for each company has a different number and that the numbers do not overlap. For example, company 1 uses 1-499 and rolls back to 1 again and company 2 uses 500-999 and rolls back to 500 again
