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

Credit Card Transaction Service Business Service

The Credit Card Transaction Service process flow follows.

• Siebel EAI passes data from a quote record and the method name to a Siebel output integration object.
• The Siebel Data Transformation Engine maps the Siebel output integration object to a CyberSource input integration object.
• The Siebel EAI XML Converter converts the vendor input integration object into XML, using the CC XML Converter Business Service, and passes the XML data and method name to the CyberSource Adapter Service.
• The CyberSource Adapter Service business service processes the data, converts it into Siebel eScript, and passes it to CyberSource using the CyberSource API.
• The CyberSource Adapter Service gets the payment information from CyberSource in Siebel eScript through the CyberSource API.
• The CyberSource Adapter Service formats the payment information into an XML string.
• The Siebel EAI XML Converter converts the XML into a vendor output integration object.
• The Siebel Data Transformation Engine maps the vendor output integration object to a Siebel input integration object.
• Siebel EAI updates the quote record with the payment information.

Business Service Methods

The Credit Card Transaction Service has business service methods for each of the following types of credit card transaction:

• AuthCharge. This transaction authorizes and settles charges. It makes sure that the funds are available, reserves them, and requests that they be transferred in one call. It does this in the case of immediate order fulfillment (for example, digital downloads).
• Authorization. Called from the eSales - Authorize Order Process workflow, this transaction allocates to the merchant a specific amount of the credit available to the cardholder, typically for one week. No funds are transferred.

  The merchant authorizes a credit card to make sure of the following:

  • The customer has the funds to pay for the purchase.
  • These funds are reserved until the merchant is able to ship the product. Credit card companies typically state that a merchant should not settle until the product has been shipped.
• Charge. This transaction is used to settle charges. A settlement request includes the authorization code and requests that funds be transferred from the cardholder's account to the merchant's bank account.
• Process. This transaction is not used, but is available to customers for calling other methods from the third-party adapter.
• Refund. A refund takes place after a settlement when the merchant needs to transfer money back to the cardholder, as in the case of a return.
• Reverse. This transaction releases the amount of money reserved by an authorization. Although it is not supported by CyberSource, Reverse is important because authorizations reserve part of a cardholder's credit and therefore reduce the total amount of credit available.

  The arguments for these methods are:

  • Input:
    • Row Id
    • Siebel Input Integration Object
    • Siebel Output Integration Object
    • Siebel to Vendor Map Name
    • Vendor to Siebel Map Name
    • Vendor Name
  • Output:
    • Credit Card Response Code
    • Credit Card Response Message
• Validate. Validation checks the credit card number, using the Mod 10 algorithm to make sure that it is valid, and the expiration date. The Siebel Business Application—not CyberSource—does this during rapid checkout and after selecting and saving payment information.

  The arguments for Validate are:

  • Input:
    • Credit Card Number
    • Credit Card Type
    • Expiration Month
    • Expiration Year
    • Return Error Code
  • Output: Error Message

Business Service User Properties

The business service user properties specify the adapter business service to call, the configuration object to use, the vendor integration objects to use, and the text of the error messages. The active business service user properties are shown in Table 7.

The complete response messages, and not the codes, are shown in the Siebel eSales application.

For more information on modifying business service user properties, see Using Siebel Tools.