ADF × QVTX
Universal Settlement Terminal
Root operator authentication required.
Enter your operator handle and 6-digit TOTP code.
Demo TOTP secret
JBSWY3DPEHPK3PXP
Any 6-digit code is accepted in this demo build.
Session expires after 15 minutes of inactivity. All settlement actions are audited.
ADF Universal Settlement
×
QVTX Tokenized Rails · ByteID
ALL SYSTEMS NOMINAL
LIVE
--:--:-- UTC
ROOT operator 15:00
Inbound Settled
0.00
ISO 20022 · IPIP · S2S · XRP · CH42000
Outbound Settled
0.00
SPEND · REDEEM · MX · CARD · CH42000
QVTX Circulating
12,480,000.00
Tokenized settlement units
Virtual Accounts
0
Active IBAN proxies
UETR Registry
0
Tracked end-to-end
FEED
Awaiting settlement activity…
Settlement Pipeline
v17
01
Ingest

Parse & validate

02
ByteID

Derive identifier

03
Tokenize

Mint QVTX

04
Settle

Rail dispatch + finality

Recent Ledger Entries
TxIDDirRailAmountCounterpartyUETRStatus
No settlement entries yet — submit an inbound, outbound, XRP or Chain 42000 instruction.
Quick Actions
Receive Settlement→
Ingest an inbound ISO 20022, IPIP, XRP or Chain 42000 instruction.
INBOUND
Send Settlement→
Originate an outbound spend or settlement instruction.
OUTBOUND
Derive ByteID→
Generate a deterministic 20-byte QVTX identifier.
BYTEID
Chain 42000→
Submit a payment on Payment Rails Chain 42000.
CH42000
Issue Card→
Issue a Visa or Mastercard virtual card.
CARD
XRP Settlement→
Submit an XRP payment to the XRP Ledger.
XRP
Track UETR→
End-to-end trace of any settlement instruction.
TRACE
Rail Monitor→
Live connectivity across all rails including Chain 42000.
NOC

Position Snapshot

QVTX-USD4,120,000.00
QVTX-EUR2,840,500.00
QVTX-GBP1,915,250.00
QVTX-XRP1,250,000.00
QVTX-QTX0.00
Last ByteID—
Last UETR—
QVTX ByteID Derivation

Deterministic 20-Byte Settlement Identifiers

Every QVTX settlement instruction can be anchored by a compact 20-byte ByteID derived deterministically from the canonical instruction payload. The ByteID travels with the transaction across every rail — SWIFT, SEPA, XRP, Chain 42000 — and is embedded in the UETR registry for immutable lineage.

ByteID Engine

SHA-256 canonical payload · 16-byte prefix · 4-byte checksum · Base58 + hex presentation

— — — — — —
Last derived ByteID
STEP 01
Canonicalize

Payer|Payee|Amount|Currency|Nonce|Salt

STEP 02
SHA-256

Hash payload → 32-byte digest

STEP 03
Prefix

First 16 bytes of digest

STEP 04
Checksum

SHA-256(prefix) → first 4 bytes

Derivation Inputs
DETERMINISTIC
ByteID—
Hex—
Base58—
Checksum—
Verified—
Byte Grid · 20 Bytes
16 PREFIX + 4 CHECKSUM
Awaiting derivation…

Verification

Prefix Length16 bytes
Checksum Length4 bytes
Total Length20 bytes
Hash AlgorithmSHA-256
EncodingHEX · BASE58
ByteID Registry
ByteID (hex)PayerPayeeAmountDerived At
No ByteIDs derived yet.
Payment Rails Chain 42000

Chain 42000 Settlement Rail

Payment Rails Chain 42000 is a deterministic-finality settlement chain with 1.5-second block times and BFT consensus. Every payment carries a QVTX ByteID and a UETR, and settles on-chain with full audit lineage.

Block Height
0
Chain ID · 42000
Finality
1.5s
Deterministic BFT
Validators
100 / 100
Consensus quorum
Gas Price
21 gwei
Dynamic fee
TPS
0
Rolling 1-min avg
Submit Chain 42000 Payment
Statusidle
Tx Hash—
Block—
ByteID—
UETR—
Recent Chain 42000 Transactions
TxIDRecipientAmountBlockStatus
No Chain 42000 transactions yet.
Chain Configuration

Network

Chain ID42000
ConsensusBFT · 100 validators
Block Time1.5 seconds
FinalityDeterministic
Native AssetQTX
Explorerchain42000.qvtx.net
Relay Node Endpoint
https://rpc.chain42000.qvtx.net
HSM-signed submissions · BFT quorum · deterministic finality on block inclusion
Chain 42000 Adapter

