Mangopay

Mangopay: What Merchants Need To Know

If you operate a marketplace, platform, or multi-party commerce model, Mangopay offers a wallet-based payments architecture designed for complex flows. This overview explains how Mangopay works, where it fits, the payment methods and currencies it supports, the available integration options, and what to check before you evaluate or implement it.

Where Mangopay Fits For You

Mangopay is positioned for platforms that need to collect, split, hold, convert, and pay out funds to multiple parties while staying in control of the flow. Its product set spans Payments, Wallet, Payout, FX, Identity, and Fraud, with specific use cases called out for product marketplaces, on-demand platforms, financial platforms, and travel and hospitality. If your model involves many sellers or providers and you need programmable routing or escrow-like wallet flows, this structure is relevant.

Mangopay S.A. is an electronic money institution licensed in Luxembourg, and the group also provides UK services through a separate UK entity. That regulatory footing is important if you need e-money accounts and safeguarding under EU or UK rules.

Core Payment Capabilities With Mangopay

Mangopay supports a broad set of card and alternative payment methods. At the card level you can accept Visa, Mastercard, AMEX, Maestro, and France-specific CB. For alternative methods, the documentation lists digital wallets and regional APMs you can enable, including Apple Pay and Google Pay, plus iDEAL, Bancontact, Pay by Bank, BLIK, Bizum, MB WAY, Multibanco, TWINT, Swish, Satispay, Klarna, PayPal, SEPA Direct Debit, and Bacs Direct Debit. Availability is regional by design, for example Bancontact in Belgium or iDEAL bank redirects in the Netherlands. In practice, you select and configure methods based on your markets and business model.

On cards, Mangopay supports standard one-off payments, preauthorizations, and recurring flows. The card guide notes that all card pay-ins may be subject to chargebacks. Where regulations require it, the checkout can present co-branded network choice to the payer.

Currencies And Multi-Currency

Mangopay lists support for a wide set of settlement and transaction currencies in ISO-4217 format, including AED, AUD, CAD, CHF, CNH, CZK, DKK, EUR, GBP, HKD, HUF, ILS, JPY, MXN, NOK, NZD, PLN, RON, SAR, SEK, SGD, TRY, USD, and ZAR. Combined with the FX and multi-currency account products, this allows you to top up, hold, convert, and pay out in multiple currencies where enabled.

Checkout, Tokenization And PCI Scope

You can integrate via Mangopay’s Checkout SDK to power your payment page with minimal code. Key features called out include PCI-DSS-compliant card tokenization, integrated 3-D Secure handling, co-branded card detection, localization, and branding customization. If you prefer lower-level control, the Vault SDK provides client-side tokenization of payment cards so sensitive data does not touch your systems. Direct API endpoints exist for creating card registrations, updating the registration with the tokenization result, and using the resulting CardId for pay-ins.

From a compliance perspective, Mangopay states it is PCI DSS Level 1 for gateway and vault services. Your own PCI scope still applies. The security documentation indicates that platforms typically complete SAQ A-EP when using tokenization or hosted redirects. That division of responsibilities matters for your compliance planning.

Card validation without debit is supported, which is useful when you need to confirm a card and 3DS authentication before a future transaction. Preauthorization flows are also documented, including a 30-day authorization option where funds are reserved and later captured.

Wallet-Based Flows, Payouts And FX

Mangopay’s model centers on wallets. Best practice examples show funds first entering an author’s wallet, then being transferred to a credited user’s wallet, which mirrors the way marketplaces escrow and split proceeds. The Wallet product then connects to Payout for disbursements to bank accounts or other endpoints. The Payout product page highlights the ability to make payouts in batch or in real time to multiple countries, depending on method availability.

If you operate across currencies, the FX product lets you hold, convert, and pay out with webhook events provided for conversions. Mangopay also offers multi-currency accounts and virtual IBANs to help with local collection and reconciliation, which can reduce friction for cross-border flows if you collect in the buyer’s currency and settle to the seller in another.

Fraud, Identity And Compliance

Mangopay ships an Identity product for KYC and KYB checks with coverage for a large number of countries and languages. It integrates with your flows so you can trigger checks when needed, which can reduce onboarding friction for sellers while maintaining compliance.

For risk, Mangopay provides an AI-driven Fraud product and a Profiler SDK that captures device and behavioral signals during a checkout or user session. That data informs real-time risk recommendations and rules. The company positions its fraud capabilities as working across the full customer journey, from registration and login to checkout and payout, and the profiler is built into the Checkout SDK if you want a unified integration. If you are already working with multiple processors, note that Mangopay describes its fraud solution as processor-agnostic, which may be relevant in a multi-acquirer setup.

Reporting, Reconciliation And Disputes

For operations teams, Mangopay documents a reporting service with Echo report types that summarize intents, actions, settlements, and splits. These can be used to reconcile expected money movements to the amounts escrowed and split between parties. The platform exposes webhook event types broadly, so you can subscribe to pay-in results, dispute lifecycle, conversion events, SCA enrollment status, and more.

Dispute handling is outlined in the guides: when a card chargeback occurs, Mangopay creates both a Dispute object and a Repudiation Wallet entry for the amount at issue. Depending on the dispute type, you may be able to contest it by submitting evidence; if the dispute is lost or non-contestable, the platform must settle the repudiation balance. Specific flows differ for certain methods. For example, direct debits have non-contestable windows by scheme, and PayPal disputes are primarily handled in PayPal’s Resolution Center, with Mangopay reflecting results after a case is decided.

Integration At A Glance

If you are estimating implementation effort, the official documentation shows multiple integration paths and tooling:

• Checkout SDK for a code-light, hosted front end that includes tokenization, 3DS, profiler integration, localization, and support for card brands plus APMs such as Apple Pay and Google Pay.

• Vault SDK for client-side card tokenization on web, Android, and iOS, if you want to own the checkout UI while keeping PANs out of scope.

• Direct API endpoints for pay-ins across card and APMs, plus recurring, preauth, and validation flows.

• Webhooks to receive notifications across payments, disputes, conversions, user SCA enrollment, and more.

• Server SDKs and Postman collections to accelerate development and testing.

• Sandbox access with documented test cards and payment method test data.

Supported browser versions are specified for the web SDK, and device SDKs document initialization and version requirements.