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.
Common usage: The payment method that is commonly associated with this rule is:
- Credit card transactions
Target states: This rule specifies that the following payment actions should take place for a mapped payment method:
Payment event Target state of payment Description prime payment DNE The target state of the payment does not exist; no payment action is taken when the order is captured. reserve payment APPROVED The payment is approved when the order is released to fulfillment. Specifically, ensure the payment is in the APPROVED state. If it is, take no action. If it is not, approve it. If it is only partially approved, ensure that the difference is approved.
finalize payment DEPOSITED The payment is deposited when the order is shipped.
Example 1: Credit card payment with single release
A customer places an order for three items that total 300 U.S. dollars. All items are available for shipment. The customer uses a credit card to pay for the whole order. The payment instruction is to use a credit card payment method and amount of 300 USD.
Payment event Validation amount Reservation amount Finalization amount Back-end system Amount approved Amount deposited prime payment (order capture) 300 0 0 - - reserve payment (release to fulfillment) A release has been created (release A).
300 300 0 300 0 finalize payment (shipping) 300 300 300 300 300
Example 2: Credit card payment with single release but payment fails
A customer places an order for three items that total 300 USD. All items are available for shipment. The customer uses a credit card to pay for the whole order. The credit card is denied. The Customer Service Representative contacts the customer and corrects the expiration date of the credit card. Because the payment rule used does not require payment action during validation, the error is not discovered until payment reservation, after which time the edit occurs.
Payment event Validation amount Reservation amount Finalization amount Back-end system Amount approved Amount deposited Amount failed prime payment (order capture) 300 0 0 - - - reserve payment (release to fulfillment) A release has been created (release A).
300 0 0 0 0 300 A reserve payment action occurs again, using the correct payment information. 300 300 0 300 0 0 finalize payment (shipping) 300 300 300 300 300 0