ZVT credit card terminal protocol
ZVT central payment protocol
German terminal protocol standard
Originally developed to standardize communication between electronic cash registers and payment terminals, ZVT became one of the most widely adopted terminal integration protocols in Germany.
One protocol, multiple payment providers. How a German payment standard continues to simplify terminal integrations across Europe.
Rather than requiring a proprietary integration for every terminal manufacturer or payment provider, ZVT established a common language for initiating payments and exchanging transaction results.
From the 1990s to modern payment terminals
ZVT, short for Zahlungsverkehrsterminal (payment transaction terminal), has its roots in the German electronic payment industry of the 1990s.
The protocol has continued to evolve, with specifications maintained and published by the German Association of Terminal Manufacturers (VdTH).
What does ZVT support?
ZVT is a manufacturer-independent communication protocol connecting payment terminals to cash registers, vending machines and other applications.
It supports operations such as initiating payments, cancellations, retrieving transaction information and terminal management functions, depending on the terminal implementation.
Originally using serial connections such as RS-232, modern ZVT terminals commonly communicate over TCP/IP networks.
Importantly, ZVT does not process payments itself. It controls communication between software and the terminal, while the payment provider and acquiring infrastructure handle the actual transaction.
One standard, multiple payment providers
ZVT is supported across the payment industry, including terminals and solutions from:
-
Nexi
-
PAYONE
-
Fiserv / TeleCash
Its broad adoption makes ZVT particularly valuable for software providers and system integrators working with different payment providers and terminal manufacturers.
ZVT meets hospitality automation
At HotelPlatform, we support ZVT through our unified Payment API, making compatible payment terminals accessible to hospitality applications without implementing the protocol individually.
Whether integrating payment terminals into hotel software, reception workflows or unattended self-check-in kiosks, developers can work with a consistent API while retaining flexibility in their choice of payment hardware and provider.
A protocol with decades of history, connected to modern hospitality automation.