> 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 - Sep 12, 2024 - Peipus

Added

### Pay-in error 008008: Account linked to card does not exist

The following `ResultCode` and `ResultMessage` can be returned on card pay-ins:

* [008008](/errors/codes/008008) - Pay-in failed: the issuing bank reports that the bank account linked to this card does not exist.

This error helps identify cases where the issuing bank has reported that the account linked to the card has been closed or can no longer be used.

Changed

### Migration parameter deprecated on recurring pay-in registration

The `Migration` parameter of the [Recurring PayIn Registration](/api-reference/recurring-payin-registrations/recurring-payin-registration-object) object is deprecated and should no longer be used.

Migration of card pay-ins to a recurring card flow is no longer supported, and recurring pay-in registrations should not be created with `Migration` value of `true`.

Existing objects with `Migration` set to `true` are likely to fail or no longer be usable. This may be indicated by the `Status` changing to `AUTHENTICATION_NEEDED` or by errors on the pay-in request, for example: non-existent card account ([008008](/errors/codes/008008)), soft decline ([101305](/errors/codes/101305)), expired card ([101105](/errors/codes/101105)), or stolen card ([008003](/errors/codes/008003)).

When this happens on an object with `Migration` set to `true`, platforms must create a new recurring pay-in registration without the `Migration` parameter (default value is `false`) to re-initiate the recurrence. This will require re-authentication from the user in a CIT payment.

> **Check**
>
> **Best practice – Restart all legacy migrations**
>
> We strongly recommend that you proactively close any existing recurring pay-in registration objects with `Migration` set to `true` and create new ones to replace them. This will reduce the likelihood of failed payments and give the best experience to your users.

See the [recurring card pay-in](/guides/payment-methods/card/recurring/how-to) how-to guide for details on setting up a new recurring flow.