FusionXPay

Manho3stars

AI-native microservices payment platform integrating Stripe and PayPal. Features MCP Server (Spring AI, 8 tools) with 3-layer AOP safety pipeline, two-step confirmation for financial writes, and unifi

Finance

Install Run on PlugMCP

GitHub Website

Run on PlugMCP

1# FusionXPay

README.mdMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

Install from the publisher. Not a PlugMCP endpoint.

Run on PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: MIT
Last checked: 2026-10-28

Stars: 3
Tools: —
Uptime: —

Overview

About FusionXPay

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install FusionXPay?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does FusionXPay need an API key?

No required environment variable is listed on this record.

What transport does FusionXPay use?

FusionXPay runs locally over stdio.

When was FusionXPay last checked?

Last checked 2026-10-28. AI-native microservices payment platform integrating Stripe and PayPal. Features MCP Server (Spring AI, 8 tools) with 3-layer AOP safety pipeline, two-step confirmation for financial writes, and unified audit trail via Kafka. Built with Java 21, Spring Boot 3.5.

From the publisher

Documentation

Overview

FusionXPay is an AI-native payment platform built with Spring Cloud microservices. Beyond standard payment processing (Stripe and PayPal), webhook-driven status updates, refunds, and async notifications, FusionXPay ships with a full AI integration layer:

MCP Server — Exposes payment and order tools via the Model Context Protocol, allowing AI agents (e.g., Claude, Cursor) to query orders, initiate payments, and trigger refunds with AOP-enforced safety guards.
AI CLI — A picocli-based command-line interface for AI agents and automation pipelines to interact with FusionXPay programmatically.
AI Auth — An OAuth2-inspired browser-based consent flow that lets AI agents acquire scoped tokens for authorized API access.
Platform Audit — API Gateway emits ingress audit events to Kafka (platform-audit-log topic) for every external request, while CLI/MCP attach X-Audit-* metadata for source/action attribution.

Architecture

Services

Service	Port	What it does
API Gateway	8080	Routes requests, enforces JWT Bearer auth, Redis-backed rate limiting, emits platform audit events
Order Service	8082	Order lifecycle, merchant-scoped data isolation
Payment Service	8081	Provider integration (Stripe/PayPal), webhook handling, refunds
Notification Service	8083	Kafka-driven async notification delivery
Admin Service	8084	JWT-authenticated admin/merchant management and AI auth sessions

AI Layer

Component	What it does
MCP Server	Exposes FusionXPay tools via Model Context Protocol; AOP safety pipeline guards all invocations
AI CLI	picocli-based CLI for AI agents to authenticate, query orders/payments, and trigger actions
AI Common	Shared DTOs for AI auth flows (authorize, poll, consent, token exchange, revoke)

Infrastructure

Component	Purpose
MySQL	Persistence for all services
Redis	Rate limiting (gateway) and caching/idempotency (payment)
Kafka	Event bus — `payment-events` (payment→order), `order-events` (order→notification), `platform-audit-log` (gateway ingress audit)
Eureka	Service discovery
Prometheus + Grafana + Loki	Metrics, dashboards, and centralized log aggregation

AI Integration

MCP Server

The MCP Server (ai/ai-mcp-server) implements the Model Context Protocol so that AI agents can interact with FusionXPay as a native tool provider.

Available tools (via FusionXMcpTools):

Tool	Description
`get_order`	Retrieve full order details by order ID or order number
`get_order_status`	Get only the status projection for an order
`search_orders`	Search merchant orders with optional status, order number, and date filters
`query_payment`	Query a payment by transaction ID or order ID
`search_payments`	Search merchant payments with optional status and date filters
`initiate_payment`	Prepare a payment request — returns `CONFIRMATION_REQUIRED`; must be followed by `confirm_action`
`refund_payment`	Prepare a refund request — returns `CONFIRMATION_REQUIRED`; must be followed by `confirm_action`
`confirm_action`	Execute a previously prepared write action using its confirmation token

AOP Safety Pipeline — every tool call passes through three aspects in sequence:

InputSafetyAspect → ToolAuditAspect → OutputSafetyAspect

