Know who you're paying,
before you pay them.
Soundkeel confirms a payment recipient exists and that the name matches the account — in real time, before a bank releases funds. Built on the verification model now becoming mandatory across the EU and UK.
A misdirected payment is quietly the easiest fraud there is
A payment reference or account number is easy to get slightly wrong — by mistake, or by design. Once funds move, getting them back is slow, expensive, and often impossible. Regulators have started requiring banks to close that gap before the money leaves.
Wrong account, right bank
A single mistyped digit sends a payment to a real account that belongs to someone else entirely.
A known fraud pattern
Authorised push payment fraud relies on the sender never confirming who actually holds the receiving account.
Regulation is catching up
The EPC's Verification of Payee rulebook and the UK's Confirmation of Payee scheme now require this check for SEPA and UK transfers.
One check, under a second, zero account data exposed
Soundkeel sits between banks as a switch — it routes the question and records the answer, but never sees an account number or a customer's full identity.
-
1
Sending bank asks
Before releasing a payment, the sending bank sends Soundkeel a payee token and the name the payer entered.
-
2
Soundkeel routes, never reads
The switch forwards the token and name to the receiving bank. The account number itself never leaves that bank.
-
3
Receiving bank matches
The receiving bank compares the name against its own records — the only place that data ever lives — and returns a verdict.
-
4
A verdict, in milliseconds
match close_match no_match unable_to_verify
The sending bank shows the payer a clear signal before they confirm the transfer.
Bank-grade by default, not by request
No PII on the platform
Banks exchange a payee token, never an account number or a full identity. The switch sees tokens and results — nothing else.
Tamper-evident audit
Every request is written to an append-only, hash-chained log. Nothing can be quietly edited or deleted after the fact.
Idempotent by design
A repeated request returns the exact result already on file — never a duplicate call to the receiving bank.
Configuration, not a rebuild
Currencies, match thresholds and branding are configuration per market — the core stays the same everywhere it runs.
Watch two banks verify a payment in real time
Matches, caught typos, closed accounts, timeouts — the full picture, running on a real switch, in under ten minutes.
Request a demo