No construction draw is released until the right people have signed and the checks pass.
VERA keeps the record. Your bank moves the money.
In many disbursement processes, checks happen after funds have been released, when errors are harder to recover. VERA puts the proof ahead of the release instruction and keeps a record of every decision.
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.”
Fingerprint, approve, decide, record.
Supporting documents are fingerprinted with SHA-256. VERA records the fingerprint and a reference to the document, not the document itself.
The inspector and the loan officer each sign with their own registered key. One person cannot supply both approvals.
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.
Each decision enters a hash-chained audit log. A fingerprint of each batch of attestations is anchored to the XRP Ledger as an independent timestamp.
Every release leaves a record your bank, your title company and your examiner can read.
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 and investment disbursements. The same mechanism can extend to other disbursement workflows. None of those is offered today.
Inspector and loan-officer approval before every release, tied to the inspector’s 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, and the same person cannot give both approvals.
Automated checks run on every release before it is issued. The check list is shared with evaluating institutions under NDA.
Each entry carries a hash of the one before it, so a removed or reordered entry breaks the chain.
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, assign the inspector and loan-officer roles, set the verified payment destination and 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.
Each batch of attestations is fingerprinted and published to the XRP Ledger. Only a hash is published. No names, amounts, account numbers or documents. During the pilot, publishing runs on the ledger’s test network.
VERA is designed to hold as little personal information as possible. Your institution decides what it enters, and VERA processes it on your behalf as your 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 checks that the required approvals and release checks are in place and then issues a release instruction. Your bank pays through its own systems and confirms the outcome with its own transaction reference.
In the United States. Sensitive fields such as settlement account details are encrypted at rest, all traffic uses TLS, and supporting documents are recorded as fingerprints, not 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’s controls are designed with reference to the SOC 2 Trust Services Criteria. VERA has not completed a third-party SOC 2 examination or an independent penetration test, and we will say so here when that changes.
Your examiner role can export the record as CSV and PDF at any time. Exit terms, including delivery of your 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 [email protected].
Thank you. We will reply to the email address you gave. If you need to add anything, write to [email protected] and quote the reference above.