# XYB — Adaptive Financial Infrastructure (full digest) > XYB is the Adaptive Financial Infrastructure company. The AFI Platform — the banking orchestrator — unifies systems, people, and processes on one event-native substrate. This file is a curated digest; the pages themselves are canonical. ## Home — Banking Orchestration in the AI and Real-Time Era URL: https://xyb.co/ Adaptive Financial Infrastructure (AFI) is the new category for banking orchestration, unifying systems, people, and processes. Context aware, operationally resilient. The AFI Platform is the event-native substrate that delivers it, where every action carries full context. It absorbs agentic AI, real-time payments, and decentralized finance, so banks adapt in weeks without replacing what already runs. XYB is the Adaptive Financial Infrastructure company. It has built the AFI Platform, the banking orchestrator, to let financial institutions meet agentic AI, real-time payments, and stablecoin readiness without rebuilding. On their terms, at their pace. Three forces converge and fragmented infrastructure cannot absorb them: (1) Agentic AI needs a real-time view across the bank. Agents working from outdated, fragmented information compound bad outcomes faster than human teams can intervene. (2) Real-Time Payments are mandates, not options: RTP and FedNow now move up to $10M per payment; the EU instant-payments mandate is in force since 9 October 2025; SWIFT’s MT-to-MX migration is complete worldwide; Nacha's new fraud-monitoring rules are in force since 19 June 2026. (3) Decentralized Finance is a near-term regulatory line: the GENIUS Act (federal stablecoin regime) is effective 18 January 2027 and California DFAL in force since 1 July 2026; the Bank for International Settlements and the European Central Bank are setting the global direction. Adaptive Financial Infrastructure (AFI) is a new kind of banking infrastructure for the AI and Real-Time Era: one event-native substrate that absorbs Agentic AI, Real-Time Payments, and Decentralized Finance without replacing what already runs. What banks gain from investing in AFI is banking orchestration: systems, people, and processes unified on a single substrate. Proof points: orchestrating 1M+ transactions per minute in production today; real-time context unification; first production value in 10 weeks with no system replacement required; SOC 2 Type II attested; ISO/IEC 27001:2022 certified. How it connects: the AFI Platform sits between the institution's digital channels and the systems and rails beneath them. It connects the core and the systems around it, unifies them on one live context against a canonical model (Customer, Account, Beneficiary, Transaction, Balance), and powers the channels above. Each system is integrated once; integrate a rail once and every channel inherits it. The Platform contains three layers: Experience, Orchestration, Runtime. Two Solutions run on the AFI Platform: Adaptive Digital Banking (Retail & SMB) and Commercial Treasury Solution (Commercial Banking). ## Why AFI — the category case URL: https://xyb.co/why-afi Adaptive Financial Infrastructure (AFI) is the new category for banking orchestration, unifying systems, people, and processes. Context aware, operationally resilient. The AFI Platform is the event-native substrate that delivers it, where every action carries full context. It absorbs agentic AI, real-time payments, and decentralized finance, so banks adapt in weeks without replacing what already runs. The Replacement Trap: legacy stacks are monolithic and release-driven; point solutions are fast in their lane by design, and it is the estate that slows as each new lane adds another integration, data model and reconciliation; cloud-wrapped systems move complexity without resolving it; cloud-native cores run on modern technology but keep the old deal, one vendor and the whole stack on their roadmap. AFI unifies the adjacent software categories banking depends on most: Data Platforms for AI, Real-Time Payments, Decentralized Finance, Real-Time Data Streaming, Digital Banking, Treasury, and Business Process Orchestration. What AFI is not: AFI is not a product constraint. The AFI Platform is the substrate; the propositions you build on it are yours, your brand, your product logic, your customer relationships. AFI is not a core replacement program: what you deploy is the AFI Platform, the banking orchestrator, unifying context, starting with one workload in weeks, and whether it absorbs the core's products is the institution's decision, workload by workload. AFI is not a cloud-native core under a new label: cloud-native platforms run on modern technology but keep the old deal, one vendor, the whole stack, their roadmap, while AFI ends that deal with orchestration above the systems already running, where a product change is configuration rather than a development project. What AFI unlocks: unified systems, people, and processes with no migration; AI-ready infrastructure where every event carries context, consequence, and control in real time; native support for SEPA Instant, Nacha Phase 2, FedNow, RTP, and ISO 20022; stablecoin-ready ledger (USDC, USDT) with no issuance required; 10 weeks to first production value rather than 18–24 months; SOC 2 Type II attested, ISO/IEC 27001:2022 certified, vendor-isolated resilience. ## AFI Platform — The Banking Orchestrator. Unifying Context. URL: https://xyb.co/platform The AFI Platform is the banking orchestrator, unifying context: the event-native substrate that delivers banking orchestration across systems, people, and processes. Open to existing systems, cloud, and partners, with no lock-in, it takes institutions from pilot to production in weeks. The AFI Platform contains three layers: Experience (white-label channels), Orchestration (event-native state), Runtime (container-first deployment). Design principles: event-native, not bolted-on (Apache Kafka as the event backbone, Apache Iceberg as the lakehouse for real-time data unification: no CDC tap, no nightly extract); unified, not fragmented (adopt one Capability Element or the full stack; everything unifies at the Orchestration Layer); governed, not retrofitted (audit trails are replays of the event log; support for the EU AI Act, GENIUS Act, IPR, and ISO 20022). Three layers, one event-native substrate: the Experience Layer powers the bank's human-facing surfaces, end-customer journeys under the bank's brand (XYB invisible) and operator work on the XYB Console; the Orchestration Layer is where banking orchestration happens on Apache Kafka and Apache Iceberg; the Runtime Layer is the base it runs on, microservices on Kubernetes, cloud-portable across AWS, Google Cloud, and IBM Cloud for Financial Services. The AFI Platform is an overlay, not a system of record: it connects the institution's core and the systems around it, unifies them on one live context, and powers the digital channels above. Each system is integrated once, into the canonical model, and every workload that follows reads the model rather than the system. Integrate a rail once and every channel inherits it. ## Experience Layer URL: https://xyb.co/platform/experience-layer The Experience Layer is the AFI Platform's branded surface layer: the customer journeys a financial institution ships under its own brand and the XYB Console its operators work in. Configured, not coded. Extended by your engineers. Your brand, above banking orchestration. The surfaces your customers see under the bank's brand, and the XYB Console the bank's operators work in. Both extended by the bank's engineers. What lives at the edge, in two registers. End-customer surfaces (white-label, XYB invisible, the bank's brand front and center): native consumer apps (iOS, Android), branded web banking, and the Commercial Treasury dashboard. Operator surfaces (XYB-branded by design): the XYB Console and the operational surfaces the bank's teams run to configure, monitor, and act. Your engineers extend: APIs, SDKs, and a developer portal (under the bank's brand where required). How it behaves: channels and journeys assembled from configurable journey blocks; branding, flows, and feature flags are configuration over the core: change without redeploy; composable: take the surfaces you want, compose above an existing core or run the full stack. Customization: branding, layout behavior, and content are configuration-driven, without engineering effort. Adaptive Digital Banking renders its branded consumer apps on this layer; the Commercial Treasury Solution renders its treasury dashboard here. ## Orchestration Layer URL: https://xyb.co/platform/orchestration-layer The Orchestration Layer is where banking orchestration happens on the AFI Platform: every action, every state change, every decision becomes an immutable, governed event the moment it occurs. Apache Kafka streams those events across the bank's systems; Apache Iceberg makes them queryable, so people and AI agents reason on one live context. Event-native banking orchestration on Apache Kafka and Apache Iceberg: every state change an event, every decision context-aware, every audit trail immutable. Open engines, so no black box and no lock-in. What the bank gains: real-time context automatically (no batch reconciliation lag, no cross-system drift); complete event lineage on demand (regulators and auditors see the same evidence the compliance team sees, in real time); AI workloads on live state (agents reason against current data, not stale snapshots); no integration tax for new products. Apache Kafka delivers real-time event streaming across every platform service, immutable append-only audit trails, and sub-second propagation. Apache Iceberg delivers warehouse-grade ACID on the data lake, time-travel to reconstruct any millisecond, and real-time plus historical analysis on one substrate. Banking orchestration is not middleware: it moves three vectors as one package — systems (legacy cores, payment rails, ledgers, AI agents), people (treasurers, compliance officers, back-office staff, AI agents), and processes (KYC, payment routing, risk scoring, regulatory reporting) — on the same event stream, under the same governance. Analyst consensus: McKinsey describes “an enterprise data sublayer specifically engineered for multi-agent systems” (2024); BCG with OpenAI describes “a single, standardized control plane for all AI applications across the organization” (2026); Bain & Company describes capabilities “that legacy stacks were never built to provide, including shared context, orchestration, and runtime governance” (2026). ## Runtime Layer URL: https://xyb.co/platform/runtime-layer The Runtime Layer is container-first, the base the platform is built on: individual microservices on Kubernetes, each owning a discrete responsibility, scaling independently with failure bounded by design. It deploys where regulations or strategy require, across clouds and regions, without re-architecture. Container-first, scale with control. Microservices on Kubernetes scale with demand: up for the busiest hour, down when it passes, changes ship without downtime. Failure stays bounded, and deployment goes where regulations or strategy require. Standard runtime, and the exit door stays open. Every Platform service runs as an independent containerized microservice with its own data store, on Kubernetes, Helm, Terraform, and ArgoCD: standard tooling end to end, cloud-portable by construction. What the bank gains: vendor-isolated architecture (each adapter and integration runs in its own service, blast radius bounded at the boundary); cloud portability with no re-architecture across AWS, Google Cloud, and IBM Cloud for Financial Services; independent scaling per service; zero-downtime container-level upgrades. Adaptivity has five dimensions: Runtime (Kubernetes, Docker, ArgoCD GitOps, Helm, Resilience4j), Infrastructure (Terraform, Spacelift, GitOps, GitHub), Logic (schema-based workflows, ProductVersioning, vendor-isolated adapters), Ecosystem (open adapters for KYC, payments, fraud, AML/sanctions, ledger, credit risk), Operations (CRM, case management, ticketing, BI preserved). Operational resilience is structural, not a runbook bolted on afterward: deterministic infrastructure recovery from Git rebuilds environment and delivery state from version control in hours (evidence aligned to US interagency operational-resilience guidance and FFIEC continuity expectations); vendor-isolated architecture contains DORA concentration risk at the integration boundary; progressive, reversible canary releases support PRA/FCA impact tolerances. SOC 2 Type II attested. ISO/IEC 27001:2022 certified. The full mechanism-to-regime mapping lives on the Trust page. ## Retail & SMB Banking — Adaptive Digital Banking (ADB) URL: https://xyb.co/solutions/retail-smb-banking/adaptive-digital-banking Adaptive Digital Banking (ADB) is the future-proofed retail and SMB banking solution built on the AFI Platform: four Capabilities — Hold, Move, Lend, and Grow — orchestrated on one event-native substrate. Modernizing or Greenfield, Pick & Compose or Full Stack: financial institutions launch and change propositions in weeks, on their own release calendar. Adaptive Digital Banking (ADB) is XYB's Solution for retail and SMB digital banking on the AFI Platform. Digital banking your customers expect: adapt in weeks, out from under the vendor queue, without replacing what runs your bank. Two situational paths: Modernizing (launch above the bank's existing systems, which stay operational and migrate at the bank's pace) and Greenfield (launch without legacy constraint: a standalone digital-first bank, a digital subsidiary, or a segment-specific proposition). Four Capabilities: Hold (real-time accounts and wallets, fiat and stablecoin), Move (pay, transfer, and settle across every rail, including USDC and USDT), Lend (credit for retail and SMB customers, managed end-to-end), Grow (interest-bearing deposits). Onboarding, KYC, and White-Label Experience are horizontal to the AFI Platform, never a separate purchase. Two Starting Points: Pick & Compose (two or three Capabilities as one Solution) or Full Stack Digital Banking (all four from day one, available on either path). First production value in 10 weeks whatever the Starting Point; expansion runs on the same integration model, with no second integration. ## Retail & SMB Banking — Modernizing (the overlay path into ADB) URL: https://xyb.co/solutions/retail-smb-banking/modernizing Modernizing is the Adaptive Digital Banking path for financial institutions with an existing core: ADB deploys as an overlay, reading and writing through governed events while the systems of record keep running. Launch the digital proposition customers expect in weeks, and retire legacy on your own timeline, not the vendor's. Modernizing is one of the two situational paths into Adaptive Digital Banking, for institutions that already have a bank and need a better digital proposition. Overlay deployment, first Capability live in 10 weeks, no replacement or transformation program, and the customer relationship stays with the institution under its own brand. Who it fits: a digital proposition gap the current stack can't ship; a core with years left in it and no board case for replacement; a vendor queue the institution doesn't control, where change requests run to quarters and six figures; a brand that must stay in front of the customer. Tier 1, 2, and 3 institutions fit this path, as do digital-first banks built five to ten years ago whose first-generation stack is now the legacy. How it works, in three steps. (1) Wrap, don't replace: connect the systems of record to the event-native substrate; they keep running while the substrate reads and writes through governed events. (2) Compose new capability: launch modern onboarding, channels, and products above the old core while the back office stays put. (3) Retire on your timeline: migrate functions off legacy as confidence builds, each move incremental and reversible. Most Modernizing buyers start with a single Capability, which is Pick & Compose in action: one Capability live in 10 weeks with the rest ready in the Platform. Start with Hold (modern accounts and wallets above the existing ledger), Move (instant and stablecoin rails the current stack can't reach), Lend (digital credit origination and servicing above existing books), or Grow (term and demand deposits in weeks). Expansion runs on the same integration model, so the second Capability never pays the integration tax twice. The alternative to Modernizing is not standing still; it is another point vendor per gap, each with its own contract, integration, and failure mode. Modernizing replaces that fragmented vendor stack with one Solution: one integration plumbed once and inherited by every Capability, one governance model across everything launched above the core, and one roadmap on the institution's calendar. Proof: 10 weeks to first Capability in production, zero migration required at launch, incremental and reversible steps, and one event log across old and new. ## Retail & SMB Banking — Greenfield (the launch-complete path into ADB) URL: https://xyb.co/solutions/retail-smb-banking/greenfield Greenfield is the Adaptive Digital Banking path for launching without legacy constraint: all four Capabilities — Hold, Move, Lend, and Grow — live and integrated as one Solution from day one, with nothing incumbent to integrate against. A standalone digital-first bank, a digital subsidiary, or a segment proposition, launched complete on the AFI Platform. Greenfield is one of the two situational paths into Adaptive Digital Banking, for launches with nothing incumbent to integrate against. Full Stack Digital Banking with first production value in 10 weeks: one platform, one XYB Console, one regulatory posture. Who it fits: a larger institution launching a new digital sub-brand the incumbent stack won't host; a banking-license holder building the proposition the license was for; entry into a new market or customer segment that needs its own stack, brand, and speed; a digital-first bank whose first-generation build is now the constraint. How it works, in three phases. (1) Foundation: the AFI Platform stands up complete, with accounts, ledger, and rails on one event-native substrate, integrated once and inherited forever. (2) Channels: branded web and mobile go live, covering onboarding, servicing, and payments under the institution's brand. (3) Propositions: compose and launch products on the institution's calendar, each new proposition inheriting the substrate as-is. What's included: Channels (web and mobile experiences, onboarding and servicing journeys, configured to the brand without a build cycle); Capabilities (Hold, Move, Lend, and Grow all live from day one: accounts and wallets, payments across fiat, instant, and stablecoin rails, credit end-to-end, interest-bearing deposits); Substrate (one event log, consistent policy and audit trail, cloud-portable runtime, with no separate procurement or integration project). The alternative to Greenfield on one platform is assembling it from a ledger vendor, a KYC vendor, a payments processor, and a card issuer, each with its own contract, timeline, and failure mode, with the institution owning the seams. Greenfield means inheriting a stack instead: one integration surface so engineers build proposition rather than plumbing, one governance model consistent from the first customer, and one accountable partner. Proof: 10 weeks to first production value, full stack including channels, ledger, and rails, no legacy to integrate or migrate, and zero-downtime upgrades. ## Commercial Banking — Commercial Treasury Solution (CTS) URL: https://xyb.co/solutions/commercial-banking/commercial-treasury-solution Commercial Treasury Solution (CTS) is the future-proofed treasury offering financial institutions ship to their commercial customers, built on the AFI Platform: multi-rail orchestration, unified real-time visibility into the asset position across fiat and stablecoin, and bank-grade governance. See, Move, Govern, and Reconcile on one substrate, so treasurers adapt in weeks, on the bank's terms. Commercial Treasury Solution (CTS) is XYB's Solution for commercial banking treasury on the AFI Platform. Own the treasury offering your customers need: fiat, instant, and stablecoin treasury for your commercial customers, under your terms. Four Capabilities render into the treasurer's day: See (the full asset position across every account, every rail and every currency type, in real time; Asset Visibility, Account Aggregation, FX Engine), Move (payments across every rail with unified initiation and intelligent routing; Real-Time Payments, Multi-Rail Routing, Stablecoin Treasury, FX Engine), Govern (who can do what, at what threshold, under what audit trail; Risk Engine, Sanctions, Audit, Policy Engine), Reconcile (match what happened to what should have happened, export audit-ready evidence; Reconciliation Engine, Ledger, Audit Trail). Multi-rail orchestration: the right rail for every payment. One interface spans ACH, Wire, RTP, FedNow, SEPA, SEPA Instant and stablecoin, with the optimal rail selected per payment by speed, cost, corridor, and compliance posture. Stablecoin is a rail on the same substrate, not a separate project: same controls, same audit trail, same ledger as fiat. The multi-currency ledger treats stablecoin as a currency class at the architecture level; the rails activate on the bank's decision; records, redemption and sanctions posture are aligned to the GENIUS Act regime from day one. Two interfaces, one substrate: the XYB Console for the bank's teams (product configuration, limits and thresholds, customer administration, evidence export) and the Commercial Customer Portal for the treasurer, under the bank's brand (balances, payments, approvals, reconciliation). Why the alternatives fall short: core vendors run multi-year roadmaps and treat stablecoin as a bolt-on; fintech treasury platforms take the customer relationship out of the bank; cloud-native cores are core-replacement scope, not an overlay; stablecoin specialists deliver one rail, not a treasury offering; an internal build runs $5M–$15M and 18–24 months plus permanent maintenance. CTS delivers every rail, fiat and stablecoin as first-class currency types, under the bank's brand, in weeks. Regulatory deadlines for US Tier 2 and Tier 3 regional banks. Nacha Phase 2 — In force since 19 June 2026: expanded credit-monitoring rules across the ACH network, with mandatory real-time fraud monitoring. California DFAL — In force since 1 July 2026: five-year immutable transaction records for digital financial asset activity in-state. GENIUS Act — Effective 18 January 2027: 1:1 HQLA backing, monthly attestations, 24/7 redemption, and real-time sanctions for stablecoin issuance. One event-native substrate answers all three: immutable records, real-time monitoring, audit-ready evidence by construction. Proof: ACH, Wire, RTP, FedNow, SEPA and SEPA Instant on one interface; GENIUS Act-aligned stablecoin rails on one ledger; weeks to add a rail, corridor or currency; live controls and evidence on every payment event. Adoption journey: CTS starts with Faster Payables and runs the canonical arc. Deploy it with the first commercial customers, integrated once against the canonical model. Expand to a broader commercial base and bring the remaining Features online (Real-Time Asset Position, Stablecoin Treasury, Multi-Rail Routing, Risk Engine) on the integration already in place. Modernize on the institution's own timeline: legacy commercial banking portals become optional, and the roadmap belongs to the institution. ## Partnerships — who stands behind the AFI Platform URL: https://xyb.co/ecosystem/partnerships Three partners: an alliance, a product integration, and a procurement channel. IBM is a strategic alliance: the AFI Platform deploys on IBM Cloud for Financial Services for institutions whose regulatory or strategic mandates require it, and the two companies work together in regulated financial services. Bud Financial is a product partner: Bud's transaction-intelligence layer runs on the AFI Platform's live data, for institutions building data-driven banking propositions. AWS Marketplace is a procurement channel: the agreement is signed and the listing is in progress, so institutions will procure against existing AWS commitments once it is live. What partnership means in a deal. Deployment: where the alliance carries infrastructure, the AFI Platform deploys on the partner's cloud. Capability: where the partner extends the Platform, the integration is live in the product. Procurement: directly from XYB, or through partner channels where an alliance carries the deployment; AWS Marketplace procurement follows once the listing is live. ## Integrations — the vendors the AFI Platform connects URL: https://xyb.co/ecosystem/integrations The AFI Platform integrates best-of-breed partners and equivalents across the open adapters, so an institution keeps the vendors it has and adds the ones it chooses next without a second integration. ## Trust — compliance as substrate URL: https://xyb.co/trust Trust at XYB is a property of the substrate, not a compliance program beside it: audit evidence is generated by the platform's normal operation, not assembled for the exam. SOC 2 Type II attested, ISO/IEC 27001:2022 certified, built to support DORA compliance. Live control status your risk teams verify on demand. Built for the regulations live today, aligned to the regulations coming next. SOC 2 Type II attested. ISO/IEC 27001:2022 certified. Built to support DORA compliance. Real-time compliance evidence available on demand. The operational evidence surface is the XYB Trust Center at https://trust.xyb.co. Regulatory mapping. Architecture support, not a compliance determination: deterministic Git-based recovery supports US interagency operational-resilience and FFIEC continuity expectations; the vendor-isolated adapter pattern supports DORA concentration-risk isolation at the integration boundary; canary release verified in flight supports PRA/FCA impact tolerances for important business services; GitOps change control supports auditable, versioned change management for every environment; independent control attestation supports SOC 2 Type II (Security) evidence and ISO/IEC 27001:2022 certification. ## About XYB — beliefs and team URL: https://xyb.co/company/about XYB is the Adaptive Financial Infrastructure company. It created the AFI category and the banking orchestrator that delivers it, partnering with financial institutions to build infrastructure that adapts with them, on their terms and at their pace. Our beliefs. Mission: to partner with financial institutions to build adaptive infrastructure that empowers them to innovate, comply, and evolve, on their terms and at their pace. Vision: financial institutions build their future on infrastructure that adapts with them. Five values: partners, not vendors (invested in the institution's growth, not a product sale); pragmatic innovation (solving real problems, balancing new technology with what is proven in production); adaptive by default (infrastructure designed to evolve with constant regulatory and market change); control and composability (modular and transparent, never locked in, the institution chooses what to adopt and when); transparent by design (clear communication, honest metrics, visible decision-making). The team. Leadership: Derek Joyce, Co-Founder and CEO: over 20 years across fintech, previously COO at Alloy and President of Bread, with earlier roles at Klarna and American Express. Jonas Kiiver, Co-Founder and CTO: leads the composable, event-native architecture, previously CTO at Monese where he built the technical foundation that became XYB. Melissa Donohue, Chief Product and Operating Officer: product strategy, operations and go-to-market, previously across Miro, Clyde, and Klarna. Contact: Eagle House, 163 City Road, London, EC1V 1NR. Reach the team through the form at https://xyb.co/talk-to-us. ## AFI Concepts — the AFI glossary URL: https://xyb.co/resources/concepts The vocabulary of Adaptive Financial Infrastructure: AFI is the category; Banking Orchestration is the mechanism; the AFI Platform is the delivery. See the page for the full A–Z glossary. ## Adoption Journey — Deploy, Expand, Modernize URL: https://xyb.co/resources/adoption-journey The Adoption Journey runs Deploy → Expand → Modernize. A visible win at each move, and value compounds because the institution's systems are integrated once and every workload that follows reuses that integration. What each move produces is a proposition: something the institution's customers can use, that the institution owns. Deploy: land one workload. Three ways in. Each system is integrated once, into the canonical model, and every workload that follows reads the model rather than the system. The door chosen first does not limit the doors that follow. A starting ADB Capability (Hold, Move, Lend or Grow) live above the existing core; the Commercial Treasury Solution acquired as a working whole, starting with Faster Payables; or the AFI Platform itself, where the institution needs to own the substrate and run its own domains on top. Every door lands on the same substrate, against the same canonical model. Outcome: the first proposition live, first production value in 10 weeks, no migration, the existing systems preserved. Expand: reuse what you integrated. The second workload costs a fraction of the first because the integration is already done. Through a Solution, add Features, Capabilities, customer segments and regions; through the AFI Platform, add Solutions and domains onto the substrate already running. Neither path pays a second integration tax. Outcome: new propositions come online faster than the first; scope grows and integration cost does not. Modernize: own the proposition roadmap. Move more of the stack onto the substrate and retire legacy segment vendors at the institution's own pace. Legacy does not become obsolete overnight, it becomes optional. Outcome: the proposition roadmap belongs to the institution, not to the constraints of the stack beneath it. What every move shares: first production value in 10 weeks; one integration per system into the canonical model, which every workload after reads; zero repeats after the first deployment; no replacement program required. ## Insights — essays and analysis from the team URL: https://xyb.co/insights Insights from XYB, organized by what the buyer is investigating: Company, AFI Category, AFI Platform, Adaptive Digital Banking, Commercial Treasury, and Security & Compliance. The launch set published on 2026-08-17; the Company pillar opened on 2026-08-20. ## Jim Logan Joins XYB — Americas Head of Strategic Sales URL: https://xyb.co/insights/jim-logan-joins-xyb Jim Logan has been appointed Americas Head of Strategic Sales at XYB, leading North American go-to-market for the Adaptive Financial Infrastructure (AFI) Platform and its Solutions. He is based in New Jersey and reports to Derek Joyce, CEO and Co-Founder of XYB. Background: more than 30 years across commercial banking, payments, compliance, and trade, including seventeen years at JPMorgan and four at Deutsche Bank, then building and scaling Americas businesses for financial technology firms. Previously Head of Americas Sales and Global Revenue Management at Saphyre (capital markets, KYC and pre/post-trade data orchestration); SVP, Americas Head of Business at Pelican.ai; Americas Head of Business at SunTec Global Business Solutions. Industry advisory boards include Commercial Payments International and the BAFT Payments and Trade Committee, where he contributed to ISO 20022 migration and trade digitalization. The focus is North American regional and super-regional banks under pressure to compete on product velocity and customer experience while still running core systems built for a different set of demands. The AFI Platform closes that gap with a 10-week time to value, then progressive modernization of the underlying infrastructure, rather than a single multi-year transformation program. Published 2026-08-20. ## What is Adaptive Financial Infrastructure? — the AFI category, defined URL: https://xyb.co/insights/what-is-adaptive-financial-infrastructure Adaptive Financial Infrastructure (AFI) is the new category for banking orchestration, unifying systems, people, and processes. Context aware, operationally resilient. The AFI Platform is the event-native substrate that delivers it, where every action carries full context. It absorbs agentic AI, real-time payments, and decentralized finance, so banks adapt in weeks without replacing what already runs. Three forces demand it now, converging on the same clock: agentic AI, which cannot reason on fragmented data; real-time payment mandates (RTP and FedNow at $10M, Nacha Same Day ACH, SEPA Instant, RT2, ISO 20022), which cannot execute on batch reconciliation; and decentralized finance (GENIUS Act, California DFAL), which cannot be retrofitted onto a multi-day settlement cycle. AFI unifies the adjacent software categories banking depends on most: Data Platforms for AI, Real-Time Payments, Decentralized Finance, Real-Time Data Streaming, Digital Banking, Treasury, and Business Process Orchestration. It does not compete inside them; it unifies their work from above. The four moves against a fragmented estate: keep patching, which works per tool and never in aggregate; replace the core, which changes everything at once and defers the first win by years; wrap the estate, which moves fast at the surface and stalls underneath; or orchestrate what runs, deploying the orchestration substrate above the estate so the systems stay and the fragmentation goes. The fourth move is Adaptive Financial Infrastructure. Four regulatory and market-infrastructure pressures arrive at once and demand the same four things: AI governance, real-time payments, regulated digital assets, and operational resilience all require real-time monitoring, traceability, operational resilience, and scalable controls. Published 2026-08-17 and substantially rewritten 2026-08-24, authored by Germán Zurro, VP Marketing. ## What US Mid-Market Treasury Teams Are Actually Asking For — six 2026 demands URL: https://xyb.co/insights/what-us-mid-market-treasury-teams-want US mid-market treasury teams want a single real-time asset position (cash, regulated stablecoins, supervised crypto), every payment rail behind one instruction surface (ACH, RTP, FedNow, wire, GENIUS Act stablecoins), programmable API-first integration into ERPs and TMSs (NetSuite, SAP, Kyriba, Trovata), inline compliance for Nacha Phase 2 / OFAC / DFAL / GENIUS Act, and forecasting fed by event-native data. Crisil Coalition Greenwich reported in 2025 that one-third of US middle-market companies were thinking about switching banks, and its 2026 outlook adds the stakes: lead banks capture the large majority of a client's business. Deloitte's 2024 Global Corporate Treasury Survey puts visibility into cash and financial risk exposures at the top challenge for treasury executives. Published 2026-08-17, authored by Dmitri Bogatenkov, VP Engineering. ## Security at the Infrastructure Level — SOC 2 Type II and ISO 27001 in the substrate URL: https://xyb.co/insights/security-at-the-infrastructure-level Banking infrastructure security in 2026 is decided at the substrate, not the perimeter. The AFI Platform is SOC 2 Type II attested and ISO/IEC 27001:2022 certified. SOC 2 Type II attests that controls operated effectively over the examination period; ISO/IEC 27001:2022 certifies the management system that keeps them current. Together they are the two independent examinations that anchor vendor diligence in banking, so a financial institution's security review starts from an attestation report and a certificate rather than a questionnaire. The AFI Platform runs single-tenant per-account isolation on AWS or GCP with event-native auditability via Apache Kafka and Apache Iceberg. Procurement should ask four substrate questions: is tenant isolation structural, is auditability event-native, is control evidence continuous, and which financial institutions have signed after their own third-party risk review? Published 2026-08-17 and updated 2026-10-07, authored by Tarmo Suurmägi, CISO. ## XYB partners with Bud Financial to bring AI-driven intelligence to financial institutions URL: https://xyb.co/insights/xyb-partners-with-bud-financial-to-bring-ai-driven-intelligence-to-financial-institutions XYB, the Adaptive Financial Infrastructure company, announced a strategic partnership with Bud Financial, a provider of AI-powered data intelligence for financial services. The partnership connects the AFI Platform with Bud's data enrichment engine, so financial institutions can turn raw customer data into insights and act on them in real time. At announcement the two companies were already working together on projects with banks in the US and Europe. The AFI Platform unifies systems, people, and processes on one event-native substrate; Bud turns transactional data into AI-ready signals that plug into the platform through its open adapters. Together they give financial institutions one pathway to embed AI-powered decisioning in core workflows without lengthy integration cycles. Quoted: Derek Joyce, CEO of XYB, and Edward Maslaveckas, CEO at Bud. A press release from the previous site, republished with XYB's own wording updated to current positioning and both quotes unchanged. The partnership is active: Bud Financial is a product partner, listed at https://xyb.co/ecosystem/partnerships. Published 2025-06-02 and updated 2026-10-05, by XYB. ## The next era of finance needs a new foundation URL: https://xyb.co/insights/the-next-era-of-finance-needs-a-new-foundation Banks have answered fragmentation three ways: keep patching, replace the core, or wrap the estate in cloud and APIs. The essay argues the blocker is architecture, not capability. Capgemini's 2026 research found 43% of corporate and investment bank IT budgets go to running legacy systems, and in a conventional estate every product ships its own back office, so the compliance surface grows with the product count. On AI: 80% of financial services firms were at ideation or pilot stage with AI agents and 10% had deployed them at scale (Capgemini, 2026). The institutions that have scaled agents, including BNY, BNP Paribas and HSBC, each built their own orchestration and control layer first, with agents acting on shared state under one audit trail and a human decision in front of the money. On compliance: the first DORA incident report counted 3,383 major ICT incidents in the EU in 2025, mostly system failures and external events, and Swift ended cross-border MT coexistence for ISO 20022 on 22 November 2025. The fourth move is Adaptive Financial Infrastructure: deploy a substrate above what already runs. AFI names that move, and Banking Orchestration is what it delivers. On the AFI Platform, systems integrate once to a canonical model behind adapter contracts, operations govern once with workflow, policy, approval and audit as platform objects, and every action that changes money or account state receives one typed verdict. AI agents are capabilities like any other, arriving governed. Adoption follows Deploy, Expand, Modernize, with first production value in ten weeks. Published 2025-05-28 and updated 2026-10-06, authored by Melissa Donohue, Chief Product and Operating Officer. ## The Merger Tax Nobody Models — bank integration debt URL: https://xyb.co/insights/the-merger-tax-nobody-models Bank merger models price the synergies and underprice the conversion. Integration debt — the accumulated cost of architecture decisions made on the assumption of never absorbing another institution — comes due in a lump, on a date set by a deal. Five completed U.S. conversions show how the conversion bill grows after it is announced. Thirty-five years of watching the rest shows where the other synergy leaks are: attrition at cutover, frozen roadmaps, talent drain. There is a different shape: coexistence, run from a real-time layer above the core. The synergy leaks in four places: direct conversion costs, attrition at cutover, roadmap freeze, and talent drain. U.S. Bancorp announced the Union Bank acquisition with one-time pre-tax merger charges of $1.2 billion; fourteen months later the estimate had become approximately $1.4 billion, and the charges the bank ultimately reported total roughly $1.5 billion. Across the five deals (Huntington and TCF, M&T and People's United, U.S. Bancorp and Union Bank, Columbia and Umpqua, BMO and Bank of the West), announcement to conversion ran from ten months to twenty-one, and the roadmap stops on announcement day, not on conversion day. If product definition, customer data, and experience logic sit in a real-time layer above the core rather than inside it, absorption stops being a conversion and becomes a coexistence problem. You run both cores. You connect both to a common product and experience layer. Customers see one bank on day one. You migrate the book on a timeline you control, product by product and segment by segment, and you retire the acquired core when it is economically sensible. Five questions to ask before you sign: How much of the announced synergy depends on decommissioning a core? What is our roadmap opportunity cost over the integration window? Could we operate both estates for twenty-four months if we chose to? Which core are we converting onto, and is it the one we intend to be on in five years? Who owns conversion weekend? Published 2026-10-07, authored by Jim Logan, Americas Head of Strategic Sales, XYB. ## Careers — open roles at XYB URL: https://xyb.co/company/careers XYB is hiring for the Adaptive Financial Infrastructure company behind the AFI Platform. Open roles are listed at https://xyb.co/company/careers, each with its own page; applications are made on the careers site at https://careers.xyb.co, which also hosts the talent pool for when no current role fits. The roles shown are read from the recruitment site's live feed rather than maintained by hand, so the list reflects what is genuinely open at the time of the request. The page carries the canonical About XYB text, the same wording used in every job description: XYB is the company creating Adaptive Financial Infrastructure (AFI), the new category for banking orchestration, unifying systems, people, and processes. Context aware, operationally resilient. The AFI Platform, the banking orchestrator, is the event-native substrate enabling financial institutions to modernize and launch new digital propositions, adapting in weeks, not years. ## Talk to us URL: https://xyb.co/talk-to-us Reach the XYB team at https://xyb.co/talk-to-us. This is the single conversion route for the site; every CTA lands here. Five ways in, named for the contact form's own options: Book a Demo (a walkthrough of the Platform and Solutions against your stack), Technical Deep Dive (architecture, integration, and the canonical model, including where to start: above an existing core, greenfield, or one workload at a time), Speak to Sales (commercials, scope, and what a first deployment looks like), Partnership Enquiry (alliance, co-sell, or delivery), and General Enquiry (an open question about a segment, a rail, a regulatory deadline, or a migration). Separately, CTAs across the site carry the intent they were clicked with as a URL parameter: intent=demo, intent=conversation, intent=partnership, intent=adoption-mapping, with the two segment conversations adding team=commercial-banking or team=retail-smb. The page echoes a recognised value back in its heading and falls back to its default heading otherwise. ## Glossary - Adaptive Financial Infrastructure (AFI): Banking orchestration, unifying systems, people, and processes, context aware, operationally resilient. - Banking Orchestration: The defining mechanism of AFI: unifying systems, people, and processes on one event-native substrate. The AFI Platform is what delivers it. - AFI Platform: The banking orchestrator unifying context. - Adaptive Digital Banking (ADB): The future-proofed solution for retail and SMB, built on the AFI Platform. - Commercial Treasury Solution (CTS): The future-proofed offering for your customers, built on the AFI Platform. - Experience Layer: The branded consumer- and operator-facing layer of the AFI Platform. - Orchestration Layer: The event-native layer of the AFI Platform, where banking orchestration happens: the Apache Kafka event backbone, with Apache Iceberg unifying real-time and historical data. - Runtime Layer: The container-first deployment base of the AFI Platform. - Capability: The functional unit of an XYB Solution, named in the language of banking rather than software: Hold, Move, Lend, Grow in Adaptive Digital Banking; See, Move, Govern, Reconcile in Commercial Treasury Solution. - Canonical Model: The single data model every system integrates into, once: Customer, Account, Beneficiary, Transaction, Balance. Workloads read and write through the model rather than point-to-point against systems, so adding a workload never means re-integrating a system. - Integration Tax: The recurring cost of point-to-point integration: every new workload wiring to every system it touches, so effort grows with workload count times system count. On the canonical model the tax is paid once per system; workloads consume the model, and the tax does not repeat. - XYB: The Adaptive Financial Infrastructure company.