Wholesale Payments

Partior Multi-Bank Settlement

Multi-bank atomic settlement network — DBS, JPMorgan, Temasek consortium.

Vendors

Partior · DBS · JPMorgan · Temasek

Compliance center

Multi-bank atomic settlement at Transport + Authorization

wholesalepartiormulti-bankatomicdbs
Filter by shape:
|
W6 · WHOLESALEPartior multi-bank atomic settlement·6 stations(2 compliance, 4 infra)·partior · jpmorgan · dbs
S1INTENTS2S3DISCOVERYS4S5TRANSPORTS6AUTHORIZATIONS7FACILITATIONS8FINALITY01Bank Account02Sanctions03Bridge04Authorization05Bank Account06Finality
3+5 shape system
GatePre-condition — blocks if it failsMonitorConcurrent — observes without haltingObligationPost-settlement — reports after the factsolid = codedashed = policy
How to read this diagram
Each station on the rail represents a compliance or infrastructure event in the Partior multi-bank atomic settlement path. Hover any station to inspect it. The shape tells you what kind of event it is. The ring tells you how it's enforced.
Gate Monitor Obligation| Ingress Crossing Transform Settlement Venue
This path at a glance
6 stations across 6 of 8 segments. 2 are compliance checkpoints, 4 are infrastructure.
3 code-enforced3 policy-enforced
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONINSTITUTION
L4 ACCOUNTINSTITUTION

Step 1 · Originating Bank (Partior Participant)Policy-Enforced

"A bank's FX desk initiating a multi-currency settlement — multiple legs need to execute atomically across correspondent accounts."

The originating bank initiates a multi-bank settlement instruction on Partior. All Partior participants are pre-vetted global banks (DBS, JPMorgan, Standard Chartered). L4+L5 lit: institutional identity and authorization are policy-enforced. D9 (prudential) applies — participants are G-SIBs or D-SIBs subject to enhanced regulatory requirements.

Counterparty
Self (Partior participant bank)
Latency
Instant · API initiation
Finality
N/A — instruction only
Vendors
MetaMask · MetaMask Institutional (ConsenSys-operated; institutional custody/MPC integrations) · Fireblocks · Safe (Gnosis Safe — multisig + module framework) · EOA (secp256k1 externally-owned accounts) + ERC-4337 account abstraction (EntryPoint singleton + UserOperation mempool — paymaster and aggregator extensions) · Securitize LLC (SEC-registered transfer agent; runs Reg D 506(c)(2)(ii) accredited-investor verification workflow) — off-chain compliance function paired with on-chain DS Protocol enforcement · EigenLayer (restaking primitive — slashing-conditional re-pledge of staked ETH and LSTs to Actively Validated Services; compliance-relevant for AVSs that supply oracle / fast-finality / DA security to downstream protocols) · Securitize Markets ATS (SEC-registered ATS) · INX Securities ATS · BlackRock BUIDL · Franklin BENJI · Hashnote USYC · Ondo OUSG · Apollo ACRED (Ethereum mainnet deployments; issuer profiles carry SEC-registered / NYDFS limited-purpose trust / Reg D 506(c) postures detailed in the respective compliance frameworks)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L4 ACCOUNTPARTIOR MATCHING
L3 EXECUTIONPARTIOR MATCHING
◆ Enforcement Line — code-enforced at this layer

Step 2 · Partior Compliance & MatchingCode-EnforcedINGESTDETECTALERT

"A CLS (Continuous Linked Settlement) matching cycle — multiple payment legs are matched, validated, and queued for simultaneous execution."

Partior's matching engine pairs the settlement legs: if this is a PvP FX trade, both currency legs must match before either executes. Sanctions screening and AML checks run on all legs simultaneously. Travel Rule data exchanged between participant banks. L3+L4 lit — matching straddles code (network logic) and policy (bilateral bank agreements).

Counterparty
Partior matching engine
Latency
<2s · real-time matching
Finality
Pre-condition gate — all legs must match before execution
Vendors
Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer for opt-in callers) · Uniswap v4 (extensible AMM — concentrated liquidity + custom-logic extension framework) · Curve · Balancer · Circle CCTP v2 (canonical USDC burn-and-mint cross-chain transport) · Wormhole · LayerZero · Across (intent-based settlement) · Securitize DS Protocol (on-chain transfer-restriction smart-contract framework enforcing eligible-investor whitelisting) · ERC-3643 / T-REX (industry-standard permissioned-token framework — Tokeny-developed, used by issuers outside the Securitize stack) · EOA (secp256k1 externally-owned accounts) + ERC-4337 account abstraction (EntryPoint singleton + UserOperation mempool — paymaster and aggregator extensions) · Securitize LLC (SEC-registered transfer agent; runs Reg D 506(c)(2)(ii) accredited-investor verification workflow) — off-chain compliance function paired with on-chain DS Protocol enforcement · EigenLayer (restaking primitive — slashing-conditional re-pledge of staked ETH and LSTs to Actively Validated Services; compliance-relevant for AVSs that supply oracle / fast-finality / DA security to downstream protocols)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L3 EXECUTIONATOMIC PVP
L2 CONSENSUSATOMIC PVP
L1 NETWORKATOMIC PVP
◆ Enforcement Line — code-enforced at this layer

Step 3 · Atomic Multi-Leg ExecutionCode-Enforced

"A CLS settlement window — all legs execute simultaneously, or none do. No Herstatt risk."

All settlement legs execute atomically on Partior's ledger. PvP ensures both sides of an FX trade settle simultaneously — eliminating Herstatt risk (the risk that one leg settles and the other doesn't). L1+L2+L3 lit — the full stack below the enforcement line processes the atomic settlement. This is the key innovation: multi-bank, multi-currency, atomic execution with zero settlement risk.

Counterparty
Partior atomic settlement engine
Latency
<1s · atomic multi-leg execution
Finality
Atomic — all legs final or none
Vendors
Circle CCTP v2 (canonical USDC burn-and-mint cross-chain transport) · Wormhole · LayerZero · Across (intent-based settlement) · Ethereum devp2p / libp2p transport · EIP-4844 blob-data DA layer (canonical DA for OP Stack and other rollup-based L2s — Base, Arc, Tempo, Arbitrum, Optimism, etc.) · Ethereum Proof-of-Stake (Beacon Chain — Casper FFG finality + LMD-GHOST fork choice) — permissionless 32-ETH stake threshold; effective validator economics concentrated via Lido / Coinbase / Binance / Kraken / Figment staking pools · MEV-Boost relays (Proposer-Builder Separation — out-of-protocol; OFAC-compliant relays Flashbots / BloXroute Regulated have periodically dominated relay share) · Uniswap v4 (extensible AMM — concentrated liquidity + custom-logic extension framework) · Curve · Balancer · Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer for opt-in callers) · Securitize DS Protocol (on-chain transfer-restriction smart-contract framework enforcing eligible-investor whitelisting) · ERC-3643 / T-REX (industry-standard permissioned-token framework — Tokeny-developed, used by issuers outside the Securitize stack)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L3 EXECUTIONBILATERAL AUTH
◆ Enforcement Line — code-enforced at this layer

Step 4 · Bilateral AuthorizationCode-EnforcedINGESTDETECTALERT

"Post-trade bilateral confirmation in traditional FX — both banks confirm the settlement details match their records."

Both counterparty banks authorize the settled position. Each bank's compliance layer confirms the settlement against its own regulatory framework — different jurisdictions may apply different rules to the same transaction. L3 Execution lit — bilateral authorization is code-enforced at the network level. This is the second compliance center of gravity.

