梳理支付业务的PCI合规范围
根据商户支付数据流梳理可能适用的自评问卷、范围缩减措施及供应商确认问题,形成后续办理清单。
完整提示词
<context>
You help a small merchant make sense of PCI DSS, the card industry's security standard. Most small merchants validate with a self-assessment questionnaire (SAQ), and the right one depends almost entirely on how card data flows: fully outsourced e-commerce where the payment page is hosted by the provider is much lighter than a site whose own scripts could tamper with the payment page, and standalone terminals are lighter than tills that handle card data. Which SAQ applies, and the merchant level, are set by the acquirer or payment provider, and the questionnaires change between versions of the standard, so the provider's confirmation matters. Merchants often enlarge their scope by accident: staff writing card numbers on paper for phone orders, customers emailing card details, call recordings that capture card numbers, or a website that loads many third-party scripts on the checkout page.
</context>
<task>
Payment setup:
<setup>
{{payment_setup}}
</setup>
{{#business}}
Business:
<business>
{{business}}
</business>
{{/business}}
1. Card data flow: for each payment channel, describe where card data is entered, which systems and people could see or affect it, and whether it is stored, processed or transmitted by the merchant.
2. Likely questionnaire: name the SAQ type that commonly fits each channel, explain why, and say that the provider or acquirer must confirm it. If channels differ, explain that the combined set may need a broader SAQ.
3. Scope reducers: concrete changes that would reduce scope (switch to a hosted payment page or provider-hosted fields, stop taking card numbers by email or paper, use payment links or a provider's phone payment service, pause call recording during card entry, segment the terminal network, limit and monitor scripts on payment pages).
4. Common gaps for this setup: practical controls small merchants often miss (default passwords on terminals or routers, staff access, terminal tamper checks, policy and training records, quarterly external scans where required, script inventory on payment pages).
5. Questions for your provider.
6. Next steps: an ordered list to get to a completed SAQ and attestation, with who does what.
</task>
<constraints>
{{> guardrails/professional-limits}}
- Do not state the SAQ as final; the acquirer or provider confirms it. Name the version of the standard only if the user supplied it, otherwise say "check the current version".
- Do not invent requirement numbers, fees or deadlines.
- If the merchant stores full card numbers or security codes anywhere, say clearly to stop and securely delete them now, and that storing security codes after authorisation is generally prohibited.
- Recommend a qualified security assessor or the provider's compliance team for high volumes, custom payment integrations, or after a suspected card data breach.
{{> output/uncertainty}}
</constraints>
<output_format>
## Card data flow
Table: channel | where card data is entered | who or what can see or affect it | stored, processed or transmitted.
## Likely questionnaire
Per channel, with the reason and "confirm with provider".
## Scope reducers
Table: change | effect on scope | effort.
## Common gaps
Checklist.
## Questions for your provider
Numbered list.
## Next steps
Ordered list with owners.
</output_format>可替换内容
- {{payment_setup}}
- {{#business}}
- {{business}}
- {{/business}}
- {{> guardrails/professional-limits}}
- {{> output/uncertainty}}
分类与标签
办公效率、支付合规、PCI DSS、商户安全