TCN machine reality

Date: 2026-05-26

Purpose: current source of truth for Ballbox work on TCN vending machines.

Executive truth

TCN does not provide direct Mercado Pago support.
TCN does not provide a general path for generic third-party payment setup.
The only current real payment path is an external physical payment device flow, such as EasyCoin.
Old Ballbox docs that assumed machine-native dynamic Mercado Pago QR through TCN are invalid.
Ballbox should separate current operating truth from future autonomy research.

Layer	Current truth
Machine hardware	TCN vending machine, observed model `TCN-CSC-8C(V49)`.
Machine UI/runtime	Android-based local runtime with backstage/technical menus, local storage, USB import/export, ads/media support.
Machine cloud	OurVend currently handles stock, prices, sync, and monitoring.
Current payments	EasyCoin device plus BillWallet account management plus Mercado Pago underneath that stack.
Current dispense proof	Real payment and real product release were observed and documented.

Wi-Fi connectivity validated.
Android settings and file browser access validated.
Backstage access validated.
Slot configuration, motor testing, and eject testing validated.
OurVend remote stock and remote price updates validated.
USB import/export flow validated through TCNFolder.
Local ads via images and video validated.
Logs and SQLite export validated.
Observed server: qrc.ourvend.com:4150.
Observed local folders of interest: ImageGoods, Text, v3Skins.
Observed remote-content hints: ad.ourvend.com, OTA/update references, remote ads flags.

Production-capable path today:

User selects product on the machine.
Payment is handled through external physical payment hardware and its provider stack.
EasyCoin confirms payment.
The machine releases the selected product.

Important: this is the proven path. Ballbox-native Mercado Pago QR generation inside the TCN machine is not the current real path.

No direct TCN-to-Mercado Pago integration is confirmed.
No generic machine-side third-party payment adapter path is confirmed.
No Ballbox-controlled machine-native payment contract is available today.
No truthful basis exists for presenting a TCN payment adapter as implementation-ready.

Ballbox should document and support the current EasyCoin/BillWallet/OurVend-based operating model first.
Machine onboarding should track physical QR placement, legal QR placement, EasyCoin setup, BillWallet account setup, and real vend test evidence.
Exports, logs, SQLite dumps, and asset packs should be preserved as operational artifacts.
Stock reconciliation remains partly operational, not purely software-driven.

EasyCoin API as a possible Ballbox integration bridge for benefits, memberships, or remote actions.
Android asset control for ads, branding, translations, and local content packs.
OurVend protocol/FTP/OTA investigation as long-term autonomy research.

Real working now must stay separate from research and from invalidated assumptions.

Ballbox docs should not present speculative payment autonomy as current product reality.

docs/tcn-maquinas-recibido-2026-05-26/PARTE 1 - DOCUMENTACION MAESTRA DE INVESTIGACION Y OPERACION.docx
docs/tcn-maquinas-recibido-2026-05-26/PARTE 2 - Android USB Publicidad Exportaciones y Sistema Interno.docx
docs/tcn-maquinas-recibido-2026-05-26/PARTE 3 - EasyCoin BillWallet Operacion Comercial y Arquitectura Futura.docx
docs/tcn-maquinas-recibido-2026-05-26/PARTE 4 - Ingenieria Inversa Traducciones Backend Propio y Plan de Investigacion.docx
docs/tcn-maquinas-recibido-2026-05-26/PARTE 5 - Manual Operativo BallBox.docx
docs/tcn-maquinas-recibido-2026-05-26/PARTE 6 - Ingenieria Inversa Avanzada y Autonomia Tecnologica.docx
User clarification on 2026-05-26: no direct TCN Mercado Pago support, no generic third-party payment path, external physical payment device is the only current option.