We launched the N3XT Digital Dollar (NDD) in April 2026. Fully reserved, bank-issued, settles dollars on Ethereum in real time, 24/7/365. The press covered the hours and the novelty of a bank shipping a tokenized deposit.
Last week, we announced the extension of NDD beyond our account holders. A non-account holder's address gets screened, approved, and allow-listed on-chain, and can then hold and transact with NDD without opening a bank account. The safety and soundness of a bank deposit can now reach people who aren't our clients. The press covered that too.
What didn't get covered is the less obvious benefit to clients, which is what NDD actually is: an open standard to interact with USD. Simply put, NDD is an API to our core banking ledger.
Which means the interface isn't ours. It's EVM/ERC-20, the same interface every wallet, custodian, and treasury system on Ethereum (and variants) already knows. We didn't create an endpoint and ask you to learn it.
For a CIO or CTO, that means the integration may already be done. If your team has built for stablecoins or digital assets, you likely already have the wallets, the signing, the nodes, the monitoring. Point that stack at our contracts and you're holding a regulated bank deposit.
For a CFO, the money already spent on that development and infrastructure now covers one more thing. And if it hasn't been spent yet, it isn't a one-off. The same integration reaches every other on-chain counterparty, so it keeps paying out long after it ships.
One Integration Per Counterparty
Compare that to the alternative. Your bank has its own API. So does your payment processor, your acquirer, your gateway, your card platform, your payouts provider. Different SDKs, different webhook formats, different reconciliation files. There's no global standard to fall back on either — Europe, Brazil, and the US each went their own way — so crossing borders adds another one per region.
Every one of those is middleware your team builds and then maintains. None of it differentiates your product. It's the cost of being able to move money, and you pay it again with every counterparty you add.
The industry has spent decades trying (and failing) to define a common interface for money. Ethereum has been around a decade and the EVM hasn't seen a serious challenger since launch.
No single entity dubbed EVM the standard. Developers went where the tooling was, wallets and custodians followed the developers, auditors and exchanges standardized on the same patterns, and it became the standard. Nobody voted. It just ended up being the thing everyone supported.
So we aren't asking you to build to yet another API. We're letting you use one you've likely already integrated to, or (hopefully) convincing you to build to the protocol that's winning anyway.
One footnote. We do still run an API for anyone who wants it (docs here). It takes an afternoon to integrate, and it does something the public chain can't yet: privacy.
The Win-Win-Win
- Clients win. Reuse what you already built instead of funding a custom integration. Pay exactly and only for what you settle; historically Ethereum gas fees have dropped 20–64% a year for the last 5 years.
- The blockchain wins. Ethereum gets institutional utility. More transactions mean more fees, more fees mean a more resilient and secure network.
- N3XT wins. It's a distribution that meets clients on the stack they already have. No need for proprietary integrations, and with the added fringe benefit that every transaction is API load we don't pay for.
Turns out the best API to build was none at all.
_________________________
Thought Experiment: After writing this we got curious. If public rails reduce our API costs, are they cheap enough to carry the entire ledger? We compared the cost of our private ledger, a public ledger, and a traditional banking core, with plenty of assumptions and estimates along the way.
Spoiler: public rails can win. The Ledger We Didn't Rent
