What does Verification of Payee change for payment operators?

Operators that pay out to merchants or accept bank transfers need correct account names on file, because transfers to mismatched names trigger warnings. Clean KYB data from merchant onboarding and account-to-account rails connected to the platform reduce those failures.

Where the check bites

Since October 2025, every SEPA transfer in the euro area is checked against the name on the destination account before it is sent. A mismatch returns a warning to the payer, who may cancel. For a payment operator, that touches two flows: payouts sent to merchants and account-to-account payments collected from customers.

Payouts to merchants

• The beneficiary name on file must be the account holder's exact legal name, not a trading name.
• Merchant onboarding should capture the name from a bank document and store the IBAN with it.
• A "close match" or "no match" result on a payout batch needs a workflow: hold, verify, correct, resend.

Collections from customers

When a customer pays by transfer or request to pay, the operator's collection account must carry a name the customer recognizes, usually the merchant's brand or the operator's. A mismatch warning at that step costs conversion. Operators that route account-to-account payments should check how each rail presents the payee name and keep it consistent with the checkout.

The upside

Fewer misdirected payouts, fewer recalls and a cleaner KYB file. The name check is a constraint only for operators whose merchant data was never verified.