What is a PIN pad?

A PIN pad is a customer-facing payment device or terminal component designed to accept a personal identification number when a transaction calls for PIN entry. Many modern PIN pads also display prompts and may include card-reading features, but the exact functions depend on the device, payment application, provider, and merchant configuration.

The name can be misleading because a current PIN pad may do more than show number keys. Some devices use physical buttons, while others use a touchscreen. Some are separate from the merchant's register, and others are built into a complete payment terminal. A product should be evaluated by its documented functions rather than by its appearance or generic label.

What a PIN pad does during checkout

Shows customer prompts

The device can present the amount, request an action, and guide the customer through the configured payment flow. Prompts vary by transaction and setup, so staff should let the approved application direct the sequence.

Accepts PIN entry when requested

EMVCo describes a PIN as one type of cardholder verification method. A PIN is not required for every chip, contactless, credit, or debit transaction; the available verification path depends on the payment method and configured acceptance environment.

May capture the payment method

Depending on the model, a customer-facing device may also read a contact chip, accept a contactless tap, or provide another documented input method. Those capabilities must be confirmed for the exact hardware and deployment.

For the broader transaction sequence around the device, see how a credit card terminal works.

PIN pad, card reader, or full terminal?

PIN pad

This term emphasizes customer interaction and secure PIN entry. A PIN pad may be a peripheral connected to a register or part of a larger terminal. It should not be assumed to process payments by itself.

Card reader

A reader captures information from an enabled card or contactless device. A compact reader may rely on a phone or tablet for the merchant interface; read what a mobile card reader is for that arrangement.

Payment terminal

A full terminal may combine customer prompts, card-reading interfaces, a keypad or touchscreen, connectivity, and a merchant workflow. The phrase credit card machine is often used informally for this broader category.

These labels overlap in everyday use. The useful question is not what the seller calls the device, but which functions the documented and configured setup actually provides.

How a PIN-pad transaction typically flows

The merchant starts the sale. The amount and permitted transaction details are entered through the register, POS system, or terminal.
The customer follows the device prompt. The customer presents an enabled payment method through the interface shown by the configured application.
Verification occurs when requested. If the transaction flow calls for a PIN, the customer enters it on the approved interface without sharing it with staff.
The payment environment sends the request. The device works with the configured application, network, and payment service to transmit the transaction request.
The merchant follows the response. Staff complete the approved workflow shown by the system. Possessing a PIN pad does not guarantee approval of any transaction.

Features merchants should evaluate

Customer interaction: Check display readability, physical versus touchscreen input, placement, accessibility needs, and the clarity of prompts.
Documented payment interfaces: Confirm the exact model's supported card-reading methods and whether each needed function is enabled in the proposed setup.
Register and service configuration: Determine how the device connects to the merchant workflow. Do not infer integration or processor compatibility from a connector, logo, or model family.
Environment: Consider counter space, cable routing, power, network needs, customer reach, and whether the hardware is intended for attended or unattended use.
Support status: Ask the responsible provider for the exact hardware and software versions, update path, support process, and replacement plan before deployment.

A merchant comparing form factors may also review guidance on cleaning payment equipment so placement and care expectations are understood before rollout.

Safe operation and privacy

PCI Security Standards Council materials distinguish several types of point-of-interaction devices, including PIN-entry devices and encrypting PIN pads. The category or feature name alone does not establish that a particular merchant deployment meets every applicable requirement. Device selection, configuration, key management, payment application, and provider responsibilities can all matter, so merchants should use the documentation and support channel for their actual setup.

Keep an inventory of deployed devices and train staff to recognize changes in the case, seals, cables, connections, or surroundings. If a device appears altered or unfamiliar, stop using it and contact the responsible terminal provider or merchant bank through a verified support channel. Do not attempt an unapproved repair.

Customers should enter their own PIN privately. Staff should never request, write down, photograph, repeat, or submit a customer's PIN through a general contact form. Merchants seeking help should share the device model and a description of the workflow, not card numbers, PINs, passwords, bank credentials, or secret keys.

Does every merchant need a PIN pad?

Not necessarily. The appropriate customer-facing hardware depends on the payment methods a business intends to accept, its checkout workflow, the requirements of its provider and acquiring arrangement, and the functions supported by the exact device. A merchant should document those needs first and then have the responsible provider confirm the proposed configuration.

Choose hardware around the checkout workflow

Before requesting equipment, write down where customers pay, which payment methods the business expects to accept, how the register or POS operates, and who will support the device. Payments Max can use that non-sensitive context to help frame the next questions for a provider without promising compatibility, availability, or transaction approval.

Discuss your payment workflow

Do not send cardholder data, PINs, passwords, bank credentials, complete account numbers, or API keys through a general inquiry.

To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.