- The Payer initiates the payment to a virtual IBAN, providing the payee’s IBAN and account holder name to their bank.
- The Payer’s bank, the Requesting PSP, performs the Verification of Payee check with Mangopay.
- Mangopay, the Responding PSP, checks the name of the payee against the IBAN provided by the Requesting PSP, and responds with a result. The check result is not visible to the your platform in the Mangopay API.
- The Requesting PSP displays the VOP result to the Payer in their banking app or other interface. The Requesting PSP has discretion over what it displays to the Payer and how it handles the result, wether payment is automatic or upon confirmation by the Payer, for example.
VOP results
There are 4 possible outcomes of the VOP check:Result | Explanation | Impact |
---|---|---|
Match | The IBAN and account holder name correspond. | Payment made to this account will reach its intended counterparty. |
Close Match | There are minor discrepancies (such as typos) between the name requested and the one registered. | Payment made to this account may not reach its intended counterparty. |
No Match | The details do not match, indicating a possible error or fraudulent attempt. | Payment made to this account may not reach its intended counterparty. |
Match Not Possible | A technical issue prevents verification from being carried out, such as formatting errors or the responding service being unreachable. | Payment made to this account may not reach its intended counterparty. |
Integration recommendations
- Ensure that the Payer can easily see and copy the relevant value in your platform’s interface:
AccountOwner
returned on GET View a Virtual AccountOwnerName
returned on GET View a Banking Alias
- If your platforms is using the Banking Alias endpoints, plan to re-integrate using the the Virtual Accounts endpoints for greater control over the naming pattern, as well as all future feature developments.
Id
and its WalletId
as the path parameters.
This means your platform can already integrate the GET to retrieve the account data of Banking Alias objects.
- If your platform is using the Bank Wire PayIn endpoint, ensure Payers are provided the
BankAccount.OwnerName
returned in the response of POST Create a Bank Wire PayIn. Note that for direct bank wire pay-ins, Mangopay is not the responding PSP – that role is played by its partners.
Banking Alias categorization
The legacy Banking Alias object (replaced by Virtual Accounts) did not allow for accounts to be categorized between Collection and User-Owned. VOP makes this categorization necessary because Mangopay must provide the correct account holder name data to the Requesting PSP. TheVirtualAccountPurpose
field has been added to the Banking Alias object to enable categorization.
The categorization applies to all Banking Alias objects, including those with the Country
value GB
.
Criteria for Banking Alias categorization
User-Owned case
IF the User owning the Banking Alias object’sWalletId
has:
- The
UserCategory
ofOWNER
orPLATFORM
- AND the
KYCLevel
ofREGULAR
- The
USER_OWNED
value is assigned forVirtualAccountPurpose
- AND the account’s
OwnerName
will be defined as theFirstName
andLastName
for a Natural User orName
for a Legal User
Note – Payouts from User-Owned Account holders may be blockedRead more about how payouts made by User-Owned Account holders are impacted by Verification of Payee.
Collection case
IF the User owning the Banking Alias object’sWalletId
has:
- The
UserCategory
ofPAYER
- OR the
KYCLevel
ofLIGHT
- The
COLLECTION
value is assigned forVirtualAccountPurpose
- AND the account’s
OwnerName
is changed to “MGPPlatformTradingName
”
Example categorization
Account OwnerName before categorization | User’s UserCategory | User’s KYCLevel | Account OwnerName after categorization | VirtualAccountPurpose after categorization |
---|---|---|---|---|
John Doe | PAYER | LIGHT | MGP PlatformTradingName | COLLECTION |
John Doe | OWNER | LIGHT | MGP PlatformTradingName | COLLECTION |
John Doe | PAYER | REGULAR | MGP PlatformTradingName | COLLECTION |
John Doe | OWNER | REGULAR | John Doe | USER_OWNED |
One-time categorization for existing accounts
Starting Monday, September 15, 2025, Mangopay will categorize existing and newly created Banking Aliases by setting theVirtualAccountPurpose
value to either COLLECTION
or USER_OWNED
.
In some cases, the OwnerName
value will be changed to rename the account holder correctly, as described above.
Once the one-time categorization is performed, it is final and cannot be changed. This means that the VirtualAccountPurpose
will not subsequently be changed if the user becomes KYC verified, for example; a new wallet and virtual account would need to be created in future.
Ongoing categorization for new accounts
The categorization will also apply to newly created Banking Alias objects. Platforms using the POST Create a Banking Alias endpoint should take this into account:- The
OwnerName
property is still required but ignored and set automatically by Mangopay. Platforms use theOwnerName
provided in the response or retrieve it systematically via the GET View a Banking Alias endpoint. - The
VirtualAccountPurpose
is set automatically by Mangopay on creation.