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.
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.”
The required parties sign, the release checks run, and the decision is recorded. Supporting documents are fingerprinted when they are added.
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.
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.
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.
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.
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.
0x9c3e…41ab, checkable on a public pageThe record is built as the work happens, not assembled afterwards.
VERA sits in front of your existing draw process. It does not replace your loan system or your decision.
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.
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.
Each approval is signed with the approver’s own key. VERA never holds an approver’s private key.
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.
Automated checks run on every release before it is issued. The check list is available to evaluating institutions under a non-disclosure agreement.
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.
A read-only role for audit and examination staff, with CSV and PDF exports.
One lender, one set of real draws, a fixed 90 days. You decide at the end whether to continue.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Or Write Directly To support@verarails.com.
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.