Mangopay Echo
Mangopay’s flexible wallet system lets your platform use third-party acquirers instead of Mangopay pay-ins, while still benefiting from Mangopay’s wallet and payout capabilities.
Mangopay Echo is the unified solution for declaring funds that Mangopay didn’t acquire, but that still transit the Mangopay environment as part of the workflow.
In the Echo product, the payment authorization is declared as an Intent. Its subsequent lifecycle is tracked through actions against that Intent: Intent Capture, Intent Refund, or Intent Dispute.
Tracking the externally processed payment as an Intent lets you reconcile it correctly against the funds Mangopay later receives.
Which integration applies to your platform?
Your platform falls into one of two core categories, and then may need to integrate specific features depending on the payment flows you operate.
1. Select your core integration
Your platform is either using Mangopay’s Mirakl Connector, or not, and the core integration is different for each:
2. Account for your flow types
Your platform may be only operating 3P flows (read more below), or also selling directly to the user in 1P transactions.
This distinction impacts line items in Intents, and applies regardless of the core integration.
3. Account for Mangopay-acquired pay-ins
Your platform may be acquiring pay-ins with Mangopay as well as one or more third-party PSPs, in which case you need to integrate Echo for the Mangopay-acquired flows.
This situation can apply regardless of the core integration, and also alongside 1P flows.
Flow types
Echo applies to three flow types that your platform may be using:
Third-party transactions (3P) — The most common scenario where your platform is an intermediary between a buyer and a seller. The seller on your platform is the beneficiary of the funds.
First-party transactions (1P) — Your platform is the seller, selling directly to the buyer (as in standard e-commerce). Your platform operator is the beneficiary of the funds.
Your platform may be performing 1P or 3P transactions, or a combination. The difference impacts how Intents are declared – see the section on Intent line items for more details.
In additon to the distinction between 1P and 3P transactions, there is another aspect which impacts your integration if you are also acquiring pay-ins with Mangopay:
Hybrid flows — Your platform acquires pay-ins with both Mangopay and one or more third-party PSPs. Note that this may be the case for 1P or 3P flows (or both).
If this is the case, the hybrid guide describes the integration approach for your platform.
If your platform only aquires funds with a third-party PSP, and so uses Mangopay for its wallet infrastructure and payout capabilities, then the hybrid approach is not applicable.