Articles · Money & Agents
The invoice that looked exactly right
One look-alike invoice, with new bank details, can take a small business down. Verified Payment Requests let a customer prove a request really came from you — before any money moves.
By Lucian · Lux Automations
The problem
A criminal imitates a business and emails its customer: a familiar-looking invoice, with “new bank details.” The customer pays in good faith, the money lands in the criminal’s account, and it is gone. The business did nothing wrong except be imitated — and until now there has been no reliable way for the payer to check whether a request really came from them.
The losses behind that simple trick are not small. Business email compromise losses in 2024 averaged roughly $129,000 per reported incident (FBI IC3 figures) — a company-ending number for a small firm. The usual defences are thin: a confirmation call that goes to the number printed in the fraudulent email itself, or a tired person squinting at a look-alike domain.
The technology
Verified Payment Requests replaces hope with a registry. A business enrols once, and its true payment details live in the registry under its signed identity. From then on, every invoice and payment request it sends carries that signed identity, so the proof travels with the request instead of living in someone’s memory of what the business’s email usually looks like.
Before paying, the customer checks two things: that the request carries the business’s genuine signed identity, and that the destination matches the one registered. An imitation has neither, and it shows. Changing bank details stops being a casual email and becomes a ceremony — signed and logged — so a real change is provable and a fake one stands out. As everywhere in this house, we sell the check, never custody: no customer money passes through our hands.
What it changes
For the small business, the change is that being imitated stops being a silent risk carried by its customers. Its real requests can be proven real, in the moment that matters — before payment, not in an argument after the money has gone.
For the customer, paying becomes calmer. Instead of trusting a familiar layout and a plausible story, they have something to check: an identity that verifies, and a destination that matches the record. One check, done once per request, stands between an ordinary payment and an expensive lesson.
It is worth saying what this does not ask of anyone. The customer is not asked to trust an email more, or to learn a new ritual for every bill they pay. They are asked to check one thing, once, at the moment it matters — does this request carry the business’s signed identity, and does the destination match the registered one. A request that passes both has earned its payment. A request that fails either has told the customer everything they need to know, before any money has moved.
See it
Verified Payment Requests make a business’s real payment details checkable, so an imitation shows itself before it is paid. Verified Payment Requests — the product page · All the house articles · Lux Automations — ailux.ca