Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Customer Insights API Baseline Proposal #11

Open
PedroDiez opened this issue Nov 27, 2024 · 2 comments · May be fixed by #12
Open

Customer Insights API Baseline Proposal #11

PedroDiez opened this issue Nov 27, 2024 · 2 comments · May be fixed by #12
Labels
enhancement New feature or request

Comments

@PedroDiez
Copy link

PedroDiez commented Nov 27, 2024

Problem description
Baseline Proposal for Customer Insights API
Parent Issue: #14

Possible evolution
N/A. It is a NEW API

Associated PR: #12

Alternative solution
N/A

Additional context

This API is intended to provide credit scoring for a given user.

  • API is targeted to work in both 2-legged and 3-legged, depending on business scenario
  • Two credit scoring systems proposed initially others may be added later. At least "veritasIndex" is needed by TEF use cases
@PedroDiez PedroDiez added the enhancement New feature or request label Nov 27, 2024
@PedroDiez PedroDiez changed the title Customer Insights - Telco Index API Baseline Proposal Customer Insights API Baseline Proposal Nov 27, 2024
@PedroDiez PedroDiez linked a pull request Nov 27, 2024 that will close this issue
@KevScarr
Copy link

KevScarr commented Dec 9, 2024

Sorry for the delay, I've collated my feedback on the proposal and also the notes from our previous review call as:-

  1. "phoneNumber" to be optional in the TelcoCreditScoringRequest (as this may come from a token for 3 legged calls)
  2. "idDocument" to be optional in the TelcoCreditScoringRequest (not available in some countries, error raised when not provided in a country that requires it)
  3. "telcoCreditScoringType" (in TelcoCreditScoringRequest) you mentioned to be optional and the MNO will provide a default implementation when it's not specified that it will use
  4. Terminology
  • We have the term ‘telco’ in the specification I wondering if these should be removed, as Camara is to appear less ‘telco’ orienated, should we drop the ‘telco’ prefix?
    -- Example: “telcoCreditScoringType” --> “CreditScoringType” which is not telco specific, infact the values it holds are industry terms.
  • Do we need to lose the ‘Credit’ terminology (based on the sub-group naming discussion) as this could be used beyond credit as a generic ‘trust’ score (we probably need feedback from MNOs on this point as I think they should include a term):-
    -- Example: telcoCreditScoringValue--> scoringValue OR --> trustScoringValue

@PedroDiez
Copy link
Author

As commented in the meeting, next steps are:

  • Points 1,2,3 we are aligned
  • Check and align wording regarding point 4
  • Work on ICM and Commonalilities alignment (update spec next week)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants