Verification of Payee

From October 9, 2025, Nium must comply with the EU’s Instant Payments Regulation, which requires clients to perform a Verification of Payee (VoP) on all EUR Local payouts.

This guide helps explains:

• What changes are happening.
• How payouts will change.
• How to use Nium Verify to improve success rates (optional).

What’s changing

• All EUR local payouts will be required to perform a verification of payee check.
• The check validates that the beneficiary name matches the account holder's name at the destination bank.
• By default, if the names do not match, the payout will be rejected.

note

Nium will perform a verification of payee check on every eligible EUR Local payout, regardless of whether you submit a request to the Nium Verify endpoint.

Client actions

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.

To enable the EU override in Nium Portal:

1. Log in to Nium Portal.
2. Click to Configuration. → Client settings → Verification of Payee Override.
3. Toggle Override default.
4. Review and accept Terms & Conditions.

Verify beneficiaries

To minimize rejections and provide a smoother experience, use the Nium Verify endpoint to verify names before creating payouts.

• Nium Verify
• Test your integration in sandbox using the provided Testing data. Contact Nium Support to enable access.

Example outcomes:

• match: Safe to proceed with creating the payout.
• partial_match: Review/correct name or decide on override.
• no_match: Correct name or enable override if desired.
• invalid: Review account details.

Transfer money

If you don’t call Verify, Nium still checks during the Transfer Money request:

VoP Result	Override Disabled	Override Enabled
match	Proceed	Proceed
partial_match	Reject	Proceed
no_match	Reject	Proceed
invalid	Reject	Proceed

Key dates

Date	Milestone
Aug 8, 2025	Initial client notification
Aug–Sep 2025	Monthly reminders
Oct 9, 2025	Enforcement begins

Testing data

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

Beneficiary account number	Beneficiary name	Expected response	Notes
BE84504754703434	John Smith	Transaction Created	IBAN and name match correctly.
BE84504754703434	J Smith	NAME_MISMATCH_NO_OVERRIDE_ALLOWED	Slight variation triggers partial match.
BE84504754703434	Jane Doe	NAME_MISMATCH_NO_OVERRIDE_ALLOWED	Name does not match account records.
BE48504008294902	John smith	ACCOUNT_INVALID_NO_OVERRIDE_ALLOWED	IBAN not valid; verification of payee returns as invalid.

Sample responses

Partial Match Example

{
    "status": "BAD_REQUEST",
    "message": "Payment validation failed",
    "errors": [
        "beneficiary_name NAME_MISMATCH_NO_OVERRIDE_ALLOWED"
    ]
}

No Match Example

{
    "status": "BAD_REQUEST",
    "message": "Payment validation failed",
    "errors": [
        "beneficiary_name NAME_MISMATCH_NO_OVERRIDE_ALLOWED"
    ]
}

Invalid Account Example

{
    "status": "BAD_REQUEST",
    "message": "Payment validation failed",
    "errors": [
        "beneficiary_name ACCOUNT_INVALID_NO_OVERRIDE_ALLOWED"
    ]
}

note

Transaction will be successfully created if the override setting is True.

FAQs

Q: Is the Nium Verify endpoint mandatory?
A: No. Nium performs VoP checks automatically. However, using the Nium Verify endpoint to verify names helps you reduce payment 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.

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

Resources

• Nium Verify
• Transfer Money
• Support Contact

note

Integrate Nium Verify before October 9, 2025, to avoid disruptions.