Mangopay

Drive the product through a documented public API G

Agent access

Connect an agent via an official MCP server G

Agent access

Delegate tasks to a built-in AI assistant inside the product G

Agentic features

Plug MCP servers into this product so it can use their tools G

Agent access

Download a machine-readable API spec (OpenAPI or equivalent) G

Api quality

Point an agent at llms.txt or agent-oriented docs G

Agent access

Build against official SDKs G

Agent access

Subscribe to events via webhooks G

Agent access

Explore an interactive API reference with runnable examples G

Api quality

Run the product headlessly / in CI for automation G

Agent access

Operate the product with natural-language commands G

Agentic features

Set up automations that run autonomously in the background G

Agentic features

Get AI-generated insights and suggestions from my data inside the product G

Agentic features

Issue scoped/least-privilege API credentials for an agent G

Agent access

Rely on versioned APIs with a documented deprecation policy G

Api quality

Use an official CLI G

Agent access

Test against a sandbox environment without touching production data G

Api quality

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 C

Splits

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 C

Ledger visibility

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 C

Agent onboarding

Define rules that trigger actions automatically on events G

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 C

Dispute handling

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 G

Application fees

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 C

Onboarding api

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 C

Payout schedules

Export all of my data in open formats and leave G

Prevent my data from being used to train AI models G

Self-host the core product G

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 C

Agent money ops

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 C

Holds release

International sellers get paid properly — local-currency payouts, documented FX handling, and settlement to local bank rails rather than expensive wires C

Cross border

Do everything through the API that I can do in the UI G

Seller-facing surfaces are embeddable — white-label components or APIs for balances, payouts, and transaction history that live inside my product under my brand C

Embedded components

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 C

Negative balances

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 C

Global coverage

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 C

Portfolio risk

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 C

Funds custody

Reconciliation is automatable — settlement and balance reports per seller and rolled up, delivered as files or APIs my finance stack consumes on schedule C

Recon exports

Onboarding friction is tunable — collect the minimum to start selling and gather the rest before payout thresholds, with clear requirements-due states per seller C

Progressive requirements

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 C

Responsibility split

Choose where my data is stored (region/residency) G

Control data retention and deletion G

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 G

Buy rates

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 C

Omnichannel

Opt out of telemetry and usage tracking G

Perform bulk operations across many items at once G

Read the product's source under an open license G

Schedule recurring jobs or workflows G

Seller tax reporting is handled — 1099-K thresholds tracked, forms generated, delivered, and filed, with the data corrections workflow documented C

Tax forms

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 C

Seller reporting

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 C

Agentic commerce

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 C

Graduation path

Version, review, and roll back my automations G