Recipients and payouts

In a payout scenario, as a Requesting PSP, Mangopay will be carrying out VOP checks on recipients and payouts and returning the result in the API response.

Scope

VOP applies to EUR Recipients and Payouts using SCT or SCT Inst. In terms of Recipient properties, this means:

Currency is EUR
PayoutMethod is LocalBankTransfer
Country is a SEPA country

VOP does not apply to non-EUR payouts in SEPA countries, such as SEK payouts to a bank in Sweden (which uses the local scheme RIX). VOP also does not apply to international payouts, such as EUR to a non-SEPA country or, for example, SEK to a SEPA country that isn’t Sweden, both of which use SWIFT.

Note – VOP on Recipients available for all platformsThe VOP checks on Recipients are available for all platforms for anti-fraud purposes.If your platform offers User-Owned Accounts to your users, their payouts are also impacted by VOP and may be blocked.

VOP result API fields

The following endpoints return the Verification of Payee information in the API response:

POST Create a Payout, if the owner of the payout’s RecipientId or BankAccountId has at least one User-Owned Virtual Account
POST Create a Recipient (for all platforms)
GET View a Recipient (for all platforms)

These endpoints return an object parameter, RecipientVerificationOfPayee, containing:

RecipientVerificationId – A unique identifier of the VOP check performed by Mangopay.
RecipientVerificationCheck – The outcome of the VOP check performed by Mangopay, using the details in the Recipient object.
RecipientVerificationMessage – The explanation of the check outcome.

For example:

VOP data in API response

{
    //...
    "RecipientVerificationOfPayee": {
        "RecipientVerificationId": "623d1eff-f24e-4161-b4d2-1ce8385d1376",
        "RecipientVerificationCheck": "MATCH",
        "RecipientVerificationMessage": "Account name fully matches account identifier."
    }
    //...
}

The outcome of the check is given in fields give the result of the VOP check:

Check result	Check message	Scenario	Recommendation
`MATCH`	`Account name fully matches account identifier.`	The account is valid and the account name matches the IBAN.	Proceed with the payout or recipient.
`CLOSE_MATCH`	`Account name partially matches account identifier. Name returned by check: FirstName LastName. Payment made to this account may not reach its intended counterparty.`	The account is valid but the name doesn’t match exactly.	Confirm details with your user before proceeding. Reregister the Recipient if required.
`NO_MATCH`	`Account name does not match account identifier. Payment made to this account may not reach its intended counterparty.`	This account likely belongs to a different owner.	Do not proceed until you confirm the account details with the user.
`MATCH_NOT_POSSIBLE`	Temporary result: `Verification of payee check in progress`	The VOP check is ongoing (see below).	Retrieve final check result and message later using GET View a Recipient or GET View a Payout.
`MATCH_NOT_POSSIBLE`	Final result: `Account name could not be verified. Payment made to this account may not reach its intended counterparty.`	Responding PSP’s verification service is unreachable. The check could not be completed.	Proceed only after confirming the account details with the user.

Caution – Risk of misdirected payoutsFor any final result other than MATCH, there is a risk of the funds not reaching their intended destination. Funds sent to the wrong account may not be recoverable.

Temporary result for asynchronous processing

Mangopay may temporarily return MATCH_NOT_POSSIBLE accompanied by the message Verification of payee check in progress and with an empty RecipientVerificationId. For example:

Non-final VOP result

{
    //...
    "RecipientVerificationOfPayee": {
        "RecipientVerificationId": null,
        "RecipientVerificationCheck": "MATCH_NOT_POSSIBLE",
        "RecipientVerificationMessage": "Verification of payee check in progress"
    }
    //...
}

This non-final state resolves to one of two final states:

A definitive RecipientVerificationCheck value (MATCH, CLOSE_MATCH, or NO_MATCH) with its accompanying message
The final MATCH_NOT_POSSIBLE message: Account name could not be verified. Payment made to this account may not reach its intended counterparty.

