Finpass Book a demo

TechnologyHow it’s built

A modular core between people and the banks.

Four layers, each with one job. Only the bottom layer moves money — and Finpass doesn’t own it.

PEOPLE FINPASS RAILS MONEY WhatsApp Web dashboard Verification link buyer · broker agency banks · lenders · buyer FINPASS CORE Conversation Payment orchestrator Reconciliation Ledger Consent & credit records assistant · templates · secure links orders · state machine bank API › webhook › statement append-only · auditable signed · hashed · portable verifiable credential Pix Bank APIs Statement import Licensed partners Brazil · live webhooks any rail planned LICENSED BANKS & TRANSFER SERVICES The money moves here — and only here.
Live on Cloudflare Workers, TypeScript and the WhatsApp Business Platform, with 163 end-to-end and 73 unit tests run on every change.

Security and trust

Built so nobody has to take our word for it.

The money rules are enforced in the code and in the database — not left to good intentions.

No custody

Finpass never holds, moves or converts money. Payment codes are issued in the agency’s own bank account.

The bank has the last word

Confirmation comes from the bank’s API, its signed notification or the statement. A screenshot never marks anything as paid.

Signed messages only

Every notification from a bank or from WhatsApp is checked against its signature before it’s read.

Nothing pays twice

A retried notification, a re-imported statement or a repeated message is recognised and ignored.

Written once, never edited

Payment entries can’t be changed or deleted: the database refuses. A correction is a new entry, the contracted due date is kept, and every change records who made it.

Encrypted credentials

Each agency’s bank credentials are encrypted at rest with AES-256 and never shown again.

Each agency in its own space

Every query is scoped to one agency. No agency can ever see another’s buyers or payments.

A trail for every action

Who linked, dismissed, amended or terminated what — and when — is recorded.

An open standard for the passport

The buyer’s record is a credential in the W3C Verifiable Credentials standard, signed with Finpass’s published key. Any system can check it without depending on Finpass.

Revocation anyone can check

A public list in the W3C Bitstring Status List format shows whether a proof is still valid. Whoever checks downloads the whole list, so Finpass doesn’t learn which proof was checked.

Proof, not promises

Two things you can check for yourself.

A payment history is only worth something if nobody can quietly change it, and if the system that holds it is locked down. This is how Finpass handles both.

Append-only

A history nobody can rewrite

  • Payment entries can’t be edited or deleted. The database itself refuses, not just the app.
  • The contracted due date is kept for good. Moving it later doesn’t turn a late payment into an on-time one.
  • Every change to an instalment is recorded with who made it and when.
  • Cancelling an overdue, unpaid instalment doesn’t erase the arrear.
  • Every day, a fingerprint of the whole history is registered on the Bitcoin blockchain. It reveals nothing about payments or people, and anyone can check it. It proves nothing was changed afterwards; where each payment came from is recorded with the payment. See the daily records →

Rated A+ from the outside

Public scanners grade the security of our site and app. Anyone can run them again: each link opens the live report.

Two AI-led security reviews in October 2026. On 7 October, with Claude alongside the founder: a full code review, then a separate attempt to break the system. On 15 October, a second AI-led review by a different tool, working only from the code. Every finding was fixed, and each fix has a regression test that keeps it fixed. No outside security firm has tested Finpass yet: a professional penetration test comes before any pilot with real money and before any integration with a bank or lender.

Compliance by design · AML

Every payment carries its own evidence trail.

Finpass isn’t only built to avoid being a channel for laundering. Each step of a payment is also an anti-money-laundering (AML) control: who paid, what for and where the money came from travel with it by default. And the same verification that keeps the payment clean is, with the buyer’s consent, what becomes their credit history. The financial passport is compliance made visible to its own holder.

  1. Identity

    A known buyer

    Every payer is the buyer named in a real contract — name, document and phone, registered by the agency that sold the property.

  2. Purpose

    Bound to one instalment

    A payment counts only against a specific contract and instalment. Money that doesn’t match one is never settled automatically.

  3. Source of funds

    Confirmed by the bank

    The bank’s own record says which account the money came from. An unknown payer or a different amount goes to a person, never through.

  4. With consent

    The trail becomes credit

    That verified trail — identity, purpose and source, payment after payment — is what the buyer can carry as a passport.

The rails Finpass orchestrates

Finpass sits above whichever rail the buyer can use. We start with the simplest and add rails as corridors open.

Level 0

Same currency, instant

A Brazilian abroad pays by Pix from a non-resident account straight into the agency’s account.

Live
Level 1

Any transfer, matched later

The buyer pays however they can; Finpass matches it from the agency’s bank statement.

Live
Level 2

A licensed transfer app

The buyer sends with a licensed transfer service, using the reference Finpass gives them; Finpass matches the result.

Next
Level 3

Integrated payments

The buyer will pay through a licensed payment partner, into an account the agency owns — Finpass will still never hold the money. Switched on country by country, only where the partner lets the agency own the funds.

Planned
Level 4

Our own licence

Only once the corridor is proven and the volume justifies it.

With scale

Why starting simple costs nothing: the passport depends on the payment being confirmed and matched — not on who moved the money. Every level builds the same history.

Different currencies, one obligation. The instalment stays in the contract currency — guaraníes, reais, dollars, euros. A payment in any other currency settles it only when the rate is declared, and the amount paid, the rate and the converted value are all kept on the receipt. Two partial payments, in two currencies, can close the same instalment.

Where we are

Live, in development — and looking for a first developer and for funding.

163 + 73
end-to-end and unit tests on every change
3
languages: English, Portuguese, Spanish
49
contract currencies
0
cents held by Finpass
  1. Today

    Live

    WhatsApp flow and reminders, a reference per instalment, bank confirmation, statement matching for Brazil and Paraguay, currencies, receipts read by AI, a prepaid wallet and a tamper-evident history.

  2. Next

    In development

    Proof of international transfers (the SWIFT gpi UETR or the transfer app’s number), a compliance kit for Paraguayan developers (SEPRELAD) and two-factor login.

  3. Once funded

    Pilot in Paraguay

    The founder goes full time and the pilot starts. In its first 90 days: a developer pays, a lender wants the history, a partner sells.

  4. Earned

    A shared standard

    Other issuers and lenders use the same format.

FinpassGet started

Bring your buyers abroad into one chat.

The system is live and still in development. We’re looking for a first property developer and for funding — the pilot starts once Finpass is funded. Tell us about your contracts and we’ll show you how it would work with your bank.

  • With your own contracts. The buyer’s chat, the dashboard and how your bank connects.
  • In your language. English, Portuguese or Spanish.
  • Buyers never pay. Agencies pay a small amount per active contract and a fee on payments received.