DFlow is a Solana-native decentralized exchange (DEX) aggregation and routing infrastructure focused on low-latency best-execution for swaps across multiple liquidity venues. The project exposes routing and swap APIs for wallets, trading desks, and decentralized applications, and incorporates mechanisms to segment and mitigate “toxic” order flow with the stated aim of protecting liquidity provider (LP) yields. ^[1]

On May 5, 2026, stated that MoonPay agreed to acquire DFlow in an all‑stock transaction valued at approximately $100 million. ^[6].

Overview

DFlow is positioned as an execution infrastructure layer for Solana that synthesizes price and liquidity information from heterogeneous on‑chain venues to discover and route orders to the best available prices at low latency. In public materials, it is described both as a DEX aggregator and as an infrastructure provider that can help venues and LPs identify and segment toxic order flow to reduce adverse selection.

For integrators, DFlow provides a Swap API intended for wallets, trading desks, and DeFi applications seeking high-throughput execution and precise, route-aware pricing on Solana ^[1].

Earlier interviews further characterize DFlow as a decentralized marketplace for payment‑for‑order‑flow (PFOF) in crypto. In that model, order flow is matched with market-maker liquidity under oracle-enforced price fairness rules, with an NBBO‑like (National Best Bid and Offer) constraint adapted for on-chain markets.

This marketplace framing emphasizes transparent monetization of order flow by wallets and applications while guarding execution quality through oracle pricing. Although distinct in emphasis from the DEX-aggregation description, both perspectives place DFlow at the execution layer—either as an aggregator/router across Solana liquidity or as a marketplace where order flow is bought and sold under best‑execution constraints ^{[2] [1]}.

MoonPay Acquires DFlow

On May 5, 2026, it was reported that MoonPay agreed to acquire DFlow in an all‑stock transaction valued at approximately $100 million. ^{[2] [1]}.

With this latest acquisition, MoonPay is seeking to bolster its offerings for traders on Solana, which is known for its fast execution and low trading fees.

DFlow raised $2 million in seed funding led by Multicoin and Framework Ventures in 2022 and drew another $5.5 million in a round led by Framework in 2023. ^[5]

“We’ve been building MoonPay around four pillars: fund, tokenize, trade, and spend,” - MoonPay co-founder and CEO Ivan Soto-Wright told Fortune. MoonPay’s existing crypto ramp business, Iron, and Helio account for funding, tokenizing, and spending, and DFlow will add trading to the mix, he added. ^[6]

Technology and Architecture

Liquidity aggregation across heterogeneous venues

DFlow aggregates liquidity from multiple types of Solana-based markets, enabling a unified execution surface that can consider both automated market maker (AMM) pools and order-book venues. The set of sources described includes:

• Constant‑product AMMs
• Concentrated liquidity AMMs (CLMMs)
• Dynamic/liquidity‑managed AMMs (DLMMs)
• Proprietary AMM designs
• Central limit order books (CLOBs)

By spanning different market microstructures, DFlow’s router can compose routes that cross venue types, potentially accessing deeper liquidity and better composite prices than any single venue. This cross‑venue approach underpins the aggregator’s best‑price discovery and enables execution strategies that adapt to liquidity and price dispersion across Solana’s on‑chain markets ^[1].

Execution primitives: atomic swaps and JIT‑adaptive routing

Two execution primitives feature prominently in DFlow’s descriptions:

• Atomic swaps: Cross‑source paths are executed atomically on-chain, such that the overall transaction either completes in full at the calculated route or fails, avoiding partial fills that could expose traders to price risk during multi‑venue execution.
• JIT-adaptive routing: The router adapts route selection at execution time. This just‑in‑time (JIT) adaptation is intended to minimize slippage and mitigate the impact of ephemeral liquidity or price movements that occur between route discovery and on‑chain submission.

Together, these mechanisms are presented as a way to reduce the gap between quoted and realized execution, particularly in fast-moving markets where liquidity is fragmented or transient. The combination of atomicity and last‑moment route adjustments aligns with the broader design goal of precise, low‑latency execution for Solana swaps ^[1].

Toxic‑order‑flow identification and segmentation

DFlow’s order‑flow tooling includes identification and segmentation features designed to detect and handle “toxic” flow—order flow associated with harmful trading patterns (e.g., sandwich attacks, latency arbitrage) that can degrade LP performance.

Public materials suggest that segmentation can be used to adjust fee structures or routing decisions so that LPs and DEXs can mitigate adverse selection while still serving broader user flow. These capabilities are framed as protective for liquidity providers and as complementary to best‑execution routing for end users ^[1].

Oracle‑enforced fairness and NBBO‑like rules (marketplace model)

In addition to aggregator/routing infrastructure, DFlow has been described as a decentralized marketplace for PFOF, where wallets and applications can monetize order flow by directing it to market makers under explicitly coded execution rules. In this framing:

• Oracle‑enforced pricing: DFlow integrates decentralized price oracles—specifically, Pyth price feeds are cited in interviews—to enforce fairness constraints. Market makers are required programmatically to fill orders at or better than oracle‑reported prices.
• NBBO‑like mechanism: The enforcement mimics the spirit of NBBO rules in equities by ensuring fills are executed at or better than a fair reference, adapted to on‑chain venues via decentralized oracles.

This model aims to reconcile monetization of order flow with execution quality guarantees, relying on oracle data as a policy anchor. While conceptually distinct from multi‑venue aggregation, both designs seek best execution: one via cross‑venue routing, the other via rule‑enforced pricing in a marketplace where liquidity providers compete for order flow ^[2].

Performance characteristics and claims

DFlow is characterized in listings as a low‑latency, high‑throughput system. Specific latency or throughput metrics are not provided in the publicly cited materials, and no benchmarks or audits are described in those same sources. As such, performance characterizations should be interpreted as product claims rather than independently verified measures. The emphasis on real‑time data synthesis and JIT routing indicates a design focus on minimizing the delay and slippage between quote formation and on‑chain execution ^[1].

Products and Services

Swap and routing APIs

DFlow exposes a Swap API and related integration interfaces for third parties. These APIs allow wallets, trading desks, and DeFi applications to:

• Request best‑price routes across eligible Solana venues
• Submit atomic swap transactions
• Configure routing parameters to balance slippage tolerance, venue preferences, or other constraints unique to a given integrator

The public descriptions present the API suite as modular infrastructure rather than a single, end‑user application, positioning DFlow as an execution backbone that partners can embed within their own user experiences ^[1].

Order‑flow segmentation tools for LPs and DEXs

On the supply side of liquidity, DFlow advertises order‑flow segmentation and toxic‑flow mitigation features. DEXs and LPs can purportedly use these tools to:

• Identify patterns associated with adverse selection
• Segment flow and adjust fee or routing policies accordingly
• Preserve overall LP yields by reducing exposure to harmful trading behaviors

These tools are framed as complementary to aggregators’ best‑execution logic, aiming to improve net outcomes for liquidity providers while maintaining robust routing for traders ^[1].

DFlow‑powered exchange deployments

Interview materials refer to an early Solana exchange that adopted DFlow’s approach, with “Tsunami” identified as a DFlow‑powered deployment. While detailed metrics for that deployment are not provided in the cited interview, the reference indicates that DFlow’s mechanisms have been integrated into live Solana trading venues beyond proof‑of‑concept prototypes ^[2].

Use Cases

• Wallet integrations: Wallets embed DFlow’s Swap API to provide users with best‑price swaps across Solana venues, abstracting away path selection and multi‑venue complexity.
• Trading desks and market participants: Professional traders can leverage routing that adapts at execution time to minimize slippage, while also benefiting from the atomic completion of complex routes.
• DEXs and LPs: Venues and LPs can apply flow segmentation and toxic‑flow filters to protect yields, potentially integrating these signals into fee policies or routing preferences.
• Exchange deployments: Exchanges may build directly on DFlow’s infrastructure or marketplace mechanisms to source liquidity and enforce execution guarantees, as highlighted by references to DFlow‑powered deployments on Solana.

These use cases reflect DFlow’s dual emphasis on end‑user execution quality and LP protection, positioning the system as a neutral execution middleware for multiple classes of market participants on Solana ^{[1] [2]}.