From Static SSIs to Digital SSIs - The Wallet Era Just Got Real

Citi and SWIFT completed a fiat↔digital currency settlement workflow trial that synchronized a bank-account leg with a wallet leg using smart contracts and an orchestrator (PvP-style). In the test they even used USDC (test tokens) on Ethereum and solved for sequencing + reversibility gaps with escrow logic (not atomic, but synchronized and standards-based). This is the clearest signal yet that wallet endpoints are about to join BIC/IBAN as first‑class settlement coordinates. https://www.prnewswire.com/apac/news-releases/citi-completes-landmark-fiat-to-digital-currency-payment-settlement-workflow-trial-with-swift-302615195.html" target="_blank" rel="noopener noreferrer">PR Newswire

* Today's SSIs are static records (beneficiary bank, account, intermediary) that drive routing across correspondent chains. Errors are costly and common.
* Globally, only ~26% of cross‑border payments run fully STP; 14% incur extra charges; and name/number mismatches remain the #1 failure driver. That's millions burned in repairs and churn. Digital SSIs with verified wallet endpoints and pre‑validation are how we bend that curve.

What could change:

1. Endpoint model expands: SSIs will add a wallet layer (chain/network, token type, custody model, allowlist) alongside BIC/IBAN. SWIFT has already shown it can be the "single access point" into tokenized networks this trial pushes that from assets into payments. https://www.swift.com/news-events/press-releases/swift-unlocks-potential-tokenisation-successful-blockchain-experiments" target="_blank" rel="noopener noreferrer">Swift+1Pre‑validation becomes mandatory, not optional: Before you can "pay a wallet," you'll verify ownership, reachability and risk just as SWIFT's Payment Pre‑validation now checks accounts. Expect the same for wallets (KYC'd, whitelisted, live). https://www.swift.com/products/payment-pre-validation" target="_blank" rel="noopener noreferrer">Swift24/7 liquidity + token rails converge: Banks are stitching token services into always‑on clearing, so real-time routing between RTGS and token legs becomes a configuration, not a project. https://www.citigroup.com/global/news/press-release/2025/citi-integrates-citi-token-services-with-24-7-usd-clearing-real-time-cross-border-payments-liquidity-management" target="_blank" rel="noopener noreferrer">Citi
The playbook going forward

* Extend the SSI schema: Add fields for wallet identifier, chain, token (e.g., tokenized deposit vs. stablecoin), custody/whitelist status, travel rule reference, and fallback RTGS route.
* Governance upgrade: Treat wallet SSIs like high‑risk master data four‑eyes change control, out‑of‑band callbacks, and audit trail. (Same fraud controls, new endpoint.)
<strong>Pre‑validate everything:</strong> Turn on SWIFT pre‑validation for bank accounts and* pilot wallet verification with your custody/chain‑analytics partners. This is your STP lift. https://www.swift.com/products/payment-pre-validation" target="_blank" rel="noopener noreferrer">Swift
* Route by policy: Add rules to auto‑select rails (RTGS, correspondent, token) by value, currency, time window and counterparty risk so ops isn't hand‑picking paths at 4:55pm.
* Measure impact: Track STP%, repair rate, and $/failed payment; lexicon from the LexisNexis study gives a clean baseline for your before/after.

My take: SSIs aren't going away they're going digital. In 12-24 months, a best‑practice SSI record will include both bank coordinates and wallet coordinates, with policy‑driven selection and pre‑validation on entry. The winners will be those who operationalize Digital SSIs before the volume shows up at the helpdesk.

Topics: SSI, Tokenization, SWIFT, Stablecoins, Payments