The address you give the world

There is a moment every business owner knows. Someone wants to pay you. Maybe it’s a new client, a customer at the end of an invoice conversation, a buyer who’s found you through a referral. The intent is there. The goodwill is there. And then the friction starts.

You send them a bank account number and a BSB. They type it in wrong. Or they’re overseas and suddenly there’s a SWIFT code involved, and the question of correspondent bank fees, and whether the transfer will arrive in two days or seven, and whether the amount that lands will match the amount that was sent. Or you send them a payment link — clean, digital, modern — and the link expires before they click it. Or they click it and the payment provider is having an outage. Or they’re using a browser extension that blocks the redirect. Or the card their business uses has a limit that blocks the transaction even though the funds exist.

None of these are edge cases. Every business owner encounters some version of this on a regular basis. The payment itself — the thing that is supposed to conclude the relationship and confirm the transaction — becomes a negotiation. A support ticket. A follow-up email.

We’ve spent a lot of time thinking about this. Not as a criticism of any particular payment provider or bank, but as an honest observation about the structural problem at the centre of how money moves between people who want to do business with each other. The problem isn’t technology. The technology to move value instantly exists. The problem is architecture. The way payment systems are built, there is always something in between the person sending money and the business receiving it. That something has uptime requirements, commercial arrangements, expiry dates, and a lifecycle of its own.

What we built — the Queensland Foundation TLD infrastructure — didn’t start as a payments product. It started as a question about identity and ownership. But as we built it, we kept coming back to one realisation: a permanent address changes what a business can promise about how it gets paid.

What an address actually is

We use the word “address” so casually that we’ve stopped noticing what it means. Your business address is the location you point people to when you want them to find you. It’s stable. When someone writes your address on an envelope and posts it, they expect the letter to arrive regardless of which postal worker handles it, regardless of the weather, regardless of whether Australia Post updated its systems overnight. The address is the constant. The infrastructure that serves the address can change; the address itself should not.

What passes for a payment address in most of modern business is not really an address at all. It’s a session. A bank account number is a reference to an account at a particular institution, governed by that institution’s terms, subject to closure, modification, and the continued existence of that institution. A payment link is more obviously temporary — it’s a URL generated by a service at a point in time, routed through that service’s infrastructure, and dependent on that service’s continued operation. When the service changes its pricing model, or gets acquired, or shuts down, or simply depreciates the feature that generated your link format, your “address” breaks. The people who have saved it get nothing. The customers who bookmarked it get an error page.

This is a strange thing to accept as normal. We don’t accept it with physical addresses. We don’t expect our street address to expire. But we’ve normalised the idea that the place our customers can send us money might simply stop working — and that when it does, we bear the cost of telling everyone, updating our details, migrating to a new provider, and hoping the transition doesn’t lose anyone along the way.

An onchain address is different in kind, not in degree. It is not a reference to an account at an institution. It is not generated by a session or tied to a service’s uptime. It is a permanent record on infrastructure that nobody owns and everybody can read. When you own shop.brisbane, you own that string. Permanently. The private key that controls it is yours. No institution can revoke it. No company can retire it. No renewal fee left unpaid can cause it to lapse. There is no central authority looking at a calendar and deciding whether shop.brisbane still belongs to you today.

That is the difference that matters.

The dependency chain hiding in every payment

Let’s trace what happens when a customer wants to pay a business today. Even in the smoothest case — the customer wants to pay, has the funds, and initiates the transfer — there is a dependency chain running beneath the surface that most business owners have never mapped.

The customer’s bank must authorise the transaction. The customer’s card must not be expired, blocked, or at its limit. If it’s a payment link, the service that generated the link must be online. That service’s connection to its payment processor must be healthy. The payment processor must not be experiencing downtime. The acquiring bank that sits behind the processor must be accessible. The issuing bank that holds the customer’s funds must not be flagging the transaction for fraud review. If it’s an international payment, one or more correspondent banks must participate in the relay. Each of those institutions operates on its own schedule, with its own maintenance windows, its own risk rules, its own business interests.

