Signed Approvals For Construction Draws

The Gate Between Proof And Payment.

No release instruction is issued until both required approvals are signed and the release checks have cleared the draw. A draw the checks hold needs an administrator’s written review.

VERA keeps the record. Your bank moves the money.

Individually Signed Approvals Signed Evaluation Records (Advisory) Hash-Only Anchoring (Test Network In The Pilot) Patent Pending
Awaiting Approvals
The Problem

Verification Often Comes After The Money Moves.

Some disbursement processes check supporting documents only after funds have moved. Errors are harder to recover by then. VERA puts the proof ahead of the release instruction and records each approval, release and review.

In construction lending the risk is concrete. ALTA’s title insurance guide says construction liens have historically been “one of the greatest sources of loss to the land title industry.”

Source: ALTA, Title Insurance guide, Chapter 10, Construction Liens (2022).
The Wider Payments Landscape
Improper Federal Payments, FY2024
$162B
Estimated Annual Federal Losses To Fraud
$233–521B
Improper Federal Payments Since FY2003
$2.8T
Reported Consumer Fraud Losses, 2024
$12.5B
What VERA Puts In Front Of A Release
  • No release instruction is issued until both required approvals are signed and the release checks have cleared the draw.
  • Approvals, releases and reviews are recorded in a hash-chained audit log.
  • Read-only examiner access, with CSV and PDF exports, supports independent review.
  • VERA refuses a second approval from the same sign-in or the same signing key.
The federal and consumer figures describe the wider payments landscape. They are not VERA results. Sources: GAO-25-107753 (March 2025), GAO-24-105833 (April 2024), FTC Consumer Sentinel (March 2025).
How The Gate Works

What Happens On A Release.

The required parties sign, the release checks run, and the decision is recorded. Supporting documents are fingerprinted when they are added.

01 · Fingerprint

Fingerprints, Not Files

Supporting documents are fingerprinted with SHA-256 in the user’s browser. VERA stores the fingerprint and a reference to the document. The app has no feature for uploading the document itself.

02 · Approve

Required Parties Sign

The inspector and the loan officer each sign with their own registered key. VERA refuses a second approval from the same sign-in or the same signing key.

03 · Decide

The Gate Evaluates

Automated release checks run on every draw. The draw is released, held for review or denied, with a reason. A separate decision service also records a signed policy evaluation of each release. In the pilot it is advisory and does not block a release. VERA does not screen payees for sanctions; that is expected to stay with your institution’s own program, agreed in the pilot. Because VERA supplies no screening result, the decision service’s recorded evaluation currently reads DENY. That is not a refusal of the release, which the application’s own checks decide.

04 · Record

Recorded, With A Test-Network Timestamp

Approvals, releases and reviews enter a hash-chained audit log. The attestation for each released draw is fingerprinted and published to the XRP Ledger test network. The test network is reset from time to time, so these entries demonstrate the mechanism and are not permanent records.

What A Release Record Looks Like

One Draw, Start To Finish.

Every release leaves a record in VERA that your bank and your examiner can read and export. After the bank confirms, a sealed closing record can be checked on a public page by anyone who holds the documents, such as your title company.

The record is built as the work happens, not assembled afterwards.

  • Every approval is signed with the approver’s own key. VERA refuses a second approval from the same sign-in or the same signing key.
  • The bank pulls the instruction and confirms it with its own reference.
  • The sealed record can be checked by anyone holding the document, without a VERA account.

VERA sits in front of your existing draw process. It does not replace your loan system or your decision.

What Is In Place Today

Built For Construction And Commercial Real Estate Lending.

VERA is offered today to banks and lenders for construction draws, and to family offices for real estate draws. VERA is built and tested for construction draws. Other disbursement workflows are not built, tested or offered today.

Construction Draws

Inspector and loan-officer approval before every release. The release checks compare each draw with the project’s latest completion report. After the bank confirms a release, one sealed closing record ties the approvals, the instruction and the bank’s confirmation together.

