Agentic Payments

Mastercard Multi-Token Fabric

Mastercard's multi-token network connecting banks, fintechs, and blockchains for tokenized asset movement.

Vendors

Mastercard · Partner Banks

Compliance center

Network-level compliance at Authorization

agenticmastercardmulti-tokencard-network
Filter by shape:
|
A5 · AGENTICMastercard Multi-Token Fabric·5 stations(2 compliance, 3 infra)·mastercard
S1INTENTS2S3DISCOVERYS4S5TRANSPORTS6S7FACILITATIONS8FINALITY01Custody02Network Gate03Token Route04Custody05Filing
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 Mastercard Multi-Token Fabric 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
5 stations across 5 of 8 segments. 2 are compliance checkpoints, 3 are infrastructure.
2 code-enforced3 policy-enforced
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONINSTITUTION
L4 ACCOUNTINSTITUTION

Step 1 · Participating Bank/FintechPolicy-Enforced

"A bank's treasury desk initiating a tokenized payment — the institution is pre-vetted, the operator authenticated."

A participating bank or fintech initiates a tokenized asset transfer through Mastercard's Multi-Token Network. L4+L5 lit — identity and authorization are policy-enforced. The participant operates under existing financial licenses; MTN inherits the institution's regulatory posture.

Counterparty
Self (participating institution)
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 ACCOUNTMTN COMPLIANCE
L3 EXECUTIONMTN COMPLIANCE
◆ Enforcement Line — code-enforced at this layer

Step 2 · MTN Compliance GatewayCode-EnforcedINGESTDETECTALERT

"Mastercard's network authorization — the transaction is screened, validated, and routed through Mastercard's compliance infrastructure."

Mastercard's MTN compliance layer screens the transaction: sanctions checks, counterparty verification, and Travel Rule data exchange. The MTN smart contract layer can enforce programmable rules — whitelists, velocity limits, geographic restrictions. L3+L4 lit — compliance straddles code and policy.

Counterparty
Mastercard MTN compliance gateway
Latency
<1s · network-level screening
Finality
Pre-condition gate — blocks if compliance fails
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 EXECUTIONMTN BRIDGE
L2 CONSENSUSMTN BRIDGE
L1 NETWORKMTN BRIDGE
◆ Enforcement Line — code-enforced at this layer

Step 3 · Cross-Chain Token RoutingCode-Enforced

"The clearing leg of a card payment — value is routed through the network's settlement infrastructure."

MTN routes the tokenized asset across chains if needed, or settles on the same chain. The network's bridge layer handles cross-chain coordination with Mastercard's settlement guarantees. L1+L2+L3 lit — transport executes entirely below the enforcement line.

Counterparty
Mastercard MTN settlement layer
Latency
~12s · Ethereum block (same-chain) / variable (cross-chain)
Finality
Pending · awaiting settlement confirmation
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
L5 APPLICATIONINSTITUTION
L4 ACCOUNTINSTITUTION

Step 4 · Receiving InstitutionPolicy-Enforced

"The acquiring bank's credit confirmation — funds received, compliance obligations activate."

The receiving institution's custody account is credited. L4+L5 lit on the receiving side. Mastercard's network-level authorization at this stage provides the compliance guarantee — the receiving institution can rely on MTN's screening rather than duplicating it. Recordkeeping obligations attach.

Counterparty
Receiving institution
Latency
Instant on settlement
Finality
Final on Mastercard network confirmation
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 5 · Settlement FinalityPolicy-EnforcedINGESTDETECTALERT

"Mastercard's end-of-cycle settlement — the network's final word on the transaction."

MTN settlement is final. Both institutions hold matching settlement records. The Mastercard network provides the authoritative settlement confirmation — disputes resolve through traditional card-network arbitration, not on-chain governance. Tax and recordkeeping obligations crystallize at L5.

Counterparty
Mastercard settlement network
Latency
T+0 (real-time settlement)
Finality
Final · irrevocable on MTN
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 5 steps across 1 chain(s). 0 threshold(s) triggered. Frameworks: Common Reporting Standard / FATCA.

Coverage notes: 5 disclosed gap(s).

Other Agentic Payments Paths

SETTLEMENT CHAINS