Prevent payment fraud with a bank change verification workflow, independent verification scripts, evidence rules, and escalation paths.
Bank change requests are a top fraud vector. Most fraud succeeds because verification is informal.
This playbook installs a beginner-safe workflow that:
Not legal advice.
Stages:
Beginner-safe rule:
Use:
Copyable template (TEXT)
Vendor Bank Change Verification Script Hello, this is [Name] from [Company]. We received a request to update your payment details. To confirm: 1) Are you requesting a bank change today? 2) What is the reason for the change? 3) Please confirm the last invoice number you issued to us. 4) Please confirm the remit-to address currently on file. 5) We will only accept bank detail updates through [approved method]. Do you agree? Outcome: - Verified: yes/no - Verification method: phone / portal / other - Evidence captured: - Next action:
Copyable template (TEXT)
Bank Change Evidence Checklist - Request source captured - Risk classification completed - Independent verification completed out-of-band - Approval recorded - Vendor master data update log captured - Payment hold/test payment decision recorded (if applicable)
v1.0 (2026-01): Latest release