Skip to content
Verification of Real Assets
Contact
VORA TOKEN ENGINE

The software behind every issuance.

The VORA Token Engine accompanies a digital bond from setting up the project through acquisition to interest payment and repayment. The software keeps the register and the evidence. Money flows between issuer and investor, never through it. Within the EU legal framework.

Issuer · OverviewDemo · fictitious data
Token Engine screen: the issuer's overview with projects and placement status
Money flows directlyPayments run between issuer and investor, never via the software. It keeps the register and the evidence.
Four eyes, built inWhoever proposes cannot approve themselves. The rule is fixed in the software, not merely recommended.
Pseudonymous registerEvery holder is listed under a register ID. Record-date anchors make the status verifiable at any time.
LIFE CYCLE OF A BOND

Nine steps, one register.

From the first request to the investor's portfolio. Every step shows the actual screen intended for it.

RolesVORAISSUERINVESTOR
  1. 01VORA

    Review the request

    Every request goes through a six-point checklist. Volume, interest, term and loan-to-value sit side by side, together with a recommendation. Only then is the request created as a project.

    VORA Admin screen: requests with checklist and recommendation
  2. 02ISSUER

    Prepare the issue

    The issuer sees all projects and their issue stage by stage: master data and collateral, mandatory documents, review of the issuance. Each stage shows whose turn it is.

    Issuer screen: overview of all projects
  3. 03ISSUER

    Approve

    VORA proposes, the issuer decides. Whoever proposed cannot approve themselves. Every item is presented individually and decided individually.

    Issuer screen: approvals under the four-eyes principle
  4. 04INVESTOR

    View the offer

    Investors see interest, term, placement status and the collateral, such as a first-ranking mortgage. The risk notice sits right next to the amount.

    Investor screen: offer with interest, term and risk notice
  5. 05INVESTOR

    Acquisition in one window

    Residence, registration, identity, acquisition and payment run in one continuous flow. If a step fails, the details entered so far are kept.

    Investor screen: acquisition in six steps, starting with the place of residence
  6. 06ISSUER

    Match payments

    Acquisitions run via codes, sender accounts stay masked. When the bank statement is imported, the software detects special cases such as partial payment, overpayment or duplicate payment.

    Issuer screen: payment matching with bank statement
  7. 07ISSUER

    Register and documents

    The register keeps every holder under a pseudonymous register ID. Mandatory documents are kept in one place; record-date anchors secure the status with a hash.

    Issuer screen: register and mandatory documents
  8. 08ISSUER

    Interest and repayment

    On the interest date the software creates the payment list from the register, including CSV and SEPA files, and checks totals and interest rate against the terms and conditions of the bond. The transfer is made from the issuer's account.

    Issuer screen: interest run with payment list
  9. 09INVESTOR

    Portfolio

    Investors see their units, interest received and the next interest date, and download their register extract themselves.

    Investor screen: portfolio with positions and interest dates
VORA Admin · Requests
VORA Admin screen: requests with checklist and recommendation
INVESTORS · MOBILE

Portfolio, offer and payment in your pocket.

The investor view is built for the phone. Portfolio, offer and payment work there just as they do on the computer.

Three phone views for investors: portfolio, offer and payment
ROLES

Everyone sees what they need.

ROLE

VORA Admin

Reviews requests, creates projects and proposes approvals.

ROLE

Issuer

Prepares the issue, decides on approvals, matches payments and carries out interest and repayment.

ROLE

Investor

Sees offers, acquires units in one flow and follows interest in the portfolio.

ROLE

Observer

Sees an offer without an account, for example for review by advisers or the press.

DEMO

See the Token Engine in action.

In a conversation we walk you through the entire process, using your project as the example.