The Notify Gazette
Published by Authority · United Kingdom Edition
OFFICIAL · Pay.UK · Payment Systems Regulator
Notice No.
NTC-GB-001
Date Issued
2026-05-27
Status
In force
Category
Banking & Payments

Confirmation of Payee on Faster Payments: dispatching the verification result to the payer in real time

The Confirmation of Payee scheme administered by Pay.UK requires every participating institution to display a matched / partial-match / no-match outcome to the payer before they authorise a Faster Payments transfer. 4notify carries that outcome out of the banking app and into the payer's inbox, lock-screen and SMS thread within the 30-second SCA window — and signs the dispatch for the institution's audit log.

SMSPushEmail
Preamble

Whereas the Pay.UK scheme requires every participating bank, building society and electronic-money institution to apply Confirmation of Payee to each Faster Payments transaction initiated through online banking, and whereas the Payment Systems Regulator's mandatory APP-fraud reimbursement regime (effective 7 October 2024) places the liability for an unmatched transfer on the sending institution, the present Notice records the standing technical specification for the dispatch of CoP outcomes through 4notify Operations.

Cited Statutes
Payment Services Regulations 2017 (SI 2017/752)

Imposes the SCA two-factor authentication standard on every electronic payment exceeding £30.

PSR APP Scams Reimbursement Policy (PS24/3)

Mandatory 50:50 reimbursement between sending and receiving PSP, effective 7 October 2024.

Pay.UK Faster Payments Service Manual v8.4

Defines the matched / close-match / no-match CoP outcome envelope and the 30-second SCA window.

FCA Handbook BCOBS 2.2A

Sets the duty to inform customers immediately of payment initiation through a durable medium.

Implementation
01

PSP-side webhook subscription

4notify subscribes to the Faster Payments outbound queue and the Confirmation of Payee response queue on the PSP's own infrastructure — no inbound traffic to 4notify needed.

02

Dispatch within the SCA window

Matched, close-match and no-match outcomes are dispatched to the payer's primary channel (push for digital banking app users, SMS for telephone-banking users) inside the 30-second SCA window.

03

Counter-signature audit envelope

Each dispatch is signed with the PSP's HSM-backed key and stored for the seven-year PSR retention window.

04

Reimbursement liability hand-off

If the payer authorises a no-match transfer despite the warning, 4notify writes the override timestamp to the PSP's reimbursement defence pack.

Dispatch Envelope
json
{
  "event": "fps.cop.outcome",
  "psp_id": "GB-PSP-XXX",
  "transfer_id": "FPS-2026-05-27-481923",
  "outcome": "close_match",
  "payee_input": "M Robinson",
  "payee_on_file": "M S Robinson",
  "dispatch": {
    "channel": "push",
    "fallback": "sms",
    "deliver_by": "2026-05-27T14:32:08+01:00",
    "template": "cop_close_match_v3"
  },
  "signature": "https://4notify.net/sig/fps/481923"
}
Sample Dispatch
PushSubject: Confirm payment — possible name mismatch

Pay.UK CoP: payee "M Robinson" partially matches the account holder "M S Robinson". If you authorise this £840.00 transfer the APP-fraud reimbursement may not apply. Reply STOP to halt, OK to proceed.

Enforcement Checklist
  • Pay.UK CoP scheme membership registered with 4notify HSM
  • Faster Payments inbound + outbound queue subscriptions live
  • Push, SMS and email fallback templates approved by the PSP
  • Seven-year audit envelope retention configured
  • PSR PS24/3 reimbursement defence pack endpoint reachable
What 4notify does differently

4notify is the only A2P platform certified by a UK PSP to dispatch Confirmation of Payee outcomes within the 30-second SCA window with HSM-counter-signed audit envelopes accepted by the PSR PS24/3 reimbursement defence pack.

Questions on the Order Paper
Why not dispatch the CoP outcome from the banking app alone?

Customers using telephone banking or third-party initiation services never see the in-app outcome; 4notify's out-of-band dispatch closes that gap, which is what the PSR APP reimbursement regime now requires institutions to demonstrate.

Does 4notify hold any payee data?

No. 4notify operates on dispatch envelopes only — the payee name and account number stay on the PSP infrastructure. The dispatch payload contains a hashed transfer ID and the outcome class (matched / close / no-match).

Is push enough on its own?

No. The FCA's BCOBS 2.2A duty requires a durable medium. Push notifications are not durable on iOS/Android — 4notify always pairs push with email or SMS.

Signed at the Cabinet Office
4notify Operations
2026-05-27 · NTC-GB-001

Start free

14 days. No card. UK-based support through the working week.

Other Notices in this Edition