La Verification of Payee aiuta solo se le persone si fidano dei suoi avvisi. Se troppi plăți onesti tornano cum Bijna overeenkomst o Geen overeenkomst, gli utilizatori imparano a ignorăre il segnale — vanificandone lo scop. La soluzione nu este indebolire la Verifică, ma darle un input migliore.
Why false positives happen
The scheme matches the name you send against the titularul contului. Most false positives are formatting differences, not fraud: a missing middle name, initials vs full name, a trading name vs a registered name, accents and transliteration, or extra words like 'Ltd' or 'S.r.l.'.
Input migliore, niciodată puțin falsi allarmi
You can't change how the bank stores the name, but you can control what you send. The closer your input is to the official record, the fewer Bijna overeenkomstes you'll see.
Modi pratici pentru ridurli
- 1 Invia il nume mai ufficiale care hai — la ragione sociale o il nume legal, nu un soprannume.
- 2 Pentru companii, includi un identificativo dell'organizație (es. Partita IVA) astfel il matching nu este solo sul nume.
- 3 Normalise obvious noise (trim whitespace, consistent casing) but don't strip meaningful parts.
- 4 Cattura il nume verificat restituito pe una Bijna overeenkomst e riutilizzalo pentru i plăți futuri.
Turn Bijna overeenkomstes into clean data
A Bijna overeenkomst is an opportunity: show the suggested verified name, let the payer confirm, and store that confirmed form. Over time your records converge on the names banks recognise, and your false-positive rate falls. RoxPay returns the verified name and supports organisation-identifier matching, so you can design this loop into your flow.