hipay

This MCP server integrates HiPay's Enterprise payment processing API into a Model Context Protocol (MCP) interface. It exposes tools to manage transactions, process payments, and handle hosted payment pages through a standardized MCP command surface. You can enable specific tools or all tools, and authenticate with HiPay using Basic Auth credentials passed via environment variables or command line arguments. The available tools include transaction retrieval (both V3 and V1 where supported), updating transactions (capture, refund, etc.), retrieving all transactions for an order, and creating hosted payment pages. To run, provide credentials and select the tools you want to enable. For example, you can run the server with all tools enabled or selectively enable transactions and hosted page tools as needed.

Prerequisites:

• Node.js 18+ (as required by the repository and MCP toolchain)
• npm or yarn

Step-by-step installation:

1. Ensure you have Node.js installed. Verify with: node -v npm -v
2. Install (or run directly with npx) the HiPay MCP server package: npx @hipay/mcp-server --tools=all

If you prefer to install locally:

1. Initialize a project (if needed): mkdir hipay-mcp && cd hipay-mcp npm init -y
2. Install the MCP server package: npm install @hipay/mcp-server
3. Run the server with the desired tools, providing credentials as env vars or CLI options: HIPAY_USERNAME=your_username HIPAY_PASSWORD=your_password HIPAY_ENVIRONMENT=stage npx @hipay/mcp-server --tools=all

Configuration via environment variables:

• HIPAY_USERNAME: Your HiPay API username (required)
• HIPAY_PASSWORD: Your HiPay API password (required)
• HIPAY_ENVIRONMENT: stage or production (default: stage)

Notes:

• The server uses Basic Auth credentials; keep usernames and passwords secure. Consider using a secrets manager in production.
• Environment can be stage or production; ensure corresponding HiPay endpoints are accessible.
• If you omit --tools, all available tools are enabled by default. You can specify tools as a comma-separated list (e.g., --tools=transactions.get,transactions.update).
• For V1 vs V3 API support, some tools (like transactions.get) may have V1 as an alternative method (transactions.getV1).
• When deploying in CI/CD, inject HIPAY_USERNAME, HIPAY_PASSWORD, and HIPAY_ENVIRONMENT as secrets rather than embedding them in commands.
• If you encounter authentication errors, verify that the provided credentials have the necessary permissions for the targeted environment.