Skip to content
Pinch Payments logo

Pinch Payments MCP server

Australian payment processing platform for direct debits, credit cards, and recurring payments. Create payers, process payments, manage subscriptions, and handle payment sources with comprehensive webhook support.

Pinch Payments is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
8
Works with
Any MCP client
Auth
Custom auth
License
MIT, open source
Updated
September 2026

About the Pinch Payments MCP server

Connect Pinch Payments once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Pinch Payments and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Pinch Payments tools your AI can run

Once connected, your assistant can call any of these Pinch Payments actions by asking in plain language.

  • Create or Update Payer

    Create a new payer or update an existing one

    17 fields

  • Create Realtime Payment

    Create a real-time payment against a credit card or bank account

    15 fields

  • Add Source to Payer

    Add a payment source (bank account or credit card) to an existing payer

    8 fields

  • Create or Update Scheduled Payment

    Create a new scheduled payment or update an existing one

    9 fields

  • Add Subscription

    Create a subscription between a payer and a plan

    6 fields

  • Find Event

    Find an event using the Event ID

    1 field

  • Find Payer

    Find a payer by their Payer ID

    1 field

  • Find Subscription

    Find a subscription using the Subscription ID

    1 field

Triggers

Pinch Payments events your agent can watch

These start a run the moment something happens in Pinch Payments, so work gets picked up on its own.

  • Bank Results Event

    Triggers when a bank account transaction returns (may result in dishonour status)

  • Payer Created

    Triggers when a new payer record is created

  • Payer Updated

    Triggers when a payer record is updated

  • Realtime Payment

    Triggers when a realtime payment is executed

  • Payment Created

    Triggers when a payment is created (via Save Payment endpoint or Subscription)

  • Subscription Created

    Triggers when a subscription is created for a payer

  • Subscription Cancelled

    Triggers when a subscription is cancelled

  • Subscription Complete

    Triggers when a subscription is run to completion

  • Refund Created

    Triggers when a refund is created

  • Refund Updated

    Triggers when a refund is updated (e.g., status change)

  • Scheduled Process

    Triggers when scheduled payments are processed (daily on business days)

  • Transfer Created

    Triggers when a transfer is created to settle funds to a merchant

  • Dispute Created

    Triggers when a dispute is created

  • Dispute Updated

    Triggers when a dispute is updated

Give your assistant Pinch Payments

Connect Pinch Payments once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Pinch Payments MCP, answered.

No. That is the point of it. One Activepieces server exposes Pinch Payments alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Pinch Payments in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 8 tools, including Create or Update Payer, Create Realtime Payment, Add Source to Payer, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.