TROPTIONSFTH Trading
← Investor home

TROPTIONS · Operator

Institutional fiat rails

SWIFT, FedWire, and payment-orchestrator topology for diligence. Bloomberg-style facts — no partner logos or legal names on this page.

Not legal, securities, or banking advice. MSB, SWIFT, and FedWire require licensed counsel and executed bank agreements.
Marketing claims such as “1 of 2200” (or similar exclusivity) must be verified in diligence — we do not substantiate cohort statistics on this site.
PROJECTION figures ($825/hour, $874K/month) are modeled API math — not realized bank deposits.

Partner verification (diligence)

Answer these with the bank's treasury and compliance teams — not from marketing materials alone.

QuestionTROPTIONS todayPartner must confirmLabel
Connected BIC?PIPELINE — `swift-bridge` :4024 returns /health; no live FIN session in repo. Target: partner or sponsor bank with SWIFT FIN + RMA.Written confirmation: direct FIN member vs correspondent-only; BIC 8/11 on file; RMA matrix for message types (103/202).PIPELINE
Whose BIC on message?Ordering institution BIC = partner omnibus bank (TBD under NDA). Our stack sets beneficiary/creditor via orchestrator env — not published here.Field 52/53/57 mapping on MT103/202 samples; who appears as ordering vs intermediary; nostro account for debits.PIPELINE
MT103 today?PIPELINE — `POST /api/swift/send` stub in `fiat-rails/swift-bridge/`; no production MT103 UETR in operator logs yet.Service bureau or FIN connectivity live; test wire amount + UETR; settlement date (value date) and fee schedule.PIPELINE
FedWire RTGS today?PIPELINE — `fedwire-adapter` :4023 stub; orchestrator :4022 coordinates mint/burn when webhooks fire.ABA routing, omnibus account, cutoff times, return/wire recall policy.PIPELINE
IOU 1:1 with omnibus?PROVEN demand on ledger (~874M issued IOUs) — not bank reserves. Mint/burn 1:1 is PIPELINE until partner statements match supply.Daily reconciliation: omnibus balance vs on-chain IOU supply; attestation cadence and auditor access.PIPELINE

Contract lock-in checklist

ItemOwnerNoteLabel
MSB registration + state MTL matrix currentOperator / counselFinCEN MSB — not stored in git; partner may require proof before omnibus.PIPELINE
Executed partner / correspondent agreement (MSA + SLA)CounselFee schedule, indemnity, data processing, termination — no names on public site.PIPELINE
Omnibus account opened + webhook format signed offPartner bankCredit notification → orchestrator :4022 → compliance :4025 → mint IOU.PIPELINE
SWIFT BIC path (connected or nested correspondent) documentedPartner treasuryMaps to PARTNER_VERIFICATION_TABLE rows above.PIPELINE
BSA / AML reliance letter scope agreedComplianceOFAC/KYC provider keys in host .env only.PIPELINE
Exclusivity claims verified (e.g. “1 of 2200” cohort)Diligence / counselWe do not substantiate cohort statistics on this site — independent verification required.PIPELINE
Reserve & IOU attestation cadence (monthly minimum)Operator + partneriou-reserve-monitor :4027 vs bank statements.PIPELINE
No seed / API secrets in repo or Pages buildOperatorXRPL_SEED, TELEGRAM_BOT_TOKEN, SWIFT credentials in .env only — see OPERATOR_SEED_AND_PARTNER doc.PROVEN

Identifier reference

Standard institutional codes used when wrapping ledger IOUs into bank messages.

CodeNameRoleExampleTROPTIONS useLabel
BICBank Identifier Code (SWIFT)8 or 11 characters identifying a financial institution on SWIFT FINDEUTDEFF (8) · DEUTDEFFXXX (11)Beneficiary bank on MT103/202; env `SWIFT_BIC` on swift-bridge :4024PIPELINE
IBANInternational Bank Account NumberAccount-level identifier (country check + BBAN); required in many SEPA/cross-border wiresDE89 3704 0044 0532 0130 00Omnibus credit instructions at institutional partner — not stored in gitPIPELINE
LEILegal Entity Identifier20-character entity ID for regulatory reporting (MiFID, EMIR, derivatives)5493001KJTIIGC8Y1R12Counterparty diligence pack; maps to ISO 20022 party blocks when gateway wraps XRPLPIPELINE
MICMarket Identifier Code4-letter exchange / trading venue ID (ISO 10383)XNAS · ARCXExchange OS market data labels — separate from fiat settlement railsPROVEN

Connected vs non-connected BIC

TypeDefinitionSettlement pathNoteLabel
Connected BICInstitution holds SWIFT FIN membership; can send/receive MT messages directly (subject to RMA)Direct MT103/202 via service bureau or FINTarget state for institutional partner omnibus — credentials in operator vault onlyPIPELINE
Non-connectedNo direct FIN; routes via correspondent bank BIC (nested beneficiary)Correspondent debits omnibus; extra fee + latencyCommon for MSBs until own BIC or sponsored sub-account is livePIPELINE

MSB + institutional partner value

MSB + institutional partner (generic)PIPELINE
  • FinCEN MSB registration + state MTL where required — operator-held, not in repo
  • US omnibus at institutional partner: FedWire/ACH in, screened mint to XRPL IOU
  • EU correspondent slot: EUR out via SWIFT when IOU burned — multi-bank mesh
  • BaaS white-label API (:8097) for fintech clients — fee capture A–E when rails live
  • No partner legal name on this page — diligence under NDA with counsel

Rail ports — PIPELINE until bank wired

RailPortServicePathLive whenLabel
Payment orchestrator:4022payment-orchestratorfiat-rails/orchestrator/Bank webhook + compliance pass → mint IOU 1:1PIPELINE
FedWire RTGS:4023fedwire-adapterfiat-rails/fedwire-adapter/Partner bank FedWire participation + routing number wiredPIPELINE
SWIFT MT103/202:4024swift-bridgefiat-rails/swift-bridge/BIC + RMA + service bureau — PIPELINE until bank wiredPIPELINE
Compliance:4025compliance-enginefiat-rails/compliance-engine/OFAC/KYC provider keys in .envPIPELINE
IOU reserve monitor:4027iou-reserve-monitorfiat-rails/iou-reserve-monitor/Omnibus statements vs on-chain supply attestationPIPELINE

Canonical sequence: FedWire :4023 and SWIFT :4024 are adapters into payment-orchestrator :4022.

Partner meeting script (condensed)

  1. Open with IOU honesty: ~874M issued on XRPL/Stellar is demand proof on ledger — not bank reserves or Circle native USDC.
  2. Show PROVEN stack: Academy Stripe, launch.unykorn.org, x402 health, Polygon/KENNY, issuer wallets — GitHub Pages proof pack.
  3. State PIPELINE clearly: fiat-rails stubs on :4022–:4027 respond /health; no production wire until omnibus + BIC + FedWire live.
  4. Ask partner for: omnibus account, FedWire routing, SWIFT BIC or correspondent path, RMA matrix, webhook format, BSA reliance letter scope.
  5. Revenue: issuance/redemption fees (0.25% modeled), float, B2B SWIFT — all PIPELINE until first settled wire hits GL.
  6. Close with diligence: verify exclusivity claims (e.g. “1 of N” cohorts) independently — we do not publish partner names here.
Diligence: Institutional partners should reconcile BIC connectivity, omnibus agreements, and reserve policy against their own compliance function — not against marketing copy.

Technical documentation