◆ MUNICIPALITIES

Verify the person submitting bank instructions before public funds move.

For ACH and wire payments, WireVault lets your finance team require government-ID and biometric-liveness verification for the person providing bank details. The request happens outside the email thread, and the approved instructions are preserved in a tamper-evident record. No software installation. No bank integration.

Self-service. No subscription or annual contract. Use subject to your municipality's purchasing policies.

◆ CONTEXT

Public information makes convincing impersonation easier.

Municipalities across the country are warning planning and permit applicants about fake invoices built from public agendas, project details, staff names, and official logos. The same raw material can make a request to change vendor ACH or wire instructions look routine. Email can show what was sent. It does not, by itself, establish the identity of the person who submitted the bank details.

In 2025, the FBI's Internet Crime Complaint Center received 24,768 business email compromise complaints reporting $3.046 billion in losses. Wire transfer and ACH represented 86% of the reported transaction types in those complaints.

Source: FBI 2025 IC3 Annual Report

◆ HOW IT WORKS

Three steps for a municipal payment.

  1. Request outside the email thread.

    The finance team sends the vendor or payee a secure WireVault request instead of accepting bank details in the original email conversation.

  2. Require the identity check your policy needs.

    For sensitive payments, the municipality can require the person submitting the instructions to complete government-ID and biometric-liveness verification, with no OTP fallback. Identity and liveness verification is provided through TrustStamp.

  3. Review and preserve the approved instructions.

    WireVault stores the submitted bank details and preserves the approved instructions and any later changes in a tamper-evident audit record. The finance team then releases the ACH or wire through its existing bank portal.

◆ WHAT WIREVAULT VERIFIES

WireVault verifies the identity of the person submitting payment instructions.

It does not currently verify that the person has authority to act for the vendor or payee, or that the destination bank account belongs to the intended vendor or payee.

◆ BUILT FOR MUNICIPAL PAYMENT WORKFLOWS

Built for municipal payment workflows.

Works alongside the bank portal you already use.

No bank integration or software installation.

Requester-controlled assurance.

Require ID and liveness with no fallback when policy demands it, or allow OTP for lower-assurance workflows.

Audit support.

Preserve who submitted the instructions, the verification result, the approved details, and the record of changes.

Flexible purchasing.

Use a single $25 self-service transaction, or an annual plan payable by invoice or purchase order, subject to your municipality's purchasing rules.

◆ PRICING

Municipal pricing.

Verify one payment

$25

One self-service ACH or wire-payment verification. No subscription or annual contract.

Verify one payment for $25

Municipal annual plan

$4,200 per year

200 transactions in one annual pool, used when your municipality needs them rather than by monthly allotment. $15 for each additional transaction. Annual invoice or purchase-order billing available.

Choose the municipal annual plan

WireVault does not retain government-ID or biometric information after verification. WireVault does store the bank-account details submitted through the transaction workflow.

Start with the next new or changed payment instruction.

Add an independent identity check before the next ACH or wire payment leaves the municipality. Verify one payment self-service for $25, or use one annual pool for recurring vendor-payment workflows.

WireVault adds a verification control. It does not replace municipal approval procedures, bank controls, procurement requirements, or employee judgment.

Verify the recipient before public funds move.

Get Started