Frontend
Vue-based selection and transaction interfaces for vending and cash-in paths.
All case studies
BCH Vending Machine
A vending workflow connecting a Vue interface, Python backend services, BCH transaction handling, the Paytaca app, and Raspberry Pi hardware control.
- Role
- Web Developer Intern
- Ownership
- Internship project
- Source
- Internship team project; evidence folder available
- Stack
- Python · Django REST · Vue · Raspberry Pi
01
Context
The system and the operational problem.
A payment-backed vending flow has to coordinate user selection, transaction state, confirmation, hardware action, and failure handling. Software and physical outcomes must remain aligned.
02
Responsibility
What I owned and what I contributed.
Contributed during an industry internship in a collaborative environment, with focus on Python and Vue application behavior, external BitCash transaction integration, and Raspberry Pi communication.
03
Constraints
The engineering challenge.
- 01
Keeping payment confirmation and physical dispensing in the same state
- 02
Handling external API responses and incomplete transactions
- 03
Connecting web application events to Raspberry Pi hardware actions
04
Approach
How the problem was framed.
- 01
Model the vending flow as explicit states from selection through transaction confirmation and dispense.
- 02
Treat external payment confirmation as a boundary before allowing hardware action.
- 03
Keep interface feedback visible so the user understands pending, confirmed, and failed states.
05
Implementation
The layers that made the workflow work.
Backend
Python and Django REST workflows for transaction coordination and API communication.
Integration
BitCash API and Paytaca-supported BCH transaction flow.
Hardware
Raspberry Pi communication connecting confirmed application states to vending behavior.
06
Operational value
Concrete outcomes, without invented metrics.
- Connected a user-facing payment flow to a physical vending prototype.
- Made transaction and hardware state part of one coordinated workflow.
- Demonstrated cross-discipline debugging across interface, API, payment, and device layers.
Engineering reflection
Hardware integration makes error states tangible. The software must be explicit about when a transaction is safe to translate into a physical action.