ZVT-H e.V.›ZVT Host Interface

Current Version 4.4 — January 2024

The ZVT Host
Interface

The standardised interface between payment terminal and host system: vendor-neutral, EU-mandated, and firmly established in the German market.

Interface Architecture

Point-of-Sale Terminal

Merchant Card Terminal

ZVT Host Interface

Standardised Protocol: Version 4.4

Host-System / Acquirer

Network Operator Infrastructure

Open Standard · Vendor-Neutral · EU-Mandated

Basics

What is the ZVT Host Interface?

A technical interface with a long history and a crucial role in the German payment market.

The ZVT Host Interface defines the communication between the payment terminal and the network operator's host system: how transaction data is exchanged, authorisations are requested, and results are reported back.

Originally developed as the Poseidon® ZVT protocol, the interface was transferred to the neutral management of ZVT-H e.V. in 2016 as part of EU merger control (Worldline/Equens), independent of individual market players.

Today, the ZVT Host Interface is the de facto standard for terminal-host communication in the German market and the foundation for an interoperable, competitive payment market.

Protocol Layers

↕
Protocol Layer — ZVT Host Interface
Message Format & Encoding
BMP encoding, ISO-8583 derivative, error codes, sequence control
↕

Characteristics

Characteristics of the Standard

The ZVT Host Interface is characterised by features that are crucial for an open, reliable payment market.

Vendor-Neutral

No single provider owns the protocol. ZVT-H e.V. manages the standard in the interest of all market participants.

Interoperable

Terminals from various manufacturers communicate with hosts from different network operators without proprietary adjustments.

Fully Specified

The specification documents all message formats, error codes, and process scenarios precisely and bindingly.

Extensible

The Advisory Board evaluates and integrates new requirements. The standard evolves in a controlled manner alongside the market.

Features

Core Functions of the Interface

The protocol covers all transaction types and administrative functions of modern payment processing.

Payment Processing

Transaction

All types of card payments: contactless (NFC), chip, and magnetic stripe across all standard card schemes.

Cancellation & Refund

Transaction

Full and partial cancellations as well as refunds with unique transaction referencing.

Online & Offline Authorisation

Authorisation

Real-time communication with the host including defined timeouts, fallback scenarios, and error handling. Batch transmission of offline authorisations.

Daily Closing & Administration

Settlement

Completion and transmission of the daily revenue.

Protocol structure

Message Categories

All messages follow a clearly defined BMP structure with a unique message type.

Request & Response Messages

Request / Response

Messages initiated by the terminal with an expected host response — the fundamental principle of all transactions.

  • Payment request & authorisation result
  • Cancellation request & confirmation
  • Daily closing request & acknowledgement
  • Error codes, reference numbers, print data

Initiation & Event Messages

Initiation / Event

Commands initiated by the host as well as asynchronous event messages without immediate expectation of a response.

  • Terminal configuration & software updates
  • Forced daily closing
  • Connection and system status messages
  • Error and diagnostic events

Process

Typical Transaction Flow

This is how a card payment proceeds via the ZVT Host Interface. From initiation to confirmation.

1

Payment Initiation

Card data is captured (chip, contactless, or magnetic stripe). The terminal establishes a secure connection to the host.

Terminal
2

Authorisation Request

The terminal sends a structured request with amount, currency, card data, and terminal identification according to the ZVT specification.

Terminal → Host
3

Processing & Response

The host forwards the request to the card network, receives the result, and sends approval or decline along with a reference number and optional receipt data back to the terminal.

Host → Card Network → Terminal
4

Completion & Acknowledgement

The terminal displays the result, prints the receipt, and confirms receipt. The transaction is logged on both sides.

Terminal & Host

Security Mechanisms

TLS Transport Encryption

All communication between the terminal and host is encrypted via TLS. Certificate verification is specified.

Key Management

Defined processes for managing cryptographic keys between terminal and host, including key derivation.

Message Integrity & Replay Protection

MAC checksums and sequence numbers secure the integrity of all messages and prevent manipulation or replay attacks.

Specification

Version History

The standard is continuously maintained. All versions are approved by the Advisory Board of ZVT-H e.V.

Version 4.4
August 2025

Current

Currently Valid Version

The currently valid version with extensions for modern payment scenarios. Recommended baseline for all new implementations and integrations.

  • Extended contactless transaction types
  • Extension for EV charging stations
  • Online age verification
  • New error codes and diagnostic commands
  • Clarifications and editorial corrections
Version 4.3
March 2021

Deprecated

Security

Message security according to the AES-DUKPT standard.

  • Action Codes

Next Steps

Questions about the ZVT Host Interface?

Whether it concerns specification access, licensing, or technical questions — the board of ZVT-H e.V. is at your disposal.