Reusable practice kit
Payment-change verification script
A short second-channel script for money, payroll, password, and sensitive account changes.
What the completed kit should do
Urgency and familiarity no longer bypass a known verification and approval rule.
Capture these facts in your approved system
- Request category, date, source channel, claimed requester, and urgency signal
- Trusted contact route selected independently from the request
- Verifier, neutral verification question, result, and unresolved mismatch
- Required approver, approval method, transaction hold, and escalation contact
- Suspicious-message report, provider contact, financial contact, and record location
Use the structure in this order
- 01
Pause the request without replying through the supplied route.
- 02
Open a known contact or approved portal independently.
- 03
Verify the person and requested change without revealing protected facts.
- 04
Approve, reject, hold, or escalate through the normal business process.
Close the practice loop
The requested change has an independent verification and an authorized decision.
Protect the completed record
- Do not call a phone number or scan a QR code contained only in the suspicious request.
- Do not send account numbers, passwords, codes, or identity documents through an unverified channel.
- Contact financial providers quickly if money may have moved.