--- title: "Manual callback verification vs RealPayee: is a phone callback enough? (2026)" description: "Manual callback verification compared with RealPayee: what a callback catches, where it breaks (wrong numbers, skipped steps, voice cloning) and how to make it stronger." url: https://realpayee.com/alternatives/manual-callback-verification canonical: https://realpayee.com/alternatives/manual-callback-verification date_published: 2026-10-05 date_modified: 2026-10-05 author: RealPayee --- # Manual callback verification vs RealPayee > A manual callback means an AP team member phones the vendor on a number already on file before changing bank details. It is free and works when done every time with a trusted number. It fails when staff call the number in the fraudulent email, skip it under pressure, or accept a cloned voice, and it leaves thin evidence. RealPayee automates the hold, the out-of-band confirmation and the record. _Reviewed 2026-10-05 · By RealPayee_ ## What Manual callback verification is Callback verification is the baseline control most AP policies already require: when a vendor asks to change bank details, someone calls the vendor using contact details from the vendor master file or the original contract, never from the request itself, and confirms the change before it is saved. It is recommended by banks, auditors and insurers and is the core of our free [vendor bank-change policy template](https://realpayee.com/templates/vendor-bank-change-policy). ## Manual callback verification vs RealPayee at a glance | | Manual callback verification | RealPayee | | --- | --- | --- | | What it checks | That someone answering a known number confirms the change | Whether the real person (the vendor's known contact, or the real executive) actually made the change or request | | Can it be skipped? | Yes, it relies on each person following policy | No, the change or payment is held until confirmed | | Number source | Depends on staff using the file, not the email | Known contact from your records; no number taken from the request | | Voice cloning risk | High: a convincing voice on a call can pass | Lower: phone-bound approval or ID plus live selfie | | Evidence | Free-text note or ticket, if recorded | Audit record of who confirmed, how and when, for auditors and cyber insurers | | Cost | Staff time | Starter $250/month, Growth from $750/month, Enterprise custom | ## Where Manual callback verification wins - **No cost and no software.** Any team can start today. - **Universally understood** by auditors, banks and insurers. - **Works for any vendor**, including ones with no email or messaging access. - **A human conversation** can surface context a system would miss. ## Where RealPayee wins - **It cannot be skipped.** RealPayee holds the change or payment in the ERP until confirmation, so a busy day or a pushy request does not bypass the step. - **The channel is bound to the known contact.** Confirmation goes to the contact on record or requires ID plus live selfie, so a cloned voice or a number from the fake email does not pass. - **Evidence is automatic**: who confirmed, on what channel, when, attached to the record. - **It also covers high-value wires and executive requests**, where callbacks are often informal. ## When to choose which ### Choose Manual callback verification if - You have a handful of vendor changes a month and a disciplined team. - You are writing your first policy and need a control today. Start with the [policy template](https://realpayee.com/templates/vendor-bank-change-policy). ### Choose RealPayee if - You process enough changes that consistency is hard to guarantee. - An auditor or insurer has asked for evidence that callbacks actually happened. - You worry about voice cloning or executive impersonation on calls. - You want to see it on your own flow first: [book a demo](https://realpayee.com/demo). ## Can you use both? Yes. Keep the callback in your written policy as the fallback for vendors who cannot use SMS, Slack or Teams, and let RealPayee enforce and record the rest. ## Frequently asked questions ### Is a callback enough to stop vendor fraud? Only if it is done every time, to a number from your own records, by someone who would notice a bad answer. In practice those conditions slip. See [Is a callback enough to stop vendor fraud?](https://realpayee.com/answers/is-a-callback-enough-to-stop-vendor-fraud). ### What number should a callback use? A number from the vendor master file, the signed contract or an earlier invoice you have already paid successfully. Never a number, link or contact in the request asking for the change. ### Can AI voice cloning defeat a callback? It can when the attacker controls the number you dial, or when they call you and you treat that as a callback. An inbound call is not a callback. Read more on [deepfake scams](https://realpayee.com/blog/deepfake-scams). ## Related - [Free vendor bank-change verification policy template](https://realpayee.com/templates/vendor-bank-change-policy) - A free, copy-ready vendor bank-detail change and callback verification policy template plus checklist for AP teams. (markdown: https://realpayee.com/templates/vendor-bank-change-policy.md) - [Vendor verification: how to verify vendor bank details before you pay](https://realpayee.com/vendor-verification) - A practical guide to vendor verification for finance teams: how to confirm vendor bank-detail changes, run callbacks, and prevent vendor impersonation fraud. (markdown: https://realpayee.com/vendor-verification.md) - [Is a callback enough to stop vendor fraud?](https://realpayee.com/answers/is-a-callback-enough-to-stop-vendor-fraud) - When a phone callback stops vendor fraud, when it fails (wrong numbers, skipped calls, voice cloning) and what to add so the control holds. (markdown: https://realpayee.com/answers/is-a-callback-enough-to-stop-vendor-fraud.md) - [Deepfake scams: how AI voice and video fraud targets finance](https://realpayee.com/blog/deepfake-scams) - How deepfake scams and AI voice cloning target finance teams, what the Arup and Ferrari cases teach, and a verification protocol your team can run today. (markdown: https://realpayee.com/blog/deepfake-scams.md) --- Canonical HTML: https://realpayee.com/alternatives/manual-callback-verification · Site index: https://realpayee.com/llms.txt · Book a demo: https://realpayee.com/demo