Netaxept MCP Server

This page gives an overview of Netaxept's MCP capabilities.

Overview

The Netaxept MCP Server implements the Model Context Protocol (MCP), exposing common operations as tools that compatible LLM clients and AI agents can discover and invoke. This enables users to chat with the Netaxept APIs with natural language through LLM clients and apps like ChatGPT and Gemini.
This document covers how it works, how to integrate and the available tools.

The Netaxept MCP Server is currently in beta with functionality updated often.

How It Works

The Netaxept MCP server acts as a standardized bridge between the client and Netaxept APIs. The client interprets natural language requests, routes them to the MCP server, and the server translates intent into the specific Netaxept API calls before returning the API results to the client where the chat can continue. Sequence Diagram

Getting Started

Prerequisites

Before connecting your MCP client, confirm you have:

OAuth credentials
- token_endpoint
- scope
- client_id
- client_secret
Netaxept MCP Server URL for the given environment

For onboarding and credentials, contact your Account Manager.

Retrieving the Bearer Access Token

The Netaxept MCP Server supports the OAuth 2.0 flow to obtain Bearer Access Tokens. Once a Bearer Access Token is issued it can be used to call the Netaxept MCP endpoint by including it in the Authorization header of your HTTP requests.

If your MCP client supports OAuth negotiation, the Bearer Access Token will be automatically requested and refreshed. Alternatively, please refer to the OAuth documentation to learn more.

Note: Bearer Access Tokens are short-lived, the client must refresh tokens before expiry to call Netaxept MCP Server tools.

Connecting to Netaxept MCP Server

The Netaxept MCP server can be integrated with any MCP-compatible LLM client or agent, e.g. ChatGPT, Gemini, Claude. Please refer to your client's MCP integration documentation for guidance.

For clients where you configure MCP servers via JSON, see the following reference config:

code
{
  "mcpServers": {
    "netaxept": {
      "type": "http",
      "url": "<MCP_ENDPOINT_URL>",
      "headers": {
        "Accept": "application/json, text/event-stream",
        "Authorization": "Bearer <ACCESS_TOKEN>"
      }
    }
  }
}

For clients where you configure MCP servers in an application, see the following example: mcp config screenshot

Once configured, verify your connection by interacting with the MCP. For example, list the available tools provided by the Netaxept MCP: mcp verify connection screenshot

Tools - What can the MCP do?

The Netaxept MCP server offers the following tools with access based on the role your client has been onboarded with either for Service Operations or Commerce Operations.

Nr	Role	Tool	Description
1	Service Operations	Merchant Information	Retrieves merchant profile and account context. Required inputs: `none`.
2	Service Operations	Transaction Data	Retrieves payment status and transaction details for support and operations. Required inputs: `transaction ID`.
3	Service Operations	Daily Report	Generates a daily transaction summary report. Required inputs: `report date`.
4	Service Operations	Batch Report	Retrieves batch-oriented transaction report data by date range. Required inputs: `start date`, `end date`. Optional inputs: `timezone offset`
5	Service Operations	Turnover Report	Analyzes turnover by period and currency. Required inputs: `currency code`, `start date`, `end date`. Optional inputs: `aggregation`, `timezone offset`, `issuer IDs`.
6	Service Operations	Transactions Report	Analyzes transaction counts by period. Required inputs: `start date`, `end date`. Optional inputs: `aggregation`, `timezone offset`, `issuer IDs`, `include verified`.
7	Service Operations	Time of Purchase Report	Reviews transaction distribution by time of purchase. Required inputs: `start date`, `end date`. Optional inputs: `timezone offset`, `issuer IDs`.
8	Commerce Operations	Create Payment Link	Creates a shareable payment link to a Netaxept card payment window. Required inputs: `order ID`, `amount`, `currency code`, `expires at`, `return URL`, `idempotency key`. Optional inputs: `customer reference`, `description`, `tenant ID`.

Examples

Search for Transaction

Prompt: "Give me the transaction details for <Transaction_ID>" Transaction Search Screenshot - MCP

Retrieve Batch Report

Prompt: "Get the batch report for <Time_Period>" retrieve batch report screenshot - MCP

Create Payment Link

Prompt: "Create a payment link for <Payment_Details>" create payment link screenshot - MCP

The payment link opens a Netaxept card payment window. Below is an example of this payment window with Click to Pay enabled and the default look and feel. Some elements of this payment window can be customized and branded. See the Customization and branding section for a link to more information of this.

Support & Feedback

The Netaxept MCP Server is in active development and the list of supported tools will grow in future releases. We welcome your feedback.

For onboarding and credentials, contact your Nexi Account Manager.
For technical issues or feature requests during the beta period, reach out through your standard support channel.

Customization and Branding of the Payment Window

How to customize and brand the payment terminal window.