That’s what I thought, the sort code comes back as “government banking” so they seem to own the entire block.
I think they support COP to a degree as usually it’ll say “we couldn’t check these details”, but this came back saying they found an account. I imagine they just return a success response for any account number and it goes into some sort of catch-all system if one of the standard account numbers isn’t used.
Realised it also worked for me in July last year with that incorrect account number so it should be okay Considering my first payments in January 2023 were to the wrong account number and had no reference, and they managed to find them, they seem to have a robust system for idiots like me that can’t enter the details correctly
You sent them 8 digits of the reference number, albeit in the account number field. If it was the last 8 that’s probably all that’s likely all they really need.
Lots of orgs that own whole blocks and a few oldies literarily accept anythingnas account and reference number. Sometimes it is just sort code and all zeros for account number - which is obviously an invalid one, but hey ho.
So yeah, payee validation is half soft as it doesn’t enforce anything on those things.
That’s why I would prefer to use open-banking payment as it is mediated more strictly of who is paying whom, how much, and what for.
Similar instances are like passport office, DVLA, courts, councils etc.
With Santander releasing a new credit card giving 2% back in the first year and 1% thereafter (£15 monthly cap, £3 monthly fee), I hope Chase will hurry their offering along a bit.
I know. I get a lot of dings this time of month. You’d think they could do a long summary one although that said the DDs don’t all come out at the same time of day.
Wouldn’t help much. That would just cut the per account dings but you’d still get one per transaction. My payments go out on different days so I’d still get my going out tomorrow ding, then the ding when it actually goes out the next day.