
Zelle moves money between bank customers in minutes, using just an email or phone number. That speed and simplicity are why customers love it, and why scams are the biggest risk. This is the short version of how I take a Zelle change at a bank or credit union from idea to live, safely.
New here? Start with How a US Payment Works: 15 Steps Inside a Bank, then come back for the detail.
How a Zelle payment moves
Read from left to right. Each box is one step of a Zelle payment, from the sender’s banking app to the recipient. The band at the bottom shows the controls that matter most. Most losses come from customers being tricked into sending money, and the payment can’t be pulled back once sent.
Zelle in one minute
Zelle is owned and operated by Early Warning Services, a company owned by large US banks. In 2025 customers sent more than $1.2 trillion through Zelle, up 20% on 2024, in 4.2 billion transactions, through more than 2,300 banks and credit unions. Nearly 30% of the dollars went to or from small businesses. The standalone Zelle app closed in April 2025, so Zelle now lives inside each bank’s own app.
| Topic | What to know |
|---|---|
| Identity | Customers send to a US mobile number or email, not an account number. Zelle calls this phone number or email a “token” |
| Speed | Usually minutes between enrolled users |
| Finality | Once sent to an enrolled recipient, it can’t be cancelled |
| Limits | Set by each bank, often lower for new accounts and new payees |
The real risk: scams
Most Zelle losses come from customers being tricked into sending money themselves. Regulators and state attorneys general are watching closely. The New York Attorney General sued Early Warning Services in August 2025. So fraud controls must ship in the first release, not later.
Controls that matter most: a fraud score on every payment, clear scam warnings at the moment of sending, lower limits for new payees, checks when a phone number or email moves to a new account, and spotting “mule” accounts that criminals use to collect stolen money.
Building it: short cycles, firm checkpoints
- Test sign-up as hard as payments. Adding, changing or moving a phone number or email is where account takeovers happen.
- Pass Zelle’s own tests (certification) before go-live and after major changes.
- Prove it live. Employees send and receive across banks, send to someone not yet enrolled, trigger a scam warning and a limit decline, and raise a test claim.
| Gate | Done when |
|---|---|
| E2E exit | Zelle certification passed, 95% or more of our tests passed, fraud and token cases proven, all records match (reconciliation) |
| UAT exit | Scam claim, wrong-recipient and token takeover procedures tested by service and fraud teams |
| Go-live | Pilot payments checked, warnings and limits live, evening and weekend support in place |
Running it live
Customers send money in the evenings and at weekends, so the call center and fraud team must cover those hours. Alert on failures, declines and fraud alerts above normal. When a scam is reported, act at once: report to the network, contact the receiving bank, and check whether the receiving account looks like a mule account.
Download the full runbook (PDF, 11 pages)
Every phase in detail, with Zelle facts, rules, exit criteria and sign-off, a live pilot plan, scam and fraud controls, alerts, incident runbooks, disaster recovery and audit checklists.
The files behind this runbook
Every part of this runbook touches the same handful of files. Here is where each one shows up. For what is inside each file, with samples and a step-by-step checklist, see Zelle, step by step.
| File or moment | Where it matters in this runbook |
|---|---|
| App request and scam warning | The real risk: scams |
| Directory lookup and network API | How a Zelle payment moves |
| PENDING, CANCELLED, EXPIRED statuses | Running it live |
| Claim cases | Running it live: claims and scams |
More payment runbooks
- ACH payments
- Wire payments (Fedwire and CHIPS)
- Instant payments (RTP and FedNow)
- Card payments (debit, credit, prepaid)
- Checks and remote deposit capture
- Cross-border payments over SWIFT
- PayPal integration
- Embedded payments
The bottom line
Zelle works when customers trust it. Build scam controls into the first release, test tokens as hard as payments, and staff support for the hours customers actually use it.
Working on a payments project?
I help banks and fintechs deliver real-time payments, ISO 20022, and AI-driven AML and compliance change, from strategy to go-live.
Connect on LinkedInSee how I can help