Payhip
Payhip is an e-commerce platform that enables individuals and businesses to sell digital products, memberships, and physical goods directly to their audience.
Verdict
Common use cases
- Alert the team when a refund comes in
- Log new subscriptions to a tracking sheet
- Flag canceled subscriptions for win-back outreach
- Summarize daily sales from webhook data
- Route high-value purchases to account managers
Integration
- Vendor
- Payhip
- Category
- other
- Auth
- API_KEY
- Tools
- 4
- Composio slug
payhip
Tools
- Webhook Event - Paid
Tool to process payhip's paid webhook event. use when handling a purchase completion webhook from payhip.
- Webhook Event - Refunded Payment
Tool to process payhip's refunded webhook event. use when handling a payment refund event from payhip.
- Webhook Event - Subscription Created
Tool to process payhip's subscription.created webhook event. use when handling a subscription start event from payhip.
- Webhook Event - Subscription Deleted
Tool to process payhip's 'subscription.deleted' webhook event. use when handling a subscription cancellation event from payhip.
Setup
Setup guide
- 11. In your Payhip dashboard, navigate to Settings > Developer and copy your API key. 2. Open Switchy, click Integrations in the left sidebar, search for Payhip, and select Connect. 3. Paste your API key into the prompt and click Authorize. 4. Back in Payhip, go to Settings > Webhooks and add a new webhook URL pointing to the endpoint Switchy displays after connection (copy it from the integration settings page). 5. Select which events to send: paid, refunded, subscription.created, subscription.deleted. 6. Save the webhook in Payhip, then return to Switchy and open any Space. 7. Type '@Payhip process the latest paid event' to confirm the connection works — if configured correctly, the MCP will acknowledge it's listening for incoming webhooks.
What teammates see: by default, memories from Payhip are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Process New Purchase
@Payhip process the latest paid webhook event and show me the customer email, product purchased, and total amount.Open in a Space →
Summarize Refunds Today
@Payhip pull all refunded webhook events from today and summarize the refund reasons and totals.Open in a Space →
Track New Subscriptions
@Payhip show me all subscription.created events from the past seven days and count the new subscribers.Open in a Space →
Flag Canceled Subscriptions
@Payhip find all subscription.deleted events from the past day and list the customer emails who canceled.Open in a Space →
Daily Sales Digest
@Payhip compile a digest of all paid and subscription.created events from today, showing total revenue and new subscriber count.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Payhip process the paid webhook event for order #12345 that just came through our endpoint
Processed purchase completion for order #12345. Customer email: customer@example.com purchased 'Premium Course Bundle' for $149.00 USD. Payment method: card ending in 4242. Transaction ID: txn_abc123xyz. Sale timestamp: 2024-01-15 14:32:18 UTC. This represents a typical paid event structure—actual webhook payloads will include additional fields like affiliate data, discount codes applied, and customer location based on your Payhip account configuration.
This example shows webhook ingestion for completed purchases. Your Payhip webhook endpoint must be configured to forward events to Switchy, and the MCP requires a valid API key with webhook access. Useful for triggering fulfillment workflows or customer onboarding sequences when sales occur.
@Payhip handle the subscription.created event we received 3 minutes ago for plan 'Monthly Pro'
Processed new subscription creation. Subscriber: jane.doe@example.com started 'Monthly Pro' plan at $29/month. Subscription ID: sub_def456ghi. Billing cycle: monthly, next charge date: 2024-02-15. Payment method on file: card ending in 5678. This illustrative response reflects common subscription start data—your actual events may include trial period details, coupon applications, or custom field values depending on your Payhip product setup.
Demonstrates subscription lifecycle tracking. The MCP processes Payhip's subscription.created webhook to capture recurring revenue starts. Requires webhook configuration pointing to your Switchy workspace. Pair this with CRM or analytics MCPs to automatically tag subscribers or update revenue dashboards when subscriptions begin.
@Payhip review all refunded payment events from the past week and summarize the refund reasons if available
Analyzed 7 refunded payment events from January 8-15, 2024. Total refunded: $523.00 across 7 transactions. Common patterns: 3 refunds cited 'accidental purchase', 2 were duplicate charges, 1 customer reported 'product not as described', 1 had no reason specified. Average refund amount: $74.71. Note that Payhip's refunded webhook provides transaction IDs and amounts but reason codes depend on how you've configured refund processing—this summary interprets available data fields.
Shows how the MCP can aggregate refund webhooks for pattern analysis. The AI synthesizes multiple refunded events to surface trends. Refund reason availability depends on your Payhip settings and whether customers provide feedback during the refund process. Useful for quality control or identifying product issues early.
Use-case deep-dives
When Payhip MCP helps a two-person team spot cancellation patterns
A two-person SaaS team selling a $29/month tool through Payhip wants to understand why subscribers cancel. The Payhip MCP's subscription.deleted webhook tool routes cancellation events directly into a Switchy workspace where the team logs cancellation reasons in a shared note. Over two weeks, they spot a pattern: seven of nine cancellations came within 48 hours of the first billing cycle. That insight drives a product change (better onboarding email on day three). The MCP works here because the team is small enough to manually review every cancellation and the webhook tooling is dead simple—four events, no complex query logic. If you're processing 200+ cancellations a month, you need a real analytics stack, not a webhook relay. For early-stage teams under 50 active subscriptions, this MCP turns Payhip events into triage-ready context without leaving your AI workspace.
Why this MCP fits a three-person creator team handling refund requests
A three-person team selling design templates on Payhip gets 8-12 refund requests a week. The Payhip MCP's refunded webhook tool posts each refund event into a Switchy thread where the team decides whether to follow up (was it a duplicate purchase? a quality complaint?). The MCP doesn't automate the refund decision—it surfaces the event so the team can triage in real time. This works because Payhip already processed the refund; the team just needs to see it and decide on next steps (email the customer, flag a product issue, update the listing). The threshold: if you're issuing 40+ refunds a week, you need a CRM with refund tagging, not a webhook listener. For small creator teams where every refund is a signal worth reviewing, this MCP keeps the context in your shared workspace instead of buried in Payhip's dashboard.
When the paid webhook tool speeds up welcome email triage
A solo course creator selling a $99 video course through Payhip wants to send a personalized welcome email within an hour of purchase. The Payhip MCP's paid webhook tool drops each purchase event into a Switchy workspace where the creator drafts a custom welcome message referencing the buyer's name and purchase date. The MCP doesn't send the email—it just surfaces the purchase event so the creator can act on it without checking Payhip's dashboard every 20 minutes. This setup works for creators doing 10-30 sales a week who want to add a personal touch. If you're selling 200+ units a week, you need an email automation platform, not a manual triage flow. For early-stage creators where each customer interaction still matters, this MCP turns Payhip purchase events into actionable prompts in your AI workspace.
Frequently asked
What does the Payhip MCP do in Switchy?
The Payhip MCP processes webhook events from your Payhip store—purchases, refunds, new subscriptions, and cancellations. When a customer completes a transaction in Payhip, the MCP receives the webhook and lets your AI agents act on it immediately. You can trigger workflows, update customer records, or send notifications without building custom webhook handlers.
Do I need admin access to connect Payhip?
You need access to your Payhip account settings to generate an API key. Payhip doesn't use OAuth; you create the key in your dashboard under Developer Settings, then paste it into Switchy. Any team member with API key access can connect it, but treat the key like a password—it grants full read-write access to your store data.
Can the Payhip MCP create products or issue refunds?
No. This MCP only processes incoming webhook events—it listens for transactions that already happened. It can't create products, initiate refunds, or modify your store. If you need to push data back to Payhip, you'll have to use Payhip's REST API directly or build a custom integration outside this MCP.
Why use this instead of Payhip's native webhook URLs?
Native webhooks require you to write server code, handle retries, and parse JSON payloads yourself. The Payhip MCP hands your AI agents structured event data instantly—no middleware. If you're already running agents in Switchy to handle customer ops or fulfillment, this eliminates the glue code between Payhip and your workflows.
Does connecting Payhip count against my Switchy plan limits?
The connection itself doesn't count as a seat or user. Webhook processing consumes API call quota based on your plan—each incoming event triggers one tool invocation. If you run a high-volume store with hundreds of daily transactions, check your plan's monthly API limit to avoid throttling during peak sales periods.