Bookshelf Home | Contents | Index | Search | PDF |
Siebel eAuction Guide > Configuring the Siebel eAuction Environment > Using Third-Party Security >
Integration Objects Used with Credit Cards and Invoicing
Integration objects are used to pass static or dynamic values to the business service.
The following Integration Objects are used in the Credit Card approval process:
- CreditCard - Invoice - AuthCharge (Siebel Input)
- CreditCard - Invoice - Authorization (Siebel Input)
- CreditCard - Invoice - Authorization (Siebel Output)
- CreditCard - Invoice - Charge (Siebel Input)
- CreditCard - Invoice - Charge (Siebel Output)
- CreditCard - Invoice - Refund (Siebel Input)
- CreditCard - Invoice - Refund (Siebel Output)
In addition, there must be appropriate counterparts for each of these for the credit card processing service being used. For example, for CyberSource:
- CreditCard - AuthCharge (CyberSource Output)
- CreditCard - Authorization (CyberSource Input)
- CreditCard - Authorization (CyberSource Output)
- CreditCard - Charge (CyberSource Input)
- CreditCard - Charge (CyberSource Output)
- CreditCard - Refund (CyberSource Input)
- CreditCard - Refund (CyberSource Output)
The integration maps specific to eAuction are:
- CreditCardAuthCharge_CyberSource2Invoice
- CreditCardAuthorization_CyberSource2Invoice
- CreditCardAuthorization _ Invoice2CyberSource
- CreditCardCharge_CyberSource2Invoice
- CreditCardCharge_ Invoice2CyberSource
- CreditCardRefund_CyberSource2Invoice
- CreditCardRefund_Invoice2CyberSource
NOTE: Many of these integration components are detailed in Siebel eSales Administration Guide.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel eAuction Guide Published: 18 April 2003 |