Conto

Vendor trust controls

Vendor and counterparty controls

Pay approved vendors automatically. Review payments to new, changed, or risky recipients.

Illustrative example

One vendor, two payment checks

Helia Compute · Approved supplier

Saved payment details

$920.00

Matches the approved recipient record

Approved

Known vendor · recipient details unchanged

Recipient details changed

$920.00

Same vendor · new destination wallet

Needs review

Trust review required before paying the new address

The changed field and reviewer decision stay attached to the vendor record.

Check for recipient changes

Each row below is a reason a recipient can be refused or held. Turn on the ones that match how your team already vets vendors.

Approved-recipient policy

A defined set of vendors or merchants the agent may pay. Repeat payments to them don't need a review.

Trust thresholds

Use counterparty reputation or network intelligence to decide when a recipient is safe enough to pay automatically.

Merchant and category mapping

Tie approved recipients back to the kinds of purchases they should be able to receive.

Drift detection

Drift is when an agent starts paying someone new, or the usual vendor at a new account. Both get flagged before the payment settles.

Demo

See vendor payments proceed or pause for review

The property-management demo pays a listed plumber on sight, holds a $1,280 overnight electrical job for the manager, and refuses a handyman the property never vetted.