1. User registers & logs in using phone verification;
2. User initiates enrollment by sending POST request to enrollment creation endpoint. Request payload is only partially filled because at first user only chooses a program he is enrolling in to, so payload contains only program ID. New enrollment id is sent back as a response.
3. User chooses a service and sends PUT request to the enrollment endpoint identified by previously received enrollment id. So enrollment now has service as well.
4. If service price is greater than 0 we should initiate payment process by creating payment on Payze API and sending its details as a response after choosing service in step 3. We follow standard payment process we already have in place.
5. After successful payment, user will be presented with the list of Mentors associated to the program he chose in step 1.
6. User chooses a mentor by sending one more PUT request to the enrollment endpoint.
7. As a last action we send notifications to interested parties:
   • User should get SMS congratulating completion of the registration, with details about program he chose and contact details of his mentor (name, phone number) and a Discord invite link.
   • Mentor should also get an SMS or a message from Discord bot indicating that new student has registered for him and get student contact info

How to reproduce?

1. Create new user by submitting a Phone number on via dashboard front-end;
2. Make sure this is actually a new user (No profile data is in the database - email, first name and last name fields are empty);
3. Try to choose a program;
4. Try to choose a service;
5. Try to Buy via "ყიდვა" button;
6. You will get an error.

By debugging the back-end I found out that metadata extraAttributes email field is empty and without that field provided, Payze returns Bad request. See the screenshot:

Proposed resolution

1. Add phone number to metadata;
2. Check if all metadata fields are available;
3. Only send the fields that are available and do not send empty field values to Payze.

Include Discord bot code alongside Django

• Create new app for the bot
• Bind Discord bot and Django
• Create experimental database

Service is hardcoded in client, therefore it should be implemented in API

• #19

Setup DRF project

• Start DRF project - "back"
• Write development/production settings
• Write .gitignore file
• Write requirements.txt file
• Configure swagger / drf-spectacular
• Dockerize the project
• Update README.md

ამჟამად პრობლემაა რომ პროგრამების თანმიმდევრობა dashboard - ზე იმის მიხედვით ჩანს თუ ბოლოს რომელი პროგრამის ინფორმაცია განახლდა. უნდა შევცვალოთ და ამის მართვა უნდა შეგვეძლოს.

• უნდა დავამატოთ weight - რიცხვითი ველი;
• ეს რიცხვითი ველი უნდა გამოვიყენოთ პროგრამების სორტირებისთვის;
• პროგრამები უნდა დასორტირდეს weight ველის მიხედვით, დაბალიდან მაღალი მნიშვნელობისკენ.

• #16
• #17