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 2.2.2

• The deferred Fee Leg goes after CONFIRMED - for every transfer type the Fee Leg is executed only after payware has accepted CONFIRMED; during a DEFERRED transfer the institution keeps the Fee Amount reserved on the payer's account and releases it if the Merchant Leg fails. feeLegOutcome is optional and only NOT_EXECUTED is accepted: the finalize tool refuses RETURNED before sending
• A merchant that can no longer accept payments - the institution tools describe ERR_PAYEE_UNAVAILABLE (409): payware refuses EXECUTING for a merchant that is switched off, nothing is locked and no money may move

What's New in 2.2.1

• Partial product and schedule updates - update_product and update_schedule send only the fields you give, and payware keeps every stored value the request leaves out. 2.2.0 read the product first and sent it whole, which payware refuses once the product's start date has passed
• ISV product images - payware_products_get_product_image works for an ISV acting for a merchant, on the merchant's plan and for products in the shops the merchant assigned to the ISV
• ISV reports, two ways - with a merchant's token an ISV runs that merchant's reports, limited to the shops the merchant assigned to it; without one, its own reports on everything it handled. Each request is found only in the context it was run in

What's New in 2.2.0

• Execution lock - A payment institution finalizes with EXECUTING immediately before money moves, then CONFIRMED once the Merchant Leg has completed, or FAILED; transferType and feeLegOutcome are new
• Deferred Merchant Leg - Merchants, and ISVs for them, can allow a credit transfer that settles later with deferredAllowed
• Code examples - payware_generate_code_example writes complete, signed programs for real routes only, including the institution finalize flow

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.

• **Placeme

... View full README on GitHub