Azul Tech Joins Fintech Gathering at the Convention Centre

Azul Tech joined the fintech community at the Convention Centre for a day of conversations about how money actually moves through a country, and who owns the rails it moves on.

The team spent the day with banks, payment providers, and regulators. Three questions came up again and again: how public money reaches a citizen without leaking on the way, who holds the record when two institutions disagree about a transaction, and what happens to a national payment flow when the vendor that runs it changes its terms.

Azul Tech works one layer beneath the products most fintech companies build. Entitlements and payments sit as the second of the five sovereign layers in the Azul Stack, underneath the applications a citizen sees and on top of the identity layer that says who they are.

That position shapes the conversation. Rather than pitching a payment product, the team talked about the specification that lets many payment products interoperate: open API contracts, an auditable record of every disbursement, and a design where the state holds the keys and the data rather than renting them.

A benefit that cannot be traced from approved allocation to the hand that received it is a benefit no one can defend at audit. Most of the failures discussed at the event were not payment failures. They were record failures, where the money moved but the account of it did not survive contact with a second institution.

Sovereign payment rails treat the record as the product. Every movement carries who authorised it, when, under which allocation, and against which entitlement, in a form another agency can verify without asking a vendor for permission.

The introductions made at the Convention Centre feed directly into the entitlements and payments work already running with national partners, and into the reference specifications published through Protocol Lab.

If your institution is working on payment or public finance infrastructure and wants to build against an open specification rather than a closed product, the team is glad to continue the conversation.