Beneficiaries

Know exactly who you are paying

Most fraud losses start with a payee that was added minutes earlier. Your beneficiary list is treated as a security surface, not an address book.

Controls

Four protections on every payee

Applied by default on personal accounts, and configurable per entity on business accounts.

The account name is checked with the receiving bank before you can save the payee.

Lock a payee's details so any edit requires a passkey and a 12-hour cooling period.

First payments to a payee added in the last hour trigger a contextual scam check.

Every edit is logged with actor, device and timestamp, retained for seven years.

For teams

Bank detail changes are the single most exploited process in accounts payable. We make the change itself the controlled event.

Four-eyes on detail changes
Editing a supplier's bank details always requires a second named approver, regardless of amount.
Callback prompts
When details change, we prompt for a recorded verification callback and store the outcome on the record.
Payee groups
Group suppliers by entity, department or currency and apply limits to the whole group at once.
Bulk import with validation
Every row is name-checked and IBAN-validated before a single payment is created.

Payee record — Aster Studio Ltd

Records like this are shown before every payment so context is available at the moment of decision.

FAQs

Next step

Verification, locking and approval rules that make a mistyped sort code an inconvenience rather than a loss.