Voice AI Payment Card Entry Requires Strict Data-Exposure Testing

The article argues that voice agents should not collect card numbers, expiry dates, security codes or PINs dictated over the phone. Instead, payment entry should go through a separately controlled capture path, such as a validated keypad IVR or hosted payment page, with the agent receiving only minimized status updates. It stresses that redaction in final outputs is insufficient, since raw audio, intermediate transcripts, recordings, logs and support tools may still receive sensitive data. The author offers a fourteen-case synthetic test to verify that account data never reaches the model or downstream components, and notes that the tests are a design fixture rather than a PCI assessment. Teams are advised to confirm scope with their payment assessor and to keep card collection out of the agent if vendors cannot prove data-flow exclusion.