Decision summary
Qualify a retail payment board with the actual display, scanner, printer, payment device, application and production BSP, including failure and recovery behavior. Treat the result as approval of a recorded configuration, not every variant in a product family.
Start with the transaction
Trace item identification, price calculation, payment acknowledgement and receipt printing. Define interrupted-payment and duplicate-receipt behavior with the application and payment-service owners.
Qualify the connected devices
Record the exact peripherals, cables, protocol and supply. Test the intended combination at once, including reconnect and busy conditions; separate successful demonstrations do not establish system concurrency.
Control the software release
Identify the Android/BSP build, application and driver versions, permissions and configuration. Preserve the approved image, release notes and recovery method with the sample result.
What evidence should be requested?
- Current model specification, drawings and interface definitions.
- Board revision, software release and connected-equipment list.
- Test procedures, conditions, results and known limitations.
- Applicable model-specific compliance documents.
- Written deliverables, support, quotation and change-control terms.
No customer deployment, certification or test result is established by this guide. Review document availability, read the source policy, or send the project requirements.