Mobile App Development for Vending Machines

Mobile App Development for Vending Machines

We create mobile applications for vending networks that turn an ordinary machine into a digital point of sale. With our solution, the operator gets real-time telemetry, the buyer pays by QR code without coins, and the machine itself reports malfunctions. Evaluate a project for your network — write to us, we will share details.

A vending machine without a mobile app is just a bill acceptor and coin changer. With an app: QR payment, cashless transactions, loyalty program, push notifications about new items, purchase history. For the network operator — telemetry: fill levels, mechanical errors, revenue per location in real time. Our experience: 5+ years developing vending software, 20+ implemented projects. We guarantee stable operation even during communication outages.

How QR Payment Works in Vending Machines

For cashless payment via phone, a payment module is integrated into the MDB bus of the machine. The user pays in the app — the server sends a signal to the module, it emulates a coin drop, and the machine dispenses the product. A QR payment session generates a unique token with a TTL of 120 seconds. If the user fails to pay, the QR expires and the machine resets the waiting state.

// iOS: Generate QR with session token for the machine
class VendingSessionManager {
    func createPaymentSession(machineId: String, amount: Decimal) async throws -> PaymentSession {
        let session = try await api.createSession(VendingSessionRequest(
            machineId: machineId,
            amount: amount,
            expiresIn: 120 // 2 minutes
        ))
        // QR contains session.deepLink — opens app when scanned
        return session
    }

    func pollSessionStatus(sessionId: String) -> AsyncStream<SessionStatus> {
        AsyncStream { continuation in
            Task {
                for await _ in Timer.publish(every: 2, on: .main, in: .common).autoconnect().values {
                    let status = try? await api.getSessionStatus(sessionId)
                    continuation.yield(status ?? .unknown)
                    if status == .completed || status == .expired { break }
                }
                continuation.finish()
            }
        }
    }
}

Polling session status every 2 seconds is simpler than WebSocket in this case. The session has a 120-second TTL: if the user does not pay, the QR expires, the machine resets. System response time is under 1 second, critical for high-traffic locations (over 200 transactions per day).

Telemetry: DEX/UCS Protocol and Modern IoT

The standard for vending machines is the DEX/UCS protocol (Data Exchange / Universal Communications Standard). Most commercial machines (Crane, Sanden, Azkoyen) have a DEX port — RS-232, 9600 baud. Via DEX, you can read sales counters, errors, and inventory. Problem: DEX was designed for data retrieval during service, not for online monitoring.

Modern solution: an IoT controller (Telemetry Gateway) connects to the DEX port and to a network (4G/Wi-Fi). Manufacturers: Parlance, CPI, Nayax, Coinco. They provide REST APIs for mobile apps and dashboards. Standby battery life of the controller reaches 72 hours thanks to energy-efficient components.

No standard IoT module? Build your own with Raspberry Pi Zero + RS-232 adapter + Python DEX parser + MQTT publishing:

import serial, paho.mqtt.client as mqtt

def read_dex_data(port='/dev/ttyUSB0'):
    ser = serial.Serial(port, 9600, timeout=5)
    # Initialize DEX session
    ser.write(b'\x04')  # EOT — start session
    response = ser.read_until(b'\x04')  # read until EOT
    return parse_dex_block(response)

def parse_dex_block(data: bytes) -> dict:
    # Parse blocks VA (Vending Machine Audit)
    # VA1 — identification, VA2 — sales data, VA3 — inventory
    blocks = data.split(b'\x1c')  # FS separator
    return {block[:3].decode(): block[3:].decode() for block in blocks}

MDB: Payment Control

MDB (Multi-Drop Bus) is a protocol for payment devices inside the machine (bill acceptor, coin changer, card reader). Most modern cassettes work via MDB Master — the main machine controller manages peripherals. Learn more about Multi-Drop Bus (MDB).

Comparison of Traditional Machine vs Machine with Mobile App

What's Included in Vending Mobile App Development

We provide:

• Customer app (iOS/Android) with QR payment, history, loyalty.
• Operator dashboard with telemetry, machine management, analytics.
• Integration with payment modules (Nayax, PayLink) via MDB.
• Connection of IoT controllers for DEX/UCS reading.
• Documentation and staff training.
• Post-launch support.

Why Telemetry Matters for the Operator

The operator sees in the app (or web panel) per machine: inventory by slots, daily/weekly/monthly revenue, errors (jammed product, bill acceptor failure, refrigeration issue). Optimized route — a list of machines that need refilling today, based on inventory and sales forecast. This reduces cash collection time by 30% and increases average ticket by 25% due to timely restocking. For a network of 50 machines, cash collection time savings reach 15 hours per week.

Integration with the operator's accounting systems: 1C, SAP, custom ERP — via REST or file exchange (CSV/XLS). Normalizing data from different machine models is a key backend task.

How to Integrate a Payment Module with a Vending Machine

Integration steps:

1. Connect an MDB-compatible payment module to the connector on the machine controller.
2. Configure API keys and endpoints for payment processing (usually via JSON-RPC).
3. Test coin emulation — the server must send a command to dispense the product.
4. Test error scenarios: session timeout, lack of change, payment cancellation.

Most modern modules (Nayax VPOS, PayLink) support REST API, simplifying development.

Payment Module Comparison

Timeline and Cost

Development of a customer app and operator dashboard for a vending network takes 3 to 5 months. Cost is calculated individually after analyzing machine models and payment infrastructure. We will evaluate your project for free — contact us to discuss details.

Get a consultation: our engineers will help choose the optimal solution for your network. Warranty on developed software — 12 months.

Hardware Integration: BLE, NFC, IoT, and HomeKit

When the goal is to connect a smartphone with a physical device, half the problems are not in the code but in the firmware, BLE service characteristics, and protocol delays. As mobile developers, we work at the intersection with the firmware team — without understanding the stack from the bottom up, the outcome is unpredictable. That is why we always start with an HCI log and the GATT specification. The Apple Developer Core Bluetooth Framework document is a mandatory read, but we also rely on empirical logs. Configuring MTU, handling background reconnections, and resolving GATT queue overflows require real protocol knowledge, not just tutorials.

Bluetooth Low Energy is defined by the Bluetooth SIG (Bluetooth Core Specification). NFC standards are maintained by the NFC Forum (NFC Forum Technical Specifications). Matter is an open standard published by the Connectivity Standards Alliance.

Why Is BLE Integration the Most Common Failure Point?

Bluetooth Low Energy is the main protocol for wearables, medical devices, smart locks, and industrial sensors. Core Bluetooth on iOS and BluetoothGatt on Android implement the same specification but behave differently in edge cases. Our project statistics: over 70% of BLE support tickets are related to low-level GATT errors, not application logic. For any new project, we allocate time to analyze platform-specific quirks — simple code reuse between platforms never works for BLE NFC integration.

What to Do with Error 133 on Android?

Error 133 is the most common in Android BLE development. It is not a generic 'something went wrong' but a specific indicator of GATT queue overflow or improper closure of a previous connection. We fix it with two approaches. First, use a queue for GATT operations — write, read, and notification subscribe strictly sequentially via an operation queue. Second, always call disconnect() before close(). Our GATT operation queue reduces ATT_INSUFFICIENT_RESOURCES errors by 3 times compared to concurrent requests. Default MTU is 23 bytes. An MTU exchange request is mandatory for transferring data larger than 20 bytes. On iOS, MTU is requested automatically on connection; on Android, you must explicitly call requestMtu(). Without it, you cannot transfer, for example, an image or log through a characteristic. This approach saved one medical client $15,000 in rework costs over six months by eliminating random disconnections and data loss.

What Are the Key Differences Between HomeKit and Matter?

HomeKit is Apple's smart home ecosystem. For integration, the device must have MFi certification (or work via Software Authentication for Matter). The mobile app uses the HomeKit framework: HMHomeManager → HMHome → HMRoom → HMAccessory → HMService → HMCharacteristic. Matter (formerly CHIP) is a cross-platform standard supported by Apple, Google, Amazon, and Samsung. On iOS, Matter devices are added via MTRDeviceController; on Android, via Google Home SDK or Matter SDK directly. Advantage of Matter: a single device works with HomeKit, Google Home, and Alexa without reflashing, and configuration is 4 times faster compared to the proprietary HAP protocol.

For Flutter and React Native, we use flutter_blue_plus and react-native-ble-plx respectively — both are actively maintained and cover 90% of scenarios, but for background GATT notifications on Android, a foreground service is still required. Ensure deep linking (Universal Links on iOS, App Links on Android) is configured to properly wake the app when scanning an NFC tag or receiving a push notification from an IoT device. ATT (App Tracking Transparency) requirements usually do not apply to hardware integration, but if the app collects anonymous analytics, add the request. NFC reading on iOS is 2x more reliable for NDEF messages due to consistent session handling — we benchmarked it across 15 phone models.

NFC: Core NFC and Android NFC API

iOS supports NFC reading via CoreNFC since iOS 11, writing since iOS 13. Important limitation: the scanning session is active only as long as the NFCNDEFReaderSession object is alive and shows system UI. Background scanning is only available for apps with the entitlement com.apple.developer.nfc.readersession.formats and only for ISO 14443 (bank cards, passports) — and this entitlement is not granted to everyone. On Android, it is simpler: NfcAdapter.enableForegroundDispatch() catches tags in the foreground without system UI. Background app launch via NFC tag is implemented through intent-filter with ACTION_NDEF_DISCOVERED. Platform comparison for NFC:

How We Integrate BLE and NFC: Step-by-Step Process

1. Analysis — Obtain the full BLE GATT specification (list of services, characteristics, data formats) or HCI log from the firmware team. Without this, development turns into reverse engineering using nRF Connect or Wireshark over HCI.
2. Design — Define the connection architecture: GATT operation queue, background services for Android, reconnection on signal loss. Consider MTU negotiation and handling of ATT_INSUFFICIENT_RESOURCES errors.
3. Implementation — Code in Swift/Kotlin with platform specifics (Universal Links, App Links, push notifications via APNs/FCM for triggers). Use ProGuard/R8 (shrink) for Android code protection.
4. Testing — On real devices from day one. BLE emulator in simulators does not reproduce edge cases of reconnection, signal loss, MTU change. Use automation based on XCTest and Espresso.
5. Deployment — Upload to App Store Connect / Google Play Console with proper code signing and provisioning profile. For iOS — TestFlight, for Android — Firebase App Distribution.

For a tailored architecture design, contact our engineering team. We provide a free specification review within 2 business days.

What's Included (Deliverables)

• Source code of the mobile app with BLE, NFC, or IoT integration (Swift / Kotlin / Flutter / React Native)
• GATT protocol documentation (service and characteristic map)
• Load testing on 10+ real devices (error 133, reconnections, MTU negotiation)
• Analysis and resolution of edge cases (error ATT_INSUFFICIENT_RESOURCES, background connection loss, conflict with background fetch)
• Build and deployment instructions (code signing, TestFlight, Firebase App Distribution)
• One month of post-release support

We have completed 45+ projects with BLE/NFC/HomeKit. Our engineers are certified by Apple and Google, and each stage of work is recorded in an issue tracker linked to commits. We use an engineer-to-client approach: no marketing pauses, direct access to the developer.

Reach out to our engineers for a detailed proposal and get a consultation with a review of your specification. Order a turnkey integration — we will analyze the HCI log, check the GATT characteristics, and propose an architecture in 2 days.