Beanstream Payments Gateway for AI Agents (MCP) - n8n Workflow

AI/ML Engineers developing large language model (LLM) agents that require external tooling.
E-commerce platforms needing automated, agent-driven payment processing and customer profile management.
Developers looking for pre-built n8n templates to expose payment APIs as LLM tools.
n8n automation specialists seeking advanced examples of the n8n MCP node usage.

This specialized n8n workflow serves as a crucial middleware layer, transforming the complex Beanstream Payments API into 15 easy-to-use tools consumable by any AI agent framework (like LangChain or OpenAI Assistants). By leveraging the Multi-Channel Protocol (MCP) feature, this n8n automation allows AI agents to intelligently execute financial operations—such as making payments, managing customer profiles, and retrieving transaction reports—using natural language commands. This sophisticated n8n workflow eliminates the need for the AI agent to directly manage API keys, headers, or complex JSON structures. You can deploy this n8n workflow rapidly as one of the most effective n8n templates for fintech integrations.

This n8n workflow operates as a dedicated server endpoint, managing requests from an external AI agent:

1. AI Request: The flow is initiated by the dedicated n8n trigger, the Beanstream Payments MCP Server node, when an AI agent determines it needs to call a payment-related function.


2. Tool Selection: The MCP trigger receives the agent's request, which includes the intended tool (e.g., Make Payment or Delete profile) and necessary parameters.


3. Dynamic Execution: Based on the tool selected by the AI, the signal is routed to one of the 15 dedicated HTTP Request Tool n8n nodes.


4. Parameter Injection: Each n8n node utilizes the $fromAI() expression (e.g., {{ $fromAI('transId', 'The transaction id.', 'number') }}) to automatically inject context-relevant values provided by the AI agent into the API request URL or body.


5. API Call: The HTTP Request n8n node executes the call to the Beanstream API, handling authentication via generic HTTP headers.


6. Response Return: The Beanstream API response is then passed back through the MCP n8n trigger directly to the originating AI agent, maintaining the original data structure.

To deploy and utilize this n8n workflow, follow these steps:

1. Import the n8n Workflow: Copy the provided JSON and import it into your n8n instance.


2. Configure Credentials: All 15 HTTP Request Tool n8n nodes require authentication. You must set up a 'Generic Credential Type' in n8n, typically using HTTP Header Authorization (e.g., passing API keys in the Authorization header).


3. Activate the Workflow: Set the n8n workflow to active. This enables the MCP server.


4. Obtain the MCP URL: Copy the webhook URL exposed by the Beanstream Payments MCP Server n8n trigger node.


5. Integrate with AI Agent: Provide this copied MCP URL to your AI agent framework (e.g., in the tool configuration settings of your LLM application). The AI will automatically discover the 15 available tools (like Void Transaction and Tokenize credit card).

Beanstream Payments MCP Server (n8n trigger): This is the core n8n trigger node for the entire automation. It exposes a single webhook path (/beanstream-payments-mcp) that acts as the entry point for all AI tool calls. This critical n8n node serves as the orchestrator for the AI agent interactions.
Make Payment (n8n node - HTTP Request Tool): Handles initiating new payment transactions via a POST request to /api/v1/payments. This n8n node is configured as an AI tool.
Get payment (n8n node - HTTP Request Tool): Retrieves details of a specific payment. The transaction ID is dynamically pulled from the AI request using {{ $fromAI('transId', '...', 'number') }}.
Complete pre-auth (n8n node - HTTP Request Tool): Completes a previously authorized payment, utilizing a dynamic transaction ID provided by the AI agent.
Create Profile (n8n node - HTTP Request Tool): Manages customer profile creation, simplifying customer management tasks for the AI agent.
Delete profile (n8n node - HTTP Request Tool): Allows the AI to remove a customer profile, dynamically retrieving the required profileId via the $fromAI() n8n expression.

• Tokenize credit card (n8n node - HTTP Request Tool): Executes the process of tokenizing credit card information, a crucial security step integrated as a dedicated tool within this n8n workflow.