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 currently provides 14 triggers that can start a workflow and 8 actions a workflow can run. Use those building blocks to keep financial events visible beside the customer, vendor, or project they affect.
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
Create or Update Payer
Create a new payer or update an existing one
Create Realtime Payment
Create a real-time payment against a credit card or bank account
Add Source to Payer
Add a payment source (bank account or credit card) to an existing payer
Create or Update Scheduled Payment
Create a new scheduled payment or update an existing one
Add Subscription
Create a subscription between a payer and a plan
Find Event
Find an event using the Event ID
Find Payer
Find a payer by their Payer ID
Find Subscription
Find a subscription using the Subscription ID
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Pinch Payments event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Bank Results Event
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Pinch Payments action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create or Update Payer
Combine Pinch Payments with another integration and Coherence records to keep financial events visible beside the customer, vendor, or project they affect.
Starts with
Bank Results Event
Finishes with
Create or Update Payer, then preserve the outcome in Coherence
The exact authentication fields depend on Pinch Payments. The workflow structure stays straightforward:
Authorize the Pinch Payments account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Pinch Payments or provide a complementary trigger or action.
Pinch Payments currently provides 14 triggers that can start a workflow and 8 actions a workflow can run. Use those building blocks to keep financial events visible beside the customer, vendor, or project they affect.
Pinch Payments currently lists 14 triggers and 8 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Pinch Payments triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
