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 next LICENSED BANKS & TRANSFER SERVICES The money moves here — and only here.
In production on Cloudflare Workers, TypeScript and the WhatsApp Business Platform, with 84 automated 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

Financial entries are never changed. A correction is a new entry, so the history can always be audited.

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.

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 service such as Wise, using the reference Finpass gives them; Finpass matches the result.

Next
Level 3

Partner inside the flow

A licensed payout partner converts and delivers in guaraníes — needs registration and an AML programme.

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

In production — and still building.

84/84
automated tests on every change
3
languages: English, Portuguese, Spanish
49
contract currencies
0
cents held by Finpass
  1. Today

    In production

    WhatsApp flow, bank confirmation, statement matching, currencies and automatic reminders.

  2. Next

    More rails and corridors

    Licensed transfer apps matched by reference; new countries through adapters.

  3. 2027

    Passport alpha

    The first lender accepts a Finpass payment history.

  4. Earned

    A shared standard

    Other issuers and lenders use the same format.

Programmes. Finpass was selected for two New Zealand local-government programmes that support startups and fintechs: Creative HQ’s Fintech Programme (Wellington) and the Catalyst Programme (Christchurch).

FinpassGet started

Bring your buyers abroad into one chat.

Finpass is in production. Tell us about your contracts and we’ll show you how it runs 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 fee only on payments received — no subscription.