> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.mangopay.com/guides/echo/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mangopay.com/_mcp/server.

# Echo

## Docs

- [How Echo works](https://docs.mangopay.com/guides/echo/reconciliation.md)
- [Echo integration](https://docs.mangopay.com/guides/echo/integration.md)
- [Refunds and disputes](https://docs.mangopay.com/guides/echo/refunds-disputes.md): How to handle refunds and disputes at different stages of the Echo payment lifecycle
- [Hybrid flows](https://docs.mangopay.com/guides/echo/hybrid.md): How to integrate Echo when your platform acquires pay-ins with both Mangopay and a third-party PSP
- [Echo reports](https://docs.mangopay.com/guides/echo/reports.md): List intents, intent actions, settlements and splits


> **Note:** This page contains both a page directory (above) and the landing page content (below). The page directory is generated for agent use and does not appear on the landing page.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.mangopay.com/guides/echo/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mangopay.com/_mcp/server.

# 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 later received in the Mangopay environment.

### 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:

<table>
  <thead>
    <tr>
      <th class="header">
        Your setup
      </th>

      <th class="header">
        Core guide
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td class="table-content">
        Using Mangopay's 

        [Mirakl Connector](/connectors/mirakl)

         to sync sellers and payouts
      </td>

      <td class="table-content">
        [Echo for Mirakl Connector](/guides/echo/mirakl)
      </td>
    </tr>

    <tr>
      <td class="table-content">
        Not using the Mirakl Connector
      </td>

      <td class="table-content">
        [Echo for standard API integration](/guides/echo/integration)
      </td>
    </tr>
  </tbody>
</table>

#### 2. Account for your flow types

Your platform may be only operating 3P flows ([read more below](#flow-types)), or also selling directly to the user in 1P transactions.

This distinction impacts line items in Intents, and applies regardless of the core integration.

<table>
  <thead>
    <tr>
      <th class="header">
        Your flows
      </th>

      <th class="header">
        Approach for Intent line items
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td class="table-content">
        3P only: The seller is the beneficiary; your platform is always the intermediary
      </td>

      <td class="table-content">
        [Intent line items for 3P only](/guides/echo/integration#line-items)
      </td>
    </tr>

    <tr>
      <td class="table-content">
        Both 3P and 1P: Your platform is selling directly as the beneficiary in some transactions
      </td>

      <td class="table-content">
        [Intent line items for 3P and 1P](/guides/echo/integration##first-party-transactions-1p)
      </td>
    </tr>
  </tbody>
</table>

#### 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.

<table>
  <thead>
    <tr>
      <th class="header">
        Your acquirer(s)
      </th>

      <th class="header">
        Integration approach
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td class="table-content">
        Third-party PSPs only (and not Mangopay)
      </td>

      <td class="table-content">
        No additional integration
      </td>
    </tr>

    <tr>
      <td class="table-content">
        Mangopay and third-party PSP(s)
      </td>

      <td class="table-content">
        [Hybrid integration guide](/guides/echo/hybrid)
      </td>
    </tr>
  </tbody>
</table>

### 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](/guides/echo/integration#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](/guides/echo/hybrid) 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.

## Related resources

#### [Guide](/guides/echo/reconciliation)

How Echo works

#### [Guide](/connectors/mirakl/acquiring/echo)

Echo for Mirakl Connector platforms

#### [API reference](/api-reference/intents/intent-object)

Echo Intents and Settlements