Accounting

Pinch Payments + StackGo

Run compliance from inside Pinch Payments. Checks start from a record and the result lands back on the client.

Pinch Payments publishes 9 trigger events and 8 actions on its public Zapier listing. That is what a StackGo connector would be built on.

Accounting System of record Not connected yet
What Pinch Payments is

Pinch Payments is a PCI Compliant, Australian payments platform offering automated bank account, direct debit, and credit card payments for standard and repeating invoices or standalone transactions.

Description supplied by Pinch Payments.

The trigger

What starts a check

You do not open StackGo. A change in the system starts the work, and the system stays your source of truth.

EventWhat StackGo doesWhat comes back
A new contact or customer is createdStarts identity collectionVerification status
A designated service is addedRuns the checks that service requiresResult and risk rating
Ownership or details changeRe-screens the related partiesUpdated status
The write-back

What StackGo puts back on the record

A Pinch Payments connector would write named fields onto the record, not a link to a portal. These are the fields StackGo writes on the systems it connects to today.

  • Verification status
  • Risk rating
  • Last checked
  • Report link
  • Verified name
  • Date of birth
  • Document checked
  • Screening result
  • Beneficial owners
  • Form responses
  • Verification report (PDF)

Every field is optional. What each one holds, and which carry personal data, is set out once in what “integrates with” actually means.

Everything else Pinch Payments publishes

Pinch Payments’s public integration surface

The rest of what Pinch Payments exposes on Zapier, beyond the workflow. This is the raw material a connector would use.

9 events
  • Bank Results Event
  • Payer Created Event
  • Payer Updated Event
  • Realtime Payment Event
  • Scheduled Process Event
  • Subscription Cancelled Event
  • Subscription Complete Event
  • Subscription Created Event
  • New Event
8 actions
  • Create or Update Payer
  • Create Realtime Payment
  • Create or Update Scheduled Payment
  • Add a Source to a Payer
  • Add a Subscription
  • Find an Event
  • Find Payer
  • Find a Subscription

Names are Pinch Payments’s own, read from its public Zapier listing on 28 August 2026.

Questions

Common questions about Pinch Payments

What is payment integration?

There is no StackGo connector for Pinch Payments yet. Pinch Payments publishes 9 trigger events and 8 actions through Zapier, so building one is realistic. Requests decide the build order.

Questions taken from what people actually search in Australia. We answer only the ones our own data answers.

Where this sits

Pinch Payments is the record. StackGo runs the steps around it.

Every step writes back to Pinch Payments, so the client record stays the source of truth.

If you use Pinch Payments, you probably also use

Want Pinch Payments connected?

Requests decide the build order. Tell us and we will tell you where it sits.

Request this integration

Ready to make onboarding minutes, not hours?

Start free and run your first check today, or book a demo and we will walk you through it.