InputSafetyAspect — validates and sanitizes tool inputs before execution
ToolAuditAspect — attaches MCP audit metadata (X-Audit-*) to downstream gateway-bound requests
OutputSafetyAspect — redacts or prevents sensitive data from leaking to the AI agent

AI CLI

The AI CLI (ai/ai-cli) is a picocli-based Spring Boot application that AI agents or automated pipelines can invoke from the command line.

Available command groups:

Command	Description
`auth login`	Start the browser-based AI consent flow
`auth status`	Check current authentication status
`auth logout`	Revoke the current AI token
`order get <id>`	Get an order by ID
`order status <id>`	Get an order's current status
`order search`	Search orders
`payment pay`	Initiate a payment
`payment confirm`	Confirm a pending payment
`payment refund`	Refund a payment
`payment query`	Query payment details
`payment search`	Search payments

AI Auth Flow

AI agents obtain scoped access tokens through a browser-based consent flow managed by Admin Service (POST /api/v1/admin/auth/ai/*). The flow mode depends on the client:

CLI — attempts a callback flow first (PKCE + local HTTP server on 127.0.0.1 to receive the redirect); if that fails (e.g., no browser or port conflict), it falls back to the device-code flow where the user visits a verification URL manually.
MCP — uses the device-code flow directly, since MCP clients run headlessly without a local callback server.

Both flows share a two-phase poll-then-token exchange: poll returns only a status, and the token is obtained in a separate POST /token call once the status is APPROVED.

API base path: http://localhost:8080/api/v1/admin/auth/ai/{endpoint} (via API Gateway on port 8080; browser approval uses GET /consent, token/session operations use POST)

Platform Audit

Every external request that crosses API Gateway is recorded to Kafka and can be persisted to MySQL through Kafka Connect:

MCP Server path: ToolAuditAspect (AOP) → injects X-Audit-Source=MCP-Java, tool action name, and a correlation ID into each gateway request

CLI path: CliExecutionStrategy (picocli execution hook) → injects X-Audit-Source=CLI-Java, command action name, and a correlation ID into each gateway request

Both paths converge at:

GatewayAuditFilter emits a PlatformAuditEvent to the platform-audit-log topic for every inbound request
Kafka Connect JDBC Sink persists events to the platform_audit_log table
Source/action attribution remains consistent across CLI, MCP, and future SDK clients through the shared X-Audit-* contract

Quick Start

Prerequisites

Requirement	Version
Java	21+
Maven	3.6+
Docker	20.10+
Docker Compose	2.0+

Setup

git clone https://github.com/Manho/FusionXPay.git
cd FusionXPay
cp .env.always-on.example .env.always-on

Edit .env.always-on with your infrastructure hosts, database credentials, payment provider keys, and callback URLs.

Start Everything

docker compose -f docker-compose.always-on.yml --env-file .env.always-on up -d --build

Verify

./scripts/check-always-on-health.sh ./.env.always-on
./scripts/verify-service-chain.sh

Useful Endpoints

Endpoint	Purpose
`http://localhost:8080/actuator/health`	Gateway health
`http://localhost:8080/api/v1/admin/auth/ai/authorize`	AI Agent auth entry point (via gateway)
`http://localhost:3001`	Grafana dashboards
`http://localhost:9090`	Prometheus
`http://localhost:3100`	Loki log query

Docker Compose Profiles

File	Use case
`docker-compose.yml`	Local development — infrastructure only (MySQL, Redis, Kafka, Eureka)
`docker-compose.prod.yml`	Production image builds
`docker-compose.always-on.yml`	Long-running deployment with health checks and resource limits
`docker-compose.monitoring.yml`	Observability stack (Prometheus, Grafana, Loki, Promtail)

Testing

# Unit tests
mvn test

# Integration tests (Testcontainers spins up MySQL, Redis, Kafka)
mvn verify -pl services/api-gateway

# Service-specific tests
mvn test -pl services/payment-service
mvn test -pl services/admin-service
mvn test -pl ai/ai-mcp-server
mvn test -pl ai/ai-cli

# Runtime verification (requires running stack)
./scripts/check-always-on-health.sh ./.env.always-on
./scripts/verify-service-chain.sh

# End-to-end payment flows (sandbox keys required)
./scripts/e2e-payment-refund.sh stripe
./scripts/e2e-payment-refund.sh paypal

Project Structure

FusionXPay/
├── services/
│   ├── api-gateway/           # Spring Cloud Gateway, rate limiting, auth routing, platform audit emission
│   ├── order-service/         # Order lifecycle and merchant isolation
│   ├── payment-service/       # Provider integration, webhooks, refunds
│   ├── notification-service/  # Kafka-driven notifications
│   └── admin-service/         # Admin/merchant APIs and AI auth sessions
├── ai/
│   ├── ai-mcp-server/         # Model Context Protocol server with AOP safety pipeline
│   ├── ai-cli/                # picocli-based CLI for AI agent interactions
│   └── ai-common/             # Shared DTOs for AI auth flows
├── common/                    # Shared DTOs and utilities
├── mysql-init/                # Database initialization scripts
├── scripts/                   # Deploy, verify, backup, rollback, E2E utilities
├── monitoring/                # Prometheus, Grafana, Loki, Promtail configs
├── docs/                      # Architecture, deployment, platform audit, and testing docs
└── .github/workflows/         # CI, Docker build, and deployment pipelines

Documentation

Document	Purpose
Architecture	System structure and service responsibilities
Platform Audit Sink	Kafka Connect setup for persisting `platform-audit-log` into MySQL
Process Flow	Payment flow diagrams and sequence explanations
Requirements	Product and API requirements
Testing Strategy	Test layers and coverage approach
Performance Baseline	k6 load test results
Reliability Report	Recovery and resilience findings
Operations Runbook	Monitoring, backup, and local ops
Always-On Deployment	Long-running deployment setup
Auto Deploy	CI/CD deployment automation

Project	Description
FusionXPay Frontend	Next.js dashboard, landing page, and docs UI

License

This project is licensed under the MIT License. See LICENSE for details.

FusionXPay

Manho3stars

Finance

Install Run on PlugMCP

GitHub Website

Run on PlugMCP

1# FusionXPay

README.mdMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

Install from the publisher. Not a PlugMCP endpoint.

Run on PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: MIT
Last checked: 2026-10-28

Stars: 3
Tools: —
Uptime: —

Overview

About FusionXPay

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install FusionXPay?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does FusionXPay need an API key?

No required environment variable is listed on this record.

What transport does FusionXPay use?

FusionXPay runs locally over stdio.

When was FusionXPay last checked?

From the publisher

Documentation

Overview

MCP Server — Exposes payment and order tools via the Model Context Protocol, allowing AI agents (e.g., Claude, Cursor) to query orders, initiate payments, and trigger refunds with AOP-enforced safety guards.
AI CLI — A picocli-based command-line interface for AI agents and automation pipelines to interact with FusionXPay programmatically.
AI Auth — An OAuth2-inspired browser-based consent flow that lets AI agents acquire scoped tokens for authorized API access.
Platform Audit — API Gateway emits ingress audit events to Kafka (platform-audit-log topic) for every external request, while CLI/MCP attach X-Audit-* metadata for source/action attribution.

Architecture

Services

Service	Port	What it does
API Gateway	8080	Routes requests, enforces JWT Bearer auth, Redis-backed rate limiting, emits platform audit events
Order Service	8082	Order lifecycle, merchant-scoped data isolation
Payment Service	8081	Provider integration (Stripe/PayPal), webhook handling, refunds
Notification Service	8083	Kafka-driven async notification delivery
Admin Service	8084	JWT-authenticated admin/merchant management and AI auth sessions

AI Layer

Component	What it does
MCP Server	Exposes FusionXPay tools via Model Context Protocol; AOP safety pipeline guards all invocations
AI CLI	picocli-based CLI for AI agents to authenticate, query orders/payments, and trigger actions
AI Common	Shared DTOs for AI auth flows (authorize, poll, consent, token exchange, revoke)

Infrastructure

Component	Purpose
MySQL	Persistence for all services
Redis	Rate limiting (gateway) and caching/idempotency (payment)
Kafka	Event bus — `payment-events` (payment→order), `order-events` (order→notification), `platform-audit-log` (gateway ingress audit)
Eureka	Service discovery
Prometheus + Grafana + Loki	Metrics, dashboards, and centralized log aggregation

AI Integration

MCP Server

The MCP Server (ai/ai-mcp-server) implements the Model Context Protocol so that AI agents can interact with FusionXPay as a native tool provider.

Available tools (via FusionXMcpTools):

Tool	Description
`get_order`	Retrieve full order details by order ID or order number
`get_order_status`	Get only the status projection for an order
`search_orders`	Search merchant orders with optional status, order number, and date filters
`query_payment`	Query a payment by transaction ID or order ID
`search_payments`	Search merchant payments with optional status and date filters
`initiate_payment`	Prepare a payment request — returns `CONFIRMATION_REQUIRED`; must be followed by `confirm_action`
`refund_payment`	Prepare a refund request — returns `CONFIRMATION_REQUIRED`; must be followed by `confirm_action`
`confirm_action`	Execute a previously prepared write action using its confirmation token

AOP Safety Pipeline — every tool call passes through three aspects in sequence:

InputSafetyAspect → ToolAuditAspect → OutputSafetyAspect

InputSafetyAspect — validates and sanitizes tool inputs before execution
ToolAuditAspect — attaches MCP audit metadata (X-Audit-*) to downstream gateway-bound requests
OutputSafetyAspect — redacts or prevents sensitive data from leaking to the AI agent

AI CLI

The AI CLI (ai/ai-cli) is a picocli-based Spring Boot application that AI agents or automated pipelines can invoke from the command line.

Available command groups:

Command	Description
`auth login`	Start the browser-based AI consent flow
`auth status`	Check current authentication status
`auth logout`	Revoke the current AI token
`order get <id>`	Get an order by ID
`order status <id>`	Get an order's current status
`order search`	Search orders
`payment pay`	Initiate a payment
`payment confirm`	Confirm a pending payment
`payment refund`	Refund a payment
`payment query`	Query payment details
`payment search`	Search payments

AI Auth Flow

AI agents obtain scoped access tokens through a browser-based consent flow managed by Admin Service (POST /api/v1/admin/auth/ai/*). The flow mode depends on the client:

CLI — attempts a callback flow first (PKCE + local HTTP server on 127.0.0.1 to receive the redirect); if that fails (e.g., no browser or port conflict), it falls back to the device-code flow where the user visits a verification URL manually.
MCP — uses the device-code flow directly, since MCP clients run headlessly without a local callback server.

Both flows share a two-phase poll-then-token exchange: poll returns only a status, and the token is obtained in a separate POST /token call once the status is APPROVED.

API base path: http://localhost:8080/api/v1/admin/auth/ai/{endpoint} (via API Gateway on port 8080; browser approval uses GET /consent, token/session operations use POST)

Platform Audit

Every external request that crosses API Gateway is recorded to Kafka and can be persisted to MySQL through Kafka Connect:

MCP Server path: ToolAuditAspect (AOP) → injects X-Audit-Source=MCP-Java, tool action name, and a correlation ID into each gateway request

CLI path: CliExecutionStrategy (picocli execution hook) → injects X-Audit-Source=CLI-Java, command action name, and a correlation ID into each gateway request

Both paths converge at:

GatewayAuditFilter emits a PlatformAuditEvent to the platform-audit-log topic for every inbound request
Kafka Connect JDBC Sink persists events to the platform_audit_log table
Source/action attribution remains consistent across CLI, MCP, and future SDK clients through the shared X-Audit-* contract

Quick Start

Prerequisites

Requirement	Version
Java	21+
Maven	3.6+
Docker	20.10+
Docker Compose	2.0+

Setup

git clone https://github.com/Manho/FusionXPay.git
cd FusionXPay
cp .env.always-on.example .env.always-on

Edit .env.always-on with your infrastructure hosts, database credentials, payment provider keys, and callback URLs.

Start Everything

docker compose -f docker-compose.always-on.yml --env-file .env.always-on up -d --build

Verify

./scripts/check-always-on-health.sh ./.env.always-on
./scripts/verify-service-chain.sh

Useful Endpoints

Endpoint	Purpose
`http://localhost:8080/actuator/health`	Gateway health
`http://localhost:8080/api/v1/admin/auth/ai/authorize`	AI Agent auth entry point (via gateway)
`http://localhost:3001`	Grafana dashboards
`http://localhost:9090`	Prometheus
`http://localhost:3100`	Loki log query

Docker Compose Profiles

File	Use case
`docker-compose.yml`	Local development — infrastructure only (MySQL, Redis, Kafka, Eureka)
`docker-compose.prod.yml`	Production image builds
`docker-compose.always-on.yml`	Long-running deployment with health checks and resource limits
`docker-compose.monitoring.yml`	Observability stack (Prometheus, Grafana, Loki, Promtail)

Testing

# Unit tests
mvn test

# Integration tests (Testcontainers spins up MySQL, Redis, Kafka)
mvn verify -pl services/api-gateway

# Service-specific tests
mvn test -pl services/payment-service
mvn test -pl services/admin-service
mvn test -pl ai/ai-mcp-server
mvn test -pl ai/ai-cli

# Runtime verification (requires running stack)
./scripts/check-always-on-health.sh ./.env.always-on
./scripts/verify-service-chain.sh

# End-to-end payment flows (sandbox keys required)
./scripts/e2e-payment-refund.sh stripe
./scripts/e2e-payment-refund.sh paypal

Project Structure

FusionXPay/
├── services/
│   ├── api-gateway/           # Spring Cloud Gateway, rate limiting, auth routing, platform audit emission
│   ├── order-service/         # Order lifecycle and merchant isolation
│   ├── payment-service/       # Provider integration, webhooks, refunds
│   ├── notification-service/  # Kafka-driven notifications
│   └── admin-service/         # Admin/merchant APIs and AI auth sessions
├── ai/
│   ├── ai-mcp-server/         # Model Context Protocol server with AOP safety pipeline
│   ├── ai-cli/                # picocli-based CLI for AI agent interactions
│   └── ai-common/             # Shared DTOs for AI auth flows
├── common/                    # Shared DTOs and utilities
├── mysql-init/                # Database initialization scripts
├── scripts/                   # Deploy, verify, backup, rollback, E2E utilities
├── monitoring/                # Prometheus, Grafana, Loki, Promtail configs
├── docs/                      # Architecture, deployment, platform audit, and testing docs
└── .github/workflows/         # CI, Docker build, and deployment pipelines

Documentation

Document	Purpose
Architecture	System structure and service responsibilities
Platform Audit Sink	Kafka Connect setup for persisting `platform-audit-log` into MySQL
Process Flow	Payment flow diagrams and sequence explanations
Requirements	Product and API requirements
Testing Strategy	Test layers and coverage approach
Performance Baseline	k6 load test results
Reliability Report	Recovery and resilience findings
Operations Runbook	Monitoring, backup, and local ops
Always-On Deployment	Long-running deployment setup
Auto Deploy	CI/CD deployment automation

Project	Description
FusionXPay Frontend	Next.js dashboard, landing page, and docs UI

License

This project is licensed under the MIT License. See LICENSE for details.

Add this server

Host a copy with our keys and logs.

Server facts

About FusionXPay

Tools

Questions

How do I install FusionXPay?

Does FusionXPay need an API key?

What transport does FusionXPay use?

When was FusionXPay last checked?

Documentation

Overview

Architecture

Services

AI Layer

Infrastructure

AI Integration

MCP Server

AI CLI

AI Auth Flow

Platform Audit

Quick Start

Prerequisites

Setup

Start Everything

Verify

Useful Endpoints

Docker Compose Profiles

Testing

Project Structure

Documentation

Related

License

Add this server

Host a copy with our keys and logs.

Server facts

About FusionXPay

Tools

Questions

How do I install FusionXPay?

Does FusionXPay need an API key?

What transport does FusionXPay use?

When was FusionXPay last checked?

Documentation

Overview

Architecture

Services

AI Layer

Infrastructure

AI Integration

MCP Server

AI CLI

AI Auth Flow

Platform Audit

Quick Start

Prerequisites

Setup

Start Everything

Verify

Useful Endpoints

Docker Compose Profiles

Testing

Project Structure

Documentation

Related

License