Positive Pay is a bank control that stops altered checks and unauthorized debits, and it is very good at that job, but it cannot catch the fraud that costs businesses the most: an authorized payment you were tricked into sending to a legitimate-looking payee. If your bank offers Positive Pay, you already know the reassuring version of this story, where a forged check gets flagged and an unexpected debit gets held. This guide is about the other half, the gap Positive Pay leaves open, and why closing it needs a different kind of check. The gap is not small. The 2026 AFP Payments Fraud and Control Survey found that 76 percent of organizations faced attempted or actual payments fraud and 74 percent were hit by business email compromise1, and the FBI put reported BEC losses at $3.046 billion in 2025, with 86 percent moving by wire or ACH2. Those are authorized payments, made by your own team, to accounts that looked right, which is precisely the case Positive Pay is not built to see. This guide maps exactly what Positive Pay does, the fraud it structurally cannot catch, why the blind spot exists, how it compares to payee and pre-settlement verification, and how to cover the gap. The honest short version is that Positive Pay confirms a payment matches what you told the bank to expect; it cannot confirm that what you told the bank to expect is not itself a scam.
What Positive Pay actually does
Positive Pay is a fraud-prevention service your bank offers, and it works by matching. For checks, you send the bank a file of the checks you issued, with check numbers, amounts, and often payee names, and the bank flags or returns any check presented that does not match. Payee Positive Pay adds the payee name to that comparison, so a check altered to a different payee is caught. For ACH, ACH Positive Pay, sometimes called an ACH debit block or filter, screens debits against a list of company IDs and dollar limits you pre-approved, holding or returning anything outside it. In every form, the mechanism is the same: compare what is presented to a file of what you authorized.
Against the fraud it is built for, this works well. Altered checks, forged or counterfeit checks, and unauthorized debits all fail the match, because they are not on your approved file. For a business still moving money by check, Positive Pay is one of the most effective controls a bank offers, and pairing it with daily review closes most of the check-fraud gap. The important word, though, is authorized. Positive Pay is a check on whether a payment matches your instructions, and everything it catches is a payment that does not.
The fraud Positive Pay cannot catch: an authorized payment to a changed payee
The fraud that defeats Positive Pay is the one where the payment matches perfectly, because you authorized it. In a vendor impersonation scam, an attacker gets your team to change a supplier’s banking details, then your next payment runs to the fraudster’s account. In a CEO-wire scam, an executive impersonator gets an urgent wire approved. In both, a real, authorized person in your company originated the payment, so it matches the file you gave the bank, because you are the one who put it there after being deceived. Positive Pay confirms the match and lets it through.
This is where the money actually goes. The FBI reported $3.046 billion in business email compromise losses in 2025, with 86 percent moving by wire or ACH2, and wires in particular sit almost entirely outside Positive Pay, which is built around checks and ACH debits. An authorized wire to a changed payee is invisible to it twice over: it is a credit you sent, not a debit pulled from you, and it is authorized, not altered. The control that stops altered checks was never designed to question a payment you meant to make, which is exactly what a vendor-swap or CEO-wire scam turns into. If you want that payment checked before it leaves, you can request access.
Why the blind spot exists: matching is not verifying intent
The blind spot is not a flaw in Positive Pay; it is a consequence of what matching can and cannot do. Positive Pay compares a payment to your instructions and confirms they agree. It has no way to know whether your instructions are correct, because the instructions are its source of truth. When a fraudster tricks your team into updating a vendor’s bank account, the poisoned instruction becomes part of the file Positive Pay matches against, so the fraudulent payment passes the check by definition. The control is doing its job perfectly and approving the fraud at the same time.
That is the difference between matching a payment and verifying its intent. Matching asks whether the payment agrees with what you told the bank to expect. Verifying intent asks a harder question: is this the payee you actually mean to pay, and did an authorized person genuinely approve this specific payment, checked against records the fraudster could not quietly change. Positive Pay answers the first question well and cannot answer the second at all. Any control whose source of truth is your own instructions will share this blind spot, which is why closing it requires verification that reaches outside those instructions.
Positive Pay versus payee verification versus pre-settlement verification
Positive Pay is one of several controls businesses conflate, and the distinctions matter because they cover different fraud. Positive Pay matches presented checks and debits to your approved file. Payee, or account-name, verification confirms that an account belongs to the name you entered, which helps with paying the wrong account but not with being deceived about which payee to pay. Pre-settlement verification goes further: it checks the payer, payee, amount, and purpose and confirms an authorized approval before the payment is released, which is the only one of the three aimed at the authorized-payment gap.
Because each control answers a different question, most businesses need more than one, layered rather than swapped. The full side-by-side of what each control checks, misses, and when it fires is covered in the companion guide on payee verification, Positive Pay, and fraud scoring, and the control aimed squarely at the gap is explained in pre-settlement payment verification. The short version for this post is that Positive Pay is a necessary check on your checks and debits, not a substitute for verifying the payments you originate.
Why Positive Pay still matters, and why the gap keeps growing
It would be a mistake to read this as an argument against Positive Pay. Checks remain the payment method most targeted by fraud: the 2026 AFP Payments Fraud and Control Survey found that checks were involved in 58 percent of fraud attempts, more than any other payment type1. A control built to protect checks is still doing essential work, and any business that issues checks should keep Positive Pay running and paired with daily review. Turning it off to chase newer threats would trade one exposure for another.
The gap grows because the money is moving. As businesses shift from checks toward wires, ACH credits, and instant rails, a larger share of payments falls into the category Positive Pay cannot see: authorized credits you originate. The same survey found business email compromise hit 74 percent of organizations, and those losses land on wire and ACH, not checks. So two things are true at once: checks are still the most-attacked method, which keeps Positive Pay necessary, while the largest and fastest-moving losses shift to the authorized payments it was never built to catch. The answer is not to replace Positive Pay but to add a control for the growing half of the problem.
How to cover the Positive Pay gap
Covering the gap does not mean replacing Positive Pay; it means adding the check it cannot perform. Keep Positive Pay and ACH debit blocks for the fraud they stop, and add verification of the payee and the approval before release for the fraud they miss. In practice that means confirming any change to a vendor’s banking details out of band, requiring a second, named approver on payments and changes, and holding a payment that does not match a payee record you verified through a channel the fraudster does not control. Nacha’s fraud-monitoring rules, whose second phase took effect in June 20263, now expect exactly this kind of screening for payments made under false pretenses. In practice the sequence is simple: treat any change to where a vendor is paid as unverified until it is confirmed on a channel you trust, never release a first payment to new details without a second named approver, and let a payment that does not match a verified payee record sit on hold rather than run on the next schedule.
This is where RankShield Financial fits, and it is designed to sit alongside your bank controls rather than replace them. It sits in the authorization path as a verification and attestation layer, not a wallet or a processor, and it never takes custody of your funds; your bank and rails still move the money. It verifies the payee and proves an authorized approval before release for the vendor and invoice fraud case Positive Pay misses, and seals a signed, tamper-evident record of the decision. Unlike a private fraud score you must trust, that verdict is independently verifiable, the shared signal compounds as members join rather than claiming a scale we have not yet reached, and the signing is quantum-safe by construction, not quantum-proof. The point is not that Positive Pay is weak; it is that it was built for a different fraud, and the authorized payment it cannot see is best stopped by verifying before settlement.
