Agents and automations touch refunds, payouts, and settlement — each action is a fraud and reconciliation risk if it runs on a standing credential.
Solution domain
Payments & fintech
Early accessGuard money-movement workflows before loss events.
Domain readout
- Status
- Early access
- Protected workflows
- 1 shipped guard · 3 in design
Domain status
Early access- Shipped today
- Merchant Refund GuardShipped
- In design
- Payout Destination GuardIn design
- Settlement Exception GuardIn design
- API Key & Webhook GuardIn design
Merchant refund guard is our canonical payments guard; additional payment-ops guards available under engagement.
1 shipped guard · 3 in design
- 01Merchant Refund GuardShipped
- 02Payout Destination GuardIn design
- 03Settlement Exception GuardIn design
- 04API Key & Webhook GuardIn design
An anomalous refund is held, a named approver authorizes this exact refund, and an evidence bundle proves who approved what — before money leaves.
Humbleaf does not custody funds or replace payment infrastructure. It evaluates high-risk actions before execution and preserves evidence after the decision.
- Agent / automation / admin action
- Humbleaf authority check
- Payment ops API
- Approval systems
- Evidence store
What it receives
- 01Actor
- 02Requested action
- 03Amount / asset / destination
- 04Merchant / account context
- 05Policy snapshot
- 06Risk signals
- 07Approval state
What it returns
- 01ALLOW
- 02DENY
- 03APPROVAL_REQUIRED
- 04Reason codes
- 05Approval route
- 06Evidence bundle
4-week pilot shape
- Week 1Authority Surface Map
- Week 2Shadow-mode guard
- Week 3Approval routing
- Week 4Evidence review + production readiness
Related workflow guards
We show outcomes — not internal recipes. Verify in the Proof Lab.
See refund escalation in the Proof Lab