The general idea with PaymentPreferences (regardless of what each PaymentPreference represents) is that all but one should have a limit amount, and the one that does not have a limit amount inherits the balance of the order after the other PPs have been considered.
If this is properly applied in the checkout process then no such preference should be needed. I know there are issues with the current code setting the max amount automatically, it is not extremely well implemented for the case where a user gets to the order verification page and then goes back to earlier pages in the checkout process (ie it leaves the max amount for the PP even if the order total has changed). I may be wrong, but it seems this pattern of having all PPs but one contain a max amount and putting the rest on the remaining PP would allow the user to select where things should go and support both scenarios you mentioned. -David Si Chen wrote:
Hi.We just noticed that if an order had a billing account (OrderHeader.billingAccountId) and a credit card associated with it, only the credit card should be charged. This should be the right behavior if the billing account is used for wholesale customers as a line of credit, but if the billing account is a retail consumer's store credit (arising from a return), then most retailers would want the store credit used up first.So, how about we add a ProductStore field to control whether the billing account should be used before other payment methods?Si
smime.p7s
Description: S/MIME Cryptographic Signature
