Official service: Hypercom TPDU (Transaction Protocol Data Unit)
Port: 1430 TCP/UDP
Status: Registered port
Port 1430 carries TPDU—Transaction Protocol Data Unit—a payment processing protocol that was designed for an Internet that barely existed yet.
What TPDU Does
TPDU is a packet-based protocol used in financial transaction processing. When a credit card gets swiped at a point-of-sale terminal, that transaction needs to get from the terminal to a payment processor. TPDU provides the addressing and routing information to make that happen.1
The protocol consists of a 5-byte header that precedes the actual transaction data. This header contains:
- Destination information (which host application or network address should receive this)
- Origination information (which terminal or POS system sent this)
It's simple. It's compact. It works.
The X.25 Origins
Here's the strange part: TPDU was originally designed for X.25 networks.2
X.25 was a packet-switching protocol from the 1970s—pre-Internet infrastructure that ran over dial-up connections. Payment terminals would dial in to a central host, establish an X.25 connection, and send transaction data using TPDU.
The protocol was designed to concentrate a large number of dial-up payment devices into one central host connection. Efficient use of expensive long-distance phone lines was the entire point.
This was before TCP/IP dominated everything. Before the web. Before broadband. TPDU comes from the era when network connections were expensive, intermittent, and measured in baud.
Why It Still Exists
X.25 is dead. Dial-up networks are dead. And yet TPDU is still in use.
Payment infrastructure evolves slowly. When you have millions of terminals deployed in stores, restaurants, and gas stations worldwide, you don't replace them on a whim. The terminals that Hypercom Corporation manufactured—the T4220, the T7 Plus, countless others—were built to last.3
Many of these terminals still work. Many are still processing transactions. And they're still speaking TPDU, even if the underlying network has changed from X.25 to TCP/IP.
The protocol adapted. Modern payment processors accept TPDU over TCP on port 1430, maintaining compatibility with legacy terminals while running on modern networks.
Hypercom's Role
Hypercom Corporation was one of the largest global providers of electronic payment solutions at the point-of-transaction.4 Their terminals were ubiquitous in the payment processing industry.
TPDU was part of Hypercom's communication infrastructure—the protocol their terminals used to talk to payment processors and networks. The fact that port 1430 is specifically registered as "Hypercom TPDU" shows how dominant they were in this space.
(Hypercom was eventually acquired by VeriFone in 2011, but the protocol lives on.)
The Honest Reality
TPDU represents something important about infrastructure: it doesn't die just because something better exists.
Payment processing requires reliability above all else. When a customer swipes their card, the transaction needs to work. It doesn't matter if the protocol is elegant or modern. It matters that it's proven.
TPDU is proven. It's been processing billions of transactions for decades. And until every legacy terminal gets replaced—which might be never—port 1430 will keep carrying payment data using a protocol designed for dial-up networks.
Security Considerations
TPDU itself is just a transport protocol—it doesn't provide encryption or authentication. Security depends on the underlying network and the application layer.
Modern implementations typically run TPDU over encrypted connections (TLS/SSL) to protect payment data in transit. But the protocol itself has no built-in security features, because it was designed in an era when physical network security (dedicated phone lines) was the primary protection.
If you're running payment infrastructure, ensure that:
- TPDU traffic runs over encrypted channels
- Only authorized terminals can connect to payment processors
- Network access to port 1430 is strictly controlled
Checking What's Listening
To see if anything is listening on port 1430 on your system:
On Linux/Mac:
On Windows:
If you see something listening on this port and you're not running payment processing infrastructure, investigate. Port 1430 shouldn't be open on typical user systems.
Related Ports
- Port 1433 - Microsoft SQL Server (often confused due to proximity)
- Port 443 - HTTPS (modern payment APIs typically use this instead)
- Port 5000-5010 - Various payment gateway protocols
Frequently Asked Questions About Port 1430
Was this page helpful?