Payment Hardware

How to Calculate Payment Terminal Production Metrics: 5 Core Formulas

Work through the five formulas that size a payment terminal line: key injection capacity, flashing throughput, rolled display yield, battery runtime, and wireless test capacity, each with real units and worked numbers.

Payment terminal production lines live and die on five numbers: key injection capacity, firmware flashing throughput, rolled display assembly yield, battery runtime, and wireless test capacity. Each one gates a different station, and each has a formula you can compute in under a minute once you know where the inputs come from. Cycle times come from stopwatch studies or MES timestamps, station yields come from pass and fail logs, and power draw comes from a bench DMM profile. This guide works each formula with real units and worked numbers so you can size a line for 2,000 terminals per day without guessing.

Key injection capacity equals fixture count times units per hour per fixture times availability, where units per hour per fixture is 3600 divided by cycle time in seconds. A secure room with 8 injection fixtures, a 45 second cycle (30 seconds of HSM transaction plus 15 seconds of load and unload), and 85 percent availability delivers 8 x 80 x 0.85 = 544 terminals per hour, or about 4,080 units over a 7.5 hour effective shift. The Key Injection Capacity calculator takes these three inputs directly, so you can test whether adding two fixtures or cutting 8 seconds of handling buys more output.

Firmware flashing time per unit equals image size divided by effective write speed, plus verification, plus first boot provisioning. A 512 MB image written at 20 MB per second takes 25.6 seconds, a SHA-256 verify pass at 40 MB per second adds 12.8 seconds, and secure boot plus configuration adds 30 seconds, for 68.4 seconds per terminal. A 16 up gang programmer therefore produces 16 x 3600 / 68.4 = 842 units per hour at full availability. Watch the units: vendors quote megabits per second, so divide by 8 before planning anything. The Firmware Flashing Throughput calculator handles the conversion and the gang math.

Display assembly yield is a rolled throughput calculation, not a single station number. Multiply the first pass yield of every step: optical bonding at 98.5 percent, lamination at 99.2 percent, touch calibration at 99.6 percent, and cosmetic inspection at 99.0 percent gives 0.985 x 0.992 x 0.996 x 0.990 = 0.963. Start 10,000 display stacks and only 9,630 exit clean, so you must launch 10,385 to net 10,000 good units. The Display Assembly Yield calculator chains the station yields for you. Pull each station yield from at least 2 weeks of pass and fail records, never from a single good day.

Battery runtime equals usable energy in watt hours divided by weighted average power draw in watts. Convert capacity first: a 2,600 mAh cell at 3.7 V nominal holds 9.62 Wh. Then build a duty cycle from bench measurements: idle at 0.4 W for 80 percent of the day, transaction processing at 2.5 W for 15 percent, and receipt printing at 6.0 W for 5 percent gives a weighted draw of 0.995 W. Runtime is 9.62 / 0.995 = 9.7 hours new, and about 7.7 hours after a 20 percent derate for cell aging. The Battery Runtime calculator accepts the duty cycle segments directly.

Wireless test capacity uses the same structure as key injection, but the cycle time is a sum of radio suites. A typical terminal runs Wi-Fi TX and RX at 40 seconds, Bluetooth at 25 seconds, and LTE at 90 seconds, so 155 seconds per unit. Six shielded boxes at 90 percent availability give 6 x (3600 / 155) x 0.90 = 125 units per hour. The Wireless Test Capacity calculator sizes box count against your takt. Model secure element self test the same way with the Secure Module Test Load calculator, since tamper mesh and crypto checks add another 20 to 40 seconds at final test.

Finish by checking every station against takt time, which is available production time divided by demand. To ship 2,000 terminals per day across two 7.5 hour effective shifts, takt is 54,000 seconds / 2,000 = 27 seconds per unit, so any station delivering under 133 units per hour is your constraint. Two unit errors cause most bad plans: quoting flash speed in megabits instead of megabytes overstates throughput by a factor of 8, and using mAh instead of Wh breaks runtime math whenever pack voltage differs from 3.7 V. Run each formula, line the capacities up against takt, and fix the smallest number first.

Published 2026-07-02.