We connect payment acceptance to physical equipment, customer workflows, and operations. That covers machine connectivity, application development, payment integration, and fleet operations for self-service environments.
A customer-facing experience connected to the systems behind it.
The payment layer is similar across unattended environments. What it has to connect to is not. No single interface or payment design applies to every machine or industry, so we start with the equipment.
How payment connects to vend requests, dispensing, and any machine feedback available. Many vending machines expose an MDB interface.
Which machine and controller interfaces are available, how cycles are activated, and whether a start can be confirmed. See how to add card payments to existing laundry machines.
How a payment activates a bay, vacuum, timed service, or access controller.
How payment, ticket or session records, and access or exit systems connect.
How the payment lifecycle aligns with charging sessions and the selected platform or provider.
Which device, controller, processor, and transaction-flow dependencies apply to the proposed deployment.
How the customer application, payment device, peripherals, and fulfillment system work together.
Unusual hardware and proprietary workflows, assessed case by case.
The right path depends on the actual equipment. Compatibility is confirmed by checking that equipment, not assumed from the category.
Equipment and controller compatibility, required interface hardware, payment integration, machine state, and the feedback the machine makes available.
MDB Pay Connect →Signal requirements, pulse value or time mapping, controller compatibility, and the limits of fulfillment confirmation.
Pulse Pay Connect →Available documentation, access, supported actions and status, authentication, and operational dependencies.
Assessment and custom integration where equipment uses a different interface. We do not assume universal support.
Learn which interface your machine needs, MDB or Pulse. Read the unattended payment systems guide. Manage Android kiosks and payment devices with Castum MDM.
A successful unattended deployment is a connected system. Included work depends on what is contracted.
Kiosk and device experiences for ordering, checkout, check-in, ticketing, and custom workflows.
Processor and gateway integrations and payment device software across supported devices.
MDB, Pulse, controller API, and other device interfaces that connect the payment experience to the equipment.
Configuration, pricing, transaction visibility, updates, and support tooling across deployed devices.
Payment approval, machine activation, and fulfillment confirmation are three separate events. Treating them as one is how a customer gets charged for a service that never started.
The provider returned an approval.
The system sent the machine command or signal.
The machine reported delivery or start, where the interface supports that feedback.
A pulse alone does not prove the machine started or fulfilled the service, and not every machine supplies feedback. Where an outcome is ambiguous, the system records it and resolves it. Transaction state persistence, duplicate protection, status checks, reversal or refund handling, and reconciliation are designed around what the equipment and provider actually support. Automatic retries are not always safe. Learn how to design recovery when payment is approved but the machine did not start.
Software licensing is separate from the reader, controller or interface hardware, connectivity, processing relationship, and installation work a complete deployment needs.
Licensed software, custom engineering, hardware procurement, connectivity, processing agreements, and installation are scoped and supplied separately. We state which are included in each engagement.
An existing product fits when it matches the confirmed equipment and payment environment. Custom engineering is scoped when it does not. Each path has its own inclusions, limitations, and commercial requirements.
A customer-facing application, backend, controller adapter, or custom workflow is scoped separately. Ownership, documentation, handoff, maintenance, and support follow the terms of each engagement. See Custom Development and Platform Integrations.
Operational scope depends on the engagement and the tools involved.
Getting devices onto the network, configured, and ready for service.
Transaction visibility and reconciliation against provider records.
Software updates and support, where offered under the engagement.
Some deployments use a commercial Android device with its own supported SoftPOS implementation. Whether that is appropriate or approved for unattended use depends on the device, provider, and deployment requirements, which we confirm first.
Explore commercial Android COTS payment development → For broader acceptance work see SoftPOS and tap-to-phone development.
For MDB-compatible equipment.
For supported pulse-based equipment.
An introductory explanation.
Choosing the interface.
Controller assessment and payment modes.
Equipment assessment and retrofit planning.
For laundry equipment.
Designing recovery for unattended payments.
Also see EMV certification where certification work applies, and industries for a broader overview.
Include what you have: equipment make and model, controller and interface, payment hardware, gateway or processor and country, deployment size and locations, required activation or pricing behavior, available machine feedback, documentation and test hardware, existing application or backend, and target timing. We will recommend the right path.
Tell us about your project — we route you to the right specialist.