Individually Signed Approvals

Each approval is signed with the approver’s own key. VERA never holds an approver’s private key.

Separation Of Duties

Role-bound accounts, enforced in code. The assigned inspector and the assigned loan officer must each sign. VERA refuses a second approval from the same sign-in or the same signing key.

Release Checks

Automated checks run on every release before it is issued. The check list is available to evaluating institutions under a non-disclosure agreement.

Hash-Chained Audit Log

Each entry carries a hash of the one before it, so a removed or reordered entry shows when the log is checked. Entries since October 7, 2026 can also be checked for altered content.

Examiner Access

A read-only role for audit and examination staff, with CSV and PDF exports.

Also in place: two-step sign-in required on every account, with lockout after repeated wrong passwords; nightly database backups, with a backup file restored into a clean database and compared with production. The attestation-signing key is held in Google Cloud KMS.
The Pilot

What A 90-Day Pilot Looks Like.

One lender, one set of real draws, a fixed 90 days. You decide at the end whether to continue.

01 · Set Up And Train

Weeks 1–2

We create your accounts and assign the inspector and loan-officer roles. Your administrator or loan officer records the payment destination your bank has confirmed. VERA checks only the format of the routing number. We train the people who will sign. Everyone signs in with a second step.

02 · Run Real Draws

Weeks 3–11

Draws on your project go through the gate. Each release instruction goes to your bank desk; your bank pays through its own systems and confirms with its own reference.

03 · Review And Decide

Week 12 Onward

We review what ran, what held and why, and what to change. You keep the exports. You then choose whether to move to a license.

What Your Bank Provides
  • A pilot owner, the loan officer or officers who will sign, and an inspector for the project.
  • One project, the payment destination your bank has confirmed and a notice email address for release instructions.
  • A person who confirms each release in your bank’s own systems.
What You Get
  • Signed approvals, release checks and an approval record on every draw.
  • After the bank confirms a release, VERA can seal one closing record for that draw. The sealed record can be checked on a public page without a VERA account. During the pilot it is anchored to the ledger’s test network.
  • Read-only examiner access with CSV and PDF exports, and a review at the end.
Flat pilot fee; terms on request. During the pilot, ledger anchoring runs on the ledger’s test network.
A Verifiable Record

A Fingerprint On A Public Ledger.

The attestation for each released draw, and each sealed closing record, is fingerprinted and published to the XRP Ledger test network. Only a hash is published, with a short record-type label. No names, amounts, account numbers or documents.

Network
XRP Ledger test network during the pilot. Moving to the main network is decided with the pilot institution.
What Is Published
A SHA-256 fingerprint of one draw’s attestation, or the combined fingerprint (Merkle root) of a sealed closing record
Example Test-Network Anchor
74C5D371B5C1AC95EC65EAAA6F7E586B163A77CCBB152E4C2CB035F2FA510D2F
Approval Signatures
Signed by each approver’s own key
Evaluation Records
Signed with Ed25519; advisory in the pilot
Audit Export
CSV and PDF of the page the examiner has on screen (50 rows at a time), through a read-only examiner role. The export shows the action and the time but not the name of the user who acted.
View This Anchor On The XRPL Test-Network Explorer →
The test network is a free practice ledger. During the pilot, records are real in VERA and demonstration-grade on the ledger. Test-network anchors demonstrate the mechanism; they are not production records.
Data Handling

Sensitive Personal Information Stays With You.