When any single node in that chain fails, the payment fails. And the failure often has nothing to do with the payer’s intent or the payee’s legitimacy. It has to do with the architecture. The architecture assumes intermediaries. The intermediaries have interests. The interests are not always aligned with yours.

We’re not making an ideological argument here. We’re not saying intermediaries are bad or that the traditional financial system should be replaced. We’re saying something much simpler: when your payment address depends on a chain of third-party infrastructure, the reliability of your payment address is only as good as the weakest link in that chain. And you don’t control any of the links.

An onchain address removes the chain. When someone sends value to shop.brisbane, the address resolves because the blockchain resolves it. Not because a company’s server answered the request. Not because an institution approved the transaction. Because the record exists on distributed infrastructure that has no single point of failure and no commercial interest in whether your payment goes through today.

What changes when the address is permanent

The first thing that changes is psychological, and it’s more important than it sounds.

When you give someone a permanent address, you are making a commitment. You are saying: this is where you send things. Today, tomorrow, in five years, in twenty. The address will still be there. The record will still resolve. The relationship between that address and the key you hold will not change unless you choose to change it.

That commitment changes how customers think about your business. A business that has a permanent onchain address is a business that has invested in its own infrastructure. Not rented it. Not subscribed to it. Invested in it, the way a business invests in a physical shopfront or a professional sign out the front. It signals permanence. It signals that the business intends to be around.

Compare that to the psychology of a payment link. A payment link says: here is where you can pay me right now. It makes no claim about tomorrow. It can’t. It’s ephemeral by design. When customers — particularly business customers buying in B2B contexts — sense that ephemerality, it registers as a small but real signal about the stability of the business they’re dealing with. Payment infrastructure that looks improvised makes the business look improvised.

The second thing that changes is operational, and this is where the compound effects start to appear.

A business with a permanent payment address never has to migrate. Migration is one of the hidden costs of modern business infrastructure that almost nobody accounts for at the start, and almost everybody pays at some point. When your payment provider changes its pricing structure, you have to decide whether to accept the new terms or find a different provider. When you find a different provider, you have to update every invoice template, every website reference, every email signature, every QR code printed on any physical material. You have to email your regular clients to let them know. You have to update the details your accounting software has on file. You have to hope that nobody tries to pay you via the old method during the transition and ends up confused or lost.

This is not a theoretical concern. Every business that has changed banks, changed payment providers, or changed invoicing platforms has been through some version of this process. It takes time. It creates errors. It occasionally loses transactions. And it has to be done again, from scratch, whenever you change providers again.

With a permanent address, the migration never happens. The address is yours. If the payment infrastructure built on top of it evolves — if new wallets emerge, if new protocols are added, if the way people interact with onchain addresses changes — your address stays the same. The address is the constant. Everything else can evolve around it.

The invoice that doesn’t expire

There is a specific scenario we think about when we talk about payment addresses for business, because it captures the friction so precisely.

A freelancer sends an invoice. They’re busy; the invoice goes out at the end of a project sprint, and the client — also busy — doesn’t process it immediately. It sits in an inbox for two weeks. By the time the client’s accounts team gets to it, the payment link on the invoice has expired. The link was generated by the invoicing platform, which sets a thirty-day expiry for security reasons. The client tries to pay, gets an error message, and now has to contact the freelancer to request a new link. The freelancer has to log into their invoicing platform, regenerate the link, send it again, and wait for the client to try again.

That entire sequence of events — the failed click, the support query, the regeneration, the resend, the second attempt — is pure waste. It added no value to either party. It delayed payment. It created administrative work. It made a simple transaction complicated.

Now replace the payment link on that invoice with a permanent address: studio.brisbane. The invoice goes out. The client opens it in their own time. They click the address or scan the QR code linked to it. The address resolves. The payment goes through. There is no expiry. There is no regeneration step. There is no support query.

