pendulum-chain / pendulum-chain/vortex
Implement Avenia KYC retries.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6
- Forks
- 5
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 33
Description
Description
Right now, a user that has just been created but for whom the KYC failed cannot re-try the process.
When a user triggers the process, we first need to create a new account on Avenia's backend, and immediately we call the new-kyc endpoint. We map on our system as well the cpf to the new account id, for search purposes. Yet there is no logic implemented so far to flag an account created but rejected. Therefore when the user tries again we treat the account as a KYC'ed account, with invalid limits.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the account-creation and new-kyc flow, including how the cpf is mapped to the Avenia account id. Determine where rejected accounts are represented and how retry attempts currently resolve limits. Done means a user whose KYC was rejected can retry instead of being treated as KYC-approved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100