MoneyID is being built to check the bank details you received against payment details the vendor has confirmed with MoneyID for your organization, and to keep a record of each check.
A check against what the vendor confirmed for you.
Check the bank details you received against what the vendor confirmed with MoneyID for your organization.
Illustrative preview
Sample data
Harbor & Pine
Your organization
Northline Operations
Compared with
Details the vendor confirmed for you
Result
VALID (sample data)
Checked
Oct 5, 2026 · 11:28 ET
Record
SAMPLE-0001
A result is a comparison. It is not a verdict on the email or the sender. A check does not send or authorize a payment; your team follows its own verification policies.
What your team gets
A result, and a record of the check.
Who decides
Your team decides whether to pay.
MoneyID is meant to support, not replace, the verification steps your policies require.
The problem, and where MoneyID fits
The invoice can be real. The bank account can be wrong.
Payment redirect scams impersonate a trusted vendor and ask your team to send money somewhere else. A convincing message is not independent verification.
01
A request arrives
Illustrative example
New bank details, in a familiar name.
A vendor you pay every month emails new bank details for an invoice that is due. Nothing about it looks unusual.
02
The open question
Illustrative example
Is this account one the vendor actually confirmed?
The email cannot answer that, and neither can a reply to it. Your team has no independent record to compare against.
03
Today's answer
Illustrative example
Callbacks, holds and escalation.
Your team calls a number already on file, holds the payment, and escalates when no one picks up. It works, and it takes time on every change.