Put sensitive requests through a trusted second channel.
Connect trusted people and phones before an urgent instruction arrives. Then challenge the exact payment, access, account, or data request outside the call, email, or message that carried it.
CodeWords strengthens an existing approval process. It does not replace dual control, payment limits, call-backs, or formal identity checks.
New CodeWords challenge
From a trusted connection
Payment approval
Approve £18,400 to new supplier details?
Biometric approval required
Challenge the instructions that carry real consequences.
Use CodeWords where impersonation, a compromised account, or a rushed decision could move money, expose data, or grant access.
Payment and bank-detail changes
Challenge the amount, recipient, and reason through the enrolled phone before finance releases a payment or accepts new bank details.
Executive and supplier instructions
Check an urgent instruction made by call, text, email, or video without relying on the same channel that carried the request.
Access and recovery requests
Add a trusted approval before resetting an account, changing an administrator, issuing a credential, or granting sensitive access.
Sensitive data and file requests
Confirm who approved a request before the team shares payroll, customer, legal, financial, or confidential company information.
Meet once. Check from anywhere.
Enrol trusted people
Connect colleagues, principals, or suppliers in person. Rotating QR and authenticated Bluetooth help bind the relationship to two nearby devices.
Define the exact action
When a sensitive instruction arrives, create a short challenge that records what is being requested, not just who appears to be asking.
Approve on a separate channel
The enrolled phone shows the action and requires protected approval. Your team sees an approve, deny, pressure, expired, or revoked result before acting.
Check the action, not just the message.
Email headers, caller ID, familiar writing, and a face on video can all create false confidence. CodeWords sends the exact action to a phone enrolled in person, so the approval arrives through an independent, device-bound path.
Read the security modelTrusted phones connect while both people are together
A rotating QR session and Bluetooth check device proximity
Each approval is signed by a key held on the enrolled phone
Biometrics protect sensitive approvals on supported devices
Challenges name the exact request and expire after a short time
Device recovery revokes the old phone and trusted connections
What an approval means
CodeWords confirms that the enrolled phone approved the exact request shown in the app.
It does not prove that a voice, message, video image, or legal identity is genuine. A person may be under pressure, an unlocked phone may be compromised, or the wrong person may have been trusted at the first meeting. Stop if anything still feels wrong.
What people ask before they start
No. CodeWords adds a trusted device challenge to an existing control. Keep your dual approvals, call-backs, payment limits, and bank controls in place.
Yes. The request can arrive through any medium because the challenge and response happen through the separate CodeWords app.
It proves that the enrolled phone signed approval for the exact request shown in CodeWords. It does not prove that the original voice, email, or video was genuine, or that the phone holder was free from pressure.
Choose one narrow workflow with a clear owner and meaningful consequence, such as bank-detail changes or urgent executive payment requests. Enrol a small group and measure whether the extra check improves decisions.
Add a trusted check before the next sensitive request.
Book a short call to choose one high-risk workflow for a CodeWords pilot.