# Payhip API and MCP server

> Payhip has a narrow public API (checked 11 Oct 2026): it creates, lists and retrieves coupons, and verifies, enables, disables or counts uses of software license keys. Products, orders, customers and subscribers have no endpoints; new sales, refunds and subscription changes only arrive as 4 webhook events.

Store builder for creators who sell digital downloads, courses, coaching, memberships and physical products.

## What is the Payhip API?

Cotlet's Payhip API exposes 15 endpoints for your own Payhip account: list orders, get order, list products, get sales stats, get monthly sales report, list subscribers, list coupons, create coupon, create product, update product, add order note, reset download credits, resend receipt, cancel subscription and block customer. The list_orders endpoint returns orders from the Customers page with buyer email, items, amounts, status and date. Each endpoint takes simple JSON inputs like order_id, product_id or limit and works both as an MCP tool for agents and as a REST call for scripts.

- **Category:** [Courses & training](https://cotlet.dev/integrations/category/courses-training)
- **Endpoints:** 15 (7 read, 8 write)
- **Updated:** 2026-10-11

Payhip has a narrow public API (checked 11 Oct 2026): it creates, lists and retrieves coupons, and verifies, enables, disables or counts uses of software license keys. Cotlet is a hosted MCP server and REST API for Payhip with 15 endpoints (7 read, 8 write): your AI agent signs in as you and does the work.

## Does Payhip have an official API?

Payhip has a narrow public API (checked 11 Oct 2026): it creates, lists and retrieves coupons, and verifies, enables, disables or counts uses of software license keys. Products, orders, customers and subscribers have no endpoints; new sales, refunds and subscription changes only arrive as 4 webhook events.

| Task | Payhip official | Cotlet |
|---|---|---|
| Search orders by email, product, date or status | Partly: Webhooks send new paid and refunded orders, no history | Yes |
| Create and list coupons | Yes: Coupons API: create, list and retrieve; products must be identified by hand | Yes |
| Add and edit products | No | Yes |
| Daily sales, views and sales by product | No | Yes |
| List subscribers | Partly: Webhooks when a subscription starts or is deleted, no list | Yes |
| Cancel a subscription | No | Yes |
| Reset download credits and resend a receipt | No | Yes |
| Add private order notes and block a customer | No | Yes |

Sources: [Payhip API reference](https://payhip.com/api-reference), [Payhip Help: Public API](https://help.payhip.com/article/347-public-api), [Payhip Help: Webhooks](https://help.payhip.com/article/115-webhooks), [Payhip Help: Unable to Download or Open File](https://help.payhip.com/article/228-unable-to-open-file), [Payhip Help: Email Updates](https://help.payhip.com/article/82-email-updates), [Zapier: Payhip integrations](https://zapier.com/apps/payhip/integrations)

## For AI agents

```text
Payhip has a narrow public API (checked 11 Oct 2026): it creates, lists and retrieves coupons, and verifies, enables, disables or counts uses of software license keys. Products, orders, customers and subscribers have no endpoints; new sales, refunds and subscription changes only arrive as 4 webhook events.
Cotlet provides a hosted MCP server and REST API for Payhip: 15 tools (7 read, 8 write).
Access       Request access at https://cotlet.dev/app/signup?app=payhip; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/payhip
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_orders, get_order, list_products, get_sales_stats, get_sales_report, list_subscribers, list_coupons, create_coupon, create_product, update_product, add_order_note, reset_download_credits, resend_receipt, cancel_subscription, block_customer
Confirm      create_coupon, create_product, update_product, resend_receipt, cancel_subscription, block_customer (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/payhip-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=payhip (Payhip is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Payhip once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Payhip server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to Payhip in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Payhip's terms; Cotlet is not affiliated with Payhip.
```

## What can an AI agent do in Payhip?

Cotlet is best for Payhip sellers who answer buyer tickets, review sales or run coupons every week without running or fixing a server.

- **[Fix download limit errors and resend download links](https://cotlet.dev/integrations/payhip-api-mcp-server/fix-download-limit-errors)** (runs: daily): "A buyer at client@example.com says the Payhip link shows Download Limit Exceeded. Check the order, reset the credits if it was not refunded, resend the receipt and note what you did." → `list_orders`, `get_order`, `reset_download_credits`, `resend_receipt`, `add_order_note`
- **[Weekly sales summary with refunds and coupons](https://cotlet.dev/integrations/payhip-api-mcp-server/weekly-sales-summary)** (runs: weekly): "Summarize last week in Payhip against the week before: sales, views, best sellers, refunds and which coupon codes were used." → `get_sales_stats`, `list_orders`, `list_coupons`, `get_sales_report`
- **Cancel a member's subscription on request**: "Find the subscription for client@example.com on Design Club and cancel it." → `list_subscribers`, `cancel_subscription`
- **Create a coupon for a launch**: "Make a coupon LAUNCH25 for 25% off the Notion Budget Template, 50 uses, expiring 1 November." → `list_products`, `create_coupon`, `list_coupons`
- **Block a buyer after a dispute**: "Find the latest order from client@example.com and add the buyer to my Blocked List." → `list_orders`, `get_order`, `block_customer`

## Can Payhip automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Payhip connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to fix download limit errors and resend download links, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/payhip/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/payhip/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/payhip/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/payhip/{tool} with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 15 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 403 until the account has an API key with access to Payhip.

### list_orders

Orders from the Customers page with buyer email, items, amounts, status and date. Access: read. REST: `POST /api/v1/payhip/list_orders`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `email` | string | no | Buyer email. |
| `order_id` | string | no | Find one order by ID. |
| `product_id` | string | no | Only orders that include this product. |
| `status` | enum | no | completed, refunded or partially_refunded. |
| `shipping` | enum | no | unshipped (orders with unshipped items) or shipped (fully shipped), for physical products. |
| `from` | date | no | Orders on or after this date (UTC). |
| `to` | date | no | Orders on or before this date (UTC). |
| `limit` | integer | no | 1 to 100. Default: 25. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the same filters as the Filter Orders button on the Customers page: email, product, order date, order ID, status and shipping. Orders come newest first and every date is in UTC. Pass the cursor to read the next page.

Example response:

```json
{
  "orders": [
    {
      "order_id": "ord_7K2mQx",
      "email": "client@example.com",
      "items": [
        {
          "product_id": "RGsF",
          "name": "Notion Budget Template",
          "quantity": 1
        }
      ],
      "amount_gross": "12.00",
      "currency": "USD",
      "status": "completed",
      "coupon_code": null,
      "date": "2026-10-09T14:22:00Z"
    }
  ],
  "next_cursor": null
}
```

### get_order

One order: items, gross and net amount, fees, coupon, checkout answers and your private order notes. Access: read. REST: `POST /api/v1/payhip/get_order`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `order_id` | string | yes | Order ID from list_orders. |

Returns the amounts Payhip exports for an order: gross, net after tax and transaction fees, the Stripe or PayPal fee, the Payhip fee, the coupon applied and the buyer's answers to your checkout questions. It also returns your order notes, which only you can see.

Example response:

```json
{
  "order_id": "ord_7K2mQx",
  "email": "client@example.com",
  "status": "completed",
  "payment_type": "stripe",
  "currency": "USD",
  "items": [
    {
      "product_id": "RGsF",
      "name": "Notion Budget Template",
      "quantity": 1
    }
  ],
  "amount_gross": "12.00",
  "processor_fee": "0.65",
  "payhip_fee": "0.60",
  "amount_net": "10.75",
  "coupon_code": null,
  "checkout_responses": [],
  "notes": [],
  "date": "2026-10-09T14:22:00Z"
}
```

### list_products

Your products with type, price, visibility and link. Access: read. REST: `POST /api/v1/payhip/list_products`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `type` | enum | no | digital, course, coaching, membership or physical. Default: all. |
| `visibility` | enum | no | visible, invisible or unlisted. Default: all. |

Returns the product IDs the other tools take. Visible products are listed on your store; invisible ones only you can see while logged in; unlisted ones only open from a direct link. Prices are shown as on the product page.

Example response:

```json
{
  "products": [
    {
      "product_id": "RGsF",
      "name": "Notion Budget Template",
      "type": "digital",
      "price": "12.00",
      "visibility": "visible",
      "url": "https://payhip.com/b/RGsF"
    },
    {
      "product_id": "mVT0",
      "name": "Freelancer Contract Pack",
      "type": "digital",
      "price": "24.00",
      "visibility": "unlisted",
      "url": "https://payhip.com/b/mVT0"
    }
  ]
}
```

### get_sales_stats

Daily views, daily sales and sales by product from the Analytics page. Access: read. REST: `POST /api/v1/payhip/get_sales_stats`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | date | yes | Start date (UTC). |
| `to` | date | yes | End date (UTC). |

Returns the 3 graphs of the Analytics page as numbers. Visits from logged-in users are not counted in views, and all dates are in UTC. Only the sales breakdown is split by product.

Example response:

```json
{
  "daily_views": [
    {
      "date": "2026-10-05",
      "views": 142
    },
    {
      "date": "2026-10-06",
      "views": 98
    },
    {
      "date": "2026-10-07",
      "views": 176
    },
    {
      "date": "2026-10-08",
      "views": 120
    },
    {
      "date": "2026-10-09",
      "views": 87
    },
    {
      "date": "2026-10-10",
      "views": 64
    },
    {
      "date": "2026-10-11",
      "views": 203
    }
  ],
  "daily_sales": [
    {
      "date": "2026-10-05",
      "amount": "24.00"
    },
    {
      "date": "2026-10-06",
      "amount": "0.00"
    },
    {
      "date": "2026-10-07",
      "amount": "36.00"
    },
    {
      "date": "2026-10-08",
      "amount": "12.00"
    },
    {
      "date": "2026-10-09",
      "amount": "0.00"
    },
    {
      "date": "2026-10-10",
      "amount": "0.00"
    },
    {
      "date": "2026-10-11",
      "amount": "48.00"
    }
  ],
  "sales_by_product": [
    {
      "product_id": "RGsF",
      "name": "Notion Budget Template",
      "amount": "72.00"
    },
    {
      "product_id": "mVT0",
      "name": "Freelancer Contract Pack",
      "amount": "48.00"
    }
  ]
}
```

### get_sales_report

The monthly report from the Sales Report tab: VAT, fees, taxes, products sold and affiliate payouts. Access: read. REST: `POST /api/v1/payhip/get_sales_report`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `month` | string | yes | Month as YYYY-MM. |

Returns the 7 items of a Payhip monthly report: EU and UK VAT, Stripe and PayPal fees, Payhip fees, custom taxes, products sold, affiliate commission and affiliate sales. Reports are monthly, so a month that has not ended yet is incomplete.

Example response:

```json
{
  "month": "2026-09",
  "eu_uk_vat": "4.20",
  "processor_fees": "31.80",
  "payhip_fees": "25.00",
  "custom_taxes": "0.00",
  "products_sold": [
    {
      "name": "Notion Budget Template",
      "items": 38
    },
    {
      "name": "Freelancer Contract Pack",
      "items": 12
    }
  ],
  "affiliate_commission": "12.00",
  "affiliate_sales": 3
}
```

### list_subscribers

Subscribers to your subscription, course, coaching and membership plans with status and start date. Access: read. REST: `POST /api/v1/payhip/list_subscribers`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | active, trialing, cancelled, paused, unpaid, past_due, incomplete or incomplete_expired. |
| `email` | string | no | Find one subscriber by email. |
| `limit` | integer | no | 1 to 100. Default: 25. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the Subscribers tab of the Customers page. Buyers keep access while past_due and lose it on cancelled, incomplete and incomplete_expired. Payhip moves a subscription to cancelled on its own after a 20-day grace period of failed payments.

Example response:

```json
{
  "subscribers": [
    {
      "subscription_id": "sub_3Hf9aD",
      "email": "client@example.com",
      "product_name": "Design Club",
      "plan_name": "Monthly",
      "status": "active",
      "started": "2026-08-14"
    }
  ],
  "next_cursor": null
}
```

### list_coupons

Coupon codes with discount, scope, uses, usage limit and expiry date. Access: read. REST: `POST /api/v1/payhip/list_coupons`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `limit` | integer | no | 1 to 100. Default: 25. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the coupons from Marketing > Coupons with how often each was used. Expiry dates are in UTC. Notes are your private notes and buyers never see them.

Example response:

```json
{
  "coupons": [
    {
      "coupon_id": "cpn_9d2e41",
      "code": "LAUNCH25",
      "discount_type": "percentage",
      "amount": "25",
      "applies_to": "product",
      "product_id": "RGsF",
      "uses": 0,
      "usage_limit": 50,
      "expires_on": "2026-11-01",
      "notes": "Newsletter launch"
    }
  ],
  "next_cursor": null
}
```

### create_coupon

Coupon code for the whole order, one product or one collection. Access: write, asks the user first. REST: `POST /api/v1/payhip/create_coupon`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `code` | string | no | Code buyers type at checkout. Omit to let Payhip generate one. |
| `discount_type` | enum | yes | percentage or fixed. |
| `amount` | string | yes | Percent off or amount off. |
| `applies_to` | enum | yes | total_order, product or collection. |
| `product_id` | string | no | Required when applies_to is product. |
| `collection_id` | string | no | Required when applies_to is collection. |
| `usage_limit` | integer | no | Total uses across all buyers, not per buyer. |
| `expires_on` | date | no | Expires at 00:00 UTC on this date. |
| `notes` | string | no | Private note. Buyers never see it. |

A percentage applies to the original price and a fixed amount is deducted from it. Payhip has no per-buyer limit, so use a product-specific code or single-use codes for that. The coupon works at checkout right away. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "coupon_id": "cpn_9d2e41",
  "code": "LAUNCH25",
  "discount_type": "percentage",
  "amount": "25",
  "applies_to": "product",
  "product_id": "RGsF",
  "usage_limit": 50,
  "uses": 0,
  "expires_on": "2026-11-01",
  "expires_at": "2026-11-01T00:00:00Z",
  "notes": "Newsletter launch"
}
```

### create_product

New digital product from a file URL, with title, price, description and visibility. Access: write, asks the user first. REST: `POST /api/v1/payhip/create_product`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `title` | string | yes | Product title. |
| `price` | string | yes | Price, e.g. 12. Add + for pay what you want: 5+ means at least 5, 0+ means any amount including free. |
| `file_url` | string | yes | Public URL of the file to sell, up to 5 GB. |
| `description` | string | no | Product description. |
| `cover_image_url` | string | no | Cover image shown on the product page. |
| `visibility` | enum | no | visible, invisible or unlisted. Default: invisible. |

Creates a digital product only; courses, coaching, memberships and physical products are not created by this tool. Each file can be up to 5 GB. The default is invisible, so nothing goes on your store until you set visible or unlisted. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "product_id": "Qx7B",
  "name": "Notion Budget Template",
  "type": "digital",
  "price": "12.00",
  "visibility": "invisible",
  "url": "https://payhip.com/b/Qx7B"
}
```

### update_product

Change the title, price, description or visibility of a product. Access: write, asks the user first. REST: `POST /api/v1/payhip/update_product`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `product_id` | string | yes | Product ID from list_products. |
| `fields` | object | yes | Any of title, price, description, visibility (visible, invisible or unlisted). |

Returns the product after the change. A price change applies to new orders at once, and products with variants are not covered by this tool. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "product_id": "RGsF",
  "name": "Notion Budget Template",
  "type": "digital",
  "price": "9.00",
  "visibility": "visible",
  "url": "https://payhip.com/b/RGsF"
}
```

### add_order_note

Private note on an order. Only you see it. Access: write. REST: `POST /api/v1/payhip/add_order_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `order_id` | string | yes | Order ID from list_orders. |
| `note` | string | yes | Note text. |

Order notes are only visible to you and appear in the Order Notes column of your orders export. The note reaches no customer, so this tool runs without asking.

Example response:

```json
{
  "order_id": "ord_7K2mQx",
  "notes": [
    "Refunded in Stripe on request, emailed buyer"
  ]
}
```

### reset_download_credits

Reset a buyer's download attempts to your store's download limit. Access: write. REST: `POST /api/v1/payhip/reset_download_credits`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `order_id` | string | yes | Order ID from list_orders. |

Sets the credits back to the Download Limit in your Advanced Settings, which is 5 unless you changed it. It changes only the count and does not email the buyer; call resend_receipt for that. The call reaches no one, so it runs without asking.

Example response:

```json
{
  "order_id": "ord_7K2mQx",
  "email": "client@example.com",
  "download_limit": 5,
  "download_credits": 5,
  "status": "reset"
}
```

### resend_receipt

Email the receipt and download link to the buyer again. Access: write, asks the user first. REST: `POST /api/v1/payhip/resend_receipt`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `order_id` | string | yes | Order ID from list_orders. |

Does the same as Resend Receipt in the Customers menu: the buyer gets the receipt again. If the buyer ran out of download attempts, call reset_download_credits first. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "order_id": "ord_7K2mQx",
  "email": "client@example.com",
  "status": "sent"
}
```

### cancel_subscription

Cancel a subscriber's plan. Billing stops and access ends. Access: write, asks the user first. REST: `POST /api/v1/payhip/cancel_subscription`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `subscription_id` | string | yes | Subscription ID from list_subscribers. |

Does the same as Cancel Subscription on the Subscribers tab: it prevents future charges and unenrolls the customer, who immediately loses access to the product. It does not refund past payments. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "subscription_id": "sub_3Hf9aD",
  "email": "client@example.com",
  "product_name": "Design Club",
  "status": "cancelled",
  "access": "ended"
}
```

### block_customer

Add an order's buyer to your Blocked List so they cannot buy again. Access: write, asks the user first. REST: `POST /api/v1/payhip/block_customer`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `order_id` | string | yes | Order ID from list_orders. |

Payhip stores the PayPal payer ID or card payer ID of the order on your Blocked List, and that buyer cannot make future purchases from your store. There is no unblock tool; remove a buyer on the Blocked List page. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "order_id": "ord_7K2mQx",
  "email": "client@example.com",
  "blocked": true,
  "payer_type": "card"
}
```

## How do I connect Payhip to Claude Code, Codex or Cursor?

Connecting Payhip takes three steps: request access, sign in to Payhip once, then add one MCP server or call the REST API with the same key.

### Connect Payhip to your agent.

1. **Create an account** Sign up and add Payhip in the console. Your API key is there too.

2. **Sign in to Payhip once** Open the connect page from the console and sign in to Payhip the way you always do. We keep the session, never your password, and you can revoke it anytime.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Payhip tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
A buyer at client@example.com says the Payhip link shows Download Limit Exceeded. Check the order, reset the credits if it was not refunded, resend the receipt and note what you did.
```

