DFlow supplies Solana spot-trading infrastructure to applications and wallet users. Its current documentation specifies no DFlow protocol fee on spot swaps, while applications can add a platform charge and transactions still incur liquidity-source and network costs. MoonPay announced its acquisition on 5 May 2026. The current spot documentation and the older legal terms describe different generations of the service, so the terms’ date matters when assessing the operator and product scope.[5][8][6]
Markets & services
Sections ↑Reference table01
Product scope
| Item | Published terms |
|---|---|
| Spot trading | Wallet-signed Solana token swaps through the Trading APISource 5Source 10Source 9Source 4 |
| Liquidity | AMMs, proprietary AMMs and order-book-style venuesSource 5Source 10Source 9Source 4 |
| Identity | Proof links verified individuals and wallet addressesSource 5Source 10Source 9Source 4 |
| Adjacent historical announcement | May 2026 acquisition release also described tokenised prediction-market infrastructureSource 5Source 10Source 9Source 4 |
Reference table02
Order workflow
Reference table03
Routing choices
| Item | Published terms |
|---|---|
| Named venue examples | Raydium, Orca, Meteora and Pump.funSource 10Source 3Source 1 |
| Venue selection | API can include or exclude particular sourcesSource 10Source 3Source 1 |
| Route constraints | Direct-only routes or a maximum number of legsSource 10Source 3Source 1 |
| JIT routing | Route may be refined during on-chain execution as venue prices changeSource 10Source 3Source 1 |
Reference table04
Quote and execution bounds
| Item | Published terms |
|---|---|
| Expected output | Quote reports output after its included feesSource 3 |
| Minimum output | Transaction fails if the configured minimum is not deliveredSource 3 |
| Slippage | Basis-point allowance; 50 bps means 0.5%Source 3 |
| Price impact | Separate size-dependent price check; API supports an override thresholdSource 3 |
Reference table05
Wallet and asset handling
| Item | Published terms |
|---|---|
| Wallet | Standard Solana transaction signing supportedSource 2 |
| Asset identity | API uses mint addresses, not ticker symbolsSource 2 |
| Native SOL | Wrapping/unwrapping is supported through the WSOL mint settingSource 2 |
| Intermediate accounts | Multi-leg swaps can leave small residual balances in token accountsSource 2 |
Fees & commercial terms
Sections ↑Reference table06
Spot cost components
| Item | Published terms |
|---|---|
| DFlow protocol | No protocol fee under current spot documentationSource 6Source 2Source 3 |
| Application | Optional platform fee selected by the integrating builderSource 6Source 2Source 3 |
| Liquidity sources | Venue fees and quoted execution priceSource 6Source 2Source 3 |
| Network/token | Solana fees, optional priority fee and applicable token-transfer feesSource 6Source 2Source 3 |
Reference table07
Platform-fee collection
| Item | Published terms |
|---|---|
| Rate | Builder chooses basis points; 100 bps equals 1%Source 6 |
| Fee asset | Output token by default; input-token collection also supportedSource 6 |
| Recipient | Builder-controlled token account for the relevant assetSource 6 |
| Unsuccessful trade | No platform fee is collectedSource 6 |
Reference table08
Priority-fee settings
| Item | Published terms |
|---|---|
| Adaptive mode | Requested priority level with a maximum lamport budgetSource 7 |
| Unspecified setting | Documentation gives an automatic cap of 0.005 SOLSource 7 |
| Exact mode | Fixed priority amount regardless of congestionSource 7 |
| Execution | Paying more can improve inclusion prospects but does not guarantee a fillSource 7 |
Reference table09
Comparing application quotes
| Item | Published terms |
|---|---|
| Same router | Different applications can choose different platform feesSource 6Source 8Source 11Source 12 |
| Net output | Compare after-fee output at the same size and slippage boundSource 6Source 8Source 11Source 12 |
| Gas sponsorship | Changes who funds transaction costsSource 6Source 8Source 11Source 12 |
| API access | Developer or commercial access is separate from the spot protocol feeSource 6Source 8Source 11Source 12 |
Deposits, withdrawals & settlement
Sections ↑Reference table10
Sponsored-swap choices
| Item | Published terms |
|---|---|
| Default sponsor execution | Input transfers to sponsor accounts, swap executes there, output returns to userSource 8 |
| User execution | Swap uses the user’s token accounts directlySource 8 |
| Cost payer | Sponsor covers transaction fees and token-account creationSource 8 |
| Authorisation | Both user and sponsor sign the transactionSource 8 |
Reference table11
Sponsorship details that affect the result
| Item | Published terms |
|---|---|
| Token transfer charges | Additional transfers can matter for Token-2022 fee-bearing assetsSource 8Source 3 |
| Quote structure | Sponsorship mode must match the transaction being builtSource 8Source 3 |
| Intermediate accounts | Optional sponsor close authority exists in user-executed modeSource 8Source 3 |
| User benefit | Holding SOL for gas may be unnecessary when sponsorship is actually availableSource 8Source 3 |
Reference table12
Settlement limits
| Item | Published terms |
|---|---|
| Spot transaction | Current documentation describes composable atomic executionSource 5Source 2Source 4 |
| Liquidity failure | An unavailable route or inadequate output can prevent executionSource 5Source 2Source 4 |
| Fiat funding | Not provided by the spot-routing API itselfSource 5Source 2Source 4 |
| Separate products | Prediction-market redemption rules cannot be inferred from ordinary spot-swap mechanicsSource 5Source 2Source 4 |
Custody & asset handling
Sections ↑Reference table13
Asset-control boundaries
| Item | Published terms |
|---|---|
| User | Authorises the transaction through a walletSource 5Source 8 |
| Router and venues | Execute the selected token exchangesSource 5Source 8 |
| Sponsor | May execute through its accounts in the documented default modeSource 5Source 8 |
| Application | Constructs the request and presents fees and signature payloadSource 5Source 8 |
The FAQ’s broad statement that funds remain in a user wallet needs to be read alongside the sponsored-swap documentation: its default mode explicitly uses sponsor token accounts during execution. The meaningful checks are the actual transaction instructions, fee recipients and final destination.[2][8]
Client eligibility & restrictions
Sections ↑Reference table14
Access conditions
| Item | Published terms |
|---|---|
| Age | Published terms require 18 or overSource 12Source 2 |
| Spot identity check | Current FAQ says spot swaps do not require DFlow KYCSource 12Source 2 |
| Legal restrictions | OFAC and other contractual representations still applySource 12Source 2 |
| App-specific requirements | Wallet, issuer and integrating-service conditions can add restrictionsSource 12Source 2 |
Reference table15
Proof verification
| Item | Published terms |
|---|---|
| Purpose | Establishes a link between an identity and one or more walletsSource 9 |
| Information | Name, address, email and government identificationSource 9 |
| Checks | Document and biometric verification; signed proof of wallet controlSource 9 |
| Spot use | Proof is not required for DFlow spot tradingSource 9 |
Reference table16
Identity and privacy
| Item | Published terms |
|---|---|
| Verification provider | FAQ identifies Stripe IdentitySource 2Source 9 |
| Proof charge | FAQ states no fee for using ProofSource 2Source 9 |
| Partner access | Applications can query linked-wallet verification statusSource 2Source 9 |
| Personal data | Identity-linked wallets have a different privacy exposure from a standalone wallet addressSource 2Source 9 |
Support & contacts
Sections ↑Reference table17
Support routes
| Item | Published terms |
|---|---|
| General/partnership enquiries | [email protected]Source 14Source 11 |
| Developer help | Community links in current documentationSource 14Source 11 |
| Production API | Application form; documentation targets a response within 2–5 daysSource 14Source 11 |
| Public testing | Keyless developer endpoints are rate-limited and unsuitable for productionSource 14Source 11 |
Authorisations & registrations
Sections ↑Reference table18
Regulatory disclosure scope
| Item | Published terms |
|---|---|
| Dated terms | May 2024 terms disclaim licensed exchange, brokerage and custody statusSource 12Source 4 |
| Acquisition | Parent-company ownership announced in May 2026Source 12Source 4 |
| Affiliate boundary | A MoonPay group permission does not by itself identify the entity serving a DFlow routeSource 12Source 4 |
| User protection | Wallet signing and protocol design do not establish deposit insurance or compensation coverSource 12Source 4 |
Operator & entity scope
Sections ↑Reference table19
Operator evidence
| Item | Published terms |
|---|---|
| Named company | DFlow Inc. in the service terms and privacy policySource 12Source 13Source 4 |
| Published legal dates | Terms: 21 May 2024; privacy: 29 August 2024Source 12Source 13Source 4 |
| Location | Privacy policy describes United States headquartersSource 12Source 13Source 4 |
| Ownership event | MoonPay acquisition announcement: 5 May 2026Source 12Source 13Source 4 |
- Operator
- DFlow Inc., named in the published terms; acquisition by MoonPay announced 5 May 2026
- Exchange model
- Decentralised
- Service scope
- Solana spot-swapping and execution infrastructure, with developer APIs and the separate Proof identity service. Current spot documentation is the basis of this profile; the acquisition announcement also described prediction-market infrastructure.
- Client types
- Retail clients; Professional clients; Institutional clients
- Pricing publication
- Public and quoted pricing
- Other names
- DFlow aggregator; DFlow Trading API
- Headquarters
- United States in the privacy policy effective 29 August 2024
- Covered jurisdictions
- Solana spot services; legal and integrator restrictions apply
- Pricing scope
- No DFlow protocol fee on spot swaps. Builders may set platform fees in basis points; network, priority, venue and token-transfer charges can apply. API commercial terms are separate.
- Funding scope
- Supported Solana token balances fund swaps. Users or sponsors pay network and token-account costs; no DFlow bank deposit or cash-withdrawal account is described.
- Custody and asset handling
- Wallet-authorised transactions use external liquidity venues. Sponsored execution may temporarily route input/output through sponsor token accounts within the transaction; user-executed sponsorship avoids those transfers. DFlow describes its spot service as noncustodial.
- Client eligibility
- Published terms require age 18 and compliance with applicable restrictions, including OFAC provisions. Current spot documentation says DFlow-level KYC is not required; an integrating application may impose additional checks.
- Support
- [email protected] for general and partnership questions; current documentation links developer community channels and production API-key applications.
- Authorisation and registration scope
- The May 2024 terms describe an administrative software platform and disclaim exchange, broker and custody licensing. This dated disclosure does not establish the scope of any MoonPay affiliate’s current permissions.
Exchange metadata checked 27 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 7Source 8Source 9Source 10Source 11Source 12Source 13Source 14
Covered contracting entities
DFlow Inc.
- Jurisdiction
- United States headquarters; incorporation jurisdiction unspecified
- Covered services
- Company named in the published May 2024 service terms; MoonPay acquisition announced in May 2026
- Client and location scope
- Age, sanctions, legal and applicable supplementary terms apply.
Additional Information
Sections ↑The current developer documentation concentrates on spot trading and Proof. Older order-flow descriptions and the May acquisition’s prediction-market claims are dated context. Eligibility, token backing and redemption for any separate event-market product require its own current disclosures.[5][12][4]
Sources & further reading
- DFlow routing mechanics and self-reported operating scale DFlow · Accessed 27 Oct 2026
- DFlow current spot, fee and Proof FAQs DFlow · Accessed 27 Oct 2026
- Get Quote API: slippage and optional integrator fees DFlow · Accessed 27 Oct 2026
- 5 May 2026 acquisition announcement DFlow/MoonPay · Accessed 27 Oct 2026
- DFlow current spot-trading workflow DFlow · Accessed 27 Oct 2026
- DFlow protocol and integration platform fees DFlow · Accessed 27 Oct 2026
- DFlow priority-fee modes and default cap DFlow · Accessed 27 Oct 2026
- DFlow sponsored swaps: sponsor and user execution DFlow · Accessed 27 Oct 2026
- DFlow Proof identity verification and wallet links DFlow · Accessed 27 Oct 2026
- DFlow liquidity venues DFlow · Accessed 27 Oct 2026
- DFlow production API-key access DFlow · Accessed 27 Oct 2026
- DFlow terms, last updated 21 May 2024 DFlow · Accessed 27 Oct 2026
- DFlow privacy policy, effective 29 August 2024 DFlow · Accessed 27 Oct 2026
- DFlow official contact channels DFlow · Accessed 27 Oct 2026
This profile reports dated public information, including exchange-published services and terms. It does not independently test or guarantee trading, custody, pricing or withdrawals. Inclusion is not an endorsement. Permissions and protections apply only to the named legal entity, service and client category; check the current official records and your contract.