Payments Orchestration Platform MCP Server

   
Last updated: March 19, 2026

Connect your AI-powered application to the Payments Orchestration Platform using the Model Context Protocol.

Once connected, any MCP-compatible LLM client can discover and invoke Payments Orchestration Platform payment tools, such as capturing payments, processing refunds, and querying transactions, through natural language or programmatic agent workflows.

What is MCP? The Model Context Protocol is an open standard that provides a uniform way for LLM applications to connect to external tools and data sources. Instead of writing custom integrations for each AI framework, you configure a single MCP server and any compatible client can use it.

Prerequisites

Before you begin, make sure you have:

  • An active Payments Orchestration Platform merchant account with API credentials
  • An MCP-compatible LLM client (see Supported clients)
  • Basic familiarity with JSON configuration files

Your credentials

When you sign up for Payments Orchestration Platform API access, you receive two credentials passed as HTTP headers on every request.

HeaderDescription
X-Entity-IdIdentifies your merchant entity on the Payments Orchestration Platform
X-TokenAuthenticates your requests, treat this like a password
Security: Never commit your X-Token to source control or expose it in client-side code. Store it in environment variables or a secrets manager.

Server endpoint

The Payments Orchestration Platform MCP Server uses the Streamable HTTP transport, the current MCP standard for remote servers, broadly supported across all major LLM clients.

EnvironmentURL
Test https://eu-test.oppwa.com/agentic/v1/mcp— contact support to enable
Production https://eu-prod.oppwa.com/agentic/v1/mcp — not available yet

Configuration

MCP clients are configured via a JSON file that specifies the server endpoint, transport type, and required headers. Below is the minimal configuration to connect to the Payments Orchestration Platform MCP test server.

{
  "servers": {
    "OPP-payments": {
      "type": "http",
      "url": "https://eu-test.OPP.com/agentic/v1/mcp",
      "headers": {
        "X-Entity-Id": "YOUR_ENTITY_ID",
        "X-Token":     "YOUR_ACCESS_TOKEN"
      }
    }
  }
}

Replace YOUR_ENTITY_ID and YOUR_ACCESS_TOKEN with the credentials from your Payments Orchestration Platform merchant UI.

Supported clients

The Payments Orchestration Platform MCP Server is compatible with any LLM client that supports the Streamable HTTP (or SSE) transport, including:

ClientTransportNotes
Claude (claude.ai / Desktop)Streamable HTTPVia custom connector in Settings
Cursor / AI-powered IDEsStreamable HTTP / SSEAdd via MCP settings panel
OpenAI Agents SDK (Python)Streamable HTTPMCPServerStreamableHttp
AnythingLLMStreamable HTTPUse "type": "streamable"
Custom agents (MCP SDKs)AnyTypeScript and Python SDKs available
Clients that only support stdio transport cannot connect to remote HTTP servers directly. Consult your client's documentation for a local-to-remote gateway option.

Client examples

Claude Desktop

  1. Open Settings → Connectors → Add Custom Connector
  2. Enter the server URL: https://eu-test.OPP.com/agentic/v1/mcp
  3. Add headers X-Entity-Id and X-Token with your credentials
  4. Save and enable the connector in your chat session

OpenAI Agents SDK (Python)

from agents import Agent
from agents.mcp import MCPServerStreamableHttp

OPP_server = MCPServerStreamableHttp(
    url="https://eu-test.OPP.com/agentic/v1/mcp",
    headers={
        "X-Entity-Id": "YOUR_ENTITY_ID",
        "X-Token":     "YOUR_ACCESS_TOKEN"
    }
)

agent = Agent(
    name="PaymentAgent",
    mcp_servers=[OPP_server]
)

AnythingLLM

Add the following entry to your anythingllm_mcp_servers.json file:

{
  "mcpServers": {
    "OPP-payments": {
      "type": "streamable",
      "url": "https://eu-test.OPP.com/agentic/v1/mcp",
      "headers": {
        "X-Entity-Id": "YOUR_ENTITY_ID",
        "X-Token":     "YOUR_ACCESS_TOKEN"
      }
    }
  }
}

Testing the connection

Once configured, ask your LLM client to list available tools, most clients will discover them automatically. You can also prompt:

"What payment tools do you have available?"

A successful connection returns the full list of Payments Orchestration Platform tools.

Tools summary

The Payments Orchestration Platform MCP Server exposes 8 tools across two categories.

Note on "Destructive": In the MCP protocol, destructiveHint: true signals a tool may produce irreversible side effects. For payment tools this means the operation moves money, alters transaction state, or triggers downstream processing at the acquirer, actions that generally cannot be undone by calling the tool again. This is a hint to MCP clients to prompt the user for explicit confirmation before execution. It does not mean the operation will fail, it signals that automation without human oversight is inadvisable.
Tool Category Description Required param Destructive
perform_capture Back-office Finalizes a pre-authorization (PA) for settlement referenceId (PA) Yes
perform_reversal Back-office Voids an uncaptured pre-authorization in full referenceId (PA) Yes
perform_refund Back-office Returns funds to the shopper after a debit (DB) referenceId (DB) Yes
perform_rebill Back-office Charges an additional amount on top of a captured transaction referenceId (DB) Yes
perform_chargeback Back-office Records a bank-initiated dispute reversal referenceId (DB) Yes
perform_chargeback_reversal Back-office Reverses a chargeback after successful representment referenceId (CB) Yes
get_transactions Reporting Retrieves transaction(s) by UUID or merchant order ID — (all optional) No
search_transactions Reporting Searches transactions using rich structured filters — (all optional) No

Use cases

Below are two example use cases showing how an LLM agent can combine Payments Orchestration Platform MCP tools with natural language to automate payment workflows.

Intelligent Customer Service
Search transactions & issue refunds
search_transactions perform_refund

A support agent uses the MCP server to look up a customer's transaction history and process refunds on their behalf, without leaving the chat interface.

Example prompts
💬 "Find all failed credit card transactions for customer john.doe@example.com in the last 30 days."
💬 "Show me all refunds issued this week and their current status."
💬 "The customer says they were charged twice for order ORD-20483. Look up the transactions and issue a refund for the duplicate charge."
💬 "Issue a partial refund of €15.00 for transaction 8ac7a4a19a72d98c019a735d3b180f8d and add the memo 'item returned'."
Shopping Assistant
Discover products & issue payments
get_transactions perform_capture perform_reversal

A conversational shopping agent pre-authorizes payment while the customer confirms their order, then captures or voids the authorization based on the outcome.

Example prompts
💬 "The customer has confirmed their order. Capture the pre-authorized payment 8ac7a4a19a72d98c019a735d3b180f8d for the full amount."
💬 "The item is out of stock. Cancel the pre-authorization 8ac7a4a19a72d98c019a735d3b180f8d so the customer is not charged."
💬 "Look up all transactions for order ORD-88821 and confirm whether payment was successfully captured."
💬 "The customer added an extra item after checkout. Rebill an additional €24.99 on top of the original transaction 8ac7a4a19a72d98c019a735d3b180f8d."
Reminder: All prompts that trigger back-office operations should be gated behind human confirmation in your agent workflow. See Security best practices for guidance on configuring approval policies.

Security best practices

PracticeDetails
Use environment variablesInject X-Entity-Id and X-Token at runtime; never hardcode in config files
Test before productionAlways validate against eu-test.oppwa.com before switching to the live endpoint
Audit tool invocationsLog all payment-related tool calls, agents can invoke tools autonomously
Require human approvalConfigure MCP client approval policies for destructive tools (captures, refunds, chargebacks)

Next steps

 

See also