Unattended Commerce & Self-Service

Unattended Payment Systems and Integration Services

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.

MDB · DEXmachine protocol
Hive Back Officefleet · pricing · telemetry
Payment railPAX · Ingenico · Datacap
HONEYBEE · SELF SERVICE

Order. Pay.
Keep moving.

A customer-facing experience connected to the systems behind it.

Pay securely→
Industry applications

Different equipment. Different questions.

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.

▥

Vending

How payment connects to vend requests, dispensing, and any machine feedback available. Many vending machines expose an MDB interface.

◫

Laundry

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.

◎

Car wash

How a payment activates a bay, vacuum, timed service, or access controller.

P

Parking

How payment, ticket or session records, and access or exit systems connect.

ϟ

EV charging

How the payment lifecycle aligns with charging sessions and the selected platform or provider.

◫

Petroleum

Which device, controller, processor, and transaction-flow dependencies apply to the proposed deployment.

▦

Kiosks

How the customer application, payment device, peripherals, and fulfillment system work together.

+

Custom environments

Unusual hardware and proprietary workflows, assessed case by case.

Choose the integration path

MDB, Pulse, controller APIs, or something else.

The right path depends on the actual equipment. Compatibility is confirmed by checking that equipment, not assumed from the category.

MDB

Equipment and controller compatibility, required interface hardware, payment integration, machine state, and the feedback the machine makes available.

MDB Pay Connect →

Pulse

Signal requirements, pulse value or time mapping, controller compatibility, and the limits of fulfillment confirmation.

Pulse Pay Connect →

Controller APIs

Available documentation, access, supported actions and status, authentication, and operational dependencies.

Other interfaces

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.

Equipment assessment checklist

  • check_circleEquipment make and model
  • check_circleController and known interface or protocol
  • check_circleExisting or intended payment hardware
  • check_circleGateway or processor, and country
  • check_circleDeployment size and locations
  • check_circleRequired activation, pricing, or service behavior
  • check_circleAvailable machine status or fulfillment feedback
  • check_circleDocumentation, SDK access, and hardware available for testing
  • check_circleExisting application or backend, and rollout timing
What Paying.co builds

The screen is the visible part. We build what happens behind it.

A successful unattended deployment is a connected system. Included work depends on what is contracted.

01 / APPLICATION

Customer-facing applications

Kiosk and device experiences for ordering, checkout, check-in, ticketing, and custom workflows.

02 / PAYMENTS

Payment integrations

Processor and gateway integrations and payment device software across supported devices.

03 / MACHINE

Machine and controller connections

MDB, Pulse, controller API, and other device interfaces that connect the payment experience to the equipment.

04 / OPERATIONS

Backend services and fleet tooling

Configuration, pricing, transaction visibility, updates, and support tooling across deployed devices.

Payment and fulfillment

Approved is not the same as delivered.

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.

1 · Payment approval

The provider returned an approval.

2 · Activation

The system sent the machine command or signal.

3 · Fulfillment confirmation

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.

Hardware and dependencies

Software is one part of a complete deployment.

Software licensing is separate from the reader, controller or interface hardware, connectivity, processing relationship, and installation work a complete deployment needs.

What a deployment typically needs

  • check_circlePayment readers
  • check_circleControllers and interface hardware
  • check_circleConnectivity and power
  • check_circleSDK or documentation access
  • check_circleA processor or gateway relationship
  • check_circleInstallation and commissioning

Where responsibilities sit

Licensed software, custom engineering, hardware procurement, connectivity, processing agreements, and installation are scoped and supplied separately. We state which are included in each engagement.

Deployment options

Existing product or custom engineering.

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.

MDB Pay ConnectPayment connectivity for MDB-based unattended equipment. Fits when the equipment and payment environment are confirmed compatible.
Pulse Pay ConnectPayment connectivity for supported pulse-based equipment.
HoneyBeeSelf-service kiosk platform and deployable templates, where it fits the experience you need.
HiveBack-office control for content, pricing, transactions, device configuration, and fleet operations.

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.

Operations and support

From first machine to fleet.

Operational scope depends on the engagement and the tools involved.

Provisioning and configuration

Getting devices onto the network, configured, and ready for service.

Visibility and reconciliation

Transaction visibility and reconciliation against provider records.

Updates and support

Software updates and support, where offered under the engagement.

Commercial Android devices

When a commercial Android device fits the deployment.

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.

Related resources

Read before you scope.

Also see EMV certification where certification work applies, and industries for a broader overview.

Bring us the physical-world problem

Tell us what equipment you need to connect.

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.

Start your project

Sales online

Tell us about your project — we route you to the right specialist.

person
error_outlinePlease enter your name.
business
mail
error_outlinePlease enter a valid email address.
call
link
tune
error_outlinePlease tell us a bit about your project.

lock Your details go straight to our sales engineers — never shared or sold.