Home / Company / About
◆ About PAXORA
Money should move
as clearly as
information.
File
PXR / Company
Founded
2019 · Lisbon
People
140 across 3 offices
Layers
API · Routing · Processing · Settlement
— 01 / Story
We started with a spreadsheet
nobody trusted.
In 2019 our founders were running payments for a fast-growing marketplace. Money came in through four processors, left through three banks and was reconciled, every night, in a spreadsheet that was wrong by a few thousand euros at least once a week.
The problem was never a missing feature. It was that every system kept its own version of the truth. The processor knew what was authorised, the bank knew what had arrived and finance knew neither until the following Tuesday.
So they drew the system they wished they had: one request at the top, one ledger at the bottom and four clear layers in between — each one inspectable, each one written to the same record. That drawing became PAXORA.
Today the same four layers move money for marketplaces, SaaS platforms, lenders and enterprise treasury teams. The drawing has changed very little. That is the point.
Fig. 01 — The original drawing, redrawn
— 02 / Direction
Why we exist,
and where we are going.
Mission
Give every business the financial infrastructure that only the largest companies used to be able to build.
That means one integration instead of seven, a ledger finance can audit, and routing logic engineers can read in a single file.
Vision
A world where moving money across a border is as unremarkable as sending an email.
Settlement in hours, not days. Fees you can predict. Status you can see at every step — for the sender, the receiver and everyone in between.
— 03 / Values
Six principles
we design against.
Each value comes with the test we use in product reviews. If a decision fails the test, it does not ship.
01
Clarity over cleverness
Money is stressful enough. Every status, fee and error should be readable by the person who has to act on it.
Test · Could finance explain this screen without us?
02
The ledger is the truth
If it moved, it is recorded. We never let a convenience feature write around the ledger.
Test · Does every cent have an entry?
03
Boring where it counts
Settlement, security and uptime should be predictable to the point of dullness. We save the ambition for the product.
Test · Would we run this at 3 a.m. on a holiday?
04
Earn every integration
Engineers choose us on their own time. Documentation, errors and SDKs are product surfaces, not afterthoughts.
Test · First payment in under an hour?
05
Local by default
The best way to pay in Lagos is not the best way to pay in Lyon. We build for the local rail first, then connect it to the rest.
Test · Would a local customer recognise this checkout?
06
Honest numbers
We publish what we measure and say what we do not know. A dashboard that flatters is a dashboard that fails.
Test · Would we show this metric on a bad day?
— 04 / Timeline
One layer
at a time.
2019
Founded in Lisbon
Two payments engineers leave a marketplace to build the ledger they never had. First customer: their old employer.
REF PXR-0001
2020
Layer 04 — Settlement
The double-entry ledger ships first, reconciling bank files automatically for twelve early customers.
REF PXR-0112
2021
Layer 01 — One API
A single request format for cards, bank transfers and payouts. Seed round led by a fictional fund.
REF PXR-0420
2022
Layer 02 — Routing
Smart routing across multiple processors, with rules teams can read, test and version like code.
REF PXR-0877
2023
Layer 03 — Processing
Authorisation, capture and risk scoring move in-house. London and Singapore offices open.
REF PXR-1204
2025
Embedded finance
Accounts, cards and payouts that platforms can offer inside their own product.
REF PXR-1786
2026
All four layers, one platform
The clearing layers ship as a single product, serving teams in 40+ markets.
● Now
— 05 / Operating
How the company
runs day to day.
P-01
Write it down
Decisions start as a two-page memo. Meetings discuss the memo; they do not replace it.
P-02
Small teams, whole problems
Each layer has one team that owns it end to end — from the API reference to the on-call rota.
P-03
Customers in the room
Every engineer joins customer calls each month. Support tickets are read in the weekly review.
P-04
Ship, then measure
Changes go out behind flags, to a small cohort first, with the success metric agreed before launch.
— 06 / People
The people behind
the layers.
Sample team, fictional people. Drop your own team photos into each portrait.
Inês Valadares
Co-founder & CEO
Lisbon
Tomas Aaltonen
Co-founder & CTO
Lisbon
Amara Nwosu
Head of Settlement
London
Kenji Lau
Head of Routing
Singapore
Marta Esteves
VP Design
Lisbon
Jonah Okoye
Head of Risk
London
Priya Raman
Developer Experience
Singapore
Lucas Brandt
CFO
London
We are hiring across all four layers.
◆ Work with us
Build the next layer with us.
See how the four clearing layers fit your business.