On POST Create a Recipient, this asynchronous behavior allows your platform to redirect the User to complete SCA without undue delay. The temporary message is only returned if no response is received from the Responding PSP within 2 seconds. To retrieve the final VOP result, call GET View a Recipient. The final outcome of the VOP check should be established within a matter of minutes, but it may take up to 24 hours in a worst-case scenario. On POST Create a Payout, if a non-final result is returned, you can retrieve the final one via GET View a Payout.

Implementation recommendations

Retrieve and display the RecipientVerificationCheck and RecipientVerificationMessage to your users. These data points are both returned in the RecipientVerificationOfPayee object on GET View a Recipient, POST Create a Recipient, and POST Create a Payout.
Check the VOP result of Recipients using GET View a Recipient before initiating payouts, to avoid funds being sent to the wrong account.

Recipients

Mangopay performs a VOP check on the endpoints:

VOP is only performed on Recipients where:

Currency is EUR
PayoutMethod is LocalBankTransfer
Country is a SEPA country

The GET View a Recipient and POST Create a Recipient endpoints return the VOP result in the RecipientVerificationOfPayee parameter of the API response:

API response - 200 OK

{
    "Id": "rec_01K3V3GWJQBZXQ3HKNWCQCJRXF",
    "Status": "ACTIVE",
    "CreationDate": 1756477551,
    "DisplayName": "ExampleBusinessName EUR FR account",
    "PayoutMethodType": "LocalBankTransfer",
    "RecipientType": "Business",
    "Currency": "EUR",
    "Country": "FR",
    "UserId": "user_m_01JH2Z9GXCCHGFN65T5HDZG4GB",
    "Tag": "Created using the Mangopay API Postman collection",
    "RecipientScope": "PAYOUT",
    "BusinessRecipient": {
        "BusinessName": "ExampleBusinessName",
        "Address": {
            "AddressLine1": "3929 Dickinson Streets",
            "AddressLine2": "Stamm Tunnel",
            "City": "Paris",
            "Region": "Ile de France",
            "PostalCode": "75001",
            "Country": "FR"
        }
    },
    "LocalBankTransfer": {
        "EUR": {
            "IBAN": "FR7630004000031234567890143",
            "BIC": "BNPAFRPPXXX"
        }
    },
		"RecipientVerificationOfPayee": {
			  "RecipientVerificationId": "123456789",
			  "RecipientVerificationCheck": "MATCH",
			  "RecipientVerificationMessage": "Account name fully matches account identifier."
    }
}

The GET View a Recipient endpoint returns the latest VOP check performed for that account. If no check has ever been performed (for existing Recipient objects and Bank Account objects), then a new check will be carried out. The GET View a Bank Account endpoint will not trigger a VOP check nor return any VOP result. Ensure your platform uses GET View a Recipient object to retrieve account information. The Recipient endpoint can be used to retrieve legacy Bank Account objects by using the Bank Account Id as the RecipientId path parameter.

Payouts

Mangopay is introducing VOP checks when your platform requests a payout using POST Create a Payout only if the owner of the payout’s BankAccountId has at least one User-Owned Virtual Account.

Note – VOP only performed on payouts from users with User-Owned AccountsOn POST Create a Payout, the VOP check is only performed if the user has a User-Owned Virtual Account. If not, or if the payout does not use the SCT or SCT Inst rails, then VOP is not performed.The user must have at least one User-Owned Virtual Account from any of their wallets, not necessarily the one from which the payout is requested.

The steps are as follows:

Your platform calls POST Create a Payout.
Mangopay performs Verification of Payee (VOP) using the associated Recipient or Bank Account data (reference in the BankAccountId) by checking the IBAN and account holder name with the Responding PSP (which is the Payee’s bank).
Mangopay returns the VOP result in the API response (which may be a temporary result).
Mangopay proceeds with the payment, unless it is blocked as described in the scenarios below.

Payout scenarios

Match or close match

When Mangopay performs the VOP check with the Responding PSP, if the result is MATCH or CLOSE_MATCH, then the payout request continues.

The POST Create a Payout endpoint returns an HTTP 200 result containing the RecipientVerificationOfPayee fields:

