Google Cloud powers AI agents to make European bank payments without accounts

Google Cloud’s partnership with Italy‑based payments processor Nexi formalized in a memorandum of understanding this week unlocks the Agent Payments Protocol (AP2) as an open‑source conduit for AI‑driven transactions on Europe’s ISO 20022 network, which settles roughly €2.9 trillion annually, according to the AI‑Agents‑Can‑Now‑Make‑European‑Bank‑Payments report posted on up2itnow. The protocol sits atop the XML‑based pacs.008 and pacs.004 message formats that banks use for credit transfers and payment returns, and it removes three entrenched dependencies: a corporate bank account, a custodial processor, and a human‑in‑the‑loop approval step. By allowing an autonomous agent to generate a compliant ISO 20022 message, sign it locally with its own private key via the agentwallet‑sdk, and route the payment through a CCTP V2 USDC‑to‑EUR bridge, the new stack enables “non‑custodial” payments that bypass traditional settlement intermediaries.

The technical workflow, outlined in the same up2itnow brief, replaces the conventional ERP‑to‑bank‑API chain with a streamlined path: AI Agent → ISO 20022 pacs.008 → x402‑signed header → CCTP V2 bridge → AP2 Euro off‑ramp → creditor bank. The handler, which can be launched with a single pip install and a uvicorn command, validates IBAN checksums and BIC formats before issuing a quote, thereby catching typographical errors before they reach the clearing network. A sample response shows the quoted amount in euros, the required USDC amount (e.g., 1 389 583 333 USDC units for a €1 500 transfer), and a bridge fee, while the “sign_locally: true” flag confirms that the agent’s private key never leaves its device. The open‑source nature of AP2 means no proprietary SDK or Nexi partnership agreement is required at the message level, a point emphasized by the report’s authors.

For developers, the implications are immediate. The up2itnow article notes that the handler includes 41 unit tests covering edge‑case validation, XML parsing quirks, and full FastAPI endpoint responses, ensuring that the protocol can be integrated into production‑grade AI services without bespoke custodial infrastructure. Moreover, the protocol’s reliance on the agentwallet‑sdk and the x402 header aligns with Google’s broader AI‑shopping initiative, which The Register has described as a “masterplan for letting AI shop on your behalf.” By exposing a standardized, open‑source payment layer, Google Cloud is effectively lowering the barrier for autonomous agents to monetize services, purchase inventory, or settle invoices across the Eurozone without the friction of bank‑account onboarding.

Analysts at Forbes have highlighted the strategic dimension of AP2, calling it “the first protocol for autonomous payments” and noting that Google frames the underlying “mandates” as a way to formalize agent‑initiated purchases. The protocol’s reliance on stablecoins—specifically USDC converted to euros via the CCTP V2 bridge—provides a liquidity layer that sidesteps the need for fiat‑only settlement rails, a design choice that could accelerate adoption among fintechs and e‑commerce platforms seeking to embed AI agents directly into checkout flows. By anchoring the system to the ISO 20022 standard, Google ensures compatibility with existing banking infrastructure while offering a path to future‑proof, programmable finance.

The market impact remains to be seen, but the convergence of open‑source standards, cloud‑scale infrastructure, and non‑custodial crypto bridges positions Google Cloud as a potential catalyst for a new class of AI‑enabled financial services. If the protocol gains traction, it could reshape the economics of B2B payments by eliminating custodial fees and reducing compliance overhead, thereby expanding the addressable market for AI agents beyond data‑centric tasks to include direct monetary transactions across Europe’s vast €2.9 trillion payment ecosystem.