Skip to main content

⚠️ Nium Migration Guide: Verification of Payee (VoP) for EUR Local Payouts

Verification of Payee

From October 9, 2025, Nium must comply with the EU’s Instant Payments Regulation, which requires a Verification of Payee (VoP) check on all EUR Local payouts. This document explains:

  • What changes are happening
  • How payouts will be impacted
  • How to configure override handling in Nium Portal
  • How to use Nium Verify API to improve success rates (optional)

✅ What’s Changing?​

All EUR Local payouts will undergo a VoP check to verify that the beneficiary name matches the account holder name at the destination bank.

  • If the names match, payouts proceed.
  • If the names do not match, payouts will be rejected by default.
  • Clients may enable override to allow such payouts (accepting liability).

Note:
Nium will perform a VoP check on every eligible EUR Local payout, regardless of whether you call the Verify API explicitly or not.

Client Actions​

1. Decide on Override Handling​

  • Default (no action) → Mismatched payouts will be rejected.
  • Enable override in Nium Portal → Mismatched payouts will proceed, and your organization accepts liability. Steps to enable override in [Nium Portal]:
  1. Log in to Nium Portal.
  2. Navigate to Access menu on left hand side → SEND → Name Mismatch for Payee Verification Configuration.
  3. Toggle Override default.
  4. Review and accept Terms & Conditions.

2. (Optional) Proactively Verify Beneficiaries​

To minimize rejections and provide a smoother payer experience, clients may use the Nium Verify API to check names before initiating payouts.

  • Verify API Reference
  • Test in sandbox using provided IBANs. Contact Nium Support to enable access.
    Example outcomes:
  • match → Safe to proceed with payout
  • partial_match → Review/correct name or decide on override
  • no_match → Correct name or enable override if desired
  • invalid → Review account details

Payout Flow​

VoP Resultoverride = true (enabled)override = false (disabled/default)
match✅ Proceed✅ Proceed
partial_match✅ Proceed❌ Reject
no_match✅ Proceed❌ Reject
invalid✅ Proceed❌ Reject

📅 Key Dates​

DateMilestone
Aug 8, 2025Initial Client Notification
Aug–Sep 2025Monthly Reminders
Oct 9, 2025Enforcement Begins

Mock Data for Testing​

To help you validate your integration and VoP handling logic, Nium provides sandbox test IBANs and account names that simulate different outcomes.

Beneficiary Account NumberBeneficiary NameExpected ResultNotes
BE84504754703434Marc JanssenTransaction CreatedIBAN and name match correctly.
BE84504754703434M JanssenValidation error with message NAME_MISMATCH_NO_OVERRIDE_ALLOWEDSlight variation triggers partial match.
BE84504754703434Jane DoeValidation error with message NAME_MISMATCH_NO_OVERRIDE_ALLOWEDName does not match account records.
BE48504008294902Marc JanssenValidation error with message ACCOUNT_INVALID_NO_OVERRIDE_ALLOWEDIBAN not valid; VoP returns invalid.

Sample Payout API Responses​

No Match Example​

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "beneficiary_name NAME_MISMATCH_NO_OVERRIDE_ALLOWED"
}

Invalid Account Example​

{
  "statusCode": 400,
  "error": "Bad Request",
  "message" : "beneficiary_name ACCOUNT_INVALID_NO_OVERRIDE_ALLOWED"
}
  • Note Transaction will be successfully created if the override setting is True.

❓ FAQs​

Q: Is the /accountVerification API mandatory?
A: No. Nium performs VoP checks automatically. But using /accountVerification helps you manage customer experience and reduce rejections.

Q: Can I still override mismatches?
A: Yes, by enabling the override setting in the portal.

Q: What is the risk of enabling override?
A: You accept liability for payouts made despite a name mismatch.

Q: What happens if I do nothing?
A: From Oct 9, 2025, all EUR Local payouts with mismatched beneficiary names will be rejected.

📘 Resources​

⚠️ Please configure your override setting or integrate /accountVerification before October 9, 2025, to avoid disruptions.