API response - 200 OK

{
    "Id": "po_b_01K3GM8HWNCVDMACCRA0ZZPH02",
    "Tag": "Created using Mangopay API Postman Collection",
    "CreationDate": 1756126005,
    "AuthorId": "user_m_01K075ZBVXGFYAXM7529W2ZS5W",
    "CreditedUserId": null,
    "DebitedFunds": {
        "Currency": "EUR",
        "Amount": 1000
    },
    "CreditedFunds": {
        "Currency": "EUR",
        "Amount": 900
    },
    "Fees": {
        "Currency": "EUR",
        "Amount": 100
    },
    "Status": "CREATED",
    "ResultCode": null,
    "ResultMessage": null,
    "ExecutionDate": null,
    "Type": "PAYOUT",
    "Nature": "REGULAR",
    "CreditedWalletId": null,
    "DebitedWalletId": "wlt_m_01J9KQE9Z2S4G4R867C5H6W5ZV",
    "PaymentType": "BANK_WIRE",
    "BankAccountId": "rec_01K1ZWF7RJG9MEY8VQ0QE2RQ4D",
    "BankWireRef": "Example123",
    "ModeRequested": null,
    "ModeApplied": "PENDING_RESPONSE",
    "FallbackReason": null,
    "EndToEndId": "3b891fba337d45ec874646ac48565964",
    "PaymentRef": null,
    "RecipientVerificationOfPayee": {
      "RecipientVerificationId": "123456789",
      "RecipientVerificationCheck": "MATCH",
      "RecipientVerificationMessage": "Account name fully matches account identifier."
    }
}

Note that the POST request may return a temporary VOP result.

No match or match not possible

If the final result of the VOP check is NO_MATCH or MATCH_NOT_POSSIBLE, then the behavior depends on whether or not your platform has signed the VOP contract amendment. The VOP contract amendment is only applicable to platforms that offer User-Owned Accounts to their users, and payout VOP checks are only performed for these platforms.

If amendment signed

If the amendment is signed, the payout continues and the NO_MATCH or MATCH_NOT_POSSIBLE result is returned in the RecipientVerificationOfPayee object. This behavior can serve as a warning to your platform or the user. The NO_MATCH result means that payment may not reach its intended payee, and your platform should inform the user accordingly. In these cases, the user should check their account details and re-register the Recipient if necessary.

If amendment not signed

If the amendment is not signed, then the payout fails if the final VOP result is NO_MATCH or MATCH_NOT_POSSIBLE. While the POST Create a Payout endpoint may return a 200 OK response, the payout subsequently fails with the ResultCode 121030 –

Verification of Payee failed: account name and IBAN do not match. Please provide matching details to proceed with the payout

Note – Block only applies to UO account holdersThe block is only applied to users who hold a User-Owned Account. For these users, all payouts are blocked regardless of which wallet they are debited from (determined by the owner of the payout’s BankAccountId).The block also only applies to EUR payments via SCT and SCT Inst.Payouts authored by users without User-Owned Accounts will not be VOP checked and therefore not be blocked because of VOP.On Recipients, VOP checks are applied and available to all platforms, regardless of whether they offer User-Owned Accounts or not.

Testing

In Sandbox, Mangopay provides testing data to allow you to simulate different VOP results when you call POST Create a Recipient.

Note – You must use test data to simulate VOP checkMangopay does not perform VOP checks in Sandbox, so you must use the test IBANs and account names below to simulate the different responses.In Sandbox, any Recipient (or legacy Bank Account) created with a different IBAN and account holder name combination always returns MATCH_NOT_POSSIBLE, and the RecipientVerificationId is null, indicating that the check was not attempted.

Tip - Try in PostmanMangopay’s Sandbox API collection contains a dedicated Recipients VOP testing folder with the VOP testing data ready for you to see how it works. For more about setting up your Postman environment, see the Postman guide.

FR business recipient

IBAN	`BusinessName`	VOP result
`FR7630001007941234567890185`	`EuroCorp`	`MATCH`
	`EuroCarp`	`CLOSE_MATCH`
	Any other value	`NO_MATCH`

Insert the data above in the relevant fields when you call POST Create a Recipient, ensuring you follow the schema for a LocalBankTransfer payout method with the Country set to FR and the Currency in EUR.

API request

{
    "DisplayName": "EuroCorp EUR FR account",
    "PayoutMethodType": "LocalBankTransfer",
    "RecipientType": "Business",
    "Currency": "EUR",
    "Country": "FR",
    "Tag": "Created using the Mangopay API Postman collection",
    "RecipientScope": "PAYOUT",
    "BusinessRecipient": {
        "BusinessName": "EuroCorp", 
        "Address": {
            "AddressLine1": "6 rue de la Cité",
            "AddressLine2": "Appartement 3",
            "City": "Paris",
            "Region": "île-de-France",
            "PostalCode": "75003",
            "Country": "FR"
        }
    },
    "LocalBankTransfer": {
        "EUR": {        
            "IBAN": "FR7630001007941234567890185"
        }
    }
}

API response

{
    "Id": "rec_01K6CYKD6MW45X0TFXS8GSMNWH",
    "Status": "PENDING",
    "CreationDate": 1759223854,
    "DisplayName": "EuroCorp EUR FR account",
    "PayoutMethodType": "LocalBankTransfer",
    "RecipientType": "Business",
    "Currency": "EUR",
    "Country": "FR",
    "UserId": "user_m_01K6ATMK6BA01BHGF14P7M1Q95",
    "RecipientScope": "PAYOUT",
    "Tag": "Created using the Mangopay API Postman collection",
    "BusinessRecipient": {
        "BusinessName": "EuroCorp",
        "Address": {
            "AddressLine1": "6 rue de la Cité",
            "AddressLine2": "Appartement 3",
            "City": "Paris",
            "Region": "île-de-France",
            "PostalCode": "75003",
            "Country": "FR"
        }
    },
    "LocalBankTransfer": {
        "EUR": {
            "IBAN": "FR7630001007941234567890185",
            "BIC": "BDFEFRPPCCT"
        }
    },
    "PendingUserAction": {
        "RedirectUrl": "https://sca.sandbox.mangopay.com/?token=sca_019999e9b6f97eb49e77af2505f5a816"
    },
    "RecipientVerificationOfPayee": {
        "RecipientVerificationId": "383db3d8-2bdd-480d-bed8-28bf5be275a9",
        "RecipientVerificationCheck": "MATCH",
        "RecipientVerificationMessage": "Account name fully matches account identifier."
    }
}

DE individual recipient

IBAN	`FirstName`	`LastName`	VOP result
`DE75512108001245126199`	`John`	`Doe`	`MATCH`
	`John`	`Dae`	`CLOSE_MATCH`
	Any other value	Any other value	`NO_MATCH`

API request

{
    "DisplayName": "John Doe EUR DE account",
    "PayoutMethodType": "LocalBankTransfer",
    "RecipientType": "Individual",
    "Currency": "EUR",
    "Country": "DE",
    "Tag": "Created using the Mangopay API Postman collection",
    "RecipientScope": "PAYOUT",
    "IndividualRecipient": {
        "FirstName": "John",
        "LastName": "Doe",
        "Address": {
            "AddressLine1": "Oranienburger Str. 87",
            "City": "Berlin",
            "PostalCode": "10178",
            "Country": "DE"
        }
    },
    "LocalBankTransfer": {
        "EUR": {        
            "IBAN": "DE75512108001245126199"
        }
    }
}

API response

{
    "Id": "rec_01K6CYKD6MW45X0TFXS8GSMNWH",
    "Status": "PENDING",
    "CreationDate": 1759223854,
    "DisplayName": "EuroCorp EUR FR account",
    "PayoutMethodType": "LocalBankTransfer",
    "RecipientType": "Business",
    "Currency": "EUR",
    "Country": "FR",
    "UserId": "user_m_01K6ATMK6BA01BHGF14P7M1Q95",
    "RecipientScope": "PAYOUT",
    "Tag": "Created using the Mangopay API Postman collection",
    "BusinessRecipient": {
        "BusinessName": "EuroCorp",
        "Address": {
            "AddressLine1": "6 rue de la Cité",
            "AddressLine2": "Appartement 3",
            "City": "Paris",
            "Region": "île-de-France",
            "PostalCode": "75003",
            "Country": "FR"
        }
    },
    "LocalBankTransfer": {
        "EUR": {
            "IBAN": "FR7630001007941234567890185",
            "BIC": "BDFEFRPPCCT"
        }
    },
    "PendingUserAction": {
        "RedirectUrl": "https://sca.sandbox.mangopay.com/?token=sca_019999e9b6f97eb49e77af2505f5a816"
    },
    "RecipientVerificationOfPayee": {
        "RecipientVerificationId": "383db3d8-2bdd-480d-bed8-28bf5be275a9",
        "RecipientVerificationCheck": "MATCH",
        "RecipientVerificationMessage": "Account name fully matches account identifier."
    }
}

Technical error cases

The following IBANs allow you to simulate error cases with any account holder name.

IBAN	VOP result	Description
`FR1420041010050500013M02606`	`MATCH_NOT_POSSIBLE`	Simulates a technical error. A `RecipientVerificationId` value is returned, which generally indicates that Mangopay was able to attempt the check but that a technical error occurred.
`FR7630006000011234567890189`	`MATCH_NOT_POSSIBLE`	Simulates a PSP not responding, with delayed response. The `RecipientVerificationId` is `null`, which generally indicates that Mangopay was not able to attempt the check.

View a Recipient

If you use the testing data above, the GET View a Recipient returns the VOP check that was performed at creation, with the same RecipientVerificationId. Otherwise, in Sandbox, the GET View a Recipient for a legacy Bank Account or Recipient created before VOP always returns:

Recipient or Bank Account not using test data

{
//...
    "RecipientVerificationOfPayee": {
        "RecipientVerificationId": null,
        "RecipientVerificationCheck": "MATCH_NOT_POSSIBLE",
        "RecipientVerificationMessage": "Account name could not be verified. Payment made to this account may not reach its intended counterparty."
    }
//...
}

In Production, Mangopay performs a VOP check on all active Recipients and legacy Bank Accounts (unless one was already performed at creation or retrieval). The check result is returned on the GET View a Recipient (but not the legacy GET View a Bank Account).

Payouts

If you use the testing data above, the POST Create a Payout returns the VOP check that was performed at recipient creation, with the same RecipientVerificationId. Otherwise, in Sandbox, the POST Create a Payout returns a nulled object:

Payout created with Recipient not using test data

{
//...
    "RecipientVerificationOfPayee": null,
//...
}

Introduction

Users

SCA

User KYC/KYB verification

Payments

VOP

Payouts

FX services

Echo

Fraud prevention

Scope

VOP result API fields

Temporary result for asynchronous processing

Implementation recommendations

Recipients

Payouts

Payout scenarios

Match or close match

No match or match not possible

If amendment signed

If amendment not signed

Testing

FR business recipient

API request

API response

DE individual recipient

API request

API response

Technical error cases

View a Recipient

Payouts

Introduction

Users

SCA

User KYC/KYB verification

Payments

VOP

Payouts

FX services

Echo

Fraud prevention

Documentation Index

​Scope

​VOP result API fields

​Temporary result for asynchronous processing

​Implementation recommendations

​Recipients

​Payouts

​Payout scenarios

​Match or close match

​No match or match not possible

​If amendment signed

​If amendment not signed

​Testing

​FR business recipient

​API request

​API response

​DE individual recipient

​API request

​API response

​Technical error cases

​View a Recipient

​Payouts

Scope

VOP result API fields

Temporary result for asynchronous processing

Implementation recommendations

Recipients

Payouts

Payout scenarios

Match or close match

No match or match not possible

If amendment signed

If amendment not signed

Testing

FR business recipient

API request

API response

DE individual recipient

API request

API response

Technical error cases

View a Recipient

Payouts