# Authentication for financial services. For the AI agents your teams run, and the customers who bank with you. > Hawcx for banks and fintechs: every AI agent tied to an employee and checked before money moves, and customers who sign in without a password. Markdown version of . Last updated 2026-10-04. Tie every payments and servicing agent to an employee, check each action before it runs, and sign customers in without a password. ## No agent moves money alone. No customer needs a password. 1. **Copilots your staff use**: Each one acts as the advisor or analyst using it, and sees only what that person can. 2. **Agents your teams build**: Payments, servicing and fraud agents work within their limits, and a second person approves what moves money. 3. **Banking without a password**: Customers verify once. Then their trusted device signs them in, so there’s no password for a scam caller to ask for. ## AI agents in banking, with limits. Checked before any money moves. Every agent answers to an employee. Each call into core banking, payments or your CRM is checked against its limits, and a second person approves what your policy names. Copilots in your CRM An advisor’s copilot drafts as that advisor, and sees only their clients. Fraud and AML cases The case agent reads its case. A bulk export of customers is turned down. Limits for each agent Set what runs, what waits for a second approver, and what never runs. Evidence for your examiners Each action with its employee, decision and approver, in one export. ## Passwordless authentication for banks. From the app to the contact centre. Customers verify once with a push, a QR scan, or an email or SMS code. After that, their device signs them in with its own key. There’s no password for anyone to phish, guess or ask for. In your banking app A new payee is approved on the trusted phone itself, with no SMS code. On a new computer, customers scan with your app to sign in. In the contact centre Callers are verified with a push to their phone, not security questions. Choose the methods your customers use, and keep SMS codes as a fallback only. ## What banks and fintechs get. Both sides of sign-in. One platform for staff, customers and agents. The person who signs in with Hawcx is the one each agent answers to. - **An employee behind every agent**: Each agent’s identity comes from the employee it works for. AI agents - **A second approver for agents**: New payees and large wires wait for the person your policy names. AI agents - **Every attempt on the record**: Allowed or not, with the agent and the employee it answers to. AI agents - **Device-bound keys**: Each device holds its own private key, never exported or shared. Passwordless - **Staff sign in the same way**: Advisors, tellers and contact-centre staff sign in without a password. Passwordless - **Methods you choose**: Push, QR, or email and SMS codes, asked again only when risk changes. Passwordless ## Financial services questions, answered - [AI agent authentication](https://www.hawcx.com/ai-agents) - [Human approval for agent actions](https://www.hawcx.com/ai-agents/approvals) - [Passwordless authentication for customers](https://www.hawcx.com/passwordless/customers) ### How do banks control what their AI agents can do? Each agent answers to the employee it works for, and every tool call is checked against that agent’s limits before it runs. Routine work, like a small fee reversal, runs. A new payee or a large wire waits for a second approver, and anything beyond the agent’s limits is turned down. ### Can an AI agent send a wire without a person approving it? Only within the limits you set. Your policy decides what counts as sensitive, such as a wire over $10,000 or a new payee. A named person sees the exact request and why it was held, then approves or declines it. Everything else keeps moving. ### Does Hawcx help banks meet regulators’ expectations for AI agents? Hawcx records every attempt an agent makes, allowed or not, with the employee it answers to, the decision and any approver. That record helps you meet examiners’ expectations for supervising AI agents. It is evidence for your own controls, not a certification. ### Can customers sign in to online banking without a password? Yes. Customers verify once with a push, a QR scan, or an email or SMS code, and from then on their trusted device signs them in with its own key. Hawcx asks again only on a new device or when a risk rule trips. It works in mobile and online banking through SDKs for iOS, Android, Web, React, React Native and Flutter. ### Can customers approve a new payee without an SMS code? Yes. The customer approves it on their trusted device, which confirms with its own key, so there’s no one-time code for a scam caller to ask them to read out. You can keep SMS as a fallback. ### Does Hawcx replace our fraud and AML monitoring? No. Hawcx doesn’t score transactions or detect fraud, so it works alongside your fraud and AML tools. It removes the password customers could be tricked into sharing, and it makes every agent action answer to an employee.