Verify payment-detail changes before acting
Use a separately established verification process before changing payment instructions. Reach the authorized contact through an independently known channel and document the business approval required.
Minnesota based · Preparing for launch · Scope agreed before work begins
How can we handle a request to change bank details?
Apply the answer to your business
A convincing email can appear during a real project or invoice conversation. The accounts-payable process should not rely solely on the contact details supplied inside the change request itself.
This is an illustrative situation, not a reported CX client engagement.
Turn the question into a next action
Choose the business decision you need, involve the person responsible for the system and record what is known versus what needs validation. Keep the follow-up small enough that it has a named owner and a clear finish line.
- Ask your teamWho can approve a payment-instruction change?
- Ask your teamWhich independently known contact route is used?
- Ask your teamHow is the verification documented before payment?
Evidence to bring to the conversation.
Use the agreed scope to decide which records are relevant. These items can help the business and technical owners establish a common starting point:
- An approved payment-change workflow
- A known contact directory
- Verification and approval records
Missing evidence is an open question to document. It is not a reason to invent an answer or assume that the underlying system is protected.
Know the boundary
This is a process discussion, not a guarantee against fraud or financial advice. Your finance leadership and bank should guide the actual payment controls.
Published by CX Cyber Security · General education · Updated October 31, 2026. Further reading: NIST: phishing. CX’s original guide is not a NIST assessment or endorsement.
Plan your next step
Start with the business.
Get clear on the risk.
Tell us what your company does, the size of your team and what prompted your enquiry. We’ll discuss fit and the scope needed before proposing work.
Preparing for launch. Enquiries are welcome; delivery dates and engagements require finalized onboarding and a written agreement. Please do not email passwords or sensitive security evidence.