Skip to content
Pinch Payments logoSperse logo

Connect Pinch Payments to Sperse

Move data between Pinch Payments and Sperse the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Pinch Payments triggers
14
Pinch Payments actions
8
Sperse triggers
3
Sperse actions
6

Automation ideas

What you can build with Pinch Payments and Sperse

A few flows teams run between Pinch Payments and Sperse. Use one as a starting point, or build your own from scratch.

  • Bank Results Event in Pinch Payments creates Add or Update Contact in Sperse

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

  • New Lead in Sperse creates Create or Update Payer in Pinch Payments

    Triggers when a new lead is created

  • Bank Results Event in Pinch Payments creates Add or Update Contact (Extended) in Sperse

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

  • New Lead in Sperse creates Create Realtime Payment in Pinch Payments

    Triggers when a new lead is created

  • Bank Results Event in Pinch Payments creates Add or Update Subscription in Sperse

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

  • New Lead in Sperse creates Add Source to Payer in Pinch Payments

    Triggers when a new lead is created

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Pinch Payments and acts in Sperse, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.