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 $3.046 billion in 2025; 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 read points, zero workflow changes
Each record already lives in your AP platform. The integration reads it as an additional recipient you control, changing no approval step.
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.
Melio decouples funding from delivery, and that changes the swap
Melio splits how you pay from how the vendor gets paid, and a payee can be paid by check or ACH without ever opening an account, which opens a redirect path beyond the bank field alone.
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.
No vendor account, two ways to receive
Melio's model is deliberately frictionless for the payee: a vendor can be paid by ACH or receive a mailed paper check even if they never sign up, and can be paid by ACH without handing raw bank details to the payer. That is a genuine security benefit against one attack and a new surface for another. Because delivery can be a mailed check, a payee-swap does not always need a bank account; changing a vendor's remittance address can redirect a physical check just as effectively. The integration reads payee and payment events across both delivery methods, so a change is scored whether it altered an ACH destination or a mailing address.
First payment to new details is the game
At Melio's small-business scale the meaningful risk is concentrated almost entirely in one event: the first payment to a new or changed payee. There is no treasury team, no independent verification desk, usually one owner or bookkeeper moving money between other jobs, so the recommended callback is exactly the step a busy week erases. The integration does close to nothing on the steady state and everything on that one event, screening a first payment to new details against the verified record before it goes and holding only the high-risk case. The design goal is a friction budget a small business will actually keep, because a control that annoys its way into being switched off protects no one.
The accountant channel is the real deployment
A large share of Melio volume runs through accounting and bookkeeping practices paying bills across many small clients, and that is where an independent layer belongs. One practice touching dozens of client payment flows is both the highest-leverage place to verify and the party most exposed if a client is defrauded, because the firm's diligence is on the record. Melio's own controls sit inside each payment; they cannot give the firm portfolio-wide visibility or a receipt that proves care per engagement. The layer spans the whole book, scores every client's change and first-payment events in one pane, and seals a per-client receipt, so the practice can show diligence rather than merely assert it.
The fraud the payment run carries
The rule families map to the most-measured payment-fraud category in the economy.
Melio's twist is delivery: because a vendor can be paid by ACH or by mailed check without an account, a swap can redirect either the bank destination or the remittance address, and both look like ordinary vendor edits. With one bookkeeper moving money and no verification desk, the only reliable early signal is the first payment to a new or changed payee. Reading that event, across both ACH and check delivery, and holding it for an out-of-band check is what separates a normal new vendor from a redirected one.
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 disrupt a payment run
The default state at every phase is no-change: nothing is held until observe mode has proven accuracy on your own vendors and runs.
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 vendor-master and payment-run history: which banking-detail changes and first payments the verification would have held, before anything touches a live run.