Skip to content
Apkar

Fintech · 120 employees

Halden

A refund agent shipped in two days because the security review had an audit trail to read instead of a promise to trust.

2 days

Time to production

1

Security reviews needed

under $100

Refunds auto-cleared

2

Prior shelved attempts

The challenge

Halden had built a refund automation twice and shelved it twice. Both times the blocker was the same: security would not grant write access to a payments API for a process whose actions could not be reconstructed afterwards.

What they built

The third attempt scoped credentials to the agent, put an approval gate on every refund over a threshold, capped spend per run, and exported the full trail. The security conversation moved from a design document to a link showing exactly what the agent did in staging.

The result

Approved in one review. Two days from first line to first production run. Refunds under the threshold now clear without a human; everything above still waits for one, and the reviewer sees the amount and the customer before either button.

The review took forty minutes because there was something to actually read.
Yusuf BarakatSecurity LeadHALDEN