Stripe is excellent. For most payment use cases — a subscription, a one-time purchase, a marketplace transaction for a meaningful amount — it's the right default. But it was designed for human-scale transaction volumes. When AI agents start running workflows at scale, with many small tasks executing in parallel throughout the day, the fee structure starts to look different.
Stripe charges per transaction. At standard rates, a task that costs $3 in worker pay carries around $0.39 in fees — 13% overhead. At ten tasks a day per agent, that's manageable. At two hundred, it's a significant line item that compounds every time you add an agent or expand into new task categories. It also introduces latency: each Stripe charge is a synchronous network call, which matters when agents are managing parallel workflows that depend on payment confirmation.
The Design Problem
We needed a payment system that could handle high-frequency, small-value transactions without per-charge overhead. We also needed it to interact correctly with Stripe for the operations where Stripe is the right tool — primarily developer account top-ups and worker cash withdrawals. The answer is Amber: a credit system that sits inside Aethra's platform, between the real-world payment rails and the task payment layer.
How Amber Works
Developers top up their Amber balance via Stripe — a single Stripe charge for a meaningful credit amount. That credit goes into their Amber account. From that point forward, task funding happens entirely inside our platform: the agent calls fund_task, the cost is deducted from the Amber balance, funds move to escrow. No Stripe call. No per-transaction fee. Millisecond-level latency.
Workers accumulate Amber as tasks complete and are approved. When they want to withdraw their earnings — above a minimum threshold that keeps Stripe costs reasonable — they initiate a payout, and we process a Stripe transfer to their bank account. One Stripe call, regardless of how many individual completed tasks contributed to that balance.
Mandatory Daily Spending Caps
Before deploying their first agent, developers must configure a daily spending cap — the maximum total amount their agents can spend across all tasks in a single day. This isn't optional. It's a hard gate: you cannot create an agent until you've set a cap.
The cap is enforced at the platform level. Even if an agent attempts to fund a task that would exceed the daily limit, the transaction is blocked before any funds move. The developer's account owner is notified when agents approach the cap, giving them time to adjust before tasks start failing. This gives developers predictable cost control and protects against runaway spend from unexpected agent behavior.
Transparency on Fees
Workers pay a 2% platform fee on their Amber earnings, disclosed at task acceptance — not buried in a footer or discoverable only by reading the full terms. This is how Aethra sustains its operations alongside developer API access fees. We've deliberately kept the worker fee low enough that most workers would consider it reasonable rather than extractive. The platform economics are designed so that both sides can find Aethra worth using.