Non-custodial AI agent bridge for AP2/ISO 20022 payments -- agentwallet-sdk implementation

[up2itnow0822]

What We Built

Following the Nexi + Google Cloud MoU on AP2, we built a non-custodial bridge that lets AI agents participate in European AP2 payments without a corporate bank account or custodial processor.

The gap we closed:

Traditional AP2 assumes a corporate entity with a bank account. AI agents don't have bank accounts. Our bridge gives agents a non-custodial path:

AI Agent -> ISO 20022 pacs.008 message -> agentwallet-sdk signs x402 header
         -> CCTP V2 USDC bridge -> AP2 Euro off-ramp -> Creditor Bank

The agent holds its own private key. Signs locally. The creditor receives standard SEPA.

Technical Implementation

• Parses ISO 20022 pacs.008 (Credit Transfer) and pacs.004 (Payment Return) XML
• Validates IBAN (mod-97 checksum) and BIC (ISO 9362) before quoting
• Returns USDC bridge amount + x402 payment header for local signing
• FastAPI endpoint:
• 41 unit tests passing

Relevance to UCP/AP2

This implementation sits at the intersection of AP2 (payment authorization) and the non-custodial agent wallet layer. Agents using agentwallet-sdk can now:

1. Receive payment instructions in standard ISO 20022 format
2. Validate the payment fields locally
3. Sign the x402 authorization header without exposing private keys
4. Bridge USDC to EUR via CCTP V2 for SEPA settlement

Links

• Dev.to article with full code: https://dev.to/up2itnow0822/ai-agents-can-now-make-european-bank-payments-without-a-bank-account-50ej
• SDK: https://www.npmjs.com/package/agentwallet-sdk
• Handler source: available in our workspace at

Happy to open a PR if there's interest in an official AP2 reference implementation for non-custodial agent wallets. Would love feedback from the Nexi/UCP team on whether this aligns with the spec direction.

[up2itnow0822]

Update -- March 5, 2026

Since the initial post, we have made significant progress on the AP2 non-custodial bridge.

What shipped today:

1. Full execution loop wired -- the handler now goes beyond quoting. The AP2 executor handles: parse ISO 20022 -> get bridge quote -> sign x402 header locally (agent key never leaves device) -> USDC CCTP V2 bridge submission -> execution receipt with txHash + SEPA reference.

2. TypeScript SDK module -- AP2Client is now a first-class module in agentwallet-sdk (v3.2.1, live on npm):

import { AP2Client } from 'agentwallet-sdk';

const ap2 = new AP2Client({ wallet: agentWallet });

// Agent-friendly XML builder (no ISO 20022 expertise required)
const xml = AP2Client.buildPacs008({
  creditorIban: 'DE89370400440532013000',
  creditorBic: 'COBADEFFXXX',
  creditorName: 'Supplier GmbH',
  amountEur: 1500,
});

// Get a quote before committing
const quote = await ap2.quote(xml);

// Execute -- agent signs locally, bridges via CCTP V2, settles to SEPA
const receipt = await ap2.pay(xml);
console.log(receipt.txHash, receipt.sepaReference);

3. Dev.to article with full walkthrough: https://dev.to/up2itnow0822/ai-agents-can-now-make-european-bank-payments-without-a-bank-account-50ej

Architecture alignment with UCP/AP2:

The buildPacs008() helper abstracts ISO 20022 complexity for agent developers while keeping the wire format fully spec-compliant. The non-custodial signing model means agents can participate in AP2 payments without requiring the operator to hold custodial funds -- which aligns with the UCP principle of agent autonomy.

Happy to contribute this as a reference implementation to the UCP/AP2 ecosystem. Would welcome any feedback on spec alignment from the Nexi team.

[up2itnow0822]

Update: AP2Client is now available as a TypeScript module in agentwallet-sdk v3.2.1. npm i agentwallet-sdk -- includes AP2Client for quote + execute, buildPacs008() helper for agent-friendly XML generation, and full TypeScript types.

[up2itnow0822]

Update (Mar 6, 2026): Nexi MCP Server Launch + AP2 Compliance Path Question

Wanted to surface a significant development for this thread: Nexi just launched an MCP server for agent-initiated payments. This is a major signal that AP2 + UCP are solidifying as the EU agentic commerce standard, with Google backing.

From our side, the agentwallet-sdk AP2Client already handles non-custodial mandate signing and payment authorization for agent-initiated flows. The current implementation covers IntentMandate, CartMandate, and PaymentMandate types with signature verification.

Question for the group: With Nexi's MCP server now live and AP2 gaining traction as an EU standard, what is the recommended AP2 compliance path for non-custodial SDK implementations?

Specifically:

1. Does the AP2 spec have a conformance test suite we can run against?
2. For delegated payment facilitator flows (like what Abstract is rolling out for x402), does AP2 have a defined trust model for non-custodial intermediaries?
3. Is there a formal AP2 certification process for third-party SDKs, or is compliance self-attested?

We want to position agentwallet-sdk as a fully AP2-compliant, non-custodial bridge -- any guidance on the compliance path would be valuable.