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 were acquired by third-party PSPs and that enter 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.
Note – Mandatory integration for third-party PSP funds
Mangopay is responsible for maintaining appropriate monitoring, traceability and reconciliation of funds received from third-party PSPs. To support these objectives, Mangopay has introduced Echo product, a technical solution designed to provide more granular transaction-level information and enable systematic reconciliation of funds received from third-party PSPs.
To accept funds from a third-party PSP, Mangopay must reconcile them against a declared payment authorization — this is Echo’s function. Your platform declares the PSP’s acquisition of funds in advance, so Mangopay can reconcile them against the Intent when the funds are received.
Echo integration is mandatory to work with one or more third-party PSPs for acquisition while still benefiting from Mangopay’s wallet and payout infrastructure.
Which integration applies to your platform?
All platforms working with at least one third-party PSP must integrate Echo.
There are two core integration possibilities depending on whether you’re using the Mirakl Connector or not, and then other differences depending on the flows you operate.
Core integration
Your platform is either using Mangopay’s Mirakl Connector, or not, and the core integration is different for each:
Approach for line items
In addition to your core integration above, your platform also needs a specific approach for Intent line items, depending on the type of flows you are operating.
Third-party transactions (3P) are the most common scenario: your platform is an intermediary between a buyer and a seller, and the seller on your platform is the beneficiary of the funds.
First-party transactions (1P) are where your platform is the seller, selling directly to the buyer (as in standard e-commerce), and your platform operator is the beneficiary of the funds.
Your platform may be handling 1P or 3P transactions, or a combination of both. This distinction impacts line items in Intents, and applies regardless of the core integration.
If Mangopay is also your acquirer
Lastly, in addition to your core Echo integration and your approach for line items, your platform may be acquiring pay-ins with Mangopay alongside your third-party PSP.
Mangopay refers to this as a hybrid model, which may apply whether your platform operates 1P flows, 3P flows, or both. In this case, you also need to integrate Echo for the Mangopay-acquired flows.