Payment terminal board integration and acceptance guide
Agree the terminal workflow and acceptance checks before selecting a board. Record the exact PCB revision, firmware build and peripherals so that a passing sample can be reproduced.
What evidence should a buyer request before accepting a payment terminal board?
Ask for a configuration record and test results tied to the exact board revision, firmware and peripherals used in the sample.
Acceptance evidence by integration area| Area | Record before testing | Evidence to retain |
|---|
| Printer | Mechanism, connector and supply | Print samples and paper-out recovery log |
|---|
| Display and touch | Panel, controller, cable and firmware | Cold boot and touch alignment results |
|---|
| Reader workflow | Reader, application build and test environment | Timeout, cancellation and restart outcomes |
|---|
| Firmware recovery | Approved image and restoration procedure | Restoration log and repeated acceptance checks |
|---|
Receipt printer and power
Provide the printer mechanism, supply and interface drawing. Test printing during the intended peak workload, then repeat after paper-out recovery and restart. Record supply observations, failed prints and recovery steps.
Display and touch
Record the panel and touch controller identifiers. Verify cold boot, orientation, touch coordinates and reconnection using the intended enclosure and cables. Save the firmware build and configuration used.
Payment reader and application boundary
Identify who supplies the reader, application and final terminal. Test approved transaction workflows with test credentials. Record timeout, cancellation and restart behavior. Request evidence applicable to the exact device configuration.
Firmware recovery and change control
Restore the approved image on a sample and repeat the checks. When a PCB, peripheral or firmware revision changes, record the change and agree which checks must be repeated.
Apply the checklist to a project
Download the blank acceptance worksheet