AI Agent Pulse - the weekly briefing on the agent economy. Subscribe freePay-per-call agents: read the x402 docs
gigsoul.com

GigSoul

Intelligence on the agent ecosystem
Tuesday, November 10, 2026
Tools

Navoka gives agents a card. The mandate still needs a job.

Wirex puts payment limits outside the assistant. Purchase intent, settlement status and reversal rights still need separate checks.

Programming code on a screen, not a product screenshot

Concept photo: programming code on a screen, by luis gomes / Pexels. Illustrates programmable tools, not a Navoka product screenshot. Used under the Pexels license, which permits article, RSS and social reuse. No endorsement implied.

A payment agent can obey its spending limit and still buy the wrong thing. That is the question behind Wirex's new Navoka: a separate account and card reduce what an assistant can reach, but the rule still has to describe what its owner meant.

Wirex announced Navoka on November 12, with access by invitation. It describes a payments specialist with a dedicated IBAN, debit card and stablecoin wallet, rather than permission to spend from someone's existing personal card. Telegram is live; WhatsApp and iMessage are listed as coming later. The Paypers also reports the invitation-only launch.

The important boundary is outside the model

Navoka's controls page describes merchant and payee allowlists, monthly budgets, per-transaction ceilings, approval thresholds, country restrictions and daily count and value limits. The agent can read those rules but cannot change them. New rules default to approving each payment; unattended payments are enabled per rule.

That distinction matters more than a confident promise in a chat. The developer documentation says enforcement happens at the account, and policy changes require the holder's identity. A connected assistant cannot approve its own request or raise its own ceiling. These are documented design claims, not controls GigSoul has independently tested.

A merchant allowlist is still broader than an order. Permission to pay a familiar shop does not, by itself, specify the right product, delivery address or renewal terms. The practical review should connect the intended purchase to the actual payee, total, currency and recurring obligation before allowing the rule to run unattended.

Approved is not settled

The developer interface distinguishes held, approved, declined and settled payments. A held response is an expected outcome, not a failed request to retry until it succeeds. Navoka tells developers to explain the hold and wait, rather than splitting the amount or repeatedly trying again.

Its documentation also separates holder approval from settlement confirmation. An integration should preserve that distinction in its own status messages: a tap authorizes the next step; it does not prove that a supplier received money. The documented ledger records a payment's rule, approver, reason and timestamps, giving the holder something more useful than a conversational assurance.

A stop button is not an undo button

The agent terms say pausing stops new actions but does not reverse executed ones. They also warn that AI interpretations of messages, invoices and merchant pages can be wrong, incomplete or stale. Payment execution, fees, reversals and chargebacks fall under separate provider terms accepted during onboarding. A dedicated account is not a blanket promise of free payments or automatic refunds.

For builders, the useful starting point is the documented synthetic sandbox, not a live payment. It offers held and declined cases without real money. GigSoul has not connected an account, run that sandbox or made a purchase. The launch is worth watching because it puts the spending policy outside the assistant's reach. Whether a payment is the right one still needs evidence that the policy actually covers this job.

More in Tools

All Tools →