<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal <!--- Clearly outline the goal of the issue and why we are doing it ---> A backend api is required to both send and verify In-App user verification codes ## What needs to be done <!--- Clearly detail what needs to be done to achieve the goal set out above ---> - Figure out a schema to store all the code requests by device id - Hook into the current push notifications system ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> TBD ## UX/Design <!--- Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged. ---> N/A ## Personas <!--- Who does this user impact and why (optional) ---> Mobile users ## Experiments <!--- Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined. ---> N/A (mobile will have the toggle) ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] New module for the verification flow - [ ] Schemas built out - [ ] Working API - [ ] Endpoint to inform if verification has been completed or not - [ ] Integration tests if possible ## Dev notes - TTL for request? Parameter. ~15 mins. - Make another task for S3 data dump - Happy path etc https://gitlab.com/groups/minds/-/uploads/a395dab183ecba601730f0d679f1f0e4/In-app-registration.pdf - https://github.com/thiagoalessio/tesseract-ocr-for-php ## Definition of Ready Checklist - [x] Definition Of Done (DoD) - [x] Acceptance criteria - [x] Weighted - [x] QA - [x] UX/Design - [x] Personas - [x] Experiments