The Setup tab in the Payment Processing settings of the administration interface has a Payment Options drop-down that controls certain aspects of how split payments are processed in Commerce Cloud. This drop-down has two options:

For a registered shopper, partially paid orders are persisted and appear in the shopper’s order history. The shopper can retrieve a partially paid order from the list and complete it. If the Order Payment Initiated email is enabled in the administration interface, an email is sent to the shopper when the order is created. The email includes the order ID. The shopper can use this ID to help locate and retrieve the order, or supply the ID to a customer service agent, who can then complete the order in the Agent Console.

For an anonymous shopper, the shopper must complete a partially paid order before the session times out, because the shopper has no way to access the order when returning to the site later. However, if the Order Payment Initiated email is enabled, the shopper is sent an email with the order ID when the order is created, and can supply this ID to a customer service agent for completing the order.

If a partially paid order is not completed before the price hold period expires, the order is marked for cancellation and is subsequently removed. To handle the actual removal of orders, a scheduled service is run. This is the same service used in account-based commerce to remove orders that have been approved but not paid for after the specified amount of time. See Set the frequency of canceled order clean up for information about configuring this service.

Partial payments must be enabled if any of the payment methods you support requires the shopper to take action while the payment is being processed. For example, if you have a credit card gateway integration that supports 3D-Secure, when the payment is processed, the shopper must authenticate with the card provider. Enabling partial payments ensures that payments are processed sequentially, preventing the authentication pages for multiple payments from displaying simultaneously or overwriting each other.


Copyright © 1997, 2017 Oracle and/or its affiliates. All rights reserved. Legal Notices