Payment Provider and Card Data Handling Audit
Check how payments are taken and what data we touch.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it (what [VERIFY] means).
Audit how we handle payments. Describe checkout, payment provider integration, where card details are entered, what is stored, who can refund, and reconciliation: [PAYMENT_FLOW]. Staff who see payment information: [STAFF_ACCESS]. Past disputes or fraud: [DISPUTES]. Check whether card details ever touch our systems, what is logged, who can issue refunds, separation of duties, handling of chargebacks and fraud signals, and records kept. Suggest changes that reduce exposure. Return a table with Step, Risk (red, amber, green) and Fix, a refund authorisation rule, and a monthly reconciliation routine. Payment standards and legal duties are [VERIFY] for [JURISDICTION] with the provider. Also check support scripts, emails and chat for card numbers pasted by customers, and suggest wording that asks customers not to send them. Include a procedure for deleting any that appear in messages. Give remediation steps that are safe to try in order, with a rollback note for each, and flag any step that could cause downtime so I can schedule it with the right people.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.