How johnitopaisah/e-commerce-api works
This is a Django storefront with account, catalog, session basket, order, and Stripe payment areas. The apparent customer flow is catalog browsing, basket management, payment, and order completion, but the README is empty and most views and URLs were not sampled, so their detailed routing and handoffs cannot be confirmed. The graph shows only relationships supported by the sampled source; the JavaScript submits to the order endpoint and payment views call the order confirmation function.
Main entry points: views.py Payment views · index.js Checkout browser · basket.py Session basket · models.py Catalog models
Components 15
Accounts
- Account views
account/views.py - Account forms
account/forms.py - User model
account/models.py
Storefront
- Store views
store/views.py - Catalog models
store/models.py
Basket
- Basket views
basket/views.py - Session basket
basket/basket.py
Orders
- Order views
orders/views.py - Order models
orders/models.py - Order add endpoint
orders/views.py
Payments
- Payment views
payment/views.py - Payment models
payment/models.py - Checkout browser
static/core/payment/index.js
Other components
- Customer
- Stripe
Connections 8
- Session basket → Catalog models: queries products
- Payment views → Session basket: reads total
- Payment views → Session basket: clears basket
- Payment views → Stripe: creates intent
- Checkout browser → Order add endpoint: posts order key
- Checkout browser → Stripe: confirms card
- Payment views → Order views: confirms payment
- Customer → Checkout browser: submits checkout