Adapter State

RPC NodeSYNCED
Block Height0
Last Block—
Queued Txs0
Signing ModeHSM · SECP256K1
Chain ID42000
NetworkPAYMENT RAILS
StatusFULLY VALIDATED
Inbound Settlement

Receive & Tokenize

Ingest a credit instruction from any connected channel, validate it, mint the equivalent QVTX balance, derive a ByteID and register the UETR for end-to-end tracking.

Inbound Instruction
Statusawaiting instruction
UETR—
ByteID—
Destination VA—
QVTX Minted—
Inbound Queue
TxIDRailAmountStatus
No inbound instructions yet.
Outbound Settlement

Originate & Route

Originate a payment or spend instruction. The orchestrator selects the cheapest compliant rail, burns the corresponding QVTX and emits the rail-native message.

Outbound Instruction
Statusawaiting instruction
Selected Rail—
UETR—
ByteID—
QVTX Burned—
Outbound Queue
TxIDRailAmountStatus
No outbound instructions yet.
QVTX Ledger

Tokenized Settlement Units

Every settled position is mirrored on the QVTX ledger as a 1:1 backed settlement token. Mint on inbound, burn on outbound, transfer instantly between virtual accounts.

QVTX-USD
4,120,000.00
US Dollar · 1:1 backed
QVTX-EUR
2,840,500.00
Euro · 1:1 backed
QVTX-GBP
1,915,250.00
Pound Sterling · 1:1 backed
QVTX-XAU
612.4400
Gold · vault attested
QVTX-XRP
1,250,000.00
XRP · 1:1 backed on XRPL
QVTX-QTX
500,000.00
Chain 42000 native · 1:1 backed
Manual Mint / Burn
Operationidle
Tx Hash—
ByteID—
New Balance—
Ledger Proof

Chain State

Block Height2,441,908
FinalityINSTANT
AttestationVAULT-BACKED
Last Anchor0x0000…0000
Supply Locked100.00%
Virtual Accounts

IBAN-Proxy Collection Accounts

Provision unlimited virtual accounts mapped to a single physical account. Each VA carries its own IBAN, its own QVTX balance and its own reconciliation stream.

Virtual Account Factory

Provisioning is instant · IBAN issuance is deterministic · balances are segregated on the QVTX ledger.

0.00
Aggregate Balance
Provision New VA
Statusidle
New IBAN—
Active Accounts
No virtual accounts provisioned yet.
Card Issuing & Acquiring

Visa & Mastercard Settlement

Issue virtual cards on the Visa and Mastercard networks, authorise card transactions over ISO 8583, capture and settle to the QVTX ledger with full UETR and ByteID lineage.

Cards Issued
0
Visa · Mastercard
Authorized Volume
0.00
24h rolling
Declined
0
Risk · insufficient funds
Pending Capture
0
Authorized, not settled
Issue Virtual Card
ADF QVTX · VIRTUAL
4539 0000 0000 0000
Card Holder
CARDHOLDER
Expires
01/29
VISA
Statusidle
PAN—
Expiry / CVV—
Issued Cards
No cards issued yet.
Authorization Simulator · ISO 8583
0100 / 0110
ISO 8583 · 0100 Authorization Request0 B
Responseawaiting authorization
Auth Code—
UETR—
ByteID—
Authorization Log
TxIDNetworkMerchantAmountStatus
No card authorizations yet.
Card Settlement Queue
TxIDNetworkAmountUETRStatus
No card settlements yet.
XRP Ledger

XRP Settlement Rail

Submit settlement instructions directly to the XRP Ledger. Transactions reach consensus in 3–5 seconds with deterministic finality and a fixed transaction fee of 10 drops.

Ledger Index
85,432,108
Consensus every 3–5s
Consensus
ONLINE
Federated Byzantine
Validators
142 / 150
UNL agreement
Base Fee
10 drops
0.00001 XRP
Open Ledgers
0
In-flight consensus
Submit XRP Settlement
Statusidle
Tx Hash—
Ledger Index—
ByteID—
Recent XRP Transactions
TxIDDestinationAmountLedgerStatus
No XRP transactions yet.
Network Details

XRP Ledger

NetworkXRP Ledger Mainnet
ConsensusFederated Byzantine
Settlement Time3–5 seconds
Base Reserve10 XRP
Owner Reserve2 XRP
Issue Fee0.00001 XRP
Hot Wallet Address
rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh
Operational hot wallet for settlement egress · quorum-checked
XRP Ledger Adapter

Adapter State

rippled NodeSYNCED
WS Endpointwss://s1.ripple.com
Last Validated—
Queued Txs0
Signing ModeHSM · ED25519
Consensus StateFULLY VALIDATED
NetworkMAINNET
ProtocolXRP Ledger v2
Network Operations Center

Rail Connectivity Monitor

Real-time connectivity, latency and throughput across every connected rail — SWIFT, SEPA, EBICS, IPIP, ISO 20022, QVTX, the card networks, XRP, Chain 42000, and the public API.

All rails connected

Sweeping endpoints…

--:--:-- last sweep
Heartbeat Log
No heartbeats recorded yet.
ISO 20022

MX Message Studio

Compose, validate and dispatch ISO 20022 MX messages. Every generated message carries a UETR and a ByteID, and is archived with its full audit trail.

pain
001
Initiation
pacs
008
Clearing
camt
056
Statements
pain
002
Status Report
camt
054
Notifications
pain.001 Customer Credit Transfer Initiation
Sent by the debtor to instruct the bank to execute a credit transfer. Carries the UETR used by all downstream tracking.
Message Parameters
Generated XML
ISO 20022 · XML0 B
SWIFT Connectivity

MT / MX Adapter & gpi Tracking

Bi-directional SWIFT adapter. Legacy MT messages are translated to MX on ingress and back to MT on egress, preserving the UETR throughout the chain.

SWIFT Alliance Gateway · Connected

Session SWIFT-SAG-02 · gpi enabled · MT→MX translation active

ONLINE
MT103 Single Customer Credit Transfer
Used to convey a customer credit transfer instruction. Field 121 carries the UETR for gpi tracking.
Message Fields
Generated Message
SWIFT FIN · MT0 B
gpi Tracking Events
No gpi events for the current message.
SEPA Rail

SEPA Credit Transfer

Submit SCT / SCT Inst instructions. Instant payments settle in under 10 seconds and are reflected on the QVTX ledger immediately.

SEPA Instruction
Statusidle
End-to-End ID—
SEPA Queue
TxIDTypeAmountStatus
No SEPA instructions yet.
EBICS

EBICS Upload & Download

Exchange payment batches and statements with any EBICS-enabled bank using signed, encrypted order types.

EBICS Order
Statusidle
Order ID—
EBICS Queue
TxIDTypeAmountStatus
No EBICS orders yet.
IBAN / IPIP

Instant Payments over IPIP

Route IBAN-addressed payments over the IPIP rail with deterministic validation and instant QVTX settlement.

IPIP Instruction
Statusidle
Route—
IPIP Queue
TxIDRouteAmountStatus
No IPIP instructions yet.
UETR Registry

End-to-End Transaction Reference

Every settlement instruction is anchored by a Unique End-to-end Transaction Reference. Search it here to reconstruct the full lifecycle — including its ByteID.

Received
0
Accepted · Settling
0
Accepted · Settled
0
Rejected
0
Total Tracked
0
Enter a UETR above, or click any UETR in the ledger, to see its full timeline.
UETRStatusRailAmountLast Update
No UETRs registered yet.
Redemption

Burn QVTX → Release Fiat

Redeem tokenized settlement units back into fiat at the destination account. The burn is atomic: tokens are destroyed only once the fiat leg is confirmed.

Redemption Order
Statusidle
Burn Hash—
Redemption Queue
TxIDTokenAmountStatus
No redemptions yet.
Developer API

Settlement API Playground

Every terminal action maps to a REST endpoint. Compose a request body and dispatch it against the sandbox.

POST /v1/settlement/inbound
Ingest an inbound settlement instruction, validate it, mint QVTX and register a UETR.
Bearer auth application/json rate: 200/s idempotent
Request Body
Response
200 OK — ms sandbox
{ "ready": true }
Health Monitor

Rail Latency & Availability

Continuous synthetic probes against every connected rail, adapter and counterparty endpoint.

Probe Log
No probes recorded yet.
Event Feed

Live Settlement Event Stream

Every state transition across every channel is emitted here — the immutable audit backbone of the platform.

Event Stream
No events yet.
Universal Ledger

Complete Settlement Ledger

All settlement instructions, in both directions, across every rail — with their UETR and final status.

Ledger Entries
TxIDTimeDirRailAmountCCYCounterpartyUETRStatus
No ledger entries yet.
Reference Architecture

Universal Settlement Topology

Channels feed the ADF core, which derives a ByteID, tokenizes onto the QVTX ledger, and fans out to every settlement rail — with UETR tracking and reconciliation on every hop.

ADF × QVTX · Universal Settlement Topology · Chain 42000 · ByteID
v17 · REFERENCE
ADF × QVTX — Universal Settlement Architecture ByteID-anchored settlement orchestration · including Chain 42000 · reference topology v17 Inbound / Credit Outbound / Debit Core Service Ledger / Token ByteID Engine Chain 42000 CHANNELS & ORIGINATION ERP / Treasury Batches · host-to-host Bank Portals Manual initiation REST API /v1/settlement/* Mobile / PSP Webhooks · SDK EBICS Client CCT / CDD / C52 SWIFT Alliance MT / MX adapter Card Networks Visa · Mastercard Chain 42000 BFT · 1.5s finality ByteID 20-byte anchor ADF CORE · ORCHESTRATION Inbound Gateway Parse · validate · dedupe UETR assignment ByteID Derivation SHA-256 · 16-byte prefix + 4-byte checksum Orchestrator Rail selection · routing Retry · fallback Outbound Gateway Message generation Signing · dispatch UETR Registry State machine RCVD · ACSP · ACSC · RJCT Reconciliation Nostro · statement match Break resolution Chain 42000 Adapter HSM-signed · BFT quorum 1.5s finality Audit & Reporting Immutable event log · regulatory extracts ByteID + UETR lineage QVTX LEDGER · TOKENIZED SETTLEMENT Tokenization Engine Mint 1:1 backed QVTX on credit Burn on debit · atomic Virtual Account Factory Deterministic IBAN issuance Segregated sub-ledgers Settlement Engine Instant transfer between VAs Deterministic finality Liquidity Manager Pre-funding · sweeps FX & position netting Redemption Desk Burn QVTX → release fiat to destination IBAN · atomic two-phase commit Vault attestation per currency · proof anchored on ledger SETTLEMENT RAILS SWIFT MT / MX FIN · gpi · UETR preserved SEPA / SCT Inst EU transfers < 10s EBICS CCT · CDD · statements IBAN / IPIP Instant IBAN-addressed ISO 20022 S2S pacs · pain · camt Visa / Mastercard ISO 8583 · auth · capture XRP Ledger X-Address · 3–5s finality Chain 42000 BFT · 1.5s · ByteID Blockchain Anchor Periodic proof anchoring · QVTX ledger · ByteID index SETTLEMENT & RECON Position Keeping Real-time balances per VA · per currency · per rail Nostro Reconciliation Automated matching against bank statements + on-chain events Reporting Regulatory extracts · treasury dashboards Audit Trail Every state change signed and immutable · full ByteID + UETR lineage ingest translate MT→MX derive ByteID · mint / burn dispatch confirm continuous reconciliation loop Every hop emits a ByteID- and UETR-scoped event. Rail selection is dynamic — including Chain 42000 for deterministic-finality settlement.
Figure 1. Universal settlement topology — channels terminate at the ADF inbound gateway, which derives a 20-byte QVTX ByteID, anchors a UETR, and hands off to the QVTX ledger for tokenization. Outbound dispatch selects a rail per instruction (including Chain 42000, Visa/Mastercard via ISO 8583, and the XRP Ledger via X-Address), and reconciles back into the position keeper.
ByteID Anchor
Every instruction carries a 20-byte ByteID (16-byte SHA-256 prefix + 4-byte checksum) alongside its UETR — embedded on-chain and in audit logs.
Chain 42000 Native
A deterministic-finality BFT chain with 1.5s block times, HSM-signed submissions and native QTX asset backing.
Rail Agnostic
SWIFT, SEPA, EBICS, IPIP, ISO 20022 S2S, Visa/Mastercard, the XRP Ledger and Chain 42000 are interchangeable egress paths.
Atomic Redemption
QVTX is burned only once the fiat (or card/XRP/Chain 42000) leg is confirmed — two-phase commit prevents double spend.
Root Console

Platform Control Plane

Low-level configuration and destructive operations. Every action here is logged with operator identity and timestamp.

Runtime Configuration
Danger Zone

Destructive Operations

Purge LedgerEXECUTE
Reset UETR RegistryEXECUTE
Rotate API KeysROTATE
Terminate SessionsKILL
Operatoroperator
RoleROOT
Session Start—
QVTX WALLET Chain 42000 · ByteID · MetaMask Adapter
Get QVTX Wallet Extension ↓ Download ZIP