The address was the same on the day the invoice was sent as it is six months later. It will be the same six years later. The invoice can sit in an archive, and if the client ever needs to reference it again — for an audit, for a repeat engagement, for any reason — the payment details are still valid. They will always be valid.

This seems like a small change. It isn’t. Across a business that sends dozens or hundreds of invoices a year, eliminating the “payment link expired” failure mode is a measurable improvement in cash flow. Cash flow is not an abstraction for a small business. It is the operational reality that determines whether you can pay your own bills on time.

The business card that receives money

We’ve been describing the address in transactional terms — invoice sent, payment received. But there’s a dimension of this that goes beyond individual transactions: the address as identity infrastructure.

Your business card, your email signature, your website footer — these are all places where you declare your address to the world. Physical address for correspondence. Website address for digital presence. Email address for direct communication. Each of those addresses is associated with an identity and with a specific capability: write to us here, find us here, talk to us here.

A payment address adds a fourth capability: pay us here.

When that address is permanent and onchain, it becomes part of the identity fabric of the business in a way that a payment link never can. You wouldn’t put a payment link in your email signature because it would expire. You wouldn’t print it on your business card because the card would be worthless after the link broke. You wouldn’t add it to your website’s “About” page because you’d have to update it every time you changed payment providers.

But you could put pay.brisbane in your email signature. You could print it on your business card. You could include it in your pitch deck. You could add it to your LinkedIn bio. It would be there whenever someone needed it, whether that was today or in ten years. It would work the first time it was seen and the thousandth time. No expiry. No migration. No update required.

This changes the geography of how businesses communicate payment information. Instead of payment details being something that gets attached to a specific transaction — a link on an invoice, a BSB on a remittance advice — the payment address becomes persistent context. It travels with the business. It’s part of how the business presents itself to the world.

That is a different relationship with payment infrastructure than most businesses have ever had.

No provider means no provider risk

Here is a risk that most businesses carry without naming it: dependency on the continued existence of their payment provider.

Payment providers are companies. Companies change. They get acquired. They pivot their product focus. They exit markets. They raise prices. They shut down features. They go out of business. When any of these things happens, the businesses that depended on them have to respond, usually under time pressure, with imperfect information, while their regular payment flows are disrupted.

This is not a rare event. The history of fintech is littered with providers that were widely used and then ceased to exist in the form their customers expected. Payment gateways that were acquired and folded into acquiring companies, then eventually deprecated. Invoicing platforms that changed pricing models and made themselves economically unviable for the small businesses they were built for. P2P payment tools that got blocked by banks after regulatory changes. Regional payment processors that couldn’t scale and shut down. Each time, the customers had to find alternatives, migrate their data, update their payment details, and absorb the transition costs.

An onchain address has no provider. There is nothing to acquire. There is nothing to deprecate. There is no company whose continued existence is a dependency for the address’s continued function. The address resolves because the blockchain resolves it, and the blockchain resolves it because the distributed network of nodes that maintains it continues to operate. That network has no single owner and no single point of failure. It is not subject to acquisition, pivoting, or commercial exit.

We are not making a claim that blockchain infrastructure is indestructible or that nothing can ever go wrong with it. That would be naive. What we are saying is that the failure modes are categorically different. The failure mode of a company-provided payment link is the company. The failure mode of an onchain address is the network. The company failure mode is common; companies fail regularly. The network failure mode, for mature and widely distributed blockchain infrastructure, is several orders of magnitude less likely.

Businesses that think about counterparty risk in their supply chains, in their banking relationships, in their insurance arrangements — those same businesses rarely think about counterparty risk in their payment infrastructure. The address they use to receive money is almost always dependent on a third party whose continued operation they take for granted. An onchain address is one of the few payment infrastructure choices that actually eliminates that counterparty.

What global reach looks like without intermediaries

