Verification of Payee
As part of the Europe's Instant Payments Regulation, Nium is implementing mandatory verification of payee (VoP) checks for all EU Local payouts made by EU-based clients.
This guide outlines how to:
- Proactively validate beneficiary details using the Nium Verify request.
- Enable the name mismatch override in the Nium Portal to control how name mismatches are handled.
This guide also details w hat happens when name mismatch isn't taken into consideration when creating a payout.
Nium will perform a VoP check on every eligible EU local payout, regardless if the client calls the Nium Verify endpoint explicitly or not.
All EU Local payouts from EU-based clients include a VoP check to confirm the beneficiary name matches the account holder name at the destination bank.
- If the names match, the payout is processed.
- If the names do not match, payouts will be rejected by default.
- Clients can enable an override to process these payouts (accepting liability).
Proactive Checks
We recommend using the Nium Verify endpoint to check the name and IBAN before creating a payout.
Step 1: Verify a bank account
Use the Verify a Bank Account request.
Request fields
| Field | Suggested Action |
|---|---|
accountHolderName |
|
iban |
|
currency |
|
invalid |
|
Response fields
| Field | Values |
|---|---|
status | valid or invalid |
derivedAccountDetails.name | match or partial_match |
Step 2: Take action
| VoP Result | Suggested Action |
|---|---|
match | Proceed with payout. |
partial_match | Confirm/correct name or consider enabling an override. |
no_match | Correct name or enable override to proceed. |
invalid | Recheck account details or allow override. |
This gives your team more control and helps avoid payout delays.
Transfer money
If you don’t use the Nium Verify endpoint, Nium still runs a VoP check behind the scenes when the Transfer money request is called.
The outcome of this check, and if the override is enabled, will determine if the payout proceeds.
The request returns the following details:
| VoP Result | override = false (disabled/default) | override = true (enabled) |
|---|---|---|
match | Proceed | Proceed |
partial_match | Reject | Proceed |
no_match | Reject | Proceed |
invalid | Rejecr | Proceed |
Nium Portal
To enable the name mismatch override in Nium Portal:
- Log in to Nium Portal.
- Click:
Configuration → Client settings → Name mismatch for payee verification - Toggle the Approve name mismatch to enable the name mismatch override
- Review and accept the Terms & Conditions
If you have any issues enabling the name mismatch override, reach out to your Nium account manager or Nium Support.
Key Dates
| Date | Milestone |
|---|---|
| Aug 8, 2025 | Initial Client Notification |
| Aug–Sep 2025 | Monthly Reminders |
| Oct 9, 2025 | Enforcement Begins |
Testing
- Use Nium Verify in your sandbox account to test name mismatch.
- Mock responses are available for specific test IBANs.
- Reach out to your Nium account manager or Nium Support to enable sandbox testing.
No Action
If you are EU-regulated and don’t enable the name mismatch override, all transactions with VoP mismatches will be rejected starting October 9, 2025.
FAQs
Q: Is the Nium Verify endpoint mandatory?
A: No. Nium performs VoP checks automatically. But using the Nium Verify endpoint helps you reduce rejections.
Q: Can I still override mismatches?
A: Yes, by enabling the override setting in Nium Portal.
Q: What is the risk of enabling override?
A: You accept liability for payouts made despite a name mismatch.
Resources
Please configure your override setting or integrate the Nium Verify endpoint before October 9, 2025, to avoid disruptions.