VERA is designed to hold little personal information. Your institution decides what it enters, and VERA handles it on your behalf as a service provider.

  • No Sensitive Identifiers By Design. The database has no fields for Social Security numbers, dates of birth, payment-card numbers or government ID numbers. The client agreement asks clients not to enter them in free-text fields.
  • Fingerprints, Not Files. The app fingerprints each supporting document with SHA-256 in your browser and stores the fingerprint and a reference to it. It has no feature for uploading the document itself.
  • Hash-Only Public Record. The public ledger receives a hash and a short record-type label, sent from VERA’s own ledger account. Nothing about the draw itself is published.
  • Encrypted. Bank routing and account numbers and authenticator secrets are encrypted by the application with AES-256-GCM before they are stored. Connections to the website, the app and the API use TLS.
  • Role-Based Access. The server checks each person’s role on every action, and examiner accounts are read-only (live test, October 9, 2026). Any signed-in user in your organization can read your organization’s project data, including the last four digits of a destination account. Two-step sign-in is required on every account.
  • United States Hosting. Client data is stored and processed on servers in the United States. VERA staff may reach the service from outside the United States, over encrypted connections, to run and support it.
  • No Sale Or Advertising Use. VERA does not sell client data or use it for advertising.
  • Where We Are. VERA maps its control evidence to the SOC 2 Trust Services Criteria. VERA has not started a SOC 2 examination and has not had an independent penetration test. We will say so on this page when that changes. Security documentation will be available to evaluating institutions on request once it has been brought up to date.
Pricing

A Pilot First, Then A License And A Per-Release Fee.

Engagements usually begin with a 90-day pilot. After that, pricing combines an annual license with a gate fee on each release. Anchoring is included. Tier is set by a lender’s size and release volume. We will send the current fee schedule on request.

Sentinel

Smaller Lenders And Lower Release Volume
Contact For Pricing
Request A Walkthrough

Fortress

Mid-Size Lenders And Moderate Release Volume
Contact For Pricing
Request A Walkthrough

Citadel

Large Lenders And High Release Volume
Contact For Pricing
Request A Walkthrough
VERA is a managed service. VERA operates the platform, including the checking service and ledger anchoring. Approvals are always signed by your own people, and VERA does not hold or move funds.
Questions From Bank Reviewers

Short Answers.

Does VERA Hold Or Move Funds?

No. VERA clears a draw for release only when the required approvals and release checks are in place. An administrator or the assigned loan officer at your institution then issues a release instruction in VERA. Your bank pays through its own systems and confirms the outcome with its own transaction reference.

Where Is Our Data Kept?

In the United States. Bank account details and authenticator secrets are encrypted by the application before they are stored, connections use TLS, and the app stores fingerprints of supporting documents, not the files.

What If VERA Is Unavailable?

No release instruction is issued while VERA is unavailable, and nothing moves without your bank. Databases are backed up nightly and a restore has been tested. We make no recovery-time commitment yet.

Do We Need To Connect VERA To Our Core Banking Or Loan System?

No. In a pilot, authorized people enter and approve draw data in VERA directly, and your bank desk pulls each release instruction and confirms it. No connection to a core system, payment rail or loan-origination system exists today, and none is required. Options for connecting later are discussed during onboarding, with your technology team.

Does VERA Replace Our Draw Process Or Our Decision?

No. VERA sits in front of your existing process. Your people still decide; VERA makes sure the right people have signed, runs the release checks and keeps the record.

Do You Have A SOC 2 Report?

Not yet. VERA maps its control evidence to the SOC 2 Trust Services Criteria. No SOC 2 examination has started, and VERA has not had an independent penetration test. We will say so here when that changes.

How Do We Leave, And What Happens To Our Data?

Your examiner role can export what is on each screen as CSV and PDF, one page of results at a time. Exit terms, including delivery of your full audit record and data, are set out in the pilot agreement, which we send for your counsel to review.

See It In Action

Request A Walkthrough.

We will arrange a walkthrough of the approval flow, the release record and the audit trail. Anchoring in the walkthrough runs on the ledger’s test network.

Walkthroughs are for organizations evaluating the platform, so please use your company email address.

Or Write Directly To support@verarails.com.

Please use your company email address, not a personal one.

Request Received.

Thank you. We will reply to the email address you gave. If you need to add anything, write to support@verarails.com and quote the reference above.