For a business in Queensland sending an invoice to a client in London, Singapore, or New York, the payment experience today involves a negotiation between at least three banking systems and, depending on the currencies involved, a foreign exchange conversion with fees at multiple points along the chain. The business and the client both want the transaction to happen. Both have the intent. Both have the capacity. But the infrastructure between them extracts time, fees, and uncertainty from every transaction that crosses a border.

This is one of the underappreciated costs of international business for small and medium enterprises. Large corporations can negotiate preferential rates with their banks and hedge their FX exposure efficiently. Small businesses pay retail rates on both the exchange and the transaction fees. They wait for funds to clear. They reconcile amounts that never quite match the invoice because of bank charges deducted in transit. They occasionally chase missing payments that got stuck somewhere in the correspondent banking chain and took ten days instead of three to arrive.

An onchain payment address removes the correspondent banking chain entirely. When value moves between two onchain addresses, it doesn’t route through a relay of intermediary banks. It moves directly, on the network. The sender initiates it. The receiver’s address receives it. The blockchain records it. There is no intermediary extracting fees in transit. There is no clearing cycle that varies by geography. There is no business day consideration that means a payment sent on a Friday might not arrive until Tuesday.

For a Queensland business with international clients — and there are many, from tourism operators to software consultancies to specialist manufacturers — this is not a marginal improvement. It’s a structural one. The payment address doesn’t know whether the sender is in Brisbane or Berlin. The network doesn’t apply different rules to payments that cross imaginary lines on a map. The address just receives.

What sovereignty over your payment address means

We want to spend some time on a concept that we think is undervalued in business infrastructure discussions: sovereignty.

When we use the word sovereignty here, we don’t mean it in a political sense. We mean it in a practical, operational sense. Sovereignty over your payment address means: you control it. Not a bank. Not a payment provider. Not a registrar who can choose not to renew your domain. You.

The cryptographic keys that control an onchain address belong to the holder. The address resolves because the holder controls the keys. Nobody can take the address away. Nobody can redirect it without the holder’s authorisation. Nobody can sell it to someone else without the holder’s participation. The rights to the address are embedded in the infrastructure itself, not granted by a third party that could change its mind.

Compare this to a traditional business domain. A .com or .com.au domain is leased from a registrar. The registrar renews it annually (or every few years, if you pay upfront). If you miss a renewal — because you changed your credit card, because you changed your email address and missed the reminder, because you were busy and the invoice got buried — the domain lapses. Once it lapses, it becomes available for anyone to register. Squatters actively monitor lapsed domains and register them immediately. Businesses have lost their primary web presence because of a missed domain renewal. Some have paid significant sums to buy their own domain back from squatters. This is a known, documented failure mode of the traditional domain system.

A Queensland Foundation address doesn’t have a renewal. There is no annual fee. There is no reminder email to miss. There is no squatter watching a countdown. The address is yours, permanently, from the moment you register it. You didn’t lease it. You own it. The distinction is not semantic. It is the difference between infrastructure that can be taken from you and infrastructure that cannot.

For a business, this has implications that extend beyond convenience. It means the payment infrastructure you invest in today — the address you put on your invoices, your business cards, your website, your pitch materials — will not need to be changed because of a missed payment to a registrar. It will not change unless you choose to change it. That reliability is not a feature you can get from a leased address at any price. It’s a structural property of what ownership means in an onchain context.

The practical experience of telling someone your address

Let’s bring this back to the most ordinary moment in business: you’re talking to a potential client. The conversation has gone well. They want to know how to pay you.

In the current normal, you have a few options, and none of them is ideal. You read out a BSB and account number. They type it into their notes. Hopefully they get it right. You send them a payment link. They save it somewhere, and you hope they open it before it expires. You send an invoice via your invoicing platform and hope the PDF renders correctly on their end, that the embedded link works in their email client, that your invoicing platform’s domain isn’t blocked by their corporate email filter.

Or you say: studio.brisbane.

