Nice, FR
A proposal for Revolut — by Ashency

AI Agents Need a Bank.

They write code, deploy apps, manage infrastructure.
But they can't spend a single euro on their own.

Scroll to see why this matters

The $0 Workaround

What developers do today

  • 1Create a virtual card manually
  • 2Copy-paste card numbers into AI config
  • 3AI uses "Computer Use" to type digits into web forms
  • 4No API control — can't check balance or see transactions
  • 5Card compromised? Manual intervention.

Fragile. Insecure. Doesn't scale.

What they actually need

  • 1A sub-account designed for AI agents
  • 2Programmatic API (MCP) for payments, cards, balance
  • 3Human-controlled spending limits & approvals
  • 4Full audit trail, instant freeze, kill switch

Secure. Auditable. Built for scale.

The Race Has Already Started

Mar 2026Stripe launches Machine Payments Protocol (MPP)
Mar 2026Anthropic ships Dispatch, Computer Use, Channels
2026Every major AI lab shipping agent capabilities
$0AI agents in financial services market (2026)
$0Projected agentic AI market by 2034
"Banks that build the infrastructure for agentic payments now have an enormous first-mover advantage." — PYMNTS.com, March 2026

Stripe

MPP protocol

No banking

No accounts, no cards

Traditional Banks

Accounts, cards

No AI integration

No MCP, no API

Revolut

Accounts + cards

Spending controls + API

= EVERYTHING needed

Introducing Agent Accounts

A new account type within Revolut Business — designed for AI agents.

get_balance
Check agent balance
make_payment
Pay within limits (human approval if above threshold)
generate_card
Temporary virtual card, auto-expires
list_transactions
Full agent transaction history
request_funds
Agent asks human for more money
check_limits
Current spending limits & remaining allowance

Human in Control. Always.

Human Controls

  • Spending limits
  • Category restrictions
  • Approval thresholds
  • Instant freeze
  • Full audit trail
  • Revoke access anytime

Agent Capabilities

  • Check balance (read-only)
  • Make payments within limits
  • Generate temp cards
  • Request funds
  • View own history

Agent Cannot

  • Access main account
  • Change own limits
  • Bypass approval
  • Transfer externally
  • See other agents
  • Override kill switch

Examples:

R
Revolut
Claude wants to pay €4.99 to Hetzner Cloud
R
Revolut
Claude wants to pay €12.00 to Vercel Pro Plan
R
Revolut
Claude wants to pay €8.50 to Namecheap — domain renewal
R
Revolut
Claude requests €50 additional funds for Supabase upgrade
R
Revolut
Claude wants to pay €3.00 to Resend — email API usage

A New Revenue Stream

Free
€0
  • 1 agent
  • €100/month limit
  • Basic MCP
Attracts developers
Business
€5/agent/month
  • Unlimited agents
  • Advanced controls
  • Custom approvals
Core revenue
Enterprise
Custom
  • Multi-team
  • Compliance
  • SLA
High-value accounts
100,000 developers x 3 agents x €5/month = €1.5M/month within 18 months

You Already Have Everything

  • ✓Virtual cards — the core building block
  • ✓Spending controls — per-card limits, categories
  • ✓Business API — payment initiation, account info
  • ✓Sub-accounts — team cards with individual controls
  • ✓Mobile excellence — world-class approval UX
  • ✓Developer reputation — known for innovation

This is a packaging opportunity, not a technical challenge.

Built from Real Need

I'm Ash, founder of Ashency — an AI-powered web agency in Nice, France.

My AI agent (Claude) deploys applications, manages infrastructure, and needs to make payments autonomously every day.

I'm currently using a Revolut Business virtual card as a workaround. It works — barely.

I'd be happy to beta test, provide developer feedback, and share MCP integration documentation.

ash@ashency.fr ashency.fr
Revo-Bot AI · Ashency