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

# Terms and conditions

Mangopay terms and conditions (T\&Cs) govern the Mangopay services provided to users via your platform. All Mangopay's T\&Cs are available on the website [terms and conditions](https://mangopay.com/terms-and-conditions) page.

## Scope and requirements

Mangopay's T\&Cs apply to users [categorized as Owners](/guides/users/categories) because they are able to receive payments. Owner users must accept Mangopay's T\&Cs.

As described in the T\&Cs, users not able to receive payments (and thus categorized as Payers), are not bound by the T\&Cs even if they accept them. However, Mangopay's privacy statement does apply to Payers (as well as Owners) – see [the data privacy guide](/guides/users/privacy) for details.

For an Owner user (both [Natural](/api-reference/users/natural-user-object-sca) and [Legal](/api-reference/users/legal-user-object-sca)), your platform attests to Mangopay that they have accepted the T\&Cs by way of the `TermsAndConditionsAccepted` parameter, which must be `true` on all calls for Owners (both POST and PUT). You also need to maintain a record of the date of acceptance on your side that can be provided to Mangopay on request.

Your platform must ensure that Mangopay's T\&Cs are available at all times from your website or app.

Ideally, this should be a dedicated link mentioning the name Mangopay, but if you include a link to Mangopay's T\&Cs in your T\&Cs as described below, then making only yours available is sufficient.

## Including Mangopay's T\&Cs in yours

Given that your platform's users accept your T\&Cs, the best way to handle Mangopay's T\&Cs is to include the link to them within your platform's T\&Cs along with the wordings below.

Doing so means the user can accept both together, for example via a checkbox. If the user is a Payer, it doesn't matter that they accept Mangopay's T\&Cs because they do not apply to them.

When you include a link to Mangopay's T\&Cs inside your own, you need to do so using this wording and providing the relevant link:

> *By accepting these terms and conditions, you accept the Mangopay terms and conditions (T\&Cs) available at **this link** which constitute an agreement between you and Mangopay that governs your use of its services via our platform.*

The link you provide must be to the relevant Mangopay website page for your platform.

> **Note**
>
> **Note – Do not link to the hosted PDF**
>
> The web pages listed below contain the T\&Cs in all available languages as well as previous versions.
>
> You should link to the page provided below rather than linking to a given PDF document.

### Link to provide

Use the table below to identify the link you need to provide:

<table>
  <thead>
    <tr>
      <th class="header">
        Platform based in
      </th>

      <th class="header">
        Contract
      </th>

      <th class="header">
        Mangopay entity contracted with
      </th>

      <th class="header">
        Link to provide
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      EEA

      <td class="table-content">
        All contracts that are not Contract for Electronic Money Services, such as MSA*, Contract for Mangopay Account, MPE**, etc.
      </td>

      <td class="table-content">
        Mangopay S.A.
      </td>

      <td class="table-content">
        [Payment Services – Mangopay S.A.](https://mangopay.com/terms-and-conditions/payment-services)
      </td>
    </tr>

    <tr>
      <td class="table-content">
        Contract for Electronic Money Services
      </td>

      <td class="table-content">
        Mangopay S.A.
      </td>

      <td class="table-content">
        [E-money Services – Mangopay S.A.](https://mangopay.com/terms-and-conditions/e-money)
      </td>
    </tr>

    <tr>
      UK

      <td class="table-content">
        All contracts that are not Contract for Electronic Money Services, such as MSA*, Contract for Mangopay Account, MPE**, etc. signed 

        **before**

         Jan 1, 2024
      </td>

      <td class="table-content">
        Mangopay S.A.
      </td>

      <td class="table-content">
        [Payment Services – Mangopay S.A.](https://mangopay.com/terms-and-conditions/payment-services)
      </td>
    </tr>

    <tr>
      <td class="table-content">
        Contract for Electronic Money Services signed 

        **before**

         Jan 1, 2024
      </td>

      <td class="table-content">
        Mangopay S.A.
      </td>

      <td class="table-content">
        [E-money Services – Mangopay S.A.](https://mangopay.com/terms-and-conditions/e-money)
      </td>
    </tr>

    <tr>
      <td class="table-content">
        All contracts signed 

        **after**

         Jan 1, 2024
      </td>

      <td class="table-content">
        Mangopay U.K. Ltd.
      </td>

      <td class="table-content">
        [E-money Services – Mangopay U.K. Ltd.](https://mangopay.com/en-gb/terms-and-conditions/e-money)
      </td>
    </tr>
  </tbody>
</table>

\* MSA means Mangopay Service Agreement

\*\* MPE means Marketplace Payment Extension (with or without direct settlement)

### Description of Mangopay

Your platform’s terms and conditions should also contain an explanation of Mangopay’s identity and authorization to provide its services. Use the relevant sentence below depending on whether you contracted with Mangopay S.A. or Mangopay U.K. Ltd..

For Mangopay S.A.:

> *Mangopay S.A. is an electronic money institution authorized by the Commission de Surveillance du Secteur Financier (CSSF) in Luxembourg to provide e-money and payment services.*

For Mangopay U.K. Ltd.:

> *Mangopay U.K. Limited is an electronic money institution authorized by the Financial Conduct Authority in the UK to provide e-money and payment services.*

## Related resources

#### [Guide](/guides/users/privacy)

Lean about handling data privacy