Wirex launches Navoka with rule-bound AI payments and cards

By Elena Vasquez

Wirex launched Navoka on November 12, 2026, with a dedicated stablecoin wallet, IBAN and debit card for an AI agent that can shop, send money and pay contractors.

The launch accompanied Wirex’s Full Stack London event.

Navoka’s controls documentation puts enforcement at the account and card-authorization layer, rather than trusting instructions given only to the model.

That structure matters because Navoka keeps an autonomous assistant from changing the mandate or approving its own request.

What can Navoka do for customers?

Navoka’s product overview describes a specialized AI agent for payments and finance. It can shop, pay invoices and bills, send money and handle contractor payouts, all under instructions and spending limits set by the account holder.

The same overview lists dollar, euro and pound accounts with ACH, SEPA, Faster Payments, SWIFT and stablecoin rails. Eligibility for those rails applies during sign-in.

Navoka is separate from Wirex One. Its wallet, IBAN and card are reserved for agent transactions instead of drawing on a customer’s existing card.

Navoka’s terms identify Wirex Holdings Limited as the software operator. A separate Wirex group provider holds funds, issues cards and executes payments under its own terms.

Navoka itself is software, not a financial service. Its terms use that division to separate the AI interface from the entity responsible for underlying accounts and transactions.

What spending controls can account holders set?

The controls documentation lists monthly budgets, approval thresholds, per-transaction ceilings, daily payment-count limits and daily value limits.

It also provides merchant and payee allowlists, destination-country restrictions and merchant-category restrictions. Each rule can require approval for every payment or allow qualifying transactions to proceed automatically.

Under Navoka’s controls, new payees, amounts above the approval threshold, blocked categories and new countries stay on hold even when automatic payments are enabled.

The agent can read the mandate but cannot modify it. Approval controls remain tied to the holder’s identity and the device or web session.

Connected assistants cannot change those policies or approve their own payment requests. Navoka’s rules keep control with the account holder rather than the model.

A kill switch freezes cards, pauses rules and unlinks assistants. Pausing Navoka does not reverse transactions it has already executed.

How does Navoka protect card details?

Navoka’s security architecture keeps the full debit-card number inside the card issuer’s vault. The agent receives a network token instead.

According to Navoka, the card number does not enter the model’s context, logs or chat. Each agent runs in an isolated virtual machine with encrypted storage.

Customers do not share memory, files or context, according to Navoka’s architecture. Navoka tears down the machine and rebuilds it when access is revoked.

The ledger records each payment with its governing rule, approver, reason and timestamps. A dispute pack can bundle those details with the original instruction and receipt.

The ledger record shows why the agent initiated a transaction and which control permitted it, giving the holder evidence for a dispute.

Which assistants can connect to Navoka?

Signing in creates an account that can immediately hold and send USDC and EURC. Identity verification is required for the IBAN and card.

Navoka lists Telegram as live, while WhatsApp and iMessage are listed as coming soon. Users can alternatively connect ChatGPT, Claude or Grok to the same account and rules.

The connection guide says those assistants can request payments, purchases, transfers and payouts. They can also read the ledger and spending limits.

The guide says assistants cannot see a full card number or IBAN, alter limits or approve payments themselves. Those exclusions apply to connected assistants, not only to Navoka’s own interface.

Existing Wirex One customers can import identity verification without repeating documents or a selfie, according to Navoka’s integration guide.

The same guide says they can move money instantly and without a fee between the two accounts. The agent’s card can also earn the customer’s Wirex One cashback rate.

Rewards go into the Wirex One account rather than staying with the agent, according to the integration documentation.

What can developers build with Navoka?

Navoka’s technical documentation describes a Model Context Protocol endpoint using OAuth 2.1 with PKCE, plus an equivalent REST interface.

The documented tools cover balances, invoice payments, person and business transfers, batch payouts, card issuance and transaction status.

Requests outside policy return “a held status with a readable reason,” Navoka’s technical documentation says. Every write operation also requires a reason.

Navoka retains that reason in the ledger. The policy outcome therefore gives developers an inspectable record rather than a silent failure.

Navoka provides a free sandbox with synthetic payment rails and test cards, without identity checks or real money. Businesses can use it to test approvals, holds and declines before production.

Navoka’s documentation says the sandbox lets teams exercise those cases before connecting the system to live payment activity.

Can Navoka invest for users?

Navoka extends the same account and control model to scheduled and conditional purchases of stocks and tokenized stocks.

Navoka’s trading documentation sets monthly caps, per-order ceilings, approval thresholds and a user-selected asset list. Every fill enters the same ledger used for payments.

The trading documentation says the agent executes user-written rules instead of selecting investments or timing markets. Every order requires a rule.

Navoka does not use leverage or derivatives, according to the trading documentation.

Tokenized stocks are claims on their issuers, not the underlying shares. Those orders settle in USDC or EURC, according to Navoka’s trading terms.

What happens when the AI reads a bill wrong?

Navoka’s terms warn that AI interpretations of messages, invoices and merchant pages can be wrong, incomplete or out of date.

Users must check amounts, payees and references before approval. The terms also state that “payment data is not used to train third-party models.”

The practical consequence, as Navoka describes it, is that delegation depends heavily on the mandate and its audit trail.

Navoka says routine transactions can run without repeated approvals. Responsibility for choosing limits and checking AI output remains with the account holder.

For Wirex, the next test is whether that combination can support routine autonomous payments without giving connected assistants control over money movement.

Navoka’s limits, approvals and records leave the holder’s mandate as the final authority: routine payments may proceed automatically, while every exception stays reviewable and every executed transaction leaves a record.