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

SEP-9: add proof_of_income field #1301

Closed
JakeUrban opened this issue Aug 26, 2022 · 6 comments · Fixed by #1310
Closed

SEP-9: add proof_of_income field #1301

JakeUrban opened this issue Aug 26, 2022 · 6 comments · Fixed by #1310

Comments

@JakeUrban
Copy link
Contributor

What problem does your feature solve?

Anchors often have different KYC "tiers" that allow their users to transact in small to large amounts. For example, with a limit of $2k per day, anchor could require a user's contact information and ID number, but if the user wants to transact more than $2k per day, then they have to provide additional KYC documentation.

However, the SEP-9 list of standard KYC fields does not include a field used for collecting income information.

What would you like to see?

Adding a proof_of_income field of type binary standardizes anchors' request for the user to provide documentation proving their income level. Anchors may need this information to upgrade their users' to a higher "tier".

This field could be passed in a SEP-12 PUT /customer OR POST /customer/files request. If passed to POST /customer/files, the file ID returned would then need to be referenced in the subsequent PUT /customer request.

@JakeUrban
Copy link
Contributor Author

cc @jessieserrino @howardtw

@JakeUrban
Copy link
Contributor Author

@CassioMG

@github-actions
Copy link

This issue is stale because it has been open for 30 days with no activity. It will be closed in 30 days unless the stale label is removed.

@github-actions github-actions bot added the stale label Sep 26, 2022
@JakeUrban JakeUrban removed the stale label Sep 26, 2022
@CassioMG
Copy link
Contributor

CassioMG commented Oct 4, 2022

@JakeUrban this looks great to me. Would you mind if I open a PR for this change?

@JakeUrban
Copy link
Contributor Author

Please do!

CassioMG added a commit to CassioMG/stellar-protocol that referenced this issue Oct 5, 2022
@CassioMG
Copy link
Contributor

CassioMG commented Oct 5, 2022

Here it is: #1310

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

Successfully merging a pull request may close this issue.

3 participants
@CassioMG @JakeUrban and others