Mangopay API

Regulated European e-money and marketplace payments infrastructure. Mangopay provides a white-label wallet and payment routing system for platforms: each user gets a wallet, money flows between wallets with full audit trails, and payouts go to bank accounts after KYC verification. Unlike Stripe Connect, Mangopay is an e-money institution licensed under EU regulations, making it suitable for marketplaces that need to hold funds on behalf of users for extended periods. Supports card payments, bank transfers (SEPA/SWIFT), and local European payment methods.

Evaluated Mar 06, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Other mangopay marketplace payments e-money escrow split-payments kyc wallets europe regulated
⚙ Agent Friendliness
53
/ 100
Can an agent use this?
🔒 Security
82
/ 100
Is it safe for agents?
⚡ Reliability
76
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
--
Documentation
78
Error Messages
72
Auth Simplicity
72
Rate Limits
65

🔒 Security

TLS Enforcement
100
Auth Strength
82
Scope Granularity
65
Dep. Hygiene
80
Secret Handling
80

Licensed e-money institution under French ACPR, regulated under EU PSD2 and EMD2. Full KYC/AML compliance built into the platform. Data stored in EU. TLS enforced on all endpoints. OAuth2 tokens limit credential exposure. No per-scope granularity — credentials are all-or-nothing.

⚡ Reliability

Uptime/SLA
80
Version Stability
78
Breaking Changes
75
Error Recovery
72
AF Security Reliability

Best When

Your platform is European or EU-focused, you need to hold user funds in regulated e-money wallets (not just route payments through), and KYC/AML compliance must be built into the payment flow.

Avoid When

Your users are primarily outside the EU, you need same-day or instant payouts, or your transaction volume makes Mangopay's per-transaction fees prohibitive compared to Stripe Connect.

Use Cases

  • European marketplace platforms (rental, freelance, e-commerce) needing licensed e-money wallet infrastructure for buyer/seller fund holding
  • Escrow services where funds must be held in regulated wallets before release on contract completion
  • Crowdfunding platforms that collect payments and hold in escrow until funding goals are met
  • Platforms in regulated industries (real estate, lending) needing full KYC/AML compliance built into the payment flow
  • Multi-currency European marketplaces needing SEPA direct debit, bank wire, and card payment with automatic FX

Not For

  • Global platforms with significant non-European user bases — Mangopay's core strength is EU/EEA coverage
  • Simple single-party payment processing where Stripe standard is cheaper and simpler
  • Platforms needing instant real-time payouts at low cost — Mangopay payouts typically process in 1-3 business days

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
No
SDK
Yes
Webhooks
Yes

Authentication

Methods: oauth2-client-credentials
OAuth: Yes Scopes: No

OAuth2 Client Credentials flow using ClientId and API Key. Access tokens have a 1-hour TTL and must be refreshed. Sandbox and production use different base URLs and separate credentials. No per-operation scope granularity — the client credentials grant full API access.

Pricing

Model: pay-as-you-go
Free tier: No
Requires CC: No

Pricing is not publicly listed — requires sales engagement. Fees tend to be higher than Stripe for low-volume platforms but more favorable terms for marketplaces needing the regulatory compliance features.

Agent Metadata

Pagination
offset
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • OAuth2 access tokens expire after 1 hour; agents with long-running sessions must implement token refresh logic — using an expired token returns a 401 that looks identical to a bad credential error, making it hard to distinguish token expiry from auth misconfiguration
  • The sandbox and production environments are completely isolated with different client IDs, API keys, and base URLs (api.sandbox.mangopay.com vs api.mangopay.com); agents that hardcode URLs will need environment-specific configuration, and sandbox test users/wallets cannot be migrated to production
  • KYC document submission is asynchronous — uploading a KYC document returns immediately but the validation status (VALIDATED or REFUSED) comes back via webhook hours or days later; agents building onboarding flows cannot confirm KYC synchronously
  • Wallet-to-wallet transfers are immediate but payouts (wallet to bank account) require the user to be KYC-verified; attempting a payout for an unverified user returns a ResultCode 003-001 error with a message that does not clearly indicate the KYC issue without consulting the documentation
  • Pagination uses page and per_page query parameters with a maximum of 100 items per page; the total count is returned in a header (X-Number-Of-Items and X-Number-Of-Pages), not in the response body — agents that parse only the response body will not know how many pages remain

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Mangopay API.

$99

Scores are editorial opinions as of 2026-03-06.

5178
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered