Wirex Launches Navoka With Limits on AI-Led Payments

By Grace Kim

Wirex launched Navoka, a specialized AI agent for payments and finance, on November 12, 2026 at Full Stack London. Wirex says the agent can shop, pay invoices and bills, send money and handle contractor payouts under instructions and spending limits set by the account holder.

Navoka includes a dedicated stablecoin wallet, IBAN and debit card, according to Wirex's product overview. The overview lists dollar, euro and pound accounts with ACH, SEPA, Faster Payments, SWIFT and stablecoin rails, subject to eligibility at sign-in.

The product overview says Navoka sits apart from Wirex One: its wallet, IBAN and card are reserved for the agent's transactions rather than drawing on a customer's existing card.

Wirex's product 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 is software, not a financial service, which separates the AI interface from the entity responsible for underlying accounts and transactions.

Wirex has separated the software from the party that moves the money.

What can the agent do?

Wirex says signing in creates an account that can immediately hold and send USDC and EURC. It requires identity verification before customers can use the IBAN or debit card. Telegram is live; WhatsApp and iMessage are listed as coming soon.

Navoka's connection guide says customers can alternatively connect ChatGPT, Claude or Grok to the same account and rules. The guide lets those assistants request payments, purchases, transfers and payouts and read the ledger and spending limits. They cannot see a full card number or IBAN, alter limits or approve payments.

Several AI assistants can share one controlled account.

How do spending rules work?

Navoka's controls documentation provides for:

• Monthly budgets and per-transaction ceilings
• Approval thresholds
• Daily payment-count and value limits
• Merchant and payee allowlists
• Destination-country settings and merchant-category restrictions

Each rule can require approval for every payment or let qualifying transactions proceed automatically.

Under those controls, new payees, amounts above the approval threshold, blocked categories and new countries remain on hold even when automatic payments are enabled. The agent can read the mandate but cannot modify it.

Approval controls bind to the holder's identity and the device or web session. Connected assistants cannot change the policies or approve their own payment requests.

Wirex enforces the rules at the account and card-authorization layer rather than relying only on instructions given to the model. A kill switch freezes cards, pauses rules and unlinks assistants. Pausing the agent does not reverse transactions already executed.

The system can stop a payment before authorization, but it cannot undo a completed transaction.

How does Navoka protect data and explain payments?

The card issuer keeps the full debit-card number in its vault. The agent receives a network token, so the card number does not enter the model's context, logs or chat.

Each agent runs in an isolated virtual machine with encrypted storage under the same security architecture. Customers' agents share no memory, files or context. Wirex tears down and rebuilds the machine when access is revoked.

Navoka's ledger records each payment, governing rule, approver, reason and timestamps. Its dispute pack can bundle those details with the original instruction and receipt, showing why the agent initiated a transaction and which control permitted it.

Navoka separates card credentials from the model and keeps an audit trail for disputes.

What does the developer platform offer?

Navoka's technical documentation describes a Model Context Protocol endpoint using OAuth 2.1 with PKCE, plus an equivalent REST interface. Its tools cover:

• Balances and transaction status
• Invoice payments
• Person and business transfers
• Batch payouts
• Card issuance

Navoka's technical documentation says out-of-policy requests “return a held status with a readable reason.” Every write operation requires a reason, and Navoka retains it in the ledger.

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

The integration guide says existing Wirex One customers can import identity verification without repeating documents or a selfie. 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, with rewards paid into the Wirex One account rather than retained by the agent.

Developers can test payment behavior safely before connecting live funds.

Can Navoka trade stocks?

Navoka's trading documentation extends the same account and control model to scheduled and conditional purchases of stocks and tokenized stocks. Monthly caps, per-order ceilings, approval thresholds and a user-selected asset list govern the orders. Each fill enters the same ledger as payments.

Navoka's trading documentation states: “the agent executes user-written rules rather than selecting investments or timing markets.” Every order requires a rule. The service uses no leverage or derivatives.

Tokenized stocks represent claims on their issuers rather than the underlying shares. Those orders settle in USDC or EURC.

Investors define the strategy; Navoka carries out the written order.

What risks remain?

Wirex'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 say Navoka does not use payment data to train third-party models.

The practical consequence is that Navoka's delegation model depends heavily on the mandate and its audit trail. Routine transactions can run without repeated approvals, but the account holder remains responsible for the chosen limits and for checking AI output.

As Navoka moves beyond its November 12 launch, the mandate and audit trail will determine whether customers can delegate repeat payments without re-checking every instruction.