Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
payware
Overview
Description from the maker (original English)
payware A2A payments API for merchants, ISVs and payment institutions
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Online shops & payments
- You need to fill in: PAYWARE_PARTNER_ID, PAYWARE_SANDBOX_PRIVATE_KEY_PATH, PAYWARE_OAUTH_CLIENT_SECRET
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
PAYWARE_PARTNER_TYPE,PAYWARE_PARTNER_ID,PAYWARE_SANDBOX_PRIVATE_KEY_PATH,PAYWARE_PRODUCTION_PRIVATE_KEY_PATH,PAYWARE_OAUTH_CLIENT_ID,PAYWARE_OAUTH_CLIENT_SECRET,PAYWARE_MCP_TOOLSETS
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"payware": {
"command": "npx",
"args": [
"-y",
"@payware/mcp-server"
],
"env": {
"PAYWARE_PARTNER_TYPE": "your-value",
"PAYWARE_PARTNER_ID": "your-value",
"PAYWARE_SANDBOX_PRIVATE_KEY_PATH": "your-value",
"PAYWARE_PRODUCTION_PRIVATE_KEY_PATH": "your-value",
"PAYWARE_OAUTH_CLIENT_ID": "your-value",
"PAYWARE_OAUTH_CLIENT_SECRET": "your-value",
"PAYWARE_MCP_TOOLSETS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add payware --env PAYWARE_PARTNER_TYPE=your-value --env PAYWARE_PARTNER_ID=your-value --env PAYWARE_SANDBOX_PRIVATE_KEY_PATH=your-value --env PAYWARE_PRODUCTION_PRIVATE_KEY_PATH=your-value --env PAYWARE_OAUTH_CLIENT_ID=your-value --env PAYWARE_OAUTH_CLIENT_SECRET=your-value --env PAYWARE_MCP_TOOLSETS=your-value -- npx -y @payware/mcp-serverFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"payware": {
"command": "npx",
"args": [
"-y",
"@payware/mcp-server"
],
"env": {
"PAYWARE_PARTNER_TYPE": "your-value",
"PAYWARE_PARTNER_ID": "your-value",
"PAYWARE_SANDBOX_PRIVATE_KEY_PATH": "your-value",
"PAYWARE_PRODUCTION_PRIVATE_KEY_PATH": "your-value",
"PAYWARE_OAUTH_CLIENT_ID": "your-value",
"PAYWARE_OAUTH_CLIENT_SECRET": "your-value",
"PAYWARE_MCP_TOOLSETS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"payware": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@payware/mcp-server"
],
"env": {
"PAYWARE_PARTNER_TYPE": "your-value",
"PAYWARE_PARTNER_ID": "your-value",
"PAYWARE_SANDBOX_PRIVATE_KEY_PATH": "your-value",
"PAYWARE_PRODUCTION_PRIVATE_KEY_PATH": "your-value",
"PAYWARE_OAUTH_CLIENT_ID": "your-value",
"PAYWARE_OAUTH_CLIENT_SECRET": "your-value",
"PAYWARE_MCP_TOOLSETS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
PAYWARE_PARTNER_TYPEenvPartner role: merchant, isv or payment_institution- Partner ID from the payware dashboard
- Path to the RSA private key for the sandbox
PAYWARE_PRODUCTION_PRIVATE_KEY_PATHenvPath to the RSA private key for productionPAYWARE_OAUTH_CLIENT_IDenvOAuth2 client ID (ISV partners only)- OAuth2 client secret (ISV partners only)
PAYWARE_MCP_TOOLSETSenvComma-separated toolsets to load, e.g. products,placements. Unset loads every tool. Toolsets: auth, transactions, products, placements, data, logs, poi, shops, onboarding, utils
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account payware, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Online shops & paymentsi
- More stars than 0% of the other 1744 servers in this category
- Published to the registry more recently than 85% of the other 1744 servers in this category
- Basic checks equal to or better than 100% of the other 1744 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is payware safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: PAYWARE_PARTNER_ID, PAYWARE_SANDBOX_PRIVATE_KEY_PATH, PAYWARE_OAUTH_CLIENT_SECRET
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (2.0.1) reached the registry 3 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Stripe MCP
Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.
MCP Cn Commerce
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
payware MCP Server
Official MCP (Model Context Protocol) server for payware payment API integration. This server enables AI assistants to interact with payware APIs, automating integration workflows for all partner types.
Releases are published to npm as @payware/mcp-server and to the official MCP Registry as io.github.payware/mcp-server. MIT licensed, see LICENSE.
Who Is This For?
- Merchants - Accept payments, manage products, generate transaction reports
- ISVs (Independent Software Vendors) - Build multi-merchant platforms with OAuth2 token management
- Payment Institutions - Process A2A transfers, handle Payment Choice Architecture with multiple payment methods
What's New in v1.2.0
- SHA-256 Authentication - Upgraded from MD5 to SHA-256 for JWT content hashing (
contentSha256header) - Updated Error Codes - New error codes:
ERR_INVALID_CONTENT_HASH,ERR_MISSING_CONTENT_HASH - Backward Compatibility - Deprecated MD5 functions retained for legacy support
Features
🔐 Authentication Tools
- RSA Key Generation: Generate secure 2048-bit RSA key pairs
- JWT Token Creation: Create properly formatted JWT tokens
- Sandbox Setup: Configure sandbox authentication
💳 Transaction Tools
- Create Transaction: Support PLAIN, QR, and BARCODE transactions
- Process Transaction: Process transactions with Payment Choice Architecture support
- Transaction Status: Check transaction status by ID
- Transaction History: Get finalized transaction details
- Callback Simulation: Test callback scenarios for merchants and payment institutions
📍 Point of Interaction (POI) Tools
- Set Price: Configure POI with amount, currency, and payment details
- Cancel Price: Clear active price from POI
- Get POI: Retrieve POI details and current state
- Get Status: Check POI transaction status
- Get QR Code: Generate QR code for POI payments
- List POIs: List all POIs for a merchant
📣 Campaign, Placement and Airing Tools
For merchants, and for ISVs acting for them. Changes need the merchant's PRM plan; reading works on every plan.
- Placements: Distribute a product through posters, TV spots, packaging, links or tags, each with its own
plID, so every payment it starts is attributed to it. Includes the QR code, barcode and short link of each placement - Campaigns: Group placements, across products, and read their combined results
- Airing Rules: Schedule when a placement is on air, with recurrences, time windows and time zones, and replace a whole schedule in one call
- Airing Calendar: Every airing across all products in a time range
- Results: Offers shown, payments started and confirmed, and confirmed amounts per placement or campaign
📋 Logs Tools (Premium)
- Query Logs: Search and filter application logs by level, logger, message content, and date range
- Log Status: Check log availability and storage information
- Download Logs: Get compressed archive of logs for offline analysis
🛠️ Utility Tools
- Advanced Code Generation: Generate complete integration code across 8 languages (Python, Node.js, PHP, Java, C#, Go, Ruby, cURL) with 16+ framework support
- Framework Integration: Framework-specific examples for Django, FastAPI, Express, NestJS, Laravel, Spring Boot, ASP.NET, and more
- Real-world Scenarios: Generate complete integration scenarios (e-commerce, ISV multi-merchant, P2P payments)
- Comprehensive Documentation: Auto-generate complete API documentation with code examples
- Request Formatting: Format and validate API requests
Quick Start
1. Installation
From npm (recommended):
npm install -g @payware/mcp-server
From source:
git clone https://github.com/payware/mcp-server.git
cd mcp-server npm install
2. Environment Configuration
Copy the example environment file and configure your credentials:
cp .env.example .env
Edit .env file:
# Partner ID from payware dashboard
PAYWARE_PARTNER_ID=your_partner_id_here
Path to private key file (relative to project root)
PAYWARE_SANDBOX_PRIVATE_KEY_PATH=keys/sandbox-your-private-key.pem PAYWARE_PRODUCTION_PRIVATE_KEY_PATH=keys/production-your-private-key.pem
Optional: Sandbox base URL (defaults to https://sandbox.payware.eu/api)
PAYWARE_SANDBOX_URL=https://sandbox.payware.eu/api
⚠️ Security Note: Never commit the .env file to version control. It contains sensitive credentials.
Choosing toolsets
Every tool definition goes into the assistant's context on every turn, and a merchant has over 70 of them. To offer only the groups you use, set PAYWARE_MCP_TOOLSETS to a comma-separated list:
PAYWARE_MCP_TOOLSETS=products,placements
Toolsets: auth, transactions, products, placements, data, logs, poi, shops, onboarding, utils. Unset, or all, loads every tool. An unknown name is ignored with a warning in the server log. A tool outside the chosen toolsets is neither listed nor callable; this narrows what the assistant is offered and does not change what your partner account may do. An ISV that obtains OAuth2 tokens through this server includes auth.
3. Start the MCP Server
npm start
4. Basic Integration Flow
- Generate RSA Keys
Tool: payware_authentication_generate_rsa_keys
- Create JWT Token
Tool: payware_authentication_create_jwt_token
Parameters:
- partnerId: (from PAYWARE_PARTNER_ID)
- privateKey: (from environment-specific key path)
- Setup Sandbox
Tool: payware_authentication_setup_sandbox_auth
Parameters:
- partnerId: (from PAYWARE_PARTNER_ID)
- Create Transaction
Tool: payware_operations_create_transaction
Parameters:
- partnerId: (from PAYWARE_PARTNER_ID)
- privateKey: (from environment-specific key path)
- amount: 10.00
- currency: EUR
- reasonL1: "Payment description"
- type: PLAIN
- Check Status
Tool: payware_operations_get_transaction_status
Parameters:
- partnerId: (from PAYWARE_PARTNER_ID)
- privateKey: (from environment-specific key path)
- transactionId: TRANSACTION_ID
API Request Structure
The payware MCP server transforms flat parameter inputs into the proper nested JSON structure required by the payware API:
Create Transaction Request Structure
{
// ROOT LEVEL - Transaction metadata "shop": "SHOP001", // Optional: Shop code "account": "GB29NWBK60161331926810", // Optional: Account identifier "friendlyName": "Your Shop Name", // Optional: Account holder name "callbackUrl": "https://callback.url", // Optional: HTTPS callback URL "passbackParams": "{\"orderId\":\"12345\"}", // Optional: Callback parameters
// TRANSACTION DATA - Required transaction information "trData": { "amount": "25.50", // String/Number: Amount (can be "0.00" for flexible amounts) "currency": "EUR", // REQUIRED: ISO 3-character currency code "reasonL1": "Payment for services", // REQUIRED: Transaction description (max 100 chars) "reasonL2": "Order #12345" // Optional: Additional description (max 100 chars) },
// TRANSACTION OPTIONS - Transaction behavior settings "trOptions": { "type": "QR", // PLAIN, QR, or BARCODE (default: PLAIN) "timeToLive": 300 // Seconds: 60-600 (default: 120) },
// QR OPTIONS - Only included when type=QR "qrOptions": { "qrFormat": "PNG", // PNG, SVG, JPG, GIF, BMP (default: SVG) "qrBorder": 4, // Border modules: 1-10 (default: 4) "qrErrorCorrection": "QUARTILE", // LOW, MEDIUM, QUARTILE, HIGH (default: QUARTILE) "qrScale": 16, // Pixel size: 1-100 (default: 16, irrelevant for SVG) "qrVersion": 10 // QR version: 1-40 (default: 10, auto if not specified) },
// BARCODE OPTIONS - Only included when type=BARCODE "barOptions": { "barFormat": "SVG", // PNG, SVG, JPG (default: SVG) "barModuleWidth": 2, // Module width: 1-10 (default: 2) "barBarHeight": 100, // Height: 15-1000 (default: 100) "barFontSize": 12, // Font size: 0-24 (default: 12) "barHumanReadableLocation": "NONE" // NONE, BOTTOM, TOP (default: NONE) } }
Parameter Mapping
When using MCP tools, parameters are automatically mapped to the correct API structure:
| MCP Tool Parameter | API Location | Description |
|---|---|---|
partnerId, privateKey | Authentication | Used for JWT signing, not sent in request |
account, friendlyName, shop, callbackUrl, passbackParams | Root Level | Transaction metadata |
amount, currency, reasonL1, reasonL2 | trData object | Core transaction data |
type, timeToLive | trOptions object | Transaction behavior |
qrFormat, qrBorder, etc. | qrOptions object | QR code settings (when type=QR) |
barFormat, barModuleWidth, etc. | barOptions object | Barcode settings (when type=BARCODE) |
Available Tools
Code Generation & Documentation
payware_generate_code_example
Advanced multi-language code generation with framework support
Supports 60+ operations across all partner types:
- Transactions: create_transaction, get_transaction_status, cancel_transaction, process_transaction, get_transaction_history, simulate_callback
- Products: create_product, get_product, update_product, delete_product, list_products, get_product_image, create_schedule, update_schedule, delete_schedule, list_schedules
- OAuth2 (ISV only): obtain_token, get_token_info, create_token_simple, refresh_token, revoke_token, list_active_tokens
- Data: generate_report, get_report_status, export_report, download_export, cancel_report, list_reports, get_analytics_summary, create_custom_report
- P2P (Payment Institution): initiate_p2p_transfer, accept_p2p_transfer, reject_p2p_transfer, get_p2p_transfer_status, list_p2p_transfers, cancel_p2p_transfer, create_p2p_link, get_p2p_analytics
- Soundbites (Payment Institution): register_audio, get_audio, update_audio, delete_audio, list_audios, create_soundbite_transaction, stream_audio, download_audio, get_soundbite_analytics, create_audio_playlist, get_audio_preview
payware_generate_documentation
Comprehensive documentation generator
Generates complete API documentation with working code examples for any partner type and programming language combination.
Authentication
payware_authentication_generate_rsa_keys
Generate RSA key pair for API authentication.
Parameters:
keySize(optional): RSA key size in bits (default: 2048)
payware_authentication_create_jwt_token
Create JWT token for API authentication.
Parameters:
partnerId(required): Partner ID from paywareprivateKey(required): RSA private key in PEM format
payware_authentication_validate_jwt
Validate JWT token format and signature.
Parameters:
token(required): JWT token to validatepartnerId(required): Partner ID for validation
payware_authentication_test_jwt
Test JWT token with payware API.
Parameters:
token(required): JWT token to testpartnerId(required): Partner ID
payware_authentication_setup_sandbox_auth
Setup sa
Only the beginning is shown; read the rest in the repo