Vision

Every major computing shift has created new financial infrastructure. Mainframes needed electronic funds transfer. The web needed PayPal. E-commerce needed Stripe. Mobile needed Apple Pay and Venmo.

AI agents are the next platform. They need Bankia.

Why On-Chain?

Traditional identity and compliance systems rely on centralized databases controlled by single entities. For autonomous AI agents operating across platforms and jurisdictions, this creates friction, single points of failure, and trust dependencies.

Bankia's on-chain approach provides:

• Portability: Agent credentials work across any platform, protocol, or application
• Verifiability: Any party can verify agent authorization without trusting Bankia
• Immutability: Audit trails cannot be altered or deleted
• Privacy: ZK proofs enable compliance without exposing sensitive data

Why Zero-Knowledge?

Compliance traditionally requires revealing sensitive information — KYC documents, transaction amounts, account balances. Zero-knowledge proofs flip this paradigm:

• Prove you're compliant without revealing why
• Verify transactions are within limits without exposing the limits
• Confirm identity without sharing personal data

This creates a compliance layer that satisfies regulators while preserving user privacy — essential for the agentic economy.

Architecture Overview

Bankia consists of three distinct layers, each addressing a critical challenge in enabling agent-based financial operations:

┌─────────────────────────────────────────────────────────────────┐
│                     AI AGENT FRAMEWORKS                          │
│        (LangChain, CrewAI, AutoGen, Claude, GPT, etc.)          │
└─────────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────────┐
│              LAYER 3: DEVELOPER SDK / MCP SERVER                 │
│         Simple API  •  Guardrails  •  Webhooks & Callbacks       │
└─────────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────────┐
│              LAYER 2: OPEN FINANCE CONNECTOR                     │
│     PIX via ITP  •  Account Data  •  Consent Lifecycle           │
└─────────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────────┐
│          LAYER 1: AGENT IDENTITY & REGISTRY (KYA) ⛓️             │
│                        ON-CHAIN + ZK                             │
│  ┌─────────────┐  ┌─────────────┐  ┌─────────────────────────┐  │
│  │ SBT Agent   │  │ ZK Proofs   │  │ Immutable Audit Trail   │  │
│  │ Passports   │  │ Compliance  │  │ (Merkle Tree)           │  │
│  └─────────────┘  └─────────────┘  └─────────────────────────┘  │
│            Ethereum / Base / Arbitrum / zkSync                   │
└─────────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────────┐
│                  GLOBAL INSTANT PAYMENT RAILS                    │
│   🇧🇷 PIX  •  🇮🇳 UPI  •  🇺🇸 FedNow  •  🇪🇺 SEPA  •  🇬🇧 FPS       │
└─────────────────────────────────────────────────────────────────┘

Layer 1: Agent Identity & Registry (KYA)

"Know Your Agent" — The compliance layer, fully on-chain

On-Chain Agent Passports

• Soulbound Tokens (SBTs) on Ethereum/L2 for each agent credential
• Unique cryptographic identity, non-transferable
• Verifiable by any smart contract or dApp
• Linked to human (CPF) or company (CNPJ) owner via ZK proof
• Portable across platforms — agent identity travels with the agent

ZK Proofs for Compliance

• ZK-KYC: Prove agent owner passed KYC without revealing identity
• ZK-Limits: Prove transaction is within spending limits without revealing exact amounts
• ZK-Authorization: Prove agent has permission to transact without exposing full permission set
• ZK-Solvency: Prove sufficient funds without revealing wallet balance

Stack: Noir (Aztec), Circom, or Polygon zkEVM for proof generation

Scoped Permissions

Immutable Audit Trail

• On-chain logging: Every agent action committed to blockchain
• Merkle tree: Transaction history in verifiable data structure
• Timestamped proofs: Cryptographic proof of when each action occurred
• Dispute resolution: On-chain evidence for any contested transaction
• Regulatory exports: Generate compliance reports from immutable data

L2 recommended: Base, Arbitrum, or zkSync for low-cost, high-throughput logging

Layer 2: Open Finance Connector

The bridge to financial infrastructure

PIX via ITP

Own Central Bank license as Initiador de Transação de Pagamento (ITP). Direct payment initiation, real-time settlement, full BACEN compliance.

Open Finance Data

• Account balance queries (with consent)
• Transaction history access
• Multi-bank aggregation

PIX Automático

Recurring payment setup, subscription management, automatic renewal handling.

JSR (Jornada Sem Redirecionamento)

Frictionless transactions under R$500 — no bank app redirect required. Instant approval flow ideal for high-frequency agent operations.

Layer 3: Developer SDK / MCP Server

Simple integration for any AI framework

Supported Frameworks

LangChain, CrewAI, AutoGen, Claude (Anthropic), GPT Assistants (OpenAI), and any custom implementation.

API Reference

from bankia import Agent

agent = Agent(agent_id="ag_abc123", api_key="sk_live_xxx")

# Send PIX payment
result = agent.pay(
    pix_key="email@exemplo.com",
    amount=150.00,
    description="Pagamento serviço"
)

# Check balance
balance = agent.get_balance()

# List transactions
transactions = agent.list_transactions(limit=10)

MCP Server

For Claude and other MCP-compatible agents:

{
  "tools": [
    {"name": "bankia_pay", "description": "Send PIX payment"},
    {"name": "bankia_balance", "description": "Get account balance"},
    {"name": "bankia_transactions", "description": "List transactions"}
  ]
}

ZK & On-Chain Stack

The technical infrastructure powering Bankia's trustless verification layer.

Blockchain Layer

Zero-Knowledge Stack

Agent Passport Schema

{
  "schema": "bankia.agent.passport.v1",
  "sbt": {
    "tokenId": "0x...",
    "owner": "0x...",
    "issueDate": "2026-02-22T00:00:00Z"
  },
  "agent": {
    "id": "ag_abc123",
    "name": "PaymentBot",
    "framework": "langchain"
  },
  "owner": {
    "type": "individual",
    "countryCode": "BR",
    "kycProof": "zk:0x..."  // ZK proof of KYC completion
  },
  "permissions": {
    "spendingLimit": "zk:range:0-5000",  // ZK range proof
    "allowedRecipients": "zk:merkle:0x...",  // Merkle inclusion
    "timeWindow": "08:00-22:00"
  }
}

Regulatory Compliance

Bankia's on-chain architecture is designed to meet and exceed regulatory requirements while preserving privacy through zero-knowledge proofs.

Brazilian Requirements

• ✓ BACEN Open Finance regulations
• ✓ ITP licensing requirements
• ✓ PIX security standards
• ✓ LGPD data protection (enhanced via ZK)
• ✓ AML/CFT compliance (verifiable on-chain)

KYA Framework (Know Your Agent)

Extending traditional KYC to autonomous software, powered by ZK proofs:

Privacy-Preserving Compliance

Traditional compliance requires exposing sensitive data. Bankia's ZK approach enables:

• Regulatory satisfaction: Auditors can verify compliance cryptographically
• User privacy: No personal data exposed during verification
• Selective disclosure: Reveal only what's necessary for each transaction
• Cross-border compatibility: Proofs work across jurisdictions

Global Expansion

Milestones