Siebel eSales Administration Guide > Using Third-Party Payment Applications > CyberSource Integration with Siebel eSales >

Integration Objects


Integration objects are used to pass values, static or dynamic, to the business service. The architecture is modular, in that different integration objects can be created and used for the same core business service.

The integration objects for the Quote and Order business components and CyberSource are detailed here. Integration objects also exist for the Auction Invoice business component.

Configuration

CreditCard - Configuration (CyberSource) has the user properties shown in Table 19.

Table 19. Credit Card - Configuration (CyberSource) User Properties
User Property
Value
Comments
VendorDll
ics2api
Do not use prefix and extension.
This is necessary for compatibility with Solaris.
customer_email
nobody@nowhere.com
CyberSource enforces the format.
customer_phone
(000) 000-0000
CyberSource requires at least six digits.
ignore_avs
no
CyberSource needs "yes" or "no."
This is only used for the AuthCharge transaction.
merchant_id
ICS2Test
CyberSource varchar(20), case-sensitive.
Change this to your merchant ID. You can obtain a merchant ID for each division of your organization. The merchant IDs are set in the Divisions view under the Group Administration screen.
server_host
ics2test.ic3.com
 
server_port
80
 
timeout
90
In seconds. The default is 90.
decline_avs_flags
N
Comma-separated list of AVS codes that result in an AVS decline.
For more information, see Address Verification with CyberSource.

Authorization

Settle (Charge)

Authorize and Settle (AuthCharge)

Refund

For more information on integration objects, see Integration Platform Technologies: Siebel eBusiness Application Integration Volume II and Siebel Tools Reference.


 Siebel eSales Administration Guide 
 Published: 18 April 2003