---
title: "Discussion on \"Why Most Call Centres Are PCI SAQ D When They Don't Have To Be\" | Hashnode"
description: "Discussion on \"Why Most Call Centres Are PCI SAQ D When They Don't Have To Be\". Why most call centres default to PCI SAQ D, how SAQ A works, and what secure DTMF capture means for compliance scope."
url: "https://hashnode.com/posts/why-most-call-centres-are-pci-saq-d-when-they-don-t-have-to-be/69f0d9b410a70b3335d28370"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why Most Call Centres Are PCI SAQ D When They Don't Have To Be](https://paytia.hashnode.dev/why-most-call-centres-are-pci-saq-d-when-they-don-t-have-to-be?utm_source=hashnode&utm_medium=feed)

Why most call centres default to PCI SAQ D, how SAQ A works, and what secure DTMF capture means for compliance scope.

Apr 28 · 4 min read · paytia.hashnode.dev  
Read the article

-   [#pci-dss](https://hashnode.com/tag/pci-dss)
-   [#compliance](https://hashnode.com/tag/compliance)
-   [#payments](https://hashnode.com/tag/payments)
-   [#call-center](https://hashnode.com/tag/call-center)

## Written by

[Curtis Nash](https://hashnode.com/@curtisnash)

@curtisnash · London UK

  
[View profile](https://hashnode.com/@curtisnash)

Founder of Paytia. PCI compliance, secure phone payments, and what call centres get wrong

CEO of Paytia (https://www.paytia.com/phone-payments) — UK provider of PCI-compliant secure phone payment solutions for call centres and merchants. I write about PCI DSS, descoping payment environments, and what most call centres get wrong about compliance

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
