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

# API - June 23, 2026

## Added

### Webhook event types for user KYC/KYB renewal

> **Note**
>
> **Note – Feature being rolled out during 2026**
>
> Mangopay's continuous KYC/KYB verification feature is being rolled out during 2026.
>
> The webhook event types below can already be set up [via the API](/webhooks) or the [Mangopay Dashboard](https://hub.mangopay.com/). Notifications will start being sent before August 31st, 2026, and the first renewal-related downgrades are scheduled for December 1st, 2026.
>
> Read more about the forthcoming features and rollout for [KYC/KYB renewal](/guides/users/verification/renewal#rollout) **→**

To support Mangopay's forthcoming continuous KYC/KYB verification feature, two new webhooks event types are available.

<table>
  <tr>
    <th class="header">
      Event type
    </th>

    <td class="table-content">
      `USER_KYC_RENEWAL_REQUIRED`
    </td>
  </tr>

  <tr>
    <th class="header">
      Description
    </th>

    <td class="table-content">
      The User’s `KycRenewalDeadline` is in 90 days.

      \


      If the KYC/KYB verification process is not successfully completed before the end of this date (UTC), then the User's `KYCLevel` will be downgraded to `LIGHT` the following day.

      \


      As a result, the User will be subject to the same KYC/KYB limits as an unverified user. For platforms in the EEA, this means they will be unable to request payouts.
    </td>
  </tr>
</table>

<table>
  <tr>
    <th class="header">
      Event type
    </th>

    <td class="table-content">
      `USER_KYC_RENEWED`
    </td>
  </tr>

  <tr>
    <th class="header">
      Description
    </th>

    <td class="table-content">
      The User has successfully completed the KYC/KYB verification process and a new `KycRenewalDeadline` has been set.

      \


      The User's `KYCLevel` has not changed and remains `REGULAR`.
    </td>
  </tr>
</table>

\


The `RessourceId` on both webhooks is the `UserId`.

Once you receive a notification, you will be able to call the [GET View a User’s regulatory status](/api-reference/user-regulatory-status/view-user-regulatory-status) endpoint to retrieve the `KycRenewalDeadline`.

Read more about [KYC/KYB renewal](/guides/users/verification/renewal) **→**

---

Added

### Recurring payment support for Apple Pay and Google Pay

Platforms can now offer recurring payments with Apple Pay and Google Pay.

The feature relies on the existing [POST Create a Recurring PayIn Registration](/api-reference/recurring-payin-registrations/create-recurring-payin-registration) endpoint, which now supports new `PaymentType` values – `APPLEPAY` and `GOOGLE_PAY` – as well as accepting the `PaymentData` retrieved from the payment method's API.

Once in place, the `RecurringPayinRegistrationId` enables you to request CIT and MIT payments with the new endpoints:

* [POST Create a Recurring Apple Pay PayIn](/api-reference/apple-pay/create-recurring-apple-pay-payin)
* [POST Create a Recurring Google Pay PayIn](/api-reference/google-pay/create-recurring-google-pay-payin)

Read more about:

* [Recurring payments with Apple Pay](/guides/payment-methods/apple-pay#recurring-payments) **→**
* [Recurring payments with Google Pay](/guides/payment-methods/google-pay#recurring-payments) **→**