Wirex Navoka Buyer Guide: An AI Agent With Its Own IBAN, Card, and USDC Wallet

Wirex unveiled Navoka on November 12, 2026, at its Full Stack London event, pitching a product category that sounds simple until you read the compliance footnotes: an artificial intelligence agent that spends money from its own bank account, not yours. Each Navoka instance receives a dedicated IBAN, debit card, USDC and EURC wallets, and programmable spending rules the agent cannot modify. Access is invite-only. This buyer guide explains what that architecture means for individuals, businesses, and developers evaluating agentic payments in late 2026.

The problem Navoka claims to solve

Most experimental “AI payments” connect a chatbot to a crypto wallet or reuse the user’s personal card via screen scraping and credential vaults. Security teams hate both patterns. Consumers fear runaway subscriptions. Regulators ask who is liable when an agent misreads a prompt. Wirex’s answer is structural separation: the agent is a distinct account holder with its own instruments, topped up by the human principal under explicit limits.

That model mirrors corporate cards issued to employees, except the employee is software. Familiar controls—merchant category blocks, daily caps, country lists—become machine-readable policies evaluated at authorization time.

Account structure and funding flows

Navoka agents can hold dollars, euros, and pounds, according to Wirex, and trade digital assets including USDC, EURC, bitcoin, ether, and Solana. Funds move instantly between the user’s Wirex One account and the agent’s silo, a feature highlighted for existing Wirex customers who can import Know Your Customer verification without repeating onboarding.

Wirex One remains the user’s primary account; Navoka is a satellite. Disconnecting the agent is designed to wipe its isolated compute environment, a privacy measure that also functions as a kill switch. Card numbers never surface to connected assistants such as ChatGPT, Claude, or Grok, reducing token leakage risk in third-party logs.

How users interact day to day

At launch, messaging happens through Telegram, with WhatsApp and iMessage listed as coming soon. Users instruct Navoka to pay invoices, book travel, or send money within pre-set guardrails. Developers can embed the same agent via assistant marketplaces, turning Navoka into a payments back end for custom agents rather than only a consumer chat product.

Wirex markets recurring investment features—scheduled purchases of stocks and tokenized stocks within monthly caps and asset allowlists—suggesting Navoka targets personal finance automation, not only one-off ecommerce.

Spending controls in detail

Four control layers deserve scrutiny during procurement:

First, rule sets: allowed merchants, per-transaction limits, daily aggregates, and geography lists. Agents cannot escalate their own limits; out-of-policy charges queue for human approval.

Second, the kill switch: freeze card, pause rules, disconnect assistants—actions available without waiting for support tickets.

Third, audit trails: each payment records which rule authorized it, who approved exceptions, and free-text rationale when required.

Fourth, privacy isolation: separate machines per agent, wiped on revocation, limiting cross-tenant bleed in a multi-agent household or business unit.

Buyers should request sample audit exports and test whether their SIEM can ingest them.

Stablecoin and fiat interplay

USDC and EURC wallets position Navoka inside Wirex’s stablecoin infrastructure story, not only traditional card rails. Cross-border freelancers might prefer stablecoin settlement while contractors in SEPA countries use IBAN transfers. Multi-rail agents complicate accounting but match how hybrid workforces already get paid.

Wirex has not published interchange economics, FX spreads, or crypto conversion fees for Navoka-specific flows. Buyer guides must flag pricing TBD as a gating item before production pilots.

Who should consider early access

Individuals with heavy subscription portfolios and appetite for Telegram-first UX may trial Navoka as a delegated spender for non-essential categories—media, software tools, travel holds—while keeping mortgage and tuition on manual accounts.

Small businesses paying contractors or SaaS vendors could assign agents per department, each with distinct limits, reducing shared-card risk. Developers building vertical agents (legal research, medical admin, logistics quoting) might partner rather than obtain their own e-money licenses—a costly path in the EU and UK.

Organizations under HIPAA, PCI-DSS scope, or stringent vendor-management rules should wait for enterprise documentation beyond consumer marketing copy.

Risks and limitations

Invite-only access means no broad peer benchmarking yet. Wirex’s card network membership covers Visa and Mastercard principals, but Navoka’s specific network and BIN ranges are undisclosed. Chargeback workflows for agent-initiated purchases remain untested in public forums.

Regulatory classification matters: Wirex states Navoka is software, with financial services provided by a group entity under separate terms. Legal teams must map that split to local agent-banking rules, especially in the EU’s evolving AI Act implementation guidance.

Connected assistants introduce prompt-injection risk: malicious content in emails or websites could trick upstream models into authorizing payments if human oversight is weak. Navoka’s out-of-policy queue mitigates but does not eliminate social engineering.

Comparison shopping checklist

When evaluating Navoka against bank-led tests such as HSBC and Ant Digital’s tokenized deposit verification, ask:

Does the agent spend regulated bank money or primarily stablecoins? Who performs transaction monitoring? Can treasury export data into ERP systems? What uptime SLAs apply to authorization services?

When comparing to raw wallet agents, ask whether your risk committee accepts irreversible chain settlement without chargebacks.

Deployment steps for interested buyers

Request invitation and complete Wirex KYC. Connect Wirex One if already a customer. Start with a low top-up and narrow merchant allowlist. Log every approval for two weeks to tune rules. Only then connect third-party LLM assistants, and monitor assistant logs for anomalous tool calls.

Document internal policy: which roles may create agents, maximum balances, and mandatory review thresholds. Treat Navoka like corporate card issuance, not like installing a browser extension.

Bottom line

Navoka is among the first consumer-branded agent payment products to ship with dedicated IBANs, cards, and stablecoin wallets rather than piggybacking on the user’s primary credentials. It is early, invite-only, and pricing-opaque—but it articulates a credible control model enterprises can stress-test while global banks run parallel laboratory proofs. Buyers should pilot small, audit everything, and assume regulators will ask for the audit trail long before agents handle material spend.

Questions to ask Wirex during onboarding

Request the card network, BIN range, chargeback SLA, and geographic availability matrix before funding an agent. Ask whether USDC off-ramps settle to the IBAN or require manual conversion. Clarify whether assistant connectors log prompts that could include merchant credentials in third-party systems.

Wirex One customers

Existing Wirex One users can connect without repeating KYC; document internal approval for linking corporate Wirex One balances to experimental agents. Finance teams may classify agent top-ups as petty cash or software subscriptions depending on amount—pick a policy before month-end close.

Roadmap signals

Wirex promised WhatsApp and iMessage channels after Telegram. Buyers should treat channel expansion as a usability milestone, not a security milestone: each messaging surface introduces new phishing and prompt-injection vectors requiring updated training for employees who approve out-of-policy payments.

Insurance angle

Ask whether commercial crime policies cover agent-initiated wire transfers and card fraud when the agent, not the employee, holds credentials. Most policies were written before software held IBANs.

Reporting note

Wirex announced Navoka at Full Stack London on November 12. Pricing, geographic rollout, and network branding for the Navoka card were not disclosed in the press release. Product capabilities described here follow Wirex and Navoka marketing pages unless noted as analyst interpretation.