Ticklers created by Payment Rules
The Payment Rules subcomponent creates tickler messages that alert the Customer Service Representative (CSR) whenever a failure occurs in processing. The messages are generated by the system and appear in the IBM Sales Center tickler list in the CSR's user interface.
Customer Service Representatives are notified of problems that cannot be automatically resolved immediately, or of situations that require further attention. Tickler messages generated by Payment Rules are displayed in a tickler queue. They are associated with an ORDER or RMA object type in the tickler detail, depending on whether the situation was associated with an order payment or a refund.
The following components do not create payment-related ticklers:
- WebSphere Commerce Payments
- Payment plug-ins
- The WebSphere Commerce Payments component
- Payment cassettes
Payment plug-ins can set a flag indicating attention is required during payment or credit transactions when an Address Verification Service (AVS) check on a credit card indicates a mismatch with the cardholder's billing address on file. Payment plug-ins can also set the attention flag for other situations.
The following circumstances generate payment-related ticklers:
- An event is forced. For example, an order edit might forcibly occur even though payment has already been deposited.
- An order is changed or edited. For example, a credit card number changes and the original credit card number was already used for payment. A tickler is generated only if a deposit occurred and needed to be reversed.
- An order release is edited. For example, a last-chance edit occurs and new items are added after the order is released to fulfillment and as a result the payment amount increases.
- An unqualified AVS transaction occurred and intervention is required.
- Financial failures with the payment back-end system.
- An order with a payment amount and no payment instructions
- The deposited amount is bigger than the order total amount
(C) Copyright IBM Corporation 1996, 2006. All Rights Reserved.