Item should have attribute for supported payment modes

[BLR-0118]

Buyers often prefer to select items, from a catalog, based on the payment criteria (e.g. cash, digital). Currently, when catalog displays an item, it is not clear what the payment criteria is for that item. Item should support an attribute for supported_payment_modes with enums of "Cash", "Digital".

[BLR-0118]

Pramod, tagging you since Ravi suggested you have thoughts on this
@pramodkvarma

[pramodkvarma]

I thought we did have attributes that can carry promotional tags. Could we use that instead of fully structured payment object? Also, remember to make catalogue caching easier and have all dynamic info come through during select call. But if we can't leverage existing tags we can explore additional tags. @core-wg-admin

[ravi-prakash-v]

@pramodkvarma @BLR-0118 FYR, the current Provider schema in 0.9.4-draft is shown here

As you can see it has a property called payments that is an array of objects of type Payment.

Each of these Payment objects contain a unique payment policy of a Provider.

I believe it would be more useful to tag each item with a reference to a particular Payment policy rather than a single attribute of payment i.e payment mode. That would make it more generic and would allow a larger set of use cases to be covered.

However to enabled this, there are two changes to be made here.

Firstly, the Payment object must have an id property so that it can be referenced at other places.

Secondly, the Item schema must have a reference to a Payment object inside the payments array using a property called payment_id.

Similarly, the Provider schema must also have a payment_id property that allows a default Payment policy to be defined all across the provider's catalog overriden only by the payment_id at the Item level.

[pramodkvarma]

Would like to see a sample json before and after (based on above proposal) to make it easier for me to fully understand. Or if there is wiki/doc page on it point me to that. Thanks.