That’s the address. Same one you used on the last invoice. Same one that’s been on your business card since you registered it. They can type it. They can scan a QR code you’ve generated from it. They can come back to it six months from now and it will still work. There is nothing to remember except the address, and the address is a human-readable string that means something — it’s Brisbane, it’s Queensland, it’s yours — not a random sequence of digits and reference codes.

The communicability of a human-readable payment address is easy to underestimate because we’ve normalised the inelegance of the alternatives. Bank account numbers are not memorable. They are not searchable by the humans who receive them. They require double-checking every time they’re used. Payment links are forgettable by design — they’re machine-generated strings that no human can parse. A business name followed by .brisbane is neither of these things. It is legible. It is memorable. It can be spoken aloud, written on a whiteboard, included in a text message, passed on verbally at a networking event.

This communicability has real effects on the speed of business. The faster someone can recall or locate your payment details, the faster the gap between “yes, let’s do this” and “here are the funds” closes. That gap is real time. Real time has real value.

Identity that scales with the business

The Queensland Foundation TLDs — .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, .brisbane2032 — are not just payment addresses. They are identity addresses. But the payment dimension deserves particular attention for businesses that are thinking about how they scale.

A small business might start with one address: the founder’s name at .brisbane. As the business grows, they might register addresses for specific business units, specific product lines, specific team members. orders.brisbane for an ecommerce operation. wholesale.queensland for a B2B trade function. accounts.brisbane for a finance team. support.qld for a customer service workflow.

Each of these addresses is permanent. Each can be used across contexts — not just for payments, but for identity verification, for asset transfer, for any function that benefits from a permanent onchain address. The address infrastructure grows with the business. When the business adds a new function, it adds an address. There is no migration, no new account to open, no new service to subscribe to. The onchain infrastructure accommodates new addresses without requiring the existing addresses to change.

This is what infrastructure should feel like. Not a subscription to someone else’s service that you manage and renew and migrate and worry about. A resource you own, that you can extend, that grows with you, that you can hand to a successor or an acquirer without any transfer of account ownership at a third-party institution. The address is a business asset in the same sense that property is a business asset — owned, not rented, and therefore under your control.

The cost of getting this right

We want to be direct about something, because we think it’s part of the honest case for what we’ve built.

The price of a Queensland Foundation address starts at five dollars. Paid once. No annual fee. No renewal. No expiry.

We set that price deliberately. We set it because we believe that permanent digital infrastructure for Queensland businesses and individuals shouldn’t be a luxury. A business address that you own for life, that you can use for payments and identity across any digital context, should cost roughly what a coffee costs. Not because we undervalue what it represents, but because we believe the value of a functional, permanent payment address is not in the address itself — it’s in what you do with it. The address is the starting point. The value accrues to the business that uses it.

When we compare that to the annual fees for a traditional domain name, or to the percentage fees extracted by payment processors on every transaction, or to the time cost of migration when a payment provider changes its terms — the mathematics of ownership become very clear. You pay once. You own it permanently. Everything you save on renewals, migrations, and transaction fees from that point forward is pure return on that investment.

We’re not suggesting that every business needs to replace its entire payment infrastructure with onchain addresses immediately. The world of payments is complex, and businesses have existing relationships with banks and payment providers that serve real purposes. What we are suggesting is that adding a permanent onchain address to your payment infrastructure — as a primary payment destination, as an invoice reference, as the address that goes on your business card — costs almost nothing and changes everything about the durability of your payment identity.

The business you are running today is planting seeds for the business you will run in five years, in ten. The payment address you put on your invoices today will either need to be changed multiple times in that window — migrated, updated, regenerated, and re-communicated to everyone who has it — or it will simply still be there, working, belonging to you, unchanged. The difference between those two futures is the difference between infrastructure you own and infrastructure you rent.

We built Queensland Foundation because we believe that Queenslanders should own their piece of the onchain world. That belief applies to identity, to presence, to community — and it applies, with particular practical force, to the address where your business gets paid.

That address should be yours. Permanently. Without condition. Without renewal. Without anyone’s permission.

That is what we built it to be.