Ap2 Iso20022

io.github.sebastienrousseauPublished by GitHub account sebastienrousseauv0.0.7Updated Oct 24, 2026

Bridge AP2 / x402 agent-payment mandates into wire-valid ISO 20022 pain.001 / pacs.008 records.

VerifiedSTDIODesktop onlyFinanceDeveloper Tools

Overview

AI-generated overview

Converts AP2 and x402 agent-payment mandates into ISO 20022 pain.001 and pacs.008 records, with guardrail checks, over stdio or HTTP.

What you can do
  • Normalise AP2 and x402 payment payloads into a canonical mandate
  • Check a mandate's required fields, spending cap, expiry and authorisation proof
  • Convert a canonical mandate into pain.001 customer credit transfer or pacs.008 FI-to-FI records
  • Produce output whose field names and types match the pain001 and pacs008 generators, so it can feed XML generation
When to use it
Useful when an assistant handles agentic payments from AP2 or x402 and needs to turn an authorisation into a bank-rail ISO 20022 message, or to validate a mandate before acting on it. It only transforms and validates; it does not generate or send the payment itself.
Requirements
A local Python 3.10+ runtime; install the ap2-iso20022 package from PyPI or run it with uvx. The MCP server runs over stdio by default, or over streamable HTTP or SSE on 127.0.0.1:8000 with optional host and port flags. No accounts, API keys or environment variables are declared.
Before you install
The HTTP transports carry no authentication of their own, so bind to loopback or place the server behind a trusted gateway. Mandate payloads contain payer and payee account details and signatures, which are passed to the local process. The server does not move money, but its output feeds payment-message generation, so treat conversion results as consequential.

Installation

In SourceWeft

  1. Open Ap2 Iso20022 in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

ap2-iso20022: Agent-payment mandates → wire-valid ISO 20022

[Glama MCP server score]

Bridge AP2 (Google's Agent Payments Protocol) and x402 (Coinbase's HTTP-402) mandates into ISO 20022 pain.001 / pacs.008 records — with spending-cap, expiry and authorisation guardrails, and an MCP server. These agentic-payment protocols authorise a payment; this library turns that authorisation into the bank-rail message that actually settles it — the rail the card networks and stablecoins don't cover.

Latest release: v0.0.7: 11 MCP tools over stdio, streamable HTTP or SSE, pure-Python (only mcp), 100% branch coverage, for Python 3.10+. Output feeds straight into pain001 / pacs008 to generate wire-valid XML. Part of the ISO 20022 MCP suite.

[ap2-iso20022 Demo]


Why

An agent with a signed AP2 mandate (or an x402 payment authorisation) can prove it's allowed to pay — but nothing in those protocols emits the pain.001 a bank needs to move the money. ap2-iso20022 is that missing hop. And because moving money is consequential, it only transforms and validates — producing the ISO record is deliberately separate from generating and sending it, so the actual payment stays an explicit, guarded step.

Install

sh
pip install ap2-iso20022# or run the MCP server without installing:uvx --from ap2-iso20022 ap2-iso20022-mcp

MCP client config (e.g. Claude Desktop):

json
{  "mcpServers": {    "ap2-iso20022": {      "command": "ap2-iso20022-mcp"    }  }}

Transports

One command line, three transports:

CommandTransportEndpointProtocol revisions
ap2-iso20022-mcpstdiothe client spawns the process2026-07-28, 2025-11-25
ap2-iso20022-mcp --transport streamable-httpStreamable HTTPhttp://127.0.0.1:8000/mcp2026-07-28 (stateless, server/discover) and 2025-11-25 (initialize, Mcp-Session-Id) on the same endpoint; responses stream as server-sent events, GET opens the server-to-client stream
ap2-iso20022-mcp --transport sseHTTP+SSE (2024-11-05)http://127.0.0.1:8000/sse and /messages/for clients that still expect the older transport

--host and --port change the bind address (defaults 127.0.0.1 and 8000). The HTTP transports carry no authentication of their own: bind loopback, or put the server behind a gateway you trust before binding a routable address. Every release is verified over streamable HTTP with scout in both protocol eras and over SSE with the MCP SDK client; see ADR 0001.

json
{  "mcpServers": {    "ap2-iso20022": { "url": "http://127.0.0.1:8000/mcp" }  }}

Flow: normalise → guardrail → convert

python
from ap2_iso20022 import bridge
# 1. Normalise the protocol payload into a canonical mandate.mandate = bridge.from_ap2({    "intent_id": "AP2-CoffeeRun-7",    "payer": "Alice's Shopping Agent",    "payer_account": "DE89370400440532013000",    "merchant_name": "Blue Bottle Coffee",    "payee_account": "GB29NWBK60161331926819",    "amount": "12.50", "currency": "EUR", "memo": "oat latte",    "spending_limit": "50.00",    "signature": "eyJ...", "signature_type": "jws",})
# 2. Guardrail before it becomes a payment.check = bridge.check_mandate(mandate, as_of="2026-03-02T09:00:00")assert check["ok"]          # required fields ok, within cap, not expired, signed
# 3. Convert to a pain.001 record that feeds pain001 -> wire-valid XML.record = bridge.to_pain001(mandate)   # exact pain001 field names + JSON number amounts

Tools

  • normalize_ap2 — AP2 mandate payload → canonical mandate.
  • normalize_x402 — x402 payment payload → canonical mandate.
  • check_mandate — Guardrail: required fields, spending cap, expiry (with as_of), authorisation proof.
  • to_pain001 — Canonical mandate → pain.001 record (customer credit transfer).
  • to_pacs008 — Canonical mandate → pacs.008 record (FI-to-FI).

The output field names and types match what pain001 / pacs008 expect (validated against their JSON schemas), so to_pain001(mandate) → pain001 generate_message → XSD-valid pain.001 with no glue.

Guardrails

check_mandate returns {ok, violations, warnings}:

  • required fields — payer/payee name + account, amount, currency
  • spending cap — amount <= max_amount when a cap is present
  • expiry — refuses an expired mandate when you pass as_of
  • authorisation proof — warns when no proof_type/proof_value is present

It never moves money; it tells you whether the mandate is safe to act on.

The suite

Part of a family of vendor-neutral, Python-native ISO 20022 MCP servers:

Development

sh
git clone https://github.com/sebastienrousseau/ap2-iso20022cd ap2-iso20022python -m venv .venv && . .venv/bin/activatepip install -e . && pip install pytest pytest-cov ruff black mypypytest                      # 100% branch coverage gateruff check ap2_iso20022 tests && black --check ap2_iso20022 tests && mypy ap2_iso20022

License

Licensed under the Apache License, Version 2.0 (LICENSE).


mcp-name: io.github.sebastienrousseau/ap2-iso20022

Source: README.md at commit 9fe3b15

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

3
  1. v0.0.7LatestOct 4, 2026
  2. v0.0.6Oct 4, 2026
  3. v0.0.5Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts