Cross-border SC via SWIFT API
#fintech#stablecoin#cross-border#swift#tokenized-deposit#ibc
On this page
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 The biggest obstacle to cross-border SC adoption is “incompatibility with bank workflows / AML/CFT.” The modern pattern that solves this is a hybrid structure that places a SWIFT API at the front-end and executes blockchain settlement at the back-end. Project Pax (Progmat + Datachain · 2024-09) and the BIS Project Agorá are representative implementations of this structure. TD (Tokenized Deposit) leads on SWIFT API compatibility, while SC connection patterns diverge depending on a §501(d) interoperability license.
Basic pattern
Bank(MUFG / SMFG/SMBC / Mizuho, etc.)
↓ SWIFT MT103 / ISO 20022 message
SWIFT API mock layer(Datachain)
↓ parse → settlement instruction
Progmat Coin contract(trust-type SC)
↓ on-chain transaction
IBC + LCP(cross-chain bridge)
↓
Ethereum / Polygon / Avalanche / Cosmos
↓ cross-chain swap in the TOKI liquidity pool
receiving-side bank → credited in the receiving-side currencyWhy place the SWIFT API at the front
| Reason | Content |
|---|---|
| Protecting existing workflows | Banks’ internal systems / corporate ERPs have operated on a SWIFT premise for 50 years |
| AML/CFT compatibility | OFAC / FATF Travel Rule have accumulated operational know-how on SWIFT |
| Reassurance for supervisors | The FSA / Financial Services Agency find it easier to regard transactions as already reviewed if they go through SWIFT |
| Phased migration possible | Full on-chain is the distant future · involve banks via SWIFT and gradually raise the on-chain ratio |
TD vs SC cross-border path divergence
| Item | TD(JPM Kinexys / KDP) | Trust-type SC(Progmat / Project Pax) |
|---|---|---|
| Legal nature | Bank-deposit type | 第 3 号 EPI trust type |
| SWIFT API | Direct use of existing SWIFT | Via the SWIFT API mock layer |
| Cross-border commercialization | Already $1.5T/month(KDP) | 2026-H2 target(delayed) |
| §501(d) required? | Not required(TD is outside SC regulation) | Required(awaiting future acquisition) |
| Interoperability partner | US banking partners already in place | Asian partners not sufficiently fixed |
| Interest | Deposit interest belongs to the bank | Trust trustee fee |
Implication: Kinexys has reached commercialization via the TD path while avoiding §501 regulation. On the SC path, unless Progmat obtains a §501(d) tier, it is at a structural disadvantage to Kinexys in large-ticket cross-border business.
Technical composition of Project Pax
| Layer | Component | Provider |
|---|---|---|
| Application | SWIFT API mock + corporate wallet | Datachain |
| Settlement instruction | Progmat Coin contract | Progmat + Datachain |
| Cross-chain | IBC + LCP middleware | Datachain(Hyperledger Lab) |
| Liquidity | TOKI cross-chain pool | TOKI(a Datachain subsidiary) |
| Chains | Ethereum / Polygon / Avalanche / Cosmos | each chain |
| Compliance | OFAC / Travel Rule / KYC API | Progmat common |
Comparison with the BIS Project Agorá
| Item | Project Pax | BIS Project Agorá |
|---|---|---|
| Led by | Progmat(private · Japan) | BIS(international · 7 central banks) |
| Purpose | Put Japan-originated SC onto SWIFT | Integrate wholesale CBDC + commercial bank money |
| Settlement asset | Trust-type SC | wholesale CBDC + TD |
| Technology | Avalanche L1 + IBC | Unified Ledger(BIS-designed) |
| Commercial timeline | 2026-H2 | 2027+(proof-of-concept stage) |
| Relationship to §501(d) | Individual SC interoperability | Sovereign-network foundation |
The two are complementary: Agorá builds the inter-state skeleton, and Pax solves the last 1 mile of individual SC ↔ SWIFT.
Limits / risks
- The §501(d) channel is not established: a direct swap with US-compliant SC such as USDC is currently not possible
- Delay history: Pax failed to meet its original target at the end of 2025 → technical risk exposed
- Insufficient Asian partners: delay in fixing HK / SG / Korea counter-parties
- SWIFT dependence: if SWIFT itself migrates to ISO 20022 + onchain native in the future, the mock layer becomes obsolete
- Competition with JPM Kinexys: it has already commercialized the same kind of function on the TD path
Applications
- Can be referenced in any “blockchain + existing banking workflow” integration discussion
- Reading the relationship between SWIFT reform (ISO 20022 / GPI / GPI for Corporates) and SC
- Asia-originated cross-border SC design discussions (Korea KRW1 · Thailand Project Inthanon · Singapore Project Ubin)
- Combining with Cosmos IBC for FI for multi-chain SC transfer design
Related
Discovery
Keep reading
Read next
- DORA CTPP Third-Party Risk · Indirectly Bringing AWS/Anchorage under Financial RegulationThis entry sits under fintech index. Read it with 日本金融規制 — トークン・暗号資産・決済に関する法体系 for adjacent context and 日本 Stablecoin 法制度の三層構造（JPYC・USDC・Project Pax） for the broader system boundary.fintech/dora-eu-digital-operational-resilience-ctpp
- DORA · EU Digital Operational Resilience Act OverviewThis entry sits under fintech index. Read it with 日本金融規制 — トークン・暗号資産・決済に関する法体系 for adjacent context and 日本 Stablecoin 法制度の三層構造（JPYC・USDC・Project Pax） for the broader system boundary.fintech/dora-eu-digital-operational-resilience-overview
- Dual-currency arbitrage · the §501 legal hack and regulatory fragilityThis entry sits under fintech index. Read it with 日本金融規制 — トークン・暗号資産・決済に関する法体系 for adjacent context and 日本 Stablecoin 法制度の三層構造（JPYC・USDC・Project Pax） for the broader system boundary.fintech/dual-currency-stablecoin-arbitrage-legal-hack
Links here
- Japan stablecoin issuer regulatory classification matrix — Electronic Payment Instruments business / trust type / bank-issued type / funds-transfer-operator type / prepaid-payment-instrument boundaryJapan's yen-denominated and USD-denominated stablecoins (explicitly defined as "electronic payment instruments" under the 2023-06 amended Payment Services Act) divide into 5 regulatory categ...exchanges/japan-stablecoin-issuer-regulatory-classification-matrix
- Korea Kimchi Premium economics — the structure of Upbit/Bithumb local price spreadsThis entry sits under exchanges index. Read it against 韓国 5 大 CEX 制度比較 — Upbit / Bithumb / Coinone / Korbit / GOPAX for peer / contrast context and FSA 暗号資産交換業登録制度 — 番号体系・財務局管轄・登録要件 for the...exchanges/korea-kimchi-premium-economics
- Agorá vs mBridge · Strategic Comparison of the Dual-Track Cross-Border Payment SystemThis entry sits under fintech index. Read it with 日本金融規制 — トークン・暗号資産・決済に関する法体系 for adjacent context and 日本 Stablecoin 法制度の三層構造（JPYC・USDC・Project Pax） for the broader system boundary.fintech/bis-project-agora-vs-mbridge
- Cosmos IBC for Financial InstitutionsThis entry sits under fintech index. Read it with 日本金融規制 — トークン・暗号資産・決済に関する法体系 for adjacent context and 日本 Stablecoin 法制度の三層構造（JPYC・USDC・Project Pax） for the broader system boundary.fintech/cosmos-ibc-for-financial-institutions
- Dual-currency stablecoin arbitrage · the only legal on-chain FX path in the §501 eraThis entry sits under fintech index. Read it with 日本金融規制 — トークン・暗号資産・決済に関する法体系 for adjacent context and 日本 Stablecoin 法制度の三層構造（JPYC・USDC・Project Pax） for the broader system boundary.fintech/dual-currency-stablecoin-arbitrage-overview