Note – Impacts platforms using vIBANs and User-Owned AccountsThe VOP-related changes only impact:
- Platforms using the Virtual Account or Banking Alias feature
- Platforms whose users hold User-Owned Virtual Accounts
- The Requesting PSP, making the payment request on behalf of their customer, the Payer. Mangopay is a Requesting PSP in a payout scenario, requesting and receiving the results of the VOP check.
- The Responding PSP, who’s customer, the Payee, will receive the funds. Mangopay is a Responding PSP in a pay-in scenario, responding with the VOP data.
What Verification of Payee checks
Verification of Payee checks whether the IBAN and account holder name sent by the Requesting PSP correspond to the combination of that data held by the Responding PSP. The account holder name can be an individual (John Doe) or a business (Acme Corp.). There are 4 possible outcomes: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. |
Account holder name with Mangopay
Because Verification of Payee checks the account holder name, the identity of the account holder is important. Mangopay offers platforms the ability to create two types of virtual IBANs: Collection Accounts and User-Owned Accounts. User-Owned Accounts are created in the name of the platform’ss end user who owns the wallet, while Collection Accounts are created in the name of Mangopay on behalf of the platform. Both types of account exist as Banking Alias and Virtual Account objects, as indicated by theVirtualAccountPurpose
property, with values of COLLECTION
or USER_OWNED
.
The table below summarizes the differences, including the impact on the account holder name which is analyzed during the Verification of Payee check.
Collection account | User-owned account | |
---|---|---|
Purpose | Collection and reconciliation of funds by the platform | User’s acceptance and storing of funds |
Account owner | Mangopay S.A. or Mangopay UK Ltd. | Wallet owner |
Account holder name example | ”MGP PlatformTradingName ” * | “FirstName LastName ” (Natural user) or “Name ” (Legal user) |
Allowed user category | Owner or Payer | Owner |
KYC verification | Not required | Required |
Payouts | Prohibited from the associated wallet, except for refunds returning funds to their origin | Authorized from the associated wallet |
PlatformTradingName
, which is held by Mangopay. Your platform can retrieve it via the GET View a Client endpoint, where it is the Name
property, but it is not visible in the Dashboard. Contact Mangopay via the Dashboard to change it.
Impact for your platform
Pay-ins to virtual IBANs
In a pay-in scenario, as a Responding PSP, Mangopay supplies the account holder name and IBAN to the Requesting PSP.On the pay-in side, VOP impacts all platforms using the Virtual Account or Banking Alias feature.
Recipients and payouts
In a payout scenario, as a Requesting PSP, Mangopay will be carrying out VOP checks on recipients and payouts.On the payout side, the VOP impacts platforms whose users hold a User-Owned Account.In 2026, VOP will be available to all platforms for anti-fraud purposes.