Cross-border SC via Swift API — Verified Project Pax Configuration

Wiki route

This entry sits under fintech index. Read it with Japan Financial Regulation — Legal Framework for Tokens, Crypto Assets, and Payments for adjacent context and Three-Layer Structure of Japan's Stablecoin Regulatory Regime (JPYC, USDC, Project Pax) for the broader system boundary.

[!info] TL;DR Project Pax was announced on 2024-09-05 as a plan for Progmat and Datachain to test a prototype cross-border stablecoin-remittance infrastructure adapted to a Swift API mock / simulation environment. The published material describes an API surface for assumed bank instructions and a cross-chain surface using IBC, LCP, a jointly developed stablecoin contract, and a TOKI liquidity pool. That material alone does not verify commercial operation, a production connection to a named bank, deployment to a named chain, or final posting at a receiving bank. ^[https://www.datachain.jp/news/progmat-and-datachain-launch-project-pax]

Basic pattern

Assumed bank instruction
       ↓
Adapted to a Swift API mock / simulation environment
       ↓
Stablecoin contract jointly developed by Progmat / Datachain
       ↓
Cross-chain functionality using IBC + LCP
       ↓
Liquidity pool provided by TOKI

This diagram shows only the test configuration described in Datachain’s 2024-09-05 announcement. Do not add a messaging standard, participating bank, deployment chain, legal issuance type, or final account posting. ^[https://www.datachain.jp/news/progmat-and-datachain-launch-project-pax]

Why put the Swift API first

The table is limited to the objectives and test scope stated in the joint Progmat / Datachain announcement. Do not infer regulatory approval or AML/CFT compliance from API connectivity alone. ^[https://www.datachain.jp/news/progmat-and-datachain-launch-project-pax]

Comparison boundary with other arrangements

The Project Pax announcement does not establish that the arrangement has the “same function” as a bank-deposit ledger or another company’s payment network, or that they compete. Arrangements with different legal forms of money, operators, participation terms and operating stages must be assessed from their own direct records.

Technical composition of Project Pax

The components are based on the September 2024 joint announcement by Progmat and Datachain. The announcement describes a design and demonstration goals, not production availability of every chain, liquidity pool, or compliance feature. ^[https://www.datachain.jp/news/progmat-and-datachain-launch-project-pax]

Comparison with the BIS Project Agorá

This comparison is based on official announcements from both projects. Agorá has more than 40 private-sector participants, including Swift, but was not designed as a network above Project Pax. ^[https://www.datachain.jp/news/progmat-and-datachain-launch-project-pax; https://www.bis.org/about/bisih/topics/fmis/agora.htm; https://www.bis.org/innovation_hub/projects/agora_list_participants.pdf]

The projects differ in purpose, participants, settlement assets and test stage. The cited records do not show that Agorá is the foundation for Project Pax, that Project Pax is an endpoint function of Agorá, or that either implementation depends on the other.

Limits / risks

• Commercial status unverified: completion of Phase 2, pricing, SLA, and transaction volume require confirmation in official announcements
• Separate regulatory requirements: Swift API connectivity does not replace authorization for issuance, remittance, distribution, or AML/CFT
• Participation scope: financial-institution names and target jurisdictions must be checked in a direct announcement for each stage
• Technical scope: do not infer messaging standards, deployment chains, or final account posting from the 2024-09-05 announcement

Applications

• A case study for examining integration of “blockchain + an existing bank workflow”
• A design reference for separating the API instruction surface from the blockchain value-transfer surface
• A cross-chain technology comparison alongside Cosmos IBC for FI

---

Related

• Wiki Index
• Japan trust-type SC architecture
• Cosmos IBC for FI
• Explosive Growth in B2B Stablecoin Cross-Border Payments (733% YoY, $226B)
• Five-layer unbundling of central-banking functions
• GENIUS Act implementation status

Sources

• Datachain — Progmat and Datachain Launch Project Pax (2024-09-05)
• BIS — Project Agorá