Marketplace & Platform Payments Arena
Marketplace & Platform Payments — procurement report
ProductArena · rankings as of 2026-09-15 · evidence as of 2026-09-15 · 6 products · 53 judged requirements · 318 judged cells
Methodology: Every product is judged against a shared taxonomy of user stories using cited evidence — hands-on probes > repository code > independent community sources > vendor claims — never opinion. Full writeup: https://ultrametric.ai/productarena/methodology
Leaderboard
| # | Product | PA Score | Coverage score | Applicable cells | Confidence |
|---|---|---|---|---|---|
| 1 | Mangopay | 34.5 | 26.4 | 47/53 | C |
| 2 | Stripe Connect | 30.6 | 30.8 | 43/53 | B |
| 3 | Adyen for Platforms | 22.7 | 27.6 | 46/53 | B |
| 4 | Finix | 20.0 | 22.2 | 47/53 | C |
| 5 | Rainforest | 14.8 | 19.1 | 41/53 | C |
| 6 | Tilled | 7.0 | 10.9 | 44/53 | D |
PA Score = agent-readiness blend (see methodology). Coverage score = weighted share of judged requirements met. Confidence = how much of the score rests on tested vs claimed evidence (A–D).
Uncertainty note
The current #1/#2 gap in this arena is not close enough to qualify for the multi-judge uncertainty pass (or the pass has not covered it yet) — no extra caveat applies beyond the per-product confidence grades above.
Buyer checklist (RFP)
The arena's 53 judged user stories as requirements, grouped by theme. Priorities mirror the story weights our scoring uses (3 = must-have, 2 = should-have, 1 = nice-to-have). Interactive version with per-requirement verdicts for the top products: /arena/marketplace-payments/checklist
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
- ai-native userPlug MCP servers into this product so it can use their toolsmust-have
- ai-native userConnect an agent via an official MCP servermust-have
- ai-native userDrive the product through a documented public APImust-have
- ai-native userDelegate tasks to a built-in AI assistant inside the productmust-have
- ai-native userPoint an agent at llms.txt or agent-oriented docsshould-have
- ai-native userRun the product headlessly / in CI for automationshould-have
- ai-native userUse an official CLIshould-have
- ai-native userIssue scoped/least-privilege API credentials for an agentshould-have
- ai-native userBuild against official SDKsshould-have
- ai-native userSubscribe to events via webhooksshould-have
- ai-native userGet AI-generated insights and suggestions from my data inside the productshould-have
- ai-native userSet up automations that run autonomously in the backgroundshould-have
- ai-native userOperate the product with natural-language commandsshould-have
- ai-native userExplore an interactive API reference with runnable examplesshould-have
- ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)should-have
- ai-native userRely on versioned APIs with a documented deprecation policyshould-have
- ai-native userTest against a sandbox environment without touching production datanice-to-have
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
- ai-native userDefine rules that trigger actions automatically on eventsmust-have
- ai-native userPerform bulk operations across many items at onceshould-have
- ai-native userSchedule recurring jobs or workflowsshould-have
- ai-native userVersion, review, and roll back my automationsnice-to-have
Embedded experience — stories about embedded experience in this arenaEmbedded experience
Stories about embedded experience in this arena
- developerSeller-facing surfaces are embeddable — white-label components or APIs for balances, payouts, and transaction history that live inside my product under my brandshould-have
- 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 paymentsshould-have
- 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 meshould-have
Funds routing — stories about funds routing in this arenaFunds routing
Stories about funds routing in this arena
- 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 objectsmust-have
- 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 documentedshould-have
- 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 documentedshould-have
Marketplace disputes — stories about marketplace disputes in this arenaMarketplace disputes
Stories about marketplace disputes in this arena
- 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 automaticallymust-have
- 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 actorsshould-have
Marketplace payouts — stories about marketplace payouts in this arenaMarketplace payouts
Stories about marketplace payouts in this arena
- 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 sellermust-have
- finance leadInternational sellers get paid properly — local-currency payouts, documented FX handling, and settlement to local bank rails rather than expensive wiresshould-have
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
- ai-native userExport all of my data in open formats and leavemust-have
- ai-native userSelf-host the core productmust-have
- ai-native userDo everything through the API that I can do in the UIshould-have
- ai-native userRead the product's source under an open licenseshould-have
Payfac liability — stories about payfac liability in this arenaPayfac liability
Stories about payfac liability in this arena
- founderThere's a path up the stack — start on the managed model and graduate toward registered payment facilitation with more economics and control, without replatformingshould-have
- 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 printshould-have
- finance leadSeller tax reporting is handled — 1099-K thresholds tracked, forms generated, delivered, and filed, with the data corrections workflow documentedshould-have
Platform agent access — stories about platform agent access in this arenaPlatform agent access
Stories about platform agent access in this arena
- 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 credentialsmust-have
- 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 surfacesshould-have
- 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 flowsshould-have
Platform ledger — stories about platform ledger in this arenaPlatform ledger
Stories about platform ledger in this arena
- 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 pennymust-have
- 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 accountsshould-have
- developerReconciliation is automatable — settlement and balance reports per seller and rolled up, delivered as files or APIs my finance stack consumes on scheduleshould-have
Platform monetization — stories about platform monetization in this arenaPlatform monetization
Stories about platform monetization in this arena
- 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 costsmust-have
- 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 spreadshould-have
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
- ai-native userPrevent my data from being used to train AI modelsmust-have
- ai-native userChoose where my data is stored (region/residency)should-have
- ai-native userControl data retention and deletionshould-have
- ai-native userOpt out of telemetry and usage trackingshould-have
Seller onboarding — stories about seller onboarding in this arenaSeller onboarding
Stories about seller onboarding in this arena
- 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 formsmust-have
- 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 ticketshould-have
- ops userOnboarding friction is tunable — collect the minimum to start selling and gather the rest before payout thresholds, with clear requirements-due states per sellershould-have
Appendix: recorded probes
Hands-on probe recordings — transcripts/videos a human can replay, the strongest evidence tier. Watch them at https://ultrametric.ai/productarena/proofs
- Adyen for Platforms
curl -si -X POST https://checkout-test.adyen.com/v71/payments -H 'Content-Type: application/json' -d '{}' # keyless → 401terminal · recorded 2026-09-15 · exit 0 - Adyen for Platforms
curl -sL https://docs.adyen.com/llms.txt | head -3terminal · recorded 2026-09-15 · exit 0 - Finix
curl -si https://finix.sandbox-payments-api.com/identities | head -3 # keyless → 401terminal · recorded 2026-09-15 · exit 0 - Finix
curl -sL https://docs.finix.com/llms.txt | head -3terminal · recorded 2026-09-15 · exit 0 - Finix
curl -s -X POST https://docs.finix.com/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # keyless initialize completes with serverInfoterminal · recorded 2026-09-15 · exit 0 - Mangopay
curl -si https://api.mangopay.com/v2.01/testclient/users | head -3 # keyless → 401terminal · recorded 2026-09-15 · exit 0 - Mangopay
curl -s -X POST https://docs.mangopay.com/_mcp/server -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # keyless initialize completes with serverInfoterminal · recorded 2026-09-15 · exit 0 - Mangopay
curl -s https://docs.mangopay.com/openapi.json | head -c 120terminal · recorded 2026-09-15 · exit 0 - Rainforest
curl -sL https://docs.rainforestpay.com/llms.txt | head -3terminal · recorded 2026-09-15 · exit 0 - Stripe Connect
curl -si https://api.stripe.com/v1/accounts | head -4 # Connect accounts API, keyless → 401terminal · recorded 2026-09-15 · exit 0 - Stripe Connect
curl -sL https://docs.stripe.com/llms.txt | head -3terminal · recorded 2026-09-15 · exit 0 - Stripe Connect
curl -si -X POST https://mcp.stripe.com/ -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # the remote MCP server Stripe documents at docs.stripe.com/mcpterminal · recorded 2026-09-15 · exit 0 - Tilled
curl -s https://api.tilled.com/v1/payment-intents | head -c 120 # keyless → documented 'tilled-account' header contractterminal · recorded 2026-09-15 · exit 0
Cite as: ProductArena by Ultrametric Inc, Marketplace & Platform Payments arena, rankings as of 2026-09-15 — https://ultrametric.ai/productarena/arena/marketplace-payments
License: © 2026 Ultrametric Inc. Brief quotation of individual verdicts, scores, or evidence excerpts is permitted with attribution to "ProductArena by Ultrametric Inc (ultrametric.ai/productarena)", as is use of the data to evaluate, contest, or contribute corrections. Bulk copying, redistribution, or use to build competing datasets requires prior written permission (see DATA-LICENSE in the repository).
No liability: rankings, verdicts, and scores are research outputs derived from the cited evidence at a point in time, provided "as is", without warranties. Ultrametric Inc accepts no responsibility for procurement, purchasing, or other decisions made in reliance on them — verify against the cited evidence before acting (https://ultrametric.ai/productarena/terms).