Background & Biography
In an earlier interview, Saito explained why working inside a trust bank had appealed to him. He valued the autonomy and public importance of infrastructure, together with the opportunity to build alongside colleagues he trusted. Established institutions, he argued, could contribute customer confidence and specialist knowledge that helped unfamiliar services gain acceptance. That position shaped his approach to financial innovation. He wanted a platform on which competing banks could participate without being subordinate to one banking group. He also identified a common difficulty for tokenized securities platforms: completing the payment leg through the same digital environment. His immediate priority was to establish a useful domestic foundation. International expansion remained a possible later step, rather than the starting claim for the project.
Saito’s account of the company’s establishment traces his career at Mitsubishi UFJ Trust and Banking to April 2010. The chronology moves from planning digital financial products to an asset tokenization project in 2018 and a production securities platform in 2021. The separate company was established in October 2023. He presented independence as a way to broaden participation and improve the organisation’s ability to develop software. Bringing competing financial institutions into the shareholder group could reduce the barriers created by banking affiliations. Technology businesses also joined the structure, connecting financial expertise with development capabilities. His contribution here is an articulated approach to company formation and collaboration. The platform’s releases and operational work remain achievements of the participating organisations and their teams.
Notable Contributions
His explanation of Project Pax in September 2024 starts with the routines of the people expected to use it. Companies generally make payments through their banks’ existing interfaces. Requiring them to introduce a separate wallet process could create additional work for finance and administration staff, even when the underlying transfer technology was attractive. The proposed arrangement combined those familiar interfaces, Swift’s application connections and stablecoins. Banks could use the new transfer mechanism while preserving established relationships with business customers. He explicitly allowed for older payment routes to continue operating alongside it. This is a concrete contribution to adoption design: considering how a new settlement method fits everyday work. The account described an announced approach subject to testing and change before a commercial release.
In February 2026, his infrastructure analysis set out the requirements he believed financial institutions would bring to connected digital markets. These included confidentiality, audit trails, operational continuity and a clear allocation of responsibility when something failed. He argued that meeting familiar institutional requirements would be insufficient if the resulting platform could not readily connect to other services. The design problem therefore included both dependable operation and room for new applications to work together. He also examined a tension between retaining control over important financial infrastructure and having an accountable operator. Avoiding dependence on one provider still left a need for someone who could take responsibility during disruption. This was his stated design rationale, rather than independent certification of a particular network’s performance.
His April 2026 discussion of smaller units of equity ownership compared several possible structures. One would keep the relevant ownership interests on a blockchain outside conventional securities book entry arrangements. Another would offer two forms of interest, allowing digital trading and established exchange infrastructure to coexist. A third would retain conventional book entry ownership while using a connected ledger to supplement trading and ownership information. The practical distinction concerned how each model could work with existing markets. In the connected approach, records of activity outside the exchange would need to be reconciled with the established depository system. He also identified questions requiring consultation with the authorities about the treatment of the proposed interests. These were design options under examination, with their conditions and unresolved issues still material to implementation.
His reflection on a book chapter about stablecoins and payment infrastructure shows his educational contribution. He describes comparisons with other tokens and digital payment balances, helping business readers distinguish the instruments. He then asked why tokenization would be useful where bank accounts and digital payment services were already widespread. His answer organised potential uses around international transfers, exchanges between digital assets and payments that software could initiate under defined conditions. He examined these applications against existing methods. The emphasis was on understanding a business use case before adopting a payment instrument.
Why Katharos.ai Follows Tatsuya Saito
Saito’s writing makes the relationship between business automation and financial infrastructure explicit. In January 2025, he argued that automated agents could benefit from completing processes without repeatedly returning to manual steps. Financial services were part of that process. He distinguished connections to individual institutions from networks capable of moving value between businesses and financial firms. Katharos.ai follows this argument because it supplies a practical question for evaluating tokenization: what activity becomes possible across organisations? It connects his technical interests with public policy. In the same essay, he described a proposal he had presented to a legislators’ group in 2024. That is evidence of his participation in policy discussion, not proof that his proposals became law.
Areas to Follow
- Whether corporate payment trials demonstrate that customers can retain familiar banking processes, and what operational changes participating banks actually need to make.
- How future infrastructure designs make responsibility, service continuity and connections with outside applications explicit, including what happens when an important component stops working.
- Which equity structures proceed beyond discussion, how ownership records are reconciled, and what questions the relevant authorities resolve before broader use.
- Further explanations of stablecoin use cases that compare actual business needs with existing payment methods, including the conditions under which a business might benefit.
Reporting Scope
Coverage focuses on documented professional activity and attributable explanations. Institutional announcements are assessed at the level of the organisations involved. A founder’s account can establish what he advocated or intended; implementation requires separate evidence. Dates distinguish the original proposal from later developments. Editorial inclusion does not validate a product or settle a legal question.
Areas of Influence
His influence centres on the relationship between banking expertise and shared digital infrastructure. His interview presents cooperation across competing institutions as a condition for reaching a wider market. Governance and participation consequently matter alongside technology.
Photo: Progmat
Katharos.ai publishes this profile for information, based on the sources listed. Inclusion is not an endorsement of the individual, their organizations, or any investment product.
Source notice: Information and images are attributed to the external sources listed. Katharos.ai does not endorse the subjects or claims described and does not independently certify the authenticity of every source statement or image.