Hi!
We are starting the design of a process-API to implement the necessary business logic to decide which payment methods will be available for a customer to choose, depending on a set of data sent to this api as context (channel, customer status, customer credit limit, total amount of products in cart, etc.)
I guess it can be similar to ProductOfferingQualification, I mean, from the full list of payment methods, this api should make some validations, execute some business rules, and return a qualified list of methods, with "eligibilityUnavailabilityReason", saying for each method, the reasons why it cannot be used.
The question is: should this process be part of TMF670 (a new endpoint "/qualification"), or a new API? Have anyone faced a similar scenario?
Best Regards,
Eduardo
------------------------------
Eduardo Lo Presti
Telecom Argentina, S.A.
------------------------------