This repository has been archived by the owner on Aug 26, 2022. It is now read-only.
Identity Verification of Customers #5
Labels
enhancement
New feature or request
Comments
adamdecaf
added a commit
to adamdecaf/customers
that referenced
this issue
May 13, 2019
|
An administrative API route will be required to migrate a customer from the start state 'ReviewRequired' to the approved state. We should probably limit the OAuth security scope for this action and the action should be logged. I see a "backend" application for approving these in the future. |
adamdecaf
added a commit
to adamdecaf/customers
that referenced
this issue
May 30, 2019
adamdecaf
added a commit
to adamdecaf/customers
that referenced
this issue
May 30, 2019
This was referenced May 30, 2019
adamdecaf
added a commit
to adamdecaf/customers
that referenced
this issue
Jun 3, 2019
Not every CustomerStatus can be converted into another, so we need to block bad transistions. Issue: moov-io#5
adamdecaf
added a commit
to adamdecaf/customers
that referenced
this issue
Jun 3, 2019
Not every CustomerStatus can be converted into another, so we need to block bad transistions. Issue: moov-io#5
adamdecaf
added a commit
to adamdecaf/customers
that referenced
this issue
Jun 3, 2019
Not every CustomerStatus can be converted into another, so we need to block bad transistions. Issue: moov-io#5
|
Here's an example of checking which statuses are approved or not across projects: |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There are several levels of identity verification of customers, they are (in order, case insensitive):
When we implement these it should be done with a type that can be compared (i.e. integers) so that
KYC < CIPand we can use comparisons likecustomer.IdentityVerification < KYCin our codebase.Notes: #9
The text was updated successfully, but these errors were encountered: