Open APIs

 View Only

TMF696 Risk Management API overlap with TMF679 Product Offering Qualification

  • 1.  TMF696 Risk Management API overlap with TMF679 Product Offering Qualification

    TM Forum Member
    Posted 12 days ago
    Edited by Matthieu Hattab 12 days ago

    Hello,

    We implemented Credit Check using TMF679, based on the following principles:

    • Credit check status determines whether a customer can purchase specific products (basically only the post-paid offers).

      • This led us to store or reference these rules in the product catalogue.

    • TMF679 explicitly refers to the credit profile (to assess financial reliability) in its user guide.

    • If a customer's creditworthiness is insufficient, we use the EligibilityResultReason field to return clear messages (e.g. "You're in dunning", "Please contact support").

    This approach has worked well for us with TMF679.

    We're now evaluating an additional credit check service from a third-party financial provider. During our internal discussions, 2 new APIs were suggested to provide credit rating:

    TMF696 Risk Management API

    TMF632 Party Management API

    in TMF696 user guide, I notice a few overlaps with TMF679, for instance ProductOfferingRiskAssessment.
    in TMF632 user guide I notice a dedicated sub resource for credit check with score, agency name, expiry date etc. that's exactly what we need.

    Has anyone here implemented credit check and what did  you TMF696, TMF632 or TMF679?

    Curious to hear your thoughts and experiences.



    ------------------------------
    Kind regards,

    Matthieu Hattab
    Digital Sales Domain Architect
    Lyse Tele AS
    ------------------------------