Suggestion - Expand the PaymentStatus Enum

Hi Andrei,

Would you mind adding another value in your Payment Stats (public enum PaymentStatus) for your 3.6 release.
Something like;
/// <summary>
        /// Partial Payment
        /// </summary>
        PartialPaid = 100,

I have done a few payment plugins lately to support layaway, partial payments with echeck and this is one component I can't handle with plugins.

Thank you

Hi Chuck,

Thanks for suggestion. This work item (payments by installments) is still on the roadmap. Its addition (enum) is not enough, other logic (e.g. order status changing) should be also updated according to new enum. If I add this new payment status enum without its real support and usage, then it can confuse other developers.

Hi Andrei,

I had to use a combination of route overrides, action filters, etc. to handle the additional logic to support the partial payments approach in my plugins that your talking about.  The actual core status hook is the only component though that prevents me from distributing these on the 3.5 platform.
Looking at your work item, a lot of the "heavy lifting" the plugins are doing will be moved to the core, which will be great (and prevent some code duplication which I am having to deal with).  You are correct, developers may leverage this in an unpredictable way until the underpinning architecture is fully supported.  Perhaps in 3.7 then.

Thanks again,