About MoneyID

Building toward payment instructions that can be checked at the moment they matter.

Payment networks have spent decades getting faster and reaching further. The way organizations establish trust in a payment instruction, the bank details that say where money should go, has moved more slowly. MoneyID exists to close that gap.

Payment instructionSample

Harbor Line Supply

Bank details updated · account ending 2048

  1. Received New bank details arrive by email.
  2. Checked · 9:41 Matches the vendor’s confirmation for your organization.
  3. Changed · later Different bank details arrive.
  4. Checked again No current confirmation for these details. New confirmation needed.
Illustration with sample data. Each check reflects the moment it runs. A match does not approve a payment.
What we build
Bank-detail verification for accounts payable and treasury teams.
Our role
MoneyID does not hold funds or process payments.
Where we are
In development, tested with synthetic data.
Based in
New York, NY

01 / Then

Payments got faster. Confirmation stayed scattered.

Each generation of payments made money move faster. The record of who confirmed an instruction did not come together. It spread across more places.

  1. Paper

    How payments move: By mail

    Where confirmation lives:
    • Signed form
  2. Networks

    How payments move: In batches

    Where confirmation lives:
    • Letter on file
  3. Online

    How payments move: Online banking

    Where confirmation lives:
    • Call notes
    • Email
  4. Real time

    How payments move: In seconds

    Where confirmation lives:
    • Calls
    • Inboxes
    • Records
    • Tickets
A concept, not a measurement.
  1. Paper

    Instructions traveled slowly.

    A check, a signed form, a letter on file. Payment instructions moved at the speed of paper, and so did the people checking them.

  2. Networks

    Money sped up. Instructions became numbers.

    Electronic networks moved money across the country in a day, then faster. An account number says where money goes. It does not say who authorized it.

  3. Now

    Less time to check, more ways to ask.

    Instructions now arrive by email, attachment, portal or phone, and some payments settle in seconds. The window to check an instruction has narrowed as the ways to send one have multiplied.

02 / Today

Teams already confirm instructions. The proof ends up scattered.

Accounts payable and treasury teams run real controls. A callback to a number already on file can confirm a change. A second approver can catch a mistake.

The difficulty is what happens afterward. The confirmation lives in a call note, an inbox, a vendor record or a ticket. When details change again, or another team pays the same vendor, the work often starts over, and it can be hard to show who confirmed what, and when.

03 / The shift

From scattered confirmations to one check at the moment it matters.

MoneyID is being designed to keep the vendor’s confirmation in one place, specific to your organization, and ready to check before you pay.

QuestionTodayWith MoneyID, in the design
Where the confirmation livesAcross calls, inboxes and records.With the vendor’s confirmation for your organization.
Who confirmsWhoever your team reaches.Someone allowed to act for the vendor.
When details changeA new round of calls and approvals.New details need a new confirmation.
Before you paySaved details are often trusted because they were saved.Saved details are checked again.

A match does not approve a payment. Your team keeps its controls and decides whether to pay.

04 / Where we are today

A design, tested before it is trusted.

MoneyID is in development. The design is being tested with synthetic data, so it can be examined before it handles real bank details.

We publish where we stand. Our Security page states our readiness plainly, including what we have not done yet, and How it works shows the design step by step.

05 / Tomorrow

A world where payment instructions can be checked at the moment they matter.

  1. Less uncertainty

    Before a payment goes out, your team can see whether the instruction matches what the vendor confirmed for your organization, instead of piecing it together from old calls and emails.

  2. Fewer repeated confirmations

    Teams can check an existing authorization instead of repeating the same callback. When details change, or a confirmation no longer applies, a new confirmation is needed.

  3. Clearer responsibility when details change

    It is clear who confirmed a change, for which organization, when, and whether that confirmation still applies.

For every organization that pays vendors

  • Schools
  • Universities
  • Companies
  • Non-profits
  • Governments
  • Checked, not assumed

    Authorization can change. The right time to check an instruction is when it matters, not only when it first arrived.

  • Your controls stay yours

    A match does not approve a payment. Your team keeps its own steps and decides whether to pay.

  • Honest about what is ready

    We say what works today, what is planned and what is not on our roadmap.

See where MoneyID could fit.

Work directly with the MoneyID team to explore bank-detail checks shaped around your vendor payment workflow.