Payee verification for small businessespaying bills through Melio.For small businesses paying vendors through Melio, RankShield adds the independent check payee-swap fraud is designed to bypass: vendor banking-detail changes and first payments to new details are scored and, when high-risk, held for out-of-band verification before the payment goes — with a sealed, verifiable receipt behind every decision.
Small-business bill pay is where the losses concentrate
Melio serves the smallest end of the market — the businesses where one owner or bookkeeper handles every bill, often through an accountant channel. That is precisely the population the loss data points at: organizations without a verification function absorb payee-swap fraud disproportionately, because the recommended defense — call the vendor on a known number before honoring a banking change — depends entirely on one busy person’s discipline in a busy week. The FBI’s IC3 put reported business email compromise losses at $2.77 billion in 2024; the median victim in that number looks a great deal more like a Melio customer than a bank.
The lightest possible layer that still counts
RankShield reads vendor and payment data through the platform’s integration surface and applies exactly two disciplines where they matter: banking-detail changes verified out-of-band before the next payment relies on them, and first payments to new details screened against the verified record. Everything else flows untouched. For accountants and bookkeepers running bill pay across many small clients, the layer spans the whole book with per-client receipts — protection for the client, proof of diligence for the practice.
Three tap points, zero store changes
Each feed already exists — the integration directs it to one additional recipient you control.
Vendor & payee records
Banking-detail changes and new payees scored on arrival — the two events that precede nearly every small-business payee-swap loss.
Payment activity
Payments to new or changed details screened against the verified record before they go.
Accountant book view
Practices running bill pay for many clients see every vendor-risk event across the book, with receipts per client engagement.
What the integration reads in an AP platform
The payee swap executes through the vendor record and the payment run. The integration reads exactly those, and applies the verification federal guidance already recommends.
On this stack specifically: At the small-business end, the deployment channel is usually the accountant, not the business itself — the practice that runs bill pay across dozens of clients is where one integration protects the most money and where receipts proving diligence carry professional weight.
The vendor master is the record fraud poisons
Every AP platform holds a vendor master — payees and their banking details — and a payment run that trusts that record absolutely at execution time. The payee-swap attack changes the banking detail on a legitimate vendor record, after which every properly approved payment flows to the fraudster. The integration consumes vendor-master change events, bill records, and payment-run data through the platform’s API, and scores the events that precede loss: a banking change, a first payment to new details, an invoice breaking a vendor’s baseline.
ACH, Nacha, and the limits of “reversible”
Much AP money moves by ACH, governed by the Nacha operating rules. It is worth being precise, because “ACH is reversible” is folklore: a business gets a limited window on an unauthorized debit and effectively no return right on a credit it originates to a fraudster. Nacha’s own 2026 rule changes push account validation and fraud monitoring precisely because the return safety net is thinner than assumed. Verifying the payee before the run is the control; the return window is not.1
Out-of-band verification is the recommended control
The FBI and Nacha both name out-of-band verification of banking changes and dual control as the primary defenses against business email compromise. The integration automates exactly those steps and makes them unskippable — the manual version is what a busy AP desk skips under deadline. Independence is the design point: the layer verifying the payee sits outside the platform holding the record, and every verdict seals to a receipt that survives the dispute, the audit, and the insurer’s questionnaire.23
Why the receipt matters as much as the hold
Stopping a fraudulent payment is half the value; being able to prove diligence is the other half, and it is the half in-platform controls cannot provide about themselves. Every verification RankShield performs (the out-of-band confirmation, the person who approved it, the evidence trail behind a hold) seals to the RankShield Network as an independently checkable record. That record is what an insurer crime-policy questionnaire asks for, what an auditor reconstructing a payment needs, and what a bank recovery process wants when a loss does occur and speed of reporting drives whether funds can be frozen. A dashboard screenshot is a claim; a sealed receipt is evidence, and the distinction is the whole point of a verification vendor.
The fraud the payment run carries
The rule families map to the most-measured payment-fraud category in the economy.
Business email compromise is the payee swap at scale, and the FBI has tracked over $55 billion in exposed losses across the decade through 2023. FinCEN has since alerted institutions to generative-AI-forged documents defeating verification controls — which is why the defense is procedural, not forensic: verification against records the fraudster does not control, made unskippable, with a sealed receipt. The integration applies that discipline to the specific events a payment run produces, before the money moves. The AFP practitioner survey, the treasury profession own measurement, adds the base rate: roughly four in five organizations faced attempted or actual payments fraud, with vendor and executive impersonation the leading methods and wires the payment type most targeted. None of that is platform-specific, and the integration does not pretend a given tool invites fraud; it consumes the vendor-master and payment-run events any AP platform produces and applies verification at the two moments loss actually occurs: the banking-detail change and the first payment to new details.67
Where does your AP process stand?
Each question maps to a feed or control this integration depends on. The tally runs in your browser — nothing is transmitted.
- 01Can one person both change a vendor’s bank details and approve the payment?
- 02Do you always confirm a bank-detail change on a number from your own files, not the request?
- 03Is the first payment to a new or changed payee held for verification before it goes out?
- 04Do you keep a signed record of exactly who approved each payment?
- 05Does your platform expose vendor and payment data through an API you could authorize?
Answer all 5 to see where you stand · 0/5
The rollout that cannot break your stores
The default state at every phase is no-change: nothing is blocked until observe mode has proven accuracy on your own traffic.
Connect the AP data, change no workflow
RankShield reads the vendor master, bill records, and payment-run data your platform already exposes through its API or exports. No approval flow is modified, no payment path is touched, and your team keeps working exactly as before.
Observe mode baselines your payee risk
The rail scores historical and live payment runs — banking-detail changes, first payments to new details, invoice anomalies — and shows what it would have held, advisory-only. Accuracy is proven on your own vendors before anything is gated.
Verification before the run, sealed receipts behind it
High-risk payments hold pending out-of-band payee verification — the control the FBI and Nacha already recommend, automated and made unskippable. Every hold and clearance seals to the RankShield Network with an independently verifiable receipt.
What the rail watches on this stack
- Vendor banking-detail changes held until verified out-of-band
- First payments to new details screened before release
- New-payee risk signatures scored at creation
- A sealed, independently verifiable receipt for every hold and clearance
An integration path, not a partnership claim
Melio is a product of Melio. RankShield Financial is an independent platform and is not affiliated with, certified by, or endorsed by Melio. This page describes RankShield’s supported integration architecture for merchants who run Melio: it consumes data feeds the merchant already owns and directs — transaction journals and processor reporting — and never modifies the named system or its payment path. We hold every page on this site to the same standard as our verdicts: claims you can check.
References
Standards are cited to the bodies that maintain them; fraud statistics to government and association primaries. Measurements from industry vendors are labeled as such.
- Nacha — ACH Network Rules and fraud-monitoring / account-validation requirements
- FBI IC3 — PSA240911: Business Email Compromise, the $55 Billion Scam
- FBI IC3 — 2025 Internet Crime Report
- AFP — 2025 Payments Fraud and Control Survey (press release)
- FinCEN — Alert on Fraud Schemes Involving Deepfake Media (FIN-2024-Alert004)
Integrating beside Melio, answered
Every question buyers ask before they trust a payment-security platform, answered directly.
JAMIE KLONCZ · RANKSHIELD FINANCIAL ONLINEPick a question on the left, or search above. You will get the direct answer, the way an answer engine would give it.
Other integration paths
Start with your own data, not our promises.
Phase 1 is a findings report on sixty to ninety days of your existing journal and authorization history — what the rules would have caught, store by store, before anything touches production.