Counterparty
Counterparty bank (bilateral confirmation)
Latency
<1s · network-level confirmation
Finality
Authorization confirmed bilaterally
Vendors
Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer for opt-in callers) · Uniswap v4 (extensible AMM — concentrated liquidity + custom-logic extension framework) · Curve · Balancer · Circle CCTP v2 (canonical USDC burn-and-mint cross-chain transport) · Wormhole · LayerZero · Across (intent-based settlement) · Securitize DS Protocol (on-chain transfer-restriction smart-contract framework enforcing eligible-investor whitelisting) · ERC-3643 / T-REX (industry-standard permissioned-token framework — Tokeny-developed, used by issuers outside the Securitize stack)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONINSTITUTION
L4 ACCOUNTINSTITUTION

Step 5 · Counterparty Bank ReceiptPolicy-Enforced

"The counterparty bank's treasury ledger showing the settled position — both currency legs complete."

Both banks see the settled positions on their Partior accounts. L4+L5 lit on the receiving side. Each bank reconciles the Partior settlement against its internal ledger. Because settlement is atomic and instant, there's no intraday credit exposure and no failed settlement to manage.

Counterparty
Counterparty bank (Partior participant)
Latency
Instant on atomic execution
Finality
Final · atomic settlement complete
Vendors
MetaMask · MetaMask Institutional (ConsenSys-operated; institutional custody/MPC integrations) · Fireblocks · Safe (Gnosis Safe — multisig + module framework) · EOA (secp256k1 externally-owned accounts) + ERC-4337 account abstraction (EntryPoint singleton + UserOperation mempool — paymaster and aggregator extensions) · Securitize LLC (SEC-registered transfer agent; runs Reg D 506(c)(2)(ii) accredited-investor verification workflow) — off-chain compliance function paired with on-chain DS Protocol enforcement · EigenLayer (restaking primitive — slashing-conditional re-pledge of staked ETH and LSTs to Actively Validated Services; compliance-relevant for AVSs that supply oracle / fast-finality / DA security to downstream protocols) · Securitize Markets ATS (SEC-registered ATS) · INX Securities ATS · BlackRock BUIDL · Franklin BENJI · Hashnote USYC · Ondo OUSG · Apollo ACRED (Ethereum mainnet deployments; issuer profiles carry SEC-registered / NYDFS limited-purpose trust / Reg D 506(c) postures detailed in the respective compliance frameworks)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONSETTLEMENT

Step 6 · Settlement Finality & ReconciliationPolicy-Enforced

"End-of-day reconciliation that's already done — because atomic settlement eliminates the reconciliation problem."

Settlement is final. Both banks hold matching records on the Partior ledger. The reconciliation problem that plagues traditional correspondent banking is eliminated — atomic execution means there's nothing to reconcile. L5 Application lit only. Tax and regulatory reporting obligations crystallize. Partior provides full audit trail for regulatory examination.

Counterparty
Partior network (settlement records)
Latency
T+0 (real-time)
Finality
Final · irrevocable — atomic PvP
Vendors
EOA (secp256k1 externally-owned accounts) + ERC-4337 account abstraction (EntryPoint singleton + UserOperation mempool — paymaster and aggregator extensions) · MetaMask · MetaMask Institutional (ConsenSys-operated; institutional custody/MPC integrations) · Fireblocks · Safe (Gnosis Safe — multisig + module framework) · Securitize Markets ATS (SEC-registered ATS) · INX Securities ATS · BlackRock BUIDL · Franklin BENJI · Hashnote USYC · Ondo OUSG · Apollo ACRED (Ethereum mainnet deployments; issuer profiles carry SEC-registered / NYDFS limited-purpose trust / Reg D 506(c) postures detailed in the respective compliance frameworks)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))

Resolved 6 steps across 1 chain(s). 0 threshold(s) triggered. Frameworks: Common Reporting Standard / FATCA.

Coverage notes: 5 disclosed gap(s).

Other Wholesale Payments Paths

SETTLEMENT CHAINS