This event is associated with the order capture. When the order is captured, this event provides some guarantee that the customer has funds to pay for the order. Like the storeAndValidate event, the purpose of this event is for the merchant to find out whether a payment is bad before the customer is disengaged. An event-driven payments order and payment instructions are created during the processing of this type of event. An event-driven payments order corresponds to the payment portion of a WebSphere Commerce order, and can have multiple releases associated with it.
The primePayment event is not optional; it always occurs.
Two forms of the primePayment event exist: one with payment instructions, and one without payment instructions:
- When the event is associated with payment instructions, each payment instruction is validated. This event is used when the storeAndValidate business event has not occurred.
- When the primePayment event is not associated with payment instructions, no validation takes place. This event occurs when the storeAndValidate event has already occurred.
The possible payment actions associated with this event are: Validation, Approve, and Deposit.
Example:
- A customer shops at a store, submits an order and specifies that a particular credit card should be used as the payment method.
- (B2B) An order requiring buyer approval is entered.
A primePayment event occurs and the event-driven payment rules are read to determine what payment actions should take place for the payment method. Payment actions are configurable. For example, for credit cards, the default behavior is to check to ensure that the customer has sufficient credit and the card has not expired. If the credit card is fine, the payment is approved. If a payment action with the payment back-end system fails, a tickler is created to notify a Customer Service Representative. Other scenarios might involve other actions, such as depositing the funds immediately.