Turkey Payments (iyzico — Turkish cards / taksit)

Official3 tools

by junter1989k-ai · JavaScript

Turkey payments for AI agents — Turkish cards / taksit via iyzico. Never holds funds.

This MCP server provides “Turkey payments for AI agents” so agents can accept payments in Turkey using Turkish cards and taksit via iyzico. The service is described as never holding funds and uses HTTP requests to an MCP endpoint. It reports 3 tools and is labeled with MCP server and payments-related topics.

🛠️ Key Features

Supports Turkish cards and taksit payments via iyzico
“Never holds funds”
Accessible via an HTTP MCP endpoint (https://mcp-tr.wishpool.app/mcp)
Tool count: 3

🚀 Use Cases

Enable AI agents to accept Turkey payments
Use with MCP-capable clients (e.g., Claude Desktop, Cursor, Windsurf)

⚡ Developer Benefits

Credentials “travel as HTTP headers on each request”
“Never stored,” per the provided README excerpt

⚠️ Limitations

The provided excerpt states credentials are needed when you need them, but does not list specific auth or tool-by-tool behavior beyond the URL setup.

Topics

ai-agentclaudeiyzicomcpmcp-serverpaymentsturkeywishpool

Captured live from the server via tools/list.

create_payment_link

Create a payment link in TRY for Turkey via iyzico (Checkout Form). Buyer pays with local Turkish cards with taksit (installments), international cards. Returns a hosted checkout URL the buyer opens to pay — payment completes automatically, no confirm step. Bring your own credentials via HTTP header (x-iyzico-api-key; free test credentials from sandbox-merchant.iyzipay.com never move real money). Money always flows buyer→iyzico→merchant; this service never touches funds.

Parameters5

amount_try	number	required	Amount in TRY (decimals allowed), e.g. 10. Minimum 1.
description	string	required	What this payment is for (shown to the buyer, ≤200 chars)
customer_email	string	optional	Optional buyer email.
reference_id	string	optional	Your unique order reference (≤40 chars). Auto-generated if omitted.
success_url	string	optional	Optional https URL to send the buyer to after payment.

Raw schema

{
  "type": "object",
  "properties": {
    "amount_try": {
      "type": "number",
      "minimum": 1,
      "maximum": 10000000,
      "description": "Amount in TRY (decimals allowed), e.g. 10. Minimum 1."
    },
    "description": {
      "type": "string",
      "description": "What this payment is for (shown to the buyer, ≤200 chars)"
    },
    "customer_email": {
      "type": "string",
      "description": "Optional buyer email."
    },
    "reference_id": {
      "type": "string",
      "description": "Your unique order reference (≤40 chars). Auto-generated if omitted."
    },
    "success_url": {
      "type": "string",
      "description": "Optional https URL to send the buyer to after payment."
    }
  },
  "required": [
    "amount_try",
    "description"
  ]
}

query_payment_status

Check whether a Turkey payment (created by create_payment_link) has been paid. Queries iyzico directly — pull-based, no webhook needed. paid=true when status is PAID.

Parameters1

token

string

required

The checkout form token returned by create_payment_link

Raw schema

{
  "type": "object",
  "properties": {
    "token": {
      "type": "string",
      "description": "The checkout form token returned by create_payment_link"
    }
  },
  "required": [
    "token"
  ]
}

refund_payment

Refund a paid Turkey payment (created by create_payment_link) via iyzico. Provide payment_id (the iyzico paymentId from query_payment_status) OR conversation_id (the reference_id you used when creating the link) — the tool looks up the payment to find its transaction(s), then refunds per-transaction. Full refund by default; pass amount_try for a partial refund (single-item payments, decimals allowed). Refunds respect the same owner policy guardrails (x-agentpay-max-amount) as payments — the refund amount is checked before anything is sent to iyzico.

Parameters4

payment_id	string	optional	iyzico paymentId of the paid payment (from query_payment_status.payment_id). Provide this or conversation_id.
conversation_id	string	optional	The reference_id you used in create_payment_link (iyzico conversationId). Provide this or payment_id.
amount_try	number	optional	Optional partial-refund amount in TRY (decimals allowed). Omit for a full refund of the payment.
ip	string	optional	Optional IP address to record on the refund request.

Raw schema

{
  "type": "object",
  "properties": {
    "payment_id": {
      "type": "string",
      "description": "iyzico paymentId of the paid payment (from query_payment_status.payment_id). Provide this or conversation_id."
    },
    "conversation_id": {
      "type": "string",
      "description": "The reference_id you used in create_payment_link (iyzico conversationId). Provide this or payment_id."
    },
    "amount_try": {
      "type": "number",
      "description": "Optional partial-refund amount in TRY (decimals allowed). Omit for a full refund of the payment."
    },
    "ip": {
      "type": "string",
      "description": "Optional IP address to record on the refund request."
    }
  },
  "required": []
}

README.md3 KBView on GitHub

Turkey Payments MCP — let AI agents accept payments in Turkey

Use it in 60 seconds

Paste this into your MCP client config (Claude Desktop, Cursor, Windsurf, or any MCP-capable agent):

json

{
  "mcpServers": {
    "turkey-payments": {
      "type": "http",
      "url": "https://mcp-tr.wishpool.app/mcp"
    }
  }
}

Nothing to install. Credentials, when you need them, travel as HTTP headers on each request and are never stored — see the threat model.

Or run it yourself

Would you rather not send production credentials to a server you do not control? Deploy this identical code to your own account and point your agent at your own URL:

bash

git clone https://github.com/junter1989k-ai/turkey-payments-mcp && cd turkey-payments-mcp && npx vercel --prod

MIT-licensed. Self-hosting removes us from the picture entirely, at no cost and with no loss of function.

Live · MCP endpoint: https://mcp-tr.wishpool.app/mcp · Listed on the official MCP Registry as app.wishpool/turkey-payments-mcp · Part of a 30-country family — hub: mcp.wishpool.app

A remote MCP server that lets any AI agent (Claude, ChatGPT, Cursor…) accept payments in Turkey: local Turkish cards with taksit (installments), international cards — via iyzico's hosted checkout.

⚖️ Stateless translation layer: funds always flow buyer → iyzico → merchant directly. Never holds funds or stores credentials — no database at all.

Quick start

MCP endpoint: https://mcp-tr.wishpool.app/mcp (Streamable HTTP, stateless JSON-RPC)

Header	Value
`x-iyzico-api-key`	your iyzico API key pair (free sandbox- keys from sandbox-merchant.iyzipay.com; sandbox- prefix = test mode, never moves real money)

Tools

Tool	What it does
`create_payment_link`	Create a TRY hosted-checkout link.
`query_payment_status`	Pull-based status check; `paid=true` when PAID.
`refund_payment`	Refund a paid payment (full or partial) by `payment_id` or `conversation_id`.

Develop

bash

node test/serve.js      # local server (http://localhost:3231/mcp)
node test/e2e.js        # protocol + validation suite (probes real iyzico auth errors)

Zero runtime dependencies; Node ≥ 18. MIT license.

Install

Tools (3)

create_payment_linkquery_payment_statusrefund_payment

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://mcp-tr.wishpool.app/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "turkey-payments-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp-tr.wishpool.app/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

create_payment_link

query_payment_status

refund_payment

Turkey Payments MCP — let AI agents accept payments in Turkey

Use it in 60 seconds

Or run it yourself

Quick start

Tools

Develop

Install

Remote endpoint

Related servers