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

Add new dimension to MBD and potentially DiamondHands endpoints to help partners identify if low score is due to poor quality transactions or lack of transactions #3130

Open
lebraat opened this issue Dec 11, 2024 · 0 comments

Comments

@lebraat
Copy link
Member

lebraat commented Dec 11, 2024

User Story:

As a partner
I want to better understand if a low score coming from MBD or DiamondHands is due to low transaction volume or poor transactions
So that I can adjust how I treat the user.

Acceptance Criteria

GIVEN a request to the MBD or DiamondHands API (tbd)
WHEN a user scores low
THEN a secondary field can help me understand if this is due to low transaction volume or poor transactions

Add a new '-1' response that indicates no or insufficient data to score

Add new dimension to MBD and potentially DiamondHands endpoints to help partners identify if low score is due to poor quality transactions or lack of transactions

@Jkd-eth Jkd-eth moved this to Prioritized in Passport New Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Prioritized
Development

No branches or pull requests

1 participant