Reference > Payments subsystem
Payment rules provided in WebSphere Commerce
Payment rules specify the payment actions that should occur for the payment methods a store accepts for its goods or services. Payment actions and credit actions are determined in terms of current-to-target state movements. payment rules define what target state a payment should be in by defining the actions needed to move a payment from its current state to the target state.
During payment rules processing, for each specific time in the order life cycle, payment rules are read to find the payment actions required to achieve the target state for the payment amount. The following list defines the relationship of order life cycle phases and the corresponding payment events:
- The order capture life cycle phase corresponds to the PrimePayment payment event.
- The release to fulfillment life cycle phase corresponds to the ReservePayment payment event.
- The fulfillment (shipment confirmation) life cycle phase corresponds to a FinalizePayment payment event.
In effect, these order life cycle phases are translated to payment events.
Rule PrimePaymentCmd (at order capture) ReservePaymentCmd (at release to fulfillment) FinalizePaymentCmd (at shipping) Description No Validation or Reservation payment rule DNE DNE DEPOSITED Do not check to see if customer has funds at order capture, do not reserve funds before releasing to fulfillment; only deposit at shipping. Typically applies to: electronic check (Automated Clearing House, ACH) transactions.
No Validation with Approval on Reservation payment rule DNE APPROVED DEPOSITED Do not check to see if customer has the funds at order capture, but reserve funds before releasing to fulfillment and deposit payment at shipping. Typically applies to: credit card transactions.
No Validation with Deposit at Reservation payment rule DNE DEPOSITED DEPOSITED Do not check to see if customer has funds at order capture, but deposit payment at release to fulfillment. Typically applies to: electronic check (ACH) transactions.
Early Approval payment rule APPROVED APPROVED DEPOSITED Check to see that customer has funds to pay for the order when the order is captured; that is, validate the payment at the earliest opportunity. Typically applies to: credit card transactions.
Validation with Deposit at Reservation payment rule APPROVED DEPOSITED DEPOSITED Check to see that the customer has funds to pay for the order when it is captured, and ensure that deposits occur at release to fulfillment. Typically applies to: Credit card transactions.
Early Deposit payment rule DEPOSITED DEPOSITED DEPOSITED Deposit funds as soon as possible - at order capture or at release to fulfillment. Typically applies to: electronic check (ACH) transactions.
Because the task command called StoreAndValidatePaymentCmd does not have configurable actions, it is not listed in the following table.
Although no payment action occurs during order capture when the target state is DNE, payment instructions are still validated.
- No Validation or Reservation payment rule
The No Validation or Reservation payment rule triggers a Deposit action when the order is fulfilled. No payment action is taken before the Deposit action.
- No Validation with Approval on Reservation payment rule
The No Validation with Approval on Reservation payment rule triggers an Approve action at release to fulfillment and a Deposit action at fulfillment. Deposits can take place as they occur, or they can be accumulated for deposit in a single transaction when more than one release is involved.
- No Validation with Deposit at Reservation payment rule
The No validation with Deposit at Reservation payment rule triggers Deposit actions at both release to fulfillment and fulfillment. When more than one release is involved, the amounts are deposited as they occur and are not accumulated to be deposited at once. This rule might not be considered legal in some countries or regions.
- Early Approval payment rule
The Early Approval payment rule triggers Approve actions at both order capture and release to fulfillment, and a Deposit action at fulfillment. Deposits can take place as they occur, or they can be accumulated for deposit in a single transaction when more than one release is involved.
- Validation with Deposit at Reservation payment rule
The Validation with Deposit at Reservation payment rule triggers an Approve payment action at order capture, and Deposit actions at both release to fulfillment and fulfillment. Deposits can take place as they occur, or they can be accumulated for deposit in a single transaction when more than one release is involved. This rule might not be considered legal in some countries or regions.
- Early Deposit payment rule
The Early deposit payment rule triggers Deposit payment actions at order capture, release to fulfillment, and fulfillment. Deposits take place as they occur. When more than one release is involved, the amounts are deposited as they occur and are not accumulated to be deposited at once. In this rule, funds are captured as quickly as possible. You might want to use this rule if you are not concerned about incurring extra transaction fees for doing early deposits. This rule is recommended if the store sells fairly expensive goods and you have a low tolerance for risk. This rule might not be considered legal in some countries or regions.
Related concepts
Payment events and task commands