### Call Payhip from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is a POST endpoint at /api/v1/payhip/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/payhip/create_coupon \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"code":"LAUNCH25","discount_type":"percentage","amount":"25","applies_to":"product","product_id":"RGsF","usage_limit":50,"expires_on":"2026-11-01","notes":"Newsletter launch"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "coupon_id": "cpn_9d2e41",
  "code": "LAUNCH25",
  "discount_type": "percentage",
  "amount": "25",
  "applies_to": "product",
  "product_id": "RGsF",
  "usage_limit": 50,
  "uses": 0,
  "expires_on": "2026-11-01",
  "expires_at": "2026-11-01T00:00:00Z",
  "notes": "Newsletter launch"
}
```

## Why use Cotlet for Payhip?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Payhip yourself. We keep only the session, encrypted with AES-256.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Pick read only, or read and write.
- Anything that reaches other people waits for your OK, unless you switch it off per tool.
- Revoke access in one click.

**Kept working for you**

- We test every integration daily.
- When Payhip changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is there a Payhip MCP server on GitHub?

Zapier's Payhip app has 5 triggers and no actions. Hosted tool catalogs wrap the same coupon, license key and webhook API. We found no open-source Payhip MCP server we could confirm.

|  | Zapier | Cotlet |
|---|---|---|
| Setup | Connect Payhip in Zapier and build one Zap per trigger | Request access, sign in to Payhip once, add one MCP server or API key |
| What it can do | Triggers only: new sale, refund, new product, membership started or cancelled | Read orders, products, subscribers and stats; create coupons, edit products, cancel subscriptions |
| Past orders | Only events after the Zap is turned on | Search every order by email, product, date or status |
| Write actions | None for Payhip, so Zapier MCP has nothing to call | Each receipt, price change or subscription cancel confirmed by you |
| Your Payhip session | Not session based | Encrypted in an EU vault, limited to the actions you allow, revoked in one click |
| When the session expires | Not session based | Your agent gets a link to sign in again |
| Price | Free plan, paid plans for more tasks | Free 7-day trial with 5,000 credits, then credits per call |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Payhip changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want the session to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Payhip API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Payhip API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

| Size | Price | Credits / month | Per credit |
|---|---|---|---|
| Solo | $29/mo | 3,000 | about $0.0097 |
| Pro | $99/mo | 12,000 | about $0.0083 |
| Agency | $299/mo | 40,000 | $0.0075 |

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Payhip account.

- **Company details:** The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. [Terms](https://cotlet.dev/terms)
- **Your session:** You sign in to Payhip yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Payhip tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect Payhip in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Payhip's terms:** You use your own Payhip account and stay responsible for following Payhip's terms. Cotlet is independent and not affiliated with Payhip. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Request access and pick Payhip. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to Payhip once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is a hosted server safe? My Payhip session would leave my computer.**

Cotlet keeps your Payhip session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

**Do I need a paid Payhip plan?**

Payhip lists the same features on Free Forever, Plus and Pro, with no feature-gating, and the plans differ in transaction fee (5%, 2% and none) (checked 11 Oct 2026). A free store works.

**Which time zone do dates use?**

UTC. Payhip filters orders by date in UTC, reports analytics in UTC and expires coupons at 00:00 UTC, and Cotlet passes dates through the same way.

**Can my agent post or send messages in Payhip without asking me?**

No. Every call to create_coupon, create_product, update_product, resend_receipt, cancel_subscription or block_customer waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. add_order_note, reset_download_credits runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Payhip API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/payhip/{tool} from the HTTP Request node.