Bring Payment Gateway
to Claude Code
Learn how to connect Blink Payment to Claude Code and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Blink Payment MCP Server?
Empower your AI Agent with the full capability of Blink Payment. Blink Payment for AI Agents allows you to fully automate your financial operations directly from your isolated workspace.
What you can do
Automate Payments: Instantly list your recent payments, view detailed information, and even initiate refunds.
Generate Payment Intents: Create precise and quick payment intents and link them directly to customers without leaving your conversational flow.
Customer Management: Effortlessly create new customer profiles, fetch their details, and keep track of your customer base directly through your agent.
Paylinks on the Fly: Generate reusable paylinks to share with clients, accelerating the checkout and invoice resolution processes.
How it works
1. Secure your Blink Payment API credentials from your developer dashboard.
2. Add the API Key and Secret Key into the secure vault of your agent's platform.
3. Instruct your AI to generate a paylink, list recent successful transactions, or refund a specific payment ID.
Who is it for?
Finance & Billing Teams: Rapidly retrieve transaction data and reconcile accounts using natural language.
Sales & Support: Generate customized paylinks during a support call or sales pitch instantly.
* Developers: Eliminate manual dashboard checks and automate your billing operations via AI-driven commands.
Built-in capabilities (10)
Create a customer
Create a paylink
Create a payment intent
Get customer details by ID
Get paylink details by ID
Get payment details by ID
List customers
List paylinks
List recent payments
Refund a payment
Why Claude Code?
Claude Code registers Blink Payment as an MCP server in a single terminal command. Once connected, Claude Code discovers all 10 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Blink Payment data drives decisions without human intervention.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using Blink Payment tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
Blink Payment in Claude Code
Blink Payment and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Blink Payment to Claude Code through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Blink Payment in Claude Code
The Blink Payment MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Code only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Blink Payment for Claude Code
Every tool call from Claude Code to the Blink Payment MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can the AI Agent process a direct credit card charge?
No, for security reasons and PCI compliance, the agent uses Payment Intents and Paylinks. The end user still securely completes the payment.
Does this MCP integration support partial refunds?
Yes, you can instruct the AI to refund a specific amount. If no amount is provided, the transaction is fully refunded.
Can I use the agent to mass-delete my customer base?
No, destructive mass operations are not exposed to the AI agent to prevent accidental data loss in your Blink Payment account.
How do I add an MCP server to Claude Code?
Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
Can Claude Code run MCP tools in headless mode?
Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
How do I list all connected MCP servers?
Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable