# Devices

Process card-present EMV transactions using cloud-connected payment devices.

Payment Devices enable applications to initiate and manage EMV card-present transactions through a cloud-to-device payment architecture.

Instead of connecting directly to payment terminals, applications communicate with devices through cloud-based APIs using a unique Device ID. This approach simplifies deployment, reduces hardware integration complexity, and enables secure in-person payment acceptance.

### Cloud-to-Device Connectivity

Applications do not communicate directly with payment devices.

Instead, payment devices are securely accessed through the cloud using a unique Device ID that identifies the terminal.

This architecture enables developers to:

- Initiate EMV Sale transactions
- Initiate EMV Authorization transactions
- Initiate EMV Stand-Alone Refund transactions
- Receive transaction results through webhooks
- Manage payment devices through APIs
- Eliminate direct terminal integrations


### Supported Payment Devices

The following payment devices are currently supported:

| Device | Connectivity |
|  --- | --- |
| Ingenico Desk 2600 | Wi-Fi / Ethernet |
| Ingenico Move 5000 | Wi-Fi / 4G |
| Ingenico Lane 3000 | Ethernet |
| Ingenico Lane 3600 | Ethernet |


Supported devices and capabilities may vary based on merchant configuration, processor support, and deployment requirements.

### How Device Payments Work

Payment device transactions are initiated through cloud-based APIs and processed on the payment terminal.

**Obtain a Device ID**
Each payment device is assigned a unique Device ID during provisioning.

**Submit a Transaction Request**
Your application submits an EMV transaction request using the Device ID and API credentials.

**Customer Completes Payment**
The customer interacts directly with the payment device to complete the transaction.

**Process Transaction**
The payment device processes the transaction and returns the result through the Deluxe platform.

**Receive Transaction Result**
Transaction results are delivered asynchronously through the configured webhook endpoint.

Note
Device transactions use a cloud-to-device architecture and rely on webhook notifications for final transaction results.

### Authentication Requirements

Requests that send commands to a payment device must include:

- A bearer token in the `Authorization` header
- A valid `deviceId` in the request


Together, these values identify your application and ensure requests are routed to the correct payment device.

### Device Addressing and Control

Payment devices are identified through a persistent cloud-based Device ID.

This architecture provides:

**Unified Device Targeting**

Use a Device ID to send commands to any supported payment device, regardless of its physical location.

**Cloud-Based Connectivity**

No local IP management, port forwarding, USB connections, or device-specific network configuration is required.

**Driverless Integration**

No terminal drivers, middleware, or hardware-specific SDKs are required. Applications interact with devices through standard API requests.

### Device Provisioning

Supported payment devices are provisioned and registered in the cloud before deployment.

During provisioning:

- A unique Device ID is assigned.
- The device is associated with the appropriate merchant and location.
- Device credentials and configuration are applied.


Because devices are already registered in the cloud, manual pairing and activation are not required in the field.

### Merchant and Device Lifecycle

Device assignments are managed as part of the merchant lifecycle.

Store Device IDs and associate them with the appropriate merchant location, lane, register, or workstation to simplify transaction routing and device management.

As devices are provisioned and managed, applications can use Device IDs to identify, route, and process transactions through the appropriate payment terminal.

### When to Use Payment Devices

Payment devices are commonly used for:

- Retail checkout experiences
- Countertop payment acceptance
- Mobile point-of-sale solutions
- Field service payments
- Card-present transactions
- Contactless payment acceptance


### Related Resources

Devices Integration
Process EMV Sale and Stand-Alone Refund transactions using payment devices.

EMV API
Review payment device endpoints, request schemas, and transaction operations.

Webhook Structures & Types
Review EMV webhook payloads, transaction results, and terminal event notifications.