Skip to content

Marketplace & Platform Payments Arena

Marketplace & Platform Payments arenaBuyer checklist

Every requirement we judge marketplace & platform payments products against, as a ready-to-send RFP checklist — with each item's priority, why it matters, and how the top-ranked products score on it today.

53 requirements · 13 themes · verdicts for 6 products · updated 2026-09-15 · priorities mirror the story weights our scoring uses (methodology)

Procurement report →
Show the markdown export
# Marketplace & Platform Payments — buyer checklist (RFP)

Derived from ProductArena's evidence-graded user-story taxonomy for Marketplace & Platform Payments: 53 judged requirements. Priorities mirror story weights (3 = must-have, 2 = should-have, 1 = nice-to-have).

## Agenticness

- [ ] **[must-have]** Plug MCP servers into this product so it can use their tools
- [ ] **[must-have]** Connect an agent via an official MCP server
- [ ] **[must-have]** Drive the product through a documented public API
- [ ] **[must-have]** Delegate tasks to a built-in AI assistant inside the product
- [ ] **[should-have]** Point an agent at llms.txt or agent-oriented docs
- [ ] **[should-have]** Run the product headlessly / in CI for automation
- [ ] **[should-have]** Use an official CLI
- [ ] **[should-have]** Issue scoped/least-privilege API credentials for an agent
- [ ] **[should-have]** Build against official SDKs
- [ ] **[should-have]** Subscribe to events via webhooks
- [ ] **[should-have]** Get AI-generated insights and suggestions from my data inside the product
- [ ] **[should-have]** Set up automations that run autonomously in the background
- [ ] **[should-have]** Operate the product with natural-language commands
- [ ] **[should-have]** Explore an interactive API reference with runnable examples
- [ ] **[should-have]** Download a machine-readable API spec (OpenAPI or equivalent)
- [ ] **[should-have]** Rely on versioned APIs with a documented deprecation policy
- [ ] **[nice-to-have]** Test against a sandbox environment without touching production data

## Automation depth

- [ ] **[must-have]** Define rules that trigger actions automatically on events
- [ ] **[should-have]** Perform bulk operations across many items at once
- [ ] **[should-have]** Schedule recurring jobs or workflows
- [ ] **[nice-to-have]** Version, review, and roll back my automations

## Embedded experience

- [ ] **[should-have]** Seller-facing surfaces are embeddable — white-label components or APIs for balances, payouts, and transaction history that live inside my product under my brand
- [ ] **[should-have]** In-person works on the same stack — terminals or tap-to-pay SDKs that settle into the same seller balances and reporting as online payments
- [ ] **[should-have]** Sellers can self-serve their money questions — per-seller statements, payout reconciliation reports, and exports that let their bookkeeper close the month without contacting me

## Funds routing

- [ ] **[must-have]** Split 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
- [ ] **[should-have]** Funds 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
- [ ] **[should-have]** Refunds and chargebacks that exceed a seller's balance are recoverable — automatic debits against future earnings or their bank account, with the liability order documented

## Marketplace disputes

- [ ] **[must-have]** Disputes 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
- [ ] **[should-have]** Watch 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

## Marketplace payouts

- [ ] **[must-have]** Payouts 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
- [ ] **[should-have]** International sellers get paid properly — local-currency payouts, documented FX handling, and settlement to local bank rails rather than expensive wires

## Openness

- [ ] **[must-have]** Export all of my data in open formats and leave
- [ ] **[must-have]** Self-host the core product
- [ ] **[should-have]** Do everything through the API that I can do in the UI
- [ ] **[should-have]** Read the product's source under an open license

## Payfac liability

- [ ] **[should-have]** There's a path up the stack — start on the managed model and graduate toward registered payment facilitation with more economics and control, without replatforming
- [ ] **[should-have]** The 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
- [ ] **[should-have]** Seller tax reporting is handled — 1099-K thresholds tracked, forms generated, delivered, and filed, with the data corrections workflow documented

## Platform agent access

- [ ] **[must-have]** An 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
- [ ] **[should-have]** An agent can work the money side — read balances and payouts, investigate a seller's missing payout, draft dispute evidence — against documented, agent-usable surfaces
- [ ] **[should-have]** The 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

## Platform ledger

- [ ] **[must-have]** The 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
- [ ] **[should-have]** Platform 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
- [ ] **[should-have]** Reconciliation is automatable — settlement and balance reports per seller and rolled up, delivered as files or APIs my finance stack consumes on schedule

## Platform monetization

- [ ] **[must-have]** Payments 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
- [ ] **[should-have]** I 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

## Privacy posture

- [ ] **[must-have]** Prevent my data from being used to train AI models
- [ ] **[should-have]** Choose where my data is stored (region/residency)
- [ ] **[should-have]** Control data retention and deletion
- [ ] **[should-have]** Opt out of telemetry and usage tracking

## Seller onboarding

- [ ] **[must-have]** Onboard 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
- [ ] **[should-have]** Sellers 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
- [ ] **[should-have]** Onboarding friction is tunable — collect the minimum to start selling and gather the rest before payout thresholds, with clear requirements-due states per seller

---

Source: https://ultrametric.ai/productarena/arena/marketplace-payments (evidence-graded verdicts for 6 products) · methodology: https://ultrametric.ai/productarena/methodology

Chips show the top 5 ranked products' current verdict on each requirement — ✓ full · ~ partial · ! disputed · — none · n/a not applicable.

Agenticness — how well agents can access and operate the productAgenticness· 17 items

How well agents can access and operate the product

Automation depth — how much of the product can run unattendedAutomation depth· 4 items

How much of the product can run unattended

Embedded experience — stories about embedded experience in this arenaEmbedded experience· 3 items

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 brand

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-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 payments

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-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 me

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have

Funds routing — stories about funds routing in this arenaFunds routing· 3 items

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 objects

    Core requirement — weighs 3× in arena scoring · no product fully delivers this yet

    must-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 documented

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-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 documented

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have

Marketplace disputes — stories about marketplace disputes in this arenaMarketplace disputes· 2 items

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 automatically

    Core requirement — weighs 3× in arena scoring · no product fully delivers this yet

    must-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 actors

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have

Marketplace payouts — stories about marketplace payouts in this arenaMarketplace payouts· 2 items

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 seller

    Core requirement — weighs 3× in arena scoring · 2 of 6 products fully deliver this today

    must-have
  • finance leadInternational sellers get paid properly — local-currency payouts, documented FX handling, and settlement to local bank rails rather than expensive wires

    Important, not disqualifying — weighs 2× in arena scoring · 1 of 6 products fully deliver this today

    should-have

Openness — open source, data portability, and self-hosting storiesOpenness· 4 items

Open source, data portability, and self-hosting stories

Payfac liability — stories about payfac liability in this arenaPayfac liability· 3 items

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 replatforming

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-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 print

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have
  • finance leadSeller tax reporting is handled — 1099-K thresholds tracked, forms generated, delivered, and filed, with the data corrections workflow documented

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have

Platform agent access — stories about platform agent access in this arenaPlatform agent access· 3 items

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 credentials

    Core requirement — weighs 3× in arena scoring · no product fully delivers this yet

    must-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 surfaces

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-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 flows

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have

Platform ledger — stories about platform ledger in this arenaPlatform ledger· 3 items

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 penny

    Core requirement — weighs 3× in arena scoring · no product fully delivers this yet

    must-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 accounts

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have
  • developerReconciliation is automatable — settlement and balance reports per seller and rolled up, delivered as files or APIs my finance stack consumes on schedule

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have

Platform monetization — stories about platform monetization in this arenaPlatform monetization· 2 items

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 costs

    Core requirement — weighs 3× in arena scoring · 1 of 6 products fully deliver this today

    must-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 spread

    Important, not disqualifying — weighs 2× in arena scoring · 1 of 6 products fully deliver this today

    should-have

Privacy posture — data-handling and privacy storiesPrivacy posture· 4 items

Data-handling and privacy stories

Seller onboarding — stories about seller onboarding in this arenaSeller onboarding· 3 items

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 forms

    Core requirement — weighs 3× in arena scoring · 3 of 6 products fully deliver this today

    must-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 ticket

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-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 seller

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have

Full evidence behind every verdict lives on the arena page and each product page — chips above deep-link straight to the judged story.