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

Order managers should be able to see a risk evaluation for an order #2322

Closed
spencern opened this issue May 22, 2017 · 7 comments
Closed

Order managers should be able to see a risk evaluation for an order #2322

spencern opened this issue May 22, 2017 · 7 comments

Comments

@spencern
Copy link
Contributor

spencern commented May 22, 2017

Users with permissions to see the order details view should be able to see a risk evaluation for an order.

Orders with a normal risk evaluation should not be highlighted abnormally.

Orders with an elevated or high risk evaluation should be highlighted and there should be a large notification present on the order details page as well as a badge on the order list page.

Orders with a high risk evaluation should require the order manager to acknowledge that the order is a high risk order before they may capture the payment.

Resources

@rymorgan
Copy link
Contributor

rymorgan commented Jun 1, 2017

@spencern What constitutes a high risk order?

@spencern
Copy link
Contributor Author

spencern commented Jun 1, 2017

@rymorgan it all comes from the Stripe (or other payment provider) - Stripe does risk assessment for every transaction and provides that information as part of the response. See the Stripe Risk Evaluation Docs for more details

@rymorgan
Copy link
Contributor

rymorgan commented Jun 2, 2017 via email

@impactmass
Copy link
Contributor

Status: WIP PR #2744. Need to touch base with @spencern on some things around paymentMethod.... and @rymorgan about current design.

@rymorgan
Copy link
Contributor

Update here: After talking through the requirements with @spencern -- A risk flag needs stay persistently with the order. So my thinking is that it should be a flag rather than a status, as I originally designed it. We don't have a design for this type of flag but think it'll but useful for other purposes as well.

@rymorgan
Copy link
Contributor

@impactmass I think this is a better way to handle this.

RC LInk:
https://zpl.io/awlXg7b

Public link:
https://scene.zeplin.io/project/58af8900737c137280322bd6/screen/59a07f2216413c8ca1d52a96

@impactmass impactmass removed their assignment Sep 1, 2017
@impactmass
Copy link
Contributor

closed by #2744

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

No branches or pull requests

3 participants