Finix vs Mangopay
usage-based
·usage-based
Mangopay wins · 8–16 (22 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round drawnFinix has a confirmed llms.txt endpoint returning HTTP 200 with a description of the docs, plus documented agent-oriented resources including an official MCP server for AI agents to query the API. This directly satisfies the story of pointing an agent at llms.txt or agent-oriented docs. Missing for 10: independent/community corroboration of actual agent usage against llms.txt or MCP server in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.finix.com/llms.txt # Finix Docs > Explore our documentation, guides, and APIs to start building yo…”
- [probe] “official MCP server documented at https://docs.finix.com/additional-resources/developers/mcp-server”
- [claimed-docs] “Ask an AI agent questions about the Finix API to get accurate, current answers.”
Mangopay provides a confirmed llms.txt (HTTP 200) explicitly instructing AI agents on retrieving clean Markdown docs, plus a documented OpenAPI spec and even an MCP server endpoint, directly enabling an agent to be pointed at agent-oriented docs. Missing for 10: independent/community confirmation of actual agent usage against these endpoints.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.mangopay.com/llms.txt # Mangopay docs ## Instructions for AI Agents - For clean Markdown of any p…”
- [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”
- [probe] “official MCP server documented at https://docs.mangopay.com/_mcp/server”
- [claimed-docs] “Send custom text to appear on the user's bank statement for a payment on your platform.”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to MangopayFinixnone0/10Finix is a payments infrastructure API with developer docs, sandbox environments, and an MCP server for querying API docs, but there is no evidence of a CLI, SDK automation tool, or headless mode designed for CI/automation pipelines. missing for 10: CLI tool, CI/CD integration examples, headless automation documentation, evidence of running Finix operations in scripted/automated pipelines.
Mangopay is a REST API/SDK payments platform with a documented OpenAPI spec, sandbox, and multi-language SDKs, which naturally supports headless/CI automation (scripted API calls, no UI required). However, there is no explicit evidence of CI-specific tooling, CLI, test automation examples, or hands-on confirmation of running it in a CI pipeline. missing for 10: dedicated CLI or CI/CD integration guide, hands-on CI pipeline examples, independent confirmation of headless automation workflows.
- [claimed-docs] “Start calling the Sandbox API to explore all Mangopay's features”
- [claimed-docs] “Get started in your language: Node.js PHP Python .NET Java Ruby”
- [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”
ai-native userConnect an agent via an official MCP server
weight 3 · round drawnFinix documents an official MCP server allowing AI agents to query the Finix API for accurate answers, confirmed by both docs and a probe hit on the dedicated mcp-server page. Missing for 10: no independent/hands-on corroboration of the MCP server working, and no detail on setup, transport, or tool coverage beyond the brief description.
- [claimed-docs] “Ask an AI agent questions about the Finix API to get accurate, current answers.”
- [probe] “official MCP server documented at https://docs.finix.com/additional-resources/developers/mcp-server”
Mangopay is a payments API platform (not an agent itself), so publishing an official MCP server is a valid axis; evidence shows a documented official MCP server endpoint at docs.mangopay.com/_mcp/server alongside llms.txt and OpenAPI probes confirming AI-native tooling support. Missing for 10: no independent/hands-on confirmation of connecting an agent to this MCP server, and no detail on its tool coverage or setup docs beyond the endpoint existing.
- [probe] “official MCP server documented at https://docs.mangopay.com/_mcp/server”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.mangopay.com/llms.txt # Mangopay docs ## Instructions for AI Agents - For clean Markdown of any p…”
- [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”
ai-native userUse an official CLI
weight 2 · round drawnFinixnone0/10No evidence of an official CLI tool; Finix's docs cover APIs, Dashboard, and an MCP server but nothing about a command-line interface for developers.
ai-native userDrive the product through a documented public API
weight 3 · round to MangopayFinix provides extensive documented public APIs for onboarding, payouts, disputes, subscriptions, and webhooks, plus a sandbox environment and an llms.txt discovery file for AI agents, showing clear support for programmatic/API-driven use. missing for 10: independent third-party hands-on confirmation of API usability, and more detail on API completeness/versioning beyond docs listing.
- [claimed-docs] “With Finix, you can easily onboard your sellers to start processing their payments and payouts.”
- [claimed-docs] “Use Finix's APIs to build your own custom onboarding experience for your sellers.”
- [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
- [claimed-docs] “Webhooks let you receive notifications programmatically when your API resources are created or updated.”
- [claimed-docs] “Finix provides separate Sandbox and Live accounts, along with the corresponding API credentials to access the Finix API.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.finix.com/llms.txt # Finix Docs > Explore our documentation, guides, and APIs to start building yo…”
Mangopay provides a documented public REST API with OpenAPI spec, SDKs in multiple languages, sandbox environment, and confirmed live openapi.json endpoint, clearly supporting programmatic/AI-driven use. Missing for 10: independent third-party confirmation of AI-agent usage in production beyond vendor docs/probes.
- [claimed-docs] “Start calling the Sandbox API to explore all Mangopay's features”
- [claimed-docs] “Get started in your language: Node.js PHP Python .NET Java Ruby”
- [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.mangopay.com/llms.txt # Mangopay docs ## Instructions for AI Agents - For clean Markdown of any p…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnFinixnone0/10Finix docs mention separate Sandbox/Live API credentials but give no evidence of scoped or least-privilege credential issuance (e.g., role-based keys, permission scopes) for agent use cases; the MCP server doc is about querying API docs, not credential scoping.
- [claimed-docs] “Finix provides separate Sandbox and Live accounts, along with the corresponding API credentials to access the Finix API.”
- [claimed-docs] “Ask an AI agent questions about the Finix API to get accurate, current answers.”
ai-native userBuild against official SDKs
weight 2 · round to MangopayFinixnone0/10The evidence pack repeatedly references Finix's APIs, dashboard, and an MCP server for AI agents to query documentation, but never mentions official SDKs (e.g., Python, Node, Java client libraries) for developers to build against. Missing for 10: any mention of official SDKs, supported languages, or SDK documentation/repos.
- [claimed-docs] “With Finix, you can easily onboard your sellers to start processing their payments and payouts.”
- [claimed-docs] “Use Finix's APIs to build your own custom onboarding experience for your sellers.”
- [claimed-docs] “Ask an AI agent questions about the Finix API to get accurate, current answers.”
- [probe] “official MCP server documented at https://docs.finix.com/additional-resources/developers/mcp-server”
Mangopay documents official SDKs across Node.js, PHP, Python, .NET, Java, and Ruby, plus a public OpenAPI spec, giving AI-native users concrete language-specific starting points and machine-readable API definitions to build against. Missing for 10: independent/hands-on developer corroboration of SDK quality or GitHub repo activity beyond docs claims.
- [claimed-docs] “Get started in your language: Node.js PHP Python .NET Java Ruby”
- [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”
- [claimed-docs] “Start calling the Sandbox API to explore all Mangopay's features”
ai-native userSubscribe to events via webhooks
weight 2 · round to MangopayFinix has documented webhook support for programmatic notifications when API resources are created/updated, matching the core subscribe-to-events story. missing for 10: no detail on payload schema/signature verification, no independent/hands-on corroboration of webhook reliability, and no explicit AI-agent-specific webhook consumption examples.
- [claimed-docs] “Webhooks let you receive notifications programmatically when your API resources are created or updated.”
Mangopay documents a clear webhook subscription system for event notifications on API objects, configurable via Dashboard or API, which supports agentic/automated integration patterns; docs are also machine-readable (llms.txt, OpenAPI, MCP server) aiding AI-native consumption. Missing for 10: explicit documentation of programmatic webhook creation via API (only Dashboard flow shown) and no independent/hands-on confirmation of webhook reliability.
- [claimed-docs] “Mangopay provides a webhook feature to submit notifications to other applications whenever a specific event occurs for a specific API object…”
- [claimed-docs] “If using the Dashboard, navigate to Developers > Webhooks > Add webhook, then select the event type and enter your URL.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.mangopay.com/llms.txt # Mangopay docs ## Instructions for AI Agents - For clean Markdown of any p…”
- [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round drawnFinixnone0/10No evidence of AI-generated insights or suggestions surfaced from user data within Finix's dashboard or product; the MCP server evidence only supports asking an AI agent questions about the API, not in-product data insights.
Mangopaynone0/10Mangopay is a payments infrastructure API; evidence covers wallets, payouts, disputes, webhooks, and even an MCP server, but nothing describes AI-generated insights or suggestions surfaced from a user's own data inside a Mangopay product interface. Missing for 10: any dashboard analytics/AI insight feature, any AI-generated suggestion capability, any documentation of such a feature at all.
ai-native userSet up automations that run autonomously in the background
weight 2 · round to MangopayFinixnone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
Mangopay offers webhooks for event-driven notifications and an API/SDKs that could be used to build background automations like automated payouts and fraud checks, but there is no evidence of a native scheduling, workflow, or agentic automation framework that runs autonomously without external orchestration. missing for 10: no first-party automation/scheduler product, no evidence of autonomous background job execution, no documented agent/automation orchestration layer beyond webhooks and API calls.
- [claimed-docs] “Mangopay provides a webhook feature to submit notifications to other applications whenever a specific event occurs for a specific API object…”
- [claimed-docs] “If using the Dashboard, navigate to Developers > Webhooks > Add webhook, then select the event type and enter your URL.”
- [claimed-docs] “Automate order processing and payouts for your Mirakl marketplace”
- [claimed-docs] “Define custom logic to detect and mitigate fraud attempts on your platform”
ai-native userOperate the product with natural-language commands
weight 2 · round drawnFinix documents an official MCP server that lets an AI agent 'ask questions about the Finix API to get accurate, current answers' (finix-docs-21, finix-probe-2), showing some agentic/natural-language interface exists, but the evidence describes it as a Q&A/documentation lookup tool rather than a way to actually issue commands (e.g., create payouts, onboard sellers) via natural language. Missing for 10: evidence that natural-language commands can trigger real API actions (payouts, onboarding, disputes) rather than just answer questions, and any independent confirmation of this working end-to-end.
- [claimed-docs] “Ask an AI agent questions about the Finix API to get accurate, current answers.”
- [probe] “official MCP server documented at https://docs.finix.com/additional-resources/developers/mcp-server”
Mangopay documents an official MCP server (mangopay-probe-3) and an llms.txt with agent-oriented instructions (mangopay-probe-1), which enables AI agents to invoke Mangopay's API via natural-language-mediated tool calls rather than raw SDK code. However there is no direct evidence of a natural-language command interface, chat-based operation, or hands-on confirmation that this works end-to-end. Missing for 10: evidence of actual NL command usage/testing, documentation of specific MCP tools exposed, and any user-facing chat/agent interface beyond the MCP endpoint declaration.
- [probe] “official MCP server documented at https://docs.mangopay.com/_mcp/server”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.mangopay.com/llms.txt # Mangopay docs ## Instructions for AI Agents - For clean Markdown of any p…”
- [claimed-docs] “Get started in your language: Node.js PHP Python .NET Java Ruby”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round to MangopayFinixnone0/10Evidence shows Finix has documentation, sandbox/live environments, and an MCP server, but nothing describes an interactive API reference with runnable/executable examples (e.g., no mention of embedded code sandboxes, 'try it' consoles, or in-docs request execution). Missing for 10: evidence of an interactive/runnable API reference tool, any 'try it' console feature, or runnable code snippets in docs.
- [claimed-docs] “Finix provides separate Sandbox and Live accounts, along with the corresponding API credentials to access the Finix API.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.finix.com/llms.txt # Finix Docs > Explore our documentation, guides, and APIs to start building yo…”
Mangopay provides sandbox API access, a documented OpenAPI spec, and multi-language getting-started guides, indicating a functional API reference; there's no explicit evidence of an interactive 'try it now' console with runnable examples embedded in the docs UI. missing for 10: explicit interactive try-it-now console evidence, independent hands-on confirmation of runnable examples in the reference itself.
- [claimed-docs] “Start calling the Sandbox API to explore all Mangopay's features”
- [claimed-docs] “Get started in your language: Node.js PHP Python .NET Java Ruby”
- [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.mangopay.com/llms.txt # Mangopay docs ## Instructions for AI Agents - For clean Markdown of any p…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to MangopayFinixnone0/10No evidence of a downloadable OpenAPI spec or machine-readable API schema; docs mention guides, an llms.txt file, and an MCP server, but nothing about an OpenAPI/Swagger spec download.
A live probe confirms an OpenAPI JSON spec is served at https://docs.mangopay.com/openapi.json returning HTTP 200 with an "openapi" key, directly satisfying the machine-readable spec requirement. Missing for 10: independent third-party confirmation or documentation explicitly advertising the OpenAPI download link in the docs UI.
- [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnFinix explicitly documents separate Sandbox and Live accounts with distinct API credentials, and a dedicated test environment that simulates live payments (test cards, fee schemas, payout schedules) without touching production data. missing for 10: independent/hands-on confirmation from a developer using the sandbox, and explicit detail on data isolation guarantees between sandbox and production.
- [claimed-docs] “Finix provides separate Sandbox and Live accounts, along with the corresponding API credentials to access the Finix API.”
- [claimed-docs] “Finix’s test environment allows you to simulate a live payments experience. Test card payments, configure fees schemas, set payout schedules…”
Mangopay docs explicitly describe a dedicated Sandbox API with simulated test payments, test payment methods (e.g., 3DS2 test cards), and accept/refuse payin simulation flows, allowing full testing without touching production data. Missing for 10: no independent/hands-on confirmation of sandbox-to-production parity or explicit data isolation guarantees beyond docs.
- [claimed-docs] “Simulate a test payment to get funds on a Mangopay wallet”
- [claimed-docs] “Start calling the Sandbox API to explore all Mangopay's features”
- [claimed-docs] “The following card triggers a 3DS2 challenge flow, where SCA is required.”
- [claimed-docs] “Select ***Accept the payin*** (or ***Refuse the payin***) and click ***Submit***.”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnFinixnone0/10No evidence pack item mentions API versioning scheme or a documented deprecation policy; docs cover product features, sandbox/live environments, webhooks, and an MCP server but nothing about version lifecycle or deprecation commitments.
Mangopaynone0/10Evidence shows an OpenAPI spec and sandbox API docs, but there is no mention of API versioning scheme or a documented deprecation policy anywhere in the pack. missing for 10: explicit API version numbering/headers, changelog of breaking changes, documented deprecation timeline/policy.
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round drawnFinixnone0/10Finix's evidence covers payments/payouts/onboarding APIs and an MCP server for querying API docs, but there is no mention of bulk operations, batch endpoints, or multi-item processing capabilities for AI-native automation.
Mangopaynone0/10Evidence covers individual API operations (wallets, payouts, disputes, webhooks) but no documentation of batch/bulk endpoints, multi-item transaction processing, or bulk automation tooling for AI-native workflows. Absence of evidence for this applicable capability yields none. missing for 10: bulk/batch API endpoints, batch payout or transfer operations, evidence of processing many items in a single call.
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to MangopayFinixnone0/10Finix offers webhooks to receive event notifications, but there is no evidence of a rules engine or automation layer that lets users define conditional triggers/actions on those events—webhooks only push data, requiring external logic to act on it.
Mangopay provides webhooks that notify external systems on API object events, and documents 'custom logic to detect and mitigate fraud attempts', plus automatic fee/dispute deductions, showing some event-driven automation. However, there's no evidence of a native rules-definition interface or workflow engine letting users declare 'if event X then action Y' logic within Mangopay itself—automation is limited to webhook notifications that require external code to act. Missing for 10: a documented rules/workflow builder, conditional trigger-action configuration UI, and evidence of built-in automated actions beyond webhooks and fee/dispute processing.
- [claimed-docs] “Mangopay provides a webhook feature to submit notifications to other applications whenever a specific event occurs for a specific API object…”
- [claimed-docs] “If using the Dashboard, navigate to Developers > Webhooks > Add webhook, then select the event type and enter your URL.”
- [claimed-docs] “Define custom logic to detect and mitigate fraud attempts on your platform”
- [claimed-docs] “Your fees are automatically wired to your bank account every month.”
- [claimed-docs] “The funds are automatically deducted from this wallet and sent back to the user. A dispute is created which can be contested by the platform…”
ai-native userSchedule recurring jobs or workflows
weight 2 · round to FinixFinix documents recurring billing via Subscriptions and configurable payout schedules in its test environment, which are forms of recurring financial jobs, but there is no evidence of a general-purpose workflow/automation scheduler, cron-like triggers, or AI-agent-driven recurring task orchestration beyond these payment-specific features. Missing for 10: generic recurring workflow/automation engine, scheduling API beyond payouts/subscriptions, AI-agent orchestration of recurring tasks.
- [claimed-docs] “Bill your customers and buyers using Finix's Subscriptions.”
- [claimed-docs] “Finix’s test environment allows you to simulate a live payments experience. Test card payments, configure fees schemas, set payout schedules…”
- [claimed-docs] “Use Payouts to send funds directly to a recipient's bank account or card in real-time.”
Embedded experience — stories about embedded experience in this arenaEmbedded experience
Stories about embedded experience in this arena
Embedded components
developerSeller-facing surfaces are embeddable — white-label components or APIs for balances, payouts, and transaction history that live inside my product under my brand
weight 2 · round drawnFinix documents APIs to build custom onboarding, payout, and dispute experiences under the platform's own brand (finix-docs-9, finix-docs-10, finix-docs-12, finix-docs-17) plus dashboard-based reporting (finix-docs-24), suggesting sellers' financial data/actions can be surfaced via API in a host product. However, there is no explicit mention of pre-built white-label UI components/widgets (e.g., embeddable balance or transaction-history widgets) — only APIs and Finix's own hosted Dashboard/forms are described. missing for 10: explicit embeddable/white-label UI component library for balances/transaction history, evidence of branding customization on hosted components, independent confirmation of embedding experience.
- [claimed-docs] “With Finix, you can easily onboard your sellers to start processing their payments and payouts.”
- [claimed-docs] “Use Finix's APIs to build your own custom onboarding experience for your sellers.”
- [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
- [claimed-docs] “Monitor and act on Disputes through the Finix Dashboard or API.”
- [claimed-docs] “From transactions to disputes and fees, more than 10 report types are automated and available in your personal dashboard”
- [claimed-docs] “Save time onboarding sellers by using our Onboarding Forms.”
Mangopay provides robust wallet, payout, and transaction APIs (docs-5, docs-6, docs-11, docs-18/19) that let developers build branded balance/payout/history experiences, plus webhooks for real-time updates (docs-14/15) — satisfying the 'APIs' half of the story. However, there is no evidence of prebuilt white-label UI components/widgets for embedding these surfaces directly, only raw API access and a dashboard for the platform itself. Missing for 10: documented drop-in UI components/widgets for balances/payouts/history, evidence of front-end SDKs for seller-facing embedding, and independent confirmation of embedding in production.
- [claimed-docs] “Leverage Mangopay's wallet infrastructure to receive, hold, split, and transfer funds”
- [claimed-docs] “Send funds locally and internationally in 24+ currencies”
- [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”
- [claimed-docs] “Mangopay provides a webhook feature to submit notifications to other applications whenever a specific event occurs for a specific API object…”
- [claimed-docs] “If using the Dashboard, navigate to Developers > Webhooks > Add webhook, then select the event type and enter your URL.”
- [claimed-docs] “Mangopay always attempts to use the domestic rail if the currency and country correspond.”
- [claimed-docs] “Mangopay applies a smart routing logic to always use the domestic rail if a local currency is sent, thereby optimizing routing costs and spe…”
Omnichannel
founder with offline sellersIn-person works on the same stack — terminals or tap-to-pay SDKs that settle into the same seller balances and reporting as online payments
weight 2 · round drawnFinixnone0/10The evidence pack covers Finix's online payments, payouts, onboarding, disputes, and reporting APIs, but there is no mention of in-person/card-present capabilities such as terminals, tap-to-pay SDKs, or POS hardware integrations that settle into the same seller balances as online payments. Without any documentation of card-present/terminal support, this applicable capability is unevidenced.
Mangopaynone0/10Evidence pack covers wallets, payouts, FX, disputes, webhooks, and online payin testing, but there is no mention of physical POS terminals or tap-to-pay/in-person SDKs that settle into the same wallet/balance system as online payments. Missing for 10: any documentation of terminal hardware, in-person card-present SDKs, or unified online/offline settlement flows.
Seller reporting
ops userSellers can self-serve their money questions — per-seller statements, payout reconciliation reports, and exports that let their bookkeeper close the month without contacting me
weight 2 · round to FinixFinix documents a Payouts Dashboard and >10 automated report types (transactions, disputes, fees) plus seller-payout management tools, which could support reconciliation and reporting, but there's no explicit evidence of a seller-facing self-serve statement/export portal that sellers or their bookkeepers can access directly without going through the platform's ops team. Missing for 10: seller-facing self-serve statement/export UI, explicit reconciliation report for bookkeeper close-out, and any confirmation that sellers (not just the platform) can pull these reports themselves.
- [claimed-docs] “Learn how to manage your payout activity using the Payouts Dashboard.”
- [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
- [claimed-docs] “From transactions to disputes and fees, more than 10 report types are automated and available in your personal dashboard”
- [claimed-docs] “With Finix, you can easily onboard your sellers to start processing their payments and payouts.”
Mangopaynone0/10The evidence pack covers wallets, payouts, disputes, webhooks, and FX/routing infrastructure, but contains no mention of seller-facing statements, payout reconciliation reports, or bookkeeper-ready exports that would let sellers self-serve without contacting ops. This is a fair axis for a marketplace payments platform, but no supporting documentation or feature reference exists in the pack.
Funds routing — stories about funds routing in this arenaFunds routing
Stories about funds routing in this arena
Holds release
developerFunds can wait — hold seller funds in a balance until delivery or dispute windows pass, release on my schedule or trigger, with the escrow-like mechanics and their limits documented
weight 2 · round to MangopayFinix documents controlling seller payouts on your own schedule via Dashboard or API and topping up/holding a platform balance before disbursing funds (finix-docs-12, finix-docs-13, finix-docs-15), which supports delaying seller payouts, and it has dispute-handling workflows (finix-docs-17, finix-docs-18). But there is no dedicated 'escrow' feature description — no documented hold-until-delivery mechanism, dispute-window-linked release triggers, or stated limits on how long funds can be held. Missing for 10: explicit escrow/hold-fund mechanics tied to delivery or dispute windows, documented release triggers/automation, and stated limits or edge cases of such holds.
- [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
- [claimed-docs] “Use Payouts to send funds directly to a recipient's bank account or card in real-time.”
- [claimed-docs] “Top up your Finix balance with ACH or wire transfers before sending payouts.”
- [claimed-docs] “Monitor and act on Disputes through the Finix Dashboard or API.”
- [claimed-docs] “Upload evidence and submit a response to challenge a Dispute.”
Mangopay's wallet infrastructure explicitly supports holding funds indefinitely ('as long as needed') and releasing them via API/webhook-triggered events, with dispute/chargeback mechanics documented separately, which together give escrow-like fund-holding and release-on-trigger behavior. However the evidence doesn't show a dedicated 'escrow' product or documented limits (max hold duration, fees for holding, delivery-window-specific triggers) as a unified concept. Missing for 10: explicit escrow/hold-duration limits documentation, a named delivery/dispute-window release mechanism, and independent verification of this workflow in practice.
- [claimed-docs] “Leverage Mangopay's wallet infrastructure to receive, hold, split, and transfer funds”
- [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”
- [claimed-docs] “The funds are automatically deducted from this wallet and sent back to the user. A dispute is created which can be contested by the platform…”
- [claimed-docs] “The platform may have the opportunity to contest the chargeback by providing proof prior to being requested to settle their credit to Mangop…”
- [claimed-docs] “Mangopay provides a webhook feature to submit notifications to other applications whenever a specific event occurs for a specific API object…”
Negative balances
finance leadRefunds and chargebacks that exceed a seller's balance are recoverable — automatic debits against future earnings or their bank account, with the liability order documented
weight 2 · round to MangopayFinixnone0/10Evidence covers disputes monitoring/response, payouts, and balance top-ups, but nothing describes automatic debiting of a seller's future earnings or bank account to recover chargeback/refund losses, nor any documented liability waterfall/order. missing for 10: documentation of automatic negative-balance recovery, debit reversal against future payouts or linked bank account, and liability order documentation.
- [claimed-docs] “Monitor and act on Disputes through the Finix Dashboard or API.”
- [claimed-docs] “Upload evidence and submit a response to challenge a Dispute.”
- [claimed-docs] “Use Payouts to send funds directly to a recipient's bank account or card in real-time.”
- [claimed-docs] “Top up your Finix balance with ACH or wire transfers before sending payouts.”
Mangopay's dispute/e-wallet docs confirm that chargebacks trigger automatic fund deduction from the wallet and create a contestable dispute settled with Mangopay, showing some liability handling ([mangopay-docs-12], [mangopay-docs-13]). However, there is no documented mechanism for recovering shortfalls beyond wallet balance via automatic debits against future earnings or the seller's linked bank account, nor an explicit documented liability order/waterfall for such recovery. Missing for 10: explicit negative-balance recovery via future payouts, bank debit/clawback mechanics, and a documented liability order beyond the basic dispute-contest flow.
- [claimed-docs] “The funds are automatically deducted from this wallet and sent back to the user. A dispute is created which can be contested by the platform…”
- [claimed-docs] “The platform may have the opportunity to contest the chargeback by providing proof prior to being requested to settle their credit to Mangop…”
- [claimed-docs] “Your fees are automatically wired to your bank account every month.”
- [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”
Splits
developerSplit one charge among any set of parties — route funds to multiple sellers, take my cut, and reverse or adjust the split later, all as first-class API objects
weight 3 · round to MangopayFinix's platform-payments docs show sellers can be onboarded and paid out, and platforms can 'monetize' payments and customize fees, which implies a split between seller and platform, but no evidence describes a first-class 'split' object spanning multiple sellers on one charge, nor mechanisms to reverse or adjust splits after the fact. missing for 10: explicit multi-party split/transfer API object, ability to route one charge to several sellers simultaneously, and reversal/adjustment of splits post-charge.
- [claimed-docs] “With Finix, you can easily onboard your sellers to start processing their payments and payouts.”
- [claimed-docs] “Finix allows you to easily monetize your payments. We offer out of the box customizability, efficiency, and revenue growth tools.”
- [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
- [claimed-docs] “Some of the fee customizations available are: International charges, Transaction volume discounts, Applying fees per payment method, Acceler…”
Mangopay's wallet infrastructure explicitly supports receiving, holding, splitting and transferring funds across an unlimited number of wallets, with platform fees automatically routed to the platform's bank account, which enables multi-party fund routing and fee-taking (docs-5, docs-10, docs-11). However, evidence does not detail a first-class 'split payment' API object, nor explicit mechanisms to adjust or reverse a split after the fact beyond generic dispute/chargeback handling (docs-12, docs-13) which addresses refunds, not split adjustment. Missing for 10: explicit API object/documentation for defining a payment split across multiple recipients in one transaction, and documented reversal/adjustment of that split specifically (not just wallet transfers or chargebacks).
- [claimed-docs] “Leverage Mangopay's wallet infrastructure to receive, hold, split, and transfer funds”
- [claimed-docs] “Your fees are automatically wired to your bank account every month.”
- [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”
- [claimed-docs] “The funds are automatically deducted from this wallet and sent back to the user. A dispute is created which can be contested by the platform…”
- [claimed-docs] “The platform may have the opportunity to contest the chargeback by providing proof prior to being requested to settle their credit to Mangop…”
Marketplace disputes — stories about marketplace disputes in this arenaMarketplace disputes
Stories about marketplace disputes in this arena
Dispute handling
ops userDisputes are managed per seller — chargebacks land against the right sub-merchant, evidence is submitted via API or dashboard, and outcomes flow back into seller balances automatically
weight 3 · round drawnFinix documents general dispute management (monitor/act via Dashboard or API, upload evidence, submit response) and separately documents platform/seller-based architecture (onboarding sellers, seller payouts, sub-merchant balances), implying disputes could be tied to sub-merchants, but no docs explicitly confirm chargebacks are routed per-seller or that outcomes automatically adjust seller balances. missing for 10: explicit documentation of chargebacks landing against the correct sub-merchant, and automatic balance reconciliation after dispute resolution.
- [claimed-docs] “Monitor and act on Disputes through the Finix Dashboard or API.”
- [claimed-docs] “Upload evidence and submit a response to challenge a Dispute.”
- [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
- [claimed-docs] “With Finix, you can easily onboard your sellers to start processing their payments and payouts.”
Docs confirm that disputes/chargebacks are tied to a wallet's user (i.e., per-seller) and that funds are automatically deducted and can be contested with proof (mangopay-docs-12, mangopay-docs-13), and wallets are per-platform-user (mangopay-docs-11), implying per-sub-merchant handling. However, there is no explicit documentation of an API or dashboard workflow for submitting dispute evidence, nor confirmation that outcomes automatically reconcile back into seller balances beyond the initial deduction. Missing for 10: explicit evidence-submission API/dashboard flow, confirmation of sub-merchant-specific dispute routing, and automatic balance reconciliation after outcome.
- [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”
- [claimed-docs] “The funds are automatically deducted from this wallet and sent back to the user. A dispute is created which can be contested by the platform…”
- [claimed-docs] “The platform may have the opportunity to contest the chargeback by providing proof prior to being requested to settle their credit to Mangop…”
Portfolio risk
ops userWatch risk across my seller portfolio — fraud and credit-risk signals per sub-merchant, alerts on anomalous sellers, and tools to pause payouts or offboard bad actors
weight 2 · round drawnFinix documents dispute monitoring/response tools, payout dashboards, and automated reports covering transactions/disputes/fees, which partially support portfolio oversight and dispute handling. However there is no evidence of fraud or credit-risk scoring per sub-merchant, anomaly alerts on sellers, or explicit tools to pause payouts or offboard bad actors. missing for 10: fraud/credit-risk signal scoring per sub-merchant, anomaly detection alerts, explicit payout-pause/offboarding controls, independent validation of these risk tools.
- [claimed-docs] “Monitor and act on Disputes through the Finix Dashboard or API.”
- [claimed-docs] “Upload evidence and submit a response to challenge a Dispute.”
- [claimed-docs] “Dispute Management Tools”
- [claimed-docs] “From transactions to disputes and fees, more than 10 report types are automated and available in your personal dashboard”
- [claimed-docs] “Learn how to manage your payout activity using the Payouts Dashboard.”
Mangopay docs show custom fraud-detection logic, dispute/chargeback handling, and webhook event notifications that could support risk monitoring, but there is no evidence of a per-sub-merchant risk dashboard, anomaly alerts across a seller portfolio, or explicit tools to pause payouts/offboard bad actors. missing for 10: portfolio-level risk dashboard per sub-merchant, anomaly/alerting system for sellers, payout-pause or offboarding workflow.
- [claimed-docs] “Define custom logic to detect and mitigate fraud attempts on your platform”
- [claimed-docs] “The funds are automatically deducted from this wallet and sent back to the user. A dispute is created which can be contested by the platform…”
- [claimed-docs] “The platform may have the opportunity to contest the chargeback by providing proof prior to being requested to settle their credit to Mangop…”
- [claimed-docs] “Mangopay provides a webhook feature to submit notifications to other applications whenever a specific event occurs for a specific API object…”
- [claimed-docs] “If using the Dashboard, navigate to Developers > Webhooks > Add webhook, then select the event type and enter your URL.”
Marketplace payouts — stories about marketplace payouts in this arenaMarketplace payouts
Stories about marketplace payouts in this arena
Cross border
finance leadInternational sellers get paid properly — local-currency payouts, documented FX handling, and settlement to local bank rails rather than expensive wires
weight 2 · round to MangopayFinixnone0/10Finix's documented payouts focus on US rails (ACH, wire, card, real-time bank payouts) and its only international-related mention is a fee customization for 'International charges' (finix-docs-25), not multi-currency payout support, FX handling, or local settlement rails. No evidence describes local-currency payouts to international sellers or settlement via local bank networks.
- [claimed-docs] “Use Payouts to send funds directly to a recipient's bank account or card in real-time.”
- [claimed-docs] “Top up your Finix balance with ACH or wire transfers before sending payouts.”
- [claimed-docs] “Some of the fee customizations available are: International charges, Transaction volume discounts, Applying fees per payment method, Acceler…”
- [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
Docs explicitly describe local-currency payouts via domestic bank rails (smart routing prioritizing domestic rail over wire), multi-currency sends in 24+ currencies, and embedded FX conversion for global markets, directly matching the finance-lead story. missing for 10: no explicit documented FX rate/markup transparency or fee schedule, and no independent/hands-on confirmation of settlement times or local rail coverage per country.
- [claimed-docs] “Mangopay always attempts to use the domestic rail if the currency and country correspond.”
- [claimed-docs] “Mangopay applies a smart routing logic to always use the domestic rail if a local currency is sent, thereby optimizing routing costs and spe…”
- [claimed-docs] “Send funds locally and internationally in 24+ currencies”
- [claimed-docs] “Reach global markets by seamlessly embedding FX conversions in your workflow”
- [claimed-docs] “Your fees are automatically wired to your bank account every month.”
Payout schedules
ops userPayouts run on the schedule each seller needs — daily, weekly, monthly, or manual, plus instant payouts to cards or real-time rails where supported, configurable per seller
weight 3 · round to FinixFinix docs confirm real-time payouts to bank accounts or cards, payout links, top-up via ACH/wire, and a test environment where you can 'set payout schedules,' plus per-seller payout management via Dashboard or API. However, there's no explicit documentation of configurable daily/weekly/monthly/manual cadence options per seller or instant-payout-to-real-time-rails distinctions beyond cards. missing for 10: explicit per-seller schedule configuration UI/API (daily/weekly/monthly/manual options), documentation of real-time rail support beyond cards, and independent/hands-on confirmation of scheduling flexibility.
- [claimed-docs] “Make a payout to a recipient's credit or debit card.”
- [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
- [claimed-docs] “Use Payouts to send funds directly to a recipient's bank account or card in real-time.”
- [claimed-docs] “Top up your Finix balance with ACH or wire transfers before sending payouts.”
- [claimed-docs] “Finix’s test environment allows you to simulate a live payments experience. Test card payments, configure fees schemas, set payout schedules…”
Mangopaynone0/10The evidence covers wallet infrastructure, payout routing rails (domestic vs cross-border), and platform fee wiring, but contains no mention of configurable payout schedules (daily/weekly/monthly/manual) per seller, nor instant payouts to cards or real-time rails. Missing for 10: any documentation of per-seller payout scheduling, manual vs automatic payout triggers, or instant/real-time payout options.
- [claimed-docs] “Mangopay always attempts to use the domestic rail if the currency and country correspond.”
- [claimed-docs] “Mangopay applies a smart routing logic to always use the domestic rail if a local currency is sent, thereby optimizing routing costs and spe…”
- [claimed-docs] “Your fees are automatically wired to your bank account every month.”
- [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round drawnDocs repeatedly note dual access via 'Dashboard or API' for payouts, seller payouts, disputes, and onboarding (finix-docs-6,7,8,12,17), indicating most core operations are API-accessible, and a Sandbox/Live environment plus webhooks support programmatic workflows (finix-docs-19,20). However, some UI-only surfaces like reporting/dashboard analytics and pricing/fee customization tools are described only in dashboard terms (finix-docs-22,24,25) without explicit API parity confirmation. Missing for 10: explicit API equivalents for dashboard reporting/analytics and fee-customization UI, and independent/hands-on confirmation that no UI action is API-inaccessible.
- [claimed-docs] “Learn how to onboard your sellers with Finix's APIs.”
- [claimed-docs] “Make a payout to a recipient's credit or debit card.”
- [claimed-docs] “Learn how to create payout links on the Finix Dashboard and via API”
- [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
- [claimed-docs] “Monitor and act on Disputes through the Finix Dashboard or API.”
- [claimed-docs] “Webhooks let you receive notifications programmatically when your API resources are created or updated.”
- [claimed-docs] “Finix provides separate Sandbox and Live accounts, along with the corresponding API credentials to access the Finix API.”
- [claimed-docs] “Dispute Management Tools”
- [claimed-docs] “From transactions to disputes and fees, more than 10 report types are automated and available in your personal dashboard”
Mangopay is API-first: docs show a full OpenAPI spec, sandbox API, and API-driven wallet, payout, dispute, and webhook management, suggesting broad functional parity. However, some flows (e.g., webhook setup, dispute proof submission) are documented via the Dashboard UI as an alternative path, and there is no explicit claim that all Dashboard actions are always mirrored in the API. Missing for 10: explicit statement of full UI/API parity, and evidence that dashboard-only admin actions (e.g., dispute contestation, account config) are fully API-accessible.
- [claimed-docs] “Start calling the Sandbox API to explore all Mangopay's features”
- [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”
- [claimed-docs] “Mangopay provides a webhook feature to submit notifications to other applications whenever a specific event occurs for a specific API object…”
- [claimed-docs] “If using the Dashboard, navigate to Developers > Webhooks > Add webhook, then select the event type and enter your URL.”
- [claimed-docs] “The platform may have the opportunity to contest the chargeback by providing proof prior to being requested to settle their credit to Mangop…”
- [claimed-docs] “Leverage Mangopay's wallet infrastructure to receive, hold, split, and transfer funds”
ai-native userExport all of my data in open formats and leave
weight 3 · round drawnFinixnone0/10No evidence describes an ability to export all account/transaction data in open formats or facilitate leaving the platform; only dashboard reporting features are mentioned, not full data export/portability. Missing for 10: documented bulk data export, open format guarantees (CSV/JSON), or data portability/exit tooling.
Payfac liability — stories about payfac liability in this arenaPayfac liability
Stories about payfac liability in this arena
Graduation path
founderThere's a path up the stack — start on the managed model and graduate toward registered payment facilitation with more economics and control, without replatforming
weight 2 · round drawnFinixnone0/10Evidence shows Finix's platform-payments features (seller onboarding, payouts, monetization, disputes) but nowhere describes a staged path from a managed/PayFac-as-a-service model to full registered payment facilitation, nor any assurance that such a transition avoids replatforming. This specific payfac-liability graduation story is unaddressed in the pack.
Mangopaynone0/10No evidence describes a graduation path from managed/wallet model to registered payment-facilitator status with increased economics/control, nor any migration tooling or licensing tiers. Evidence only covers wallet infrastructure, payouts, disputes, and API onboarding — nothing about payfac-liability progression. Missing for 10: any mention of licensing tiers, BIN sponsorship, PF-of-record transition, or economics/control changes as platforms scale.
Responsibility split
ops userThe responsibility split is explicit — who owns KYC/AML, card-network compliance, fraud losses, and seller misconduct between me and the provider, in the docs rather than the contract's fine print
weight 2 · round drawnFinixnone0/10Evidence pack shows only feature-level docs (onboarding, payouts, disputes, tokenization) with no explicit documentation splitting liability for KYC/AML, card-network compliance, fraud losses, or seller misconduct between Finix and the platform/ops user. Community items are unrelated commentary about branding/positioning, not liability allocation.
Mangopaynone0/10Docs mention compliance features (KYC guidance, fraud tooling, dispute/chargeback contestation) but nowhere is there an explicit ops-facing breakdown of who owns KYC/AML, card-network compliance, fraud losses, and seller misconduct versus Mangopay — it's scattered feature docs, not a liability-split reference.
- [claimed-docs] “Manage your community of paying users in full compliance”
- [claimed-docs] “Define custom logic to detect and mitigate fraud attempts on your platform”
- [claimed-docs] “The funds are automatically deducted from this wallet and sent back to the user. A dispute is created which can be contested by the platform…”
- [claimed-docs] “The platform may have the opportunity to contest the chargeback by providing proof prior to being requested to settle their credit to Mangop…”
Tax forms
finance leadSeller tax reporting is handled — 1099-K thresholds tracked, forms generated, delivered, and filed, with the data corrections workflow documented
weight 2 · round drawnFinixnone0/10No evidence in the pack mentions 1099-K thresholds, tax form generation/filing, delivery to sellers, or any data-correction workflow for tax reporting; coverage is limited to payouts, onboarding, disputes, and reporting on transactions/fees.
Mangopaynone0/10No evidence in the pack references 1099-K thresholds, tax form generation/filing, or a tax data correction workflow; the docs cover wallets, payouts, disputes, webhooks, and FX but nothing about US tax reporting compliance. missing for 10: 1099-K threshold tracking, form generation/delivery/filing, corrections workflow documentation.
Platform agent access — stories about platform agent access in this arenaPlatform agent access
Stories about platform agent access in this arena
Agent money ops
ai-native userAn agent can work the money side — read balances and payouts, investigate a seller's missing payout, draft dispute evidence — against documented, agent-usable surfaces
weight 2 · round to MangopayFinix documents API/dashboard surfaces for reading payouts, diagnosing failed payouts, and uploading dispute evidence (finix-docs-7,12,13,16,17,18), and it ships an official MCP server so agents can query API documentation (finix-docs-21, finix-probe-2). However, the MCP server is explicitly for answering questions about the API, not for performing agent actions like reading live balances or drafting/submitting dispute evidence directly — that still requires building against the REST API. Missing for 10: evidence of an agent actually executing balance/payout reads or dispute-evidence actions via the MCP server or an agent SDK, and independent/hands-on confirmation of agent usability.
- [claimed-docs] “Make a payout to a recipient's credit or debit card.”
- [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
- [claimed-docs] “Use Payouts to send funds directly to a recipient's bank account or card in real-time.”
- [claimed-docs] “Diagnose and resolve payouts that fail before funds reach the recipient.”
- [claimed-docs] “Monitor and act on Disputes through the Finix Dashboard or API.”
- [claimed-docs] “Upload evidence and submit a response to challenge a Dispute.”
- [claimed-docs] “Ask an AI agent questions about the Finix API to get accurate, current answers.”
- [probe] “official MCP server documented at https://docs.finix.com/additional-resources/developers/mcp-server”
Mangopay ships genuinely agent-usable surfaces: a documented OpenAPI spec, llms.txt agent instructions, and an official MCP server, plus docs on wallets/balances, payouts (with domestic-rail routing details useful for investigating a delayed payout), and disputes/chargebacks (including contesting with proof, which maps to 'draft dispute evidence'). However there's no explicit example or endpoint description for reading balances/payout status programmatically or a worked 'investigate missing payout' or 'draft dispute evidence' agent workflow — these are inferred from adjacent guides rather than directly documented. Missing for 10: explicit balance/payout-status API examples, a documented dispute-evidence submission workflow, and independent/hands-on confirmation the MCP server actually exposes these operations.
- [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”
- [probe] “official MCP server documented at https://docs.mangopay.com/_mcp/server”
- [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”
- [claimed-docs] “Mangopay always attempts to use the domestic rail if the currency and country correspond.”
- [claimed-docs] “Mangopay applies a smart routing logic to always use the domestic rail if a local currency is sent, thereby optimizing routing costs and spe…”
- [claimed-docs] “The funds are automatically deducted from this wallet and sent back to the user. A dispute is created which can be contested by the platform…”
- [claimed-docs] “The platform may have the opportunity to contest the chargeback by providing proof prior to being requested to settle their credit to Mangop…”
- [claimed-docs] “Send custom text to appear on the user's bank statement for a payment on your platform.”
Agent onboarding
ai-native userAn agent can run seller operations — create accounts, drive onboarding to completion, and answer requirements-due states through the API or an MCP surface with scoped credentials
weight 3 · round to MangopayFinix has API-based seller onboarding (create accounts, onboarding forms, API onboarding flows) and an official MCP server for the docs/API, but the MCP server is documented as a Q&A assistant ('ask an AI agent questions about the Finix API') rather than an actionable surface for agents to create accounts, drive onboarding, or query/answer requirements-due states. No evidence of scoped credentials for agent-driven actions or of onboarding-status/requirements-due endpoints being exposed via MCP. missing for 10: evidence that the MCP server supports actionable operations (account creation, onboarding progression) rather than just Q&A, documentation of requirements-due/onboarding-status API endpoints, and evidence of scoped/agent-specific credentialing.
- [claimed-docs] “Learn how to onboard your sellers with Finix's APIs.”
- [claimed-docs] “With Finix, you can easily onboard your sellers to start processing their payments and payouts.”
- [claimed-docs] “Use Finix's APIs to build your own custom onboarding experience for your sellers.”
- [claimed-docs] “Ask an AI agent questions about the Finix API to get accurate, current answers.”
- [probe] “official MCP server documented at https://docs.finix.com/additional-resources/developers/mcp-server”
- [claimed-docs] “Finix provides separate Sandbox and Live accounts, along with the corresponding API credentials to access the Finix API.”
Mangopay exposes a full API (with OpenAPI) and an official MCP server, plus docs on managing users/accounts in compliance, which supports agent-driven seller operations in principle. However, no evidence explicitly documents onboarding completion flows, KYC 'requirements-due' status handling, or scoped/limited credentials for agent use via the MCP surface. missing for 10: explicit onboarding-completion workflow docs, requirements-due state handling, scoped-credential/permission model for agent access.
- [probe] “PROBE openapi: HTTP 200 at https://docs.mangopay.com/openapi.json — contains "openapi" key”
- [probe] “official MCP server documented at https://docs.mangopay.com/_mcp/server”
- [claimed-docs] “Manage your community of paying users in full compliance”
- [claimed-docs] “Get started in your language: Node.js PHP Python .NET Java Ruby”
Agentic commerce
developerThe platform is ready for agent buyers — documented support for agent-initiated checkout on marketplace transactions (agentic-commerce protocols, delegated payment credentials) that works with split funds flows
weight 2 · round drawnFinixnone0/10No evidence of agent-initiated checkout support, agentic-commerce protocols, or delegated payment credentials tied to marketplace split-funds flows; docs only cover standard onboarding, payouts, disputes, and an MCP server for asking questions about the API, not enabling agent-driven purchases.
- [claimed-docs] “Ask an AI agent questions about the Finix API to get accurate, current answers.”
- [probe] “official MCP server documented at https://docs.finix.com/additional-resources/developers/mcp-server”
- [claimed-docs] “With Finix, you can easily onboard your sellers to start processing their payments and payouts.”
- [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
Mangopaynone0/10No evidence of agent-initiated checkout, agentic-commerce protocols, or delegated payment credentials; documentation covers wallets, payouts, disputes, FX, and webhooks but nothing about AI/agent buyer flows integrated with split funds. Missing for 10: any mention of agent checkout protocols, delegated payment credential support, or agent-specific API/documentation tying to split funds flows.
Platform ledger — stories about platform ledger in this arenaPlatform ledger
Stories about platform ledger in this arena
Funds custody
finance leadPlatform funds have a home — clarity on where in-flight and held funds sit, whether balances earn yield, and how money is segregated from the provider's own accounts
weight 2 · round to MangopayFinixnone0/10The evidence pack covers payouts, onboarding, disputes, and dashboard reporting, but contains no mention of where held/in-flight funds are custodied, whether balances earn yield, or how platform funds are segregated from Finix's own accounts — a standard and expected disclosure for a payments/platform-ledger product. missing for 10: any documentation of fund custody/segregation structure, statements on yield/interest on held balances, and disclosure of banking partner or FBO account arrangements.
- [claimed-docs] “Top up your Finix balance with ACH or wire transfers before sending payouts.”
- [claimed-docs] “Use Payouts to send funds directly to a recipient's bank account or card in real-time.”
Docs confirm Mangopay's wallet infrastructure lets platforms hold, split and transfer funds and that platform fees are wired out monthly (mangopay-docs-5, mangopay-docs-10, mangopay-docs-11), giving some sense of where funds sit, but there is no evidence addressing regulatory fund segregation from Mangopay's own accounts or whether held balances earn yield. missing for 10: explicit safeguarding/segregation-of-client-funds statement, disclosure of interest/yield policy on wallet balances, third-party or regulatory confirmation of fund protection.
- [claimed-docs] “Leverage Mangopay's wallet infrastructure to receive, hold, split, and transfer funds”
- [claimed-docs] “Your fees are automatically wired to your bank account every month.”
- [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”
Ledger visibility
finance leadThe platform's money is legible — balances by seller and by my own fee accounts, every movement traceable from charge through split to payout, reconcilable to the penny
weight 3 · round drawnFinix provides fee/monetization tooling, a Payouts Dashboard, 10+ automated report types (transactions, disputes, fees), sandbox/live environments and webhooks for tracking resource state changes, which together support financial visibility and reconciliation workflows. However, there is no explicit documentation of a unified ledger view showing per-seller balances alongside platform fee-account balances, or a single traceable charge→split→payout audit trail guaranteed to reconcile to the penny. Missing for 10: dedicated seller-balance/fee-account balance dashboard, explicit charge-to-payout traceability/audit-trail documentation, penny-level reconciliation guarantees or tooling.
- [claimed-docs] “Learn how to manage your payout activity using the Payouts Dashboard.”
- [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
- [claimed-docs] “Top up your Finix balance with ACH or wire transfers before sending payouts.”
- [claimed-docs] “Webhooks let you receive notifications programmatically when your API resources are created or updated.”
- [claimed-docs] “From transactions to disputes and fees, more than 10 report types are automated and available in your personal dashboard”
- [claimed-docs] “Some of the fee customizations available are: International charges, Transaction volume discounts, Applying fees per payment method, Acceler…”
- [claimed-docs] “Finix’s test environment allows you to simulate a live payments experience. Test card payments, configure fees schemas, set payout schedules…”
Docs confirm wallet infrastructure supporting per-seller and platform fee wallets, automatic fee payout to bank, webhooks for event tracking (charge/payin, split/transfer, payout), and dispute/chargeback handling — the building blocks for traceability and reconciliation. However there is no explicit documentation of a unified ledger/reporting view, reconciliation reports, or per-penny audit trail tooling that a finance lead would use directly. Missing for 10: dedicated reconciliation/reporting API or dashboard view showing full charge-to-payout trace, statement/ledger export functionality, and independent confirmation that balances reconcile to the penny in practice.
- [claimed-docs] “Leverage Mangopay's wallet infrastructure to receive, hold, split, and transfer funds”
- [claimed-docs] “Your fees are automatically wired to your bank account every month.”
- [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”
- [claimed-docs] “The funds are automatically deducted from this wallet and sent back to the user. A dispute is created which can be contested by the platform…”
- [claimed-docs] “The platform may have the opportunity to contest the chargeback by providing proof prior to being requested to settle their credit to Mangop…”
- [claimed-docs] “Mangopay provides a webhook feature to submit notifications to other applications whenever a specific event occurs for a specific API object…”
- [claimed-docs] “If using the Dashboard, navigate to Developers > Webhooks > Add webhook, then select the event type and enter your URL.”
Recon exports
developerReconciliation is automatable — settlement and balance reports per seller and rolled up, delivered as files or APIs my finance stack consumes on schedule
weight 2 · round to FinixFinix docs mention automated dashboard reports (10+ report types covering transactions, disputes, fees) and webhooks for programmatic event notifications, plus seller payout management via API, which together support some reconciliation workflows. However, there is no explicit documentation of scheduled file delivery, per-seller vs rolled-up settlement/balance report APIs, or a dedicated reconciliation/reporting API for finance-stack consumption. Missing for 10: explicit scheduled report export (files/API), per-seller vs aggregate balance reconciliation endpoints, and confirmation of finance-stack integration patterns.
- [claimed-docs] “From transactions to disputes and fees, more than 10 report types are automated and available in your personal dashboard”
- [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
- [claimed-docs] “Webhooks let you receive notifications programmatically when your API resources are created or updated.”
- [claimed-docs] “Monitor and act on Disputes through the Finix Dashboard or API.”
Mangopay's docs show wallet balances, automatic monthly fee wiring, and webhook event notifications that could feed a finance stack, but there is no explicit documentation of settlement/balance report files or scheduled per-seller reconciliation APIs. missing for 10: dedicated reconciliation/settlement report API or downloadable file exports, explicit per-seller rollup reporting, and evidence of scheduled delivery cadence.
- [claimed-docs] “Your fees are automatically wired to your bank account every month.”
- [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”
- [claimed-docs] “Mangopay provides a webhook feature to submit notifications to other applications whenever a specific event occurs for a specific API object…”
- [claimed-docs] “If using the Dashboard, navigate to Developers > Webhooks > Add webhook, then select the event type and enter your URL.”
Platform monetization — stories about platform monetization in this arenaPlatform monetization
Stories about platform monetization in this arena
Application fees
founderPayments are a revenue line — take an application fee or markup on every transaction, set per-seller pricing, and see my payments revenue reported distinctly from processing costs
weight 3 · round to FinixFinix explicitly documents platform monetization: per-seller fee customization (international charges, volume discounts, per-method fees), a dedicated 'Monetizing Payments' guide, and dashboard reporting that separates transactions, disputes, and fees across 10+ automated report types. This directly supports application fees/markup, per-seller pricing, and distinct revenue reporting. Missing for 10: no independent/hands-on verification of the revenue-vs-cost reporting split or real-world confirmation that markup fees appear as distinct line items in the dashboard.
- [claimed-docs] “Finix allows you to easily monetize your payments. We offer out of the box customizability, efficiency, and revenue growth tools.”
- [claimed-docs] “From transactions to disputes and fees, more than 10 report types are automated and available in your personal dashboard”
- [claimed-docs] “Some of the fee customizations available are: International charges, Transaction volume discounts, Applying fees per payment method, Acceler…”
- [claimed-docs] “Finix’s test environment allows you to simulate a live payments experience. Test card payments, configure fees schemas, set payout schedules…”
- [claimed-docs] “Dispute Management Tools”
Mangopay's wallet infrastructure supports splitting funds and platforms have their fees automatically wired to their bank account monthly, which supports taking a fee/markup on transactions (mangopay-docs-5, mangopay-docs-10, mangopay-docs-11). However, there is no evidence of per-seller custom pricing configuration or of dashboard/reporting that separates fee revenue from processing costs. Missing for 10: per-seller/variable fee-setting documentation, dedicated revenue-vs-cost reporting/dashboard evidence, independent confirmation of fee mechanics in production.
- [claimed-docs] “Leverage Mangopay's wallet infrastructure to receive, hold, split, and transfer funds”
- [claimed-docs] “Your fees are automatically wired to your bank account every month.”
- [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”
Buy rates
finance leadI control the economics — a documented buy rate from the provider and freedom to set the sell rate my sellers see, with interchange-level cost visibility to manage the spread
weight 2 · round to FinixFinix documents platform monetization tools — fee customization (international charges, volume discounts, per-payment-method fees), configurable fee schemas in test/sandbox, and dashboard reports covering transactions, disputes, and fees — which supports setting a sell rate and viewing cost data. However there is no explicit documentation of a 'buy rate' contract from Finix itself or interchange-level cost breakdowns for spread management. Missing for 10: documented buy rate/cost-plus pricing terms, interchange-level line-item visibility, and independent confirmation of spread transparency.
- [claimed-docs] “Finix allows you to easily monetize your payments. We offer out of the box customizability, efficiency, and revenue growth tools.”
- [claimed-docs] “From transactions to disputes and fees, more than 10 report types are automated and available in your personal dashboard”
- [claimed-docs] “Some of the fee customizations available are: International charges, Transaction volume discounts, Applying fees per payment method, Acceler…”
- [claimed-docs] “Finix’s test environment allows you to simulate a live payments experience. Test card payments, configure fees schemas, set payout schedules…”
Mangopaynone0/10The evidence shows only generic fee/wallet documentation (e.g., fees wired monthly, wallet infrastructure) but nothing about a documented buy rate, ability to set a sell rate, or interchange-level cost breakdown for spread management. Community comments merely speculate about overall pricing being surprisingly low, not about rate transparency or spread control tools.
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnFinixnone0/10No evidence anywhere in the pack of data residency/region selection controls, storage location options, or compliance-region certifications; Finix's documentation is entirely about payments/payouts/onboarding functionality with no mention of data residency choices.
ai-native userControl data retention and deletion
weight 2 · round drawnFinixnone0/10No evidence pack items address data retention policies, deletion controls, or privacy/data lifecycle management for Finix; docs focus entirely on payments, payouts, onboarding, and disputes.
Mangopaynone0/10No evidence in the pack addresses data retention policies, deletion controls, or privacy/data-lifecycle settings for users; the docs focus on payments, wallets, payouts, and disputes. Missing for 10: any documentation on data retention periods, user data deletion APIs/requests, GDPR-style erasure workflows, or privacy control settings.
Seller onboarding — stories about seller onboarding in this arenaSeller onboarding
Stories about seller onboarding in this arena
Global coverage
founderSellers can join from where they are — supported onboarding countries, local payment methods, and local-currency settlement documented as a coverage map, not discovered ticket by ticket
weight 2 · round to MangopayFinixnone0/10Evidence covers merchant onboarding mechanics (forms, APIs) but there is no documented coverage map of supported onboarding countries, local payment methods, or local-currency settlement — nothing resembling a country/currency/payment-method matrix appears anywhere in the pack.
Docs mention multi-currency payouts (24+ currencies), FX conversion, smart domestic-rail routing, and automated fee settlement, implying broad geographic/currency coverage, but there is no evidence of an explicit onboarding coverage map listing supported countries, KYC requirements per region, or local payment methods per market. Founders would still need to discover country-specific onboarding requirements piecemeal. missing for 10: a documented country/coverage map, list of supported local payment methods per country, explicit onboarding country list, independent confirmation of coverage claims.
- [claimed-docs] “Send funds locally and internationally in 24+ currencies”
- [claimed-docs] “Reach global markets by seamlessly embedding FX conversions in your workflow”
- [claimed-docs] “Mangopay always attempts to use the domestic rail if the currency and country correspond.”
- [claimed-docs] “Mangopay applies a smart routing logic to always use the domestic rail if a local currency is sent, thereby optimizing routing costs and spe…”
- [claimed-docs] “Your fees are automatically wired to your bank account every month.”
Onboarding api
developerOnboard a seller through the API — KYB and KYC, bank account linking, and terms acceptance — with hosted flows and embeddable components when I don't want to build the forms
weight 3 · round to FinixFinix docs clearly describe API-based seller onboarding (finix-docs-6, finix-docs-9, finix-docs-10) and hosted 'Onboarding Forms' to save developers from building UI (finix-docs-5), plus general merchant onboarding guidance (finix-docs-4). However, the evidence pack never explicitly details KYC/KYB data collection, bank account linking, or terms-of-service acceptance steps, nor confirms an embeddable (non-hosted-redirect) component distinct from the hosted forms. Missing for 10: explicit KYC/KYB field documentation, bank-account-linking flow details, terms-acceptance step, and confirmation of embeddable UI components (vs. only hosted forms).
- [claimed-docs] “If you are a platform, you can quickly onboard merchants to Finix.”
- [claimed-docs] “Save time onboarding sellers by using our Onboarding Forms.”
- [claimed-docs] “Learn how to onboard your sellers with Finix's APIs.”
- [claimed-docs] “With Finix, you can easily onboard your sellers to start processing their payments and payouts.”
- [claimed-docs] “Use Finix's APIs to build your own custom onboarding experience for your sellers.”
Mangopaynone0/10The evidence pack only vaguely references 'managing a community of paying users in full compliance' and wallet/payout infrastructure, but contains no documentation of KYB/KYC onboarding APIs, hosted onboarding flows, embeddable UI components, bank account linking, or terms-of-service acceptance mechanisms — the core elements of this story are entirely unevidenced.
- [claimed-docs] “Manage your community of paying users in full compliance”
Progressive requirements
ops userOnboarding friction is tunable — collect the minimum to start selling and gather the rest before payout thresholds, with clear requirements-due states per seller
weight 2 · round to FinixFinix docs show onboarding forms and APIs for onboarding sellers, plus dashboard/API controls for seller payouts, implying some flexibility in what's collected before payout, but there's no explicit documentation of a tunable 'minimum to start selling then collect more before payout thresholds' workflow or explicit per-seller requirements-due states. missing for 10: explicit documentation of configurable onboarding requirement tiers, requirements-due state tracking per seller, and evidence of payout-threshold gating tied to progressive data collection.
- [claimed-docs] “Save time onboarding sellers by using our Onboarding Forms.”
- [claimed-docs] “Learn how to onboard your sellers with Finix's APIs.”
- [claimed-docs] “With Finix, you can easily onboard your sellers to start processing their payments and payouts.”
- [claimed-docs] “Use Finix's APIs to build your own custom onboarding experience for your sellers.”
- [claimed-docs] “You can manage how sellers get paid out using the Finix Dashboard or our API.”
Mangopaynone0/10The evidence only shows generic compliance and wallet/payout docs (e.g., mangopay-docs-4, mangopay-docs-11) but nothing about tiered/progressive KYC, minimum-to-start onboarding, or explicit requirements-due states tied to payout thresholds. Missing for 10: documentation of staged KYC levels, seller onboarding status states, and payout gating tied to verification completeness.
- [claimed-docs] “Manage your community of paying users in full compliance”
- [claimed-docs] “Platforms can create an unlimited number of wallets to hold funds as long as needed.”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableFinixn/aFinix is a payments platform/API, not an AI agent or assistant product; the evidence only shows Finix exposing its own MCP server for external AI agents to query its API (finix-docs-21, finix-probe-2), not Finix itself consuming or plugging in external MCP servers to gain new tool capabilities. This client-side 'plug MCP servers in' story is a category mismatch for a payments SaaS with no agentic core.
- [claimed-docs] “Ask an AI agent questions about the Finix API to get accurate, current answers.”
- [probe] “official MCP server documented at https://docs.finix.com/additional-resources/developers/mcp-server”
Mangopayn/aMangopay is a payments API platform, not an AI agent/assistant that itself consumes tools via MCP; the only MCP-related evidence shows Mangopay publishing its own MCP server for others to consume (the reverse role), not a capability to plug external MCP servers into Mangopay so it can use their tools. This client-side axis is a category mismatch for a payments backend product.
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · not comparableFinixnone0/10Evidence shows only an MCP server for querying API documentation ([finix-probe-2], [finix-docs-21]) — a developer reference tool, not a built-in AI assistant inside the Finix product that can be delegated tasks (e.g., managing payouts, disputes, onboarding). No evidence of any in-product agentic assistant.
- [claimed-docs] “Ask an AI agent questions about the Finix API to get accurate, current answers.”
- [probe] “official MCP server documented at https://docs.finix.com/additional-resources/developers/mcp-server”
Mangopayn/aMangopay is a payments infrastructure API/platform, not a product with an interactive assistant for end-users to delegate tasks to; the evidence covers wallets, payouts, disputes, webhooks, and an MCP server for developer/agent integration, none of which is a built-in AI assistant for task delegation.
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableFinixn/aFinix is a payments infrastructure API/platform, not an automation-building tool; there is no concept of 'automations' to version, review, or roll back in its product surface—this axis is a category error for a payments processor.
ai-native userRead the product's source under an open license
weight 2 · not comparableFinixn/aFinix is a proprietary payments API/platform, not an open-source project; source availability under an open license is not a fair axis for this category of product.
ai-native userSelf-host the core product
weight 3 · not comparableFinixn/aFinix is a hosted payments infrastructure/API platform, not software designed for self-hosting; the evidence pack is entirely about cloud dashboard/API features with no self-host offering. Self-hosting the core product is a category error for this type of SaaS payments platform.
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparableFinixn/aFinix is a payments infrastructure platform, not an AI model or data-processing tool; the notion of opting out of AI training data usage is a category error for this product type, not something evidenced or expected in its docs.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableFinixn/aFinix is a payments infrastructure API/platform, not an AI agent or developer tool with client-side telemetry to opt out of; this privacy-posture story about telemetry opt-out is a category error for this kind of product.