New bank details?
Leave the message.
Build a payment-change gate around a contact channel that did not come from the request itself. Record only an alias and account last four, keep payment paused, and require a second decision before an authorized human acts.
Independent callback + approval policy
Policy sequence
Open findings
The tool does not authenticate the caller or account. If funds moved or fraud is suspected, contact the financial institution immediately through an independently obtained channel and use the incident process.
Financial-safety boundary: no output verifies account ownership, approves a payment, guarantees fraud prevention, contacts a bank or stores a full bank/routing number. Use only an alias and last four. Authorized people and the financial institution make real decisions.
$9 Minimal-Data Case Record
Generate an auditable Markdown record for this payment-change review: trusted contact source, callback result, second decision, unresolved gates, final human action and incident escalation. It is process evidence—not account verification.
- Independent contact-source and callback record
- Second-person approval or single-person escalation
- Payment-hold and conflicting-decision checks
- Incident, bank-contact and correction trail
Current official BEC and small-business guidance
PMF prior 87/100 · 90 days + 150 qualified visits + real case reuse before expansion