> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mangopay.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Mangopay Echo

Thanks to Mangopay's flexible wallet system, platforms are able to use third-party acquirers instead of Mangopay pay-ins and then benefit from Mangopay's wallet and payout capabilities.

Mangopay Echo is a unified solution for platforms to declare payments not acquired by Mangopay but which then transit the Mangopay environment as part of the workflow.

In Echo, the payment authorization is declared as an Intent, and its subsequent lifecycle is declared as actions against the Intent – Intent Capture or else Intent Refund or Intent Dispute.

Tracking the externally processed payment in Intents allows the payments to be correctly reconciled against the funds that are received on the platform's escrow wallet.

See the integration guide for an [overview of the solution](/guides/echo/integration) **→**

### Flow types

Mangopay Echo is applicable to platforms acquiring funds for goods or services sold by your platform directly (first-party or **1P transactions**), as well as for goods or services sold by third-party sellers on your platform (third-party or **3P transactions**).

Read more about the difference this makes when [declaring Intents](/guides/echo/integration) **→**

### Echo for Mirakl Connector platforms

Some platforms acquiring with a third-party PSP are also using Mangopay's Mirakl Connector to synchronize their sellers and payouts.

For more details on Echo integration for Mirakl Connector platforms, see the dedicated Mirakl Connector guide on [third-party PSPs with Echo](/guides/echo/mirakl) **→**

{/* 

### Related resources

<CardGroup col={2}>
<Card title="Guide" href="/api-reference/intents/intent-object">
The Intent object
</Card>
<Card title="Guide" href="/api-reference/settlements/settlement-file">
Read about formatting and providing settlement files to Mangopay
</Card>
</CardGroup> */}
