> 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 - November 9, 2026

## Changed

### Sandbox: New Unified Bank Wire PayIn object

In Sandbox (only), there is a new harmonized pay-in object return by [GET View a PayIn](/api-reference/payins/view-payin) for the two bank wire variants (with `PaymentType` of `BANK_WIRE`):

* A pre-declared pay-in to a pooled Mangopay account (`ExecutionType` of `DIRECT`)
* A pay-in to a Virtual Account (`ExecutionType` of `EXTERNAL_INSTRUCTION`)

These payment and execution types remain the same in each case, but the shape of the object is now harmonized.

The new object is backwards compatible with both legacy objects to facilitate adoption once it is deployed in Production.

It introduces a new structured `CreditedAccount` object, a simplified `DebitedAccount` (replacing the legacy `DebitedBankAccount`), and `ReconciliationDetails` with the received funds and wire reference. The Virtual Account variant now includes the wire transfer's `TransactionDetails`, which was previously only returned on a pre-declared pay-in. The object also introduces `VirtualAccountId` as a replacement for `BankingAliasId`, with the same value returned in both.

[Read more about the Unified Bank Wire PayIn object](/api-reference/unified-bank-wire-payin-object) **→**

---

## Added

### Sandbox: Endpoint to simulate Bank Wire PayIn processing

In Sandbox (only), there is a new endpoint to execute a pre-declared bank wire pay-in:

* [POST Simulate execution of a Bank Wire PayIn](/api-reference/simulation/simulate-execution-bank-wire-payin)

The endpoint allows you to accept or reject a pay-in created with POST Create a Bank Wire PayIn, moving its `Status` from `CREATED` to `SUCCEEDED` (crediting the wallet) or to `FAILED` (with the `ResultCode` `008500`, simulating a rejection for anti-fraud reasons).

The `PayInId` must exist in Sandbox, have the `Status` of `CREATED`, and have an `Id` beginning with the prefix `payin_wf_` — pay-ins created before this endpoint's release use a different prefix and aren't supported.

This endpoint replaces an action previously only possible via the Sandbox Operations in the [Mangopay Dashboard](https://hub.mangopay.com/).

For more details, see the guidance on [testing bank wires](/testing/payment-methods#pay-in-to-a-pooled-mangopay-account) **→**

---

## Added

### Sandbox: Endpoint to simulate funds arriving on a Virtual Account

In Sandbox (only), there is a new endpoint to execute a pre-declared bank wire pay-in:

* [POST Simulate a bank wire funding notification](/api-reference/simulation/simulate-bank-wire-funding-notification)

The endpoint simulates an incoming bank wire notification to a Virtual Account, as Mangopay would receive in Production. By referencing the IBAN and BIC of the Virtual Account in the `Creditor` fields, you can supply the payment amount and custom wire reference and debtor information.

Provided the Virtual Account's `Status` is `ACTIVE`, a `SUCCEEDED` pay-in object is created automatically and the associated wallet is credited.

This endpoint replaces an action previously only possible via the Sandbox Operations in the [Mangopay Dashboard](https://hub.mangopay.com/).

For more details, see the guidance on [testing bank wires](/testing/payment-methods#pay-in-to-a-virtual-account) **→**