The risk
Business email compromise no longer needs to fool a person.
A vendor email says the bank details changed. A person might call to check. An agent with access to the payables system just pays.
Magertron checks each payment the agent makes against the company's rules. Routine invoices go through. A payment to a new bank account, or over the limit, waits for the AP supervisor.
What does the work
The controls
- Acting for a person. The agent acts for Joe through a signed token exchange, and every call records both.
- Payment rules. Approved payees and a per-account limit, in policy data your finance team controls.
- Holds for a named approver. Named supervisors decide. They need no access to the AP system itself.
- No self-approval. Maker-checker applies to the agent and to the person behind it.
- One approval, one payment. An approval releases that payment once. A second identical call is refused.
- One trace. Every call, hold and decision, in OpenTelemetry.
See it run end to end against a live Magertron install: try it now. The same policy pack, in banking.
Questions
Frequently asked
▸Does this replace the approvals in our ERP or AP platform?
No. It adds them where the agent acts: at the API call. Your AP platform's own approval flow still applies to people using it directly.
▸Who can approve a held payment?
The people named as approvers in the policy data, for example every AP supervisor. They decide in Magertron and need no access to the AP system.
▸Can one approval pay twice?
No. An approval releases exactly that payment, once. A second identical call is refused.
Other solutions: Banking · Sales & CRM · Network operations