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:
CurrencyisEURPayoutMethodisLocalBankTransferCountryis 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 platforms
The 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
RecipientIdorBankAccountIdhas 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:
The outcome of the check is given in fields give the result of the VOP check:
Caution – Risk of misdirected payouts
For 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:
This non-final state resolves to one of two final states:
- A definitive
RecipientVerificationCheckvalue (MATCH,CLOSE_MATCH, orNO_MATCH) with its accompanying message - The final
MATCH_NOT_POSSIBLEmessage: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
RecipientVerificationCheckandRecipientVerificationMessageto your users. These data points are both returned in theRecipientVerificationOfPayeeobject 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:
CurrencyisEURPayoutMethodisLocalBankTransferCountryis 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:
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.
If the user doesn’t have at least one User-Owned Virtual Account, or if the payout does not use the SCT or SCT Inst rails, then VOP is not performed.
Note – VOP only performed on payouts from users with User-Owned Accounts
On 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:
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 holders
The 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 check
Mangopay 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.
Best practice - Try in Postman
Mangopay’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
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
API response
DE individual recipient
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 DE and the Currency in EUR.
Follow the examples below.
API request
API response
Technical error cases
The following IBANs allow you to simulate error cases with any account holder name.
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:
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: