Skip to content
Pinch Payments logo

Pinch Payments integration

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.

Actions
8
Triggers
14
Auth
Custom auth
License
MIT, open source
Updated
September 2026

About the Pinch Payments integration

Add the Pinch Payments piece to a flow, connect your account once, and the rest of the builder can read from it and write to it. Because the piece is open source you can run it on our cloud or self-host it, and combine Pinch Payments with 760+ other apps in the same flow.

Triggers

Start a flow the moment something happens in Pinch Payments

Each trigger below can start a flow on its own, either instantly or on a schedule.

  • 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

Actions

Everything Activepieces can do in Pinch Payments

Drop any of these into a flow and fill in the fields. No code is required.

  • 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

Use Pinch Payments in a flow

Connect Pinch Payments once and every trigger and action above is yours to drop into the builder, alongside 760+ other apps. Free to start, on our cloud or your own servers.

Pinch Payments, answered.

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

Add the Pinch Payments piece to a flow, then authenticate with Custom auth. Once connected, its 14 triggers and 8 actions are available anywhere in the builder.

"Bank Results Event" can start a flow that runs "Create or Update Payer", and you can chain Pinch Payments together with any of 760+ other apps and AI steps in between.

Yes. Activepieces is fully self-hostable, so you can run the Pinch Payments piece on your own infrastructure with your connections and your data staying in your environment.

Yes. Every piece you connect can be exposed over one Activepieces MCP server, so Claude, Cursor, Windsurf or any MCP client can call Pinch Payments actions as tools.