Skip to content
Pinch Payments logoPaywhirl logo

Connect Pinch Payments to Paywhirl

Move data between Pinch Payments and Paywhirl 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
Paywhirl triggers
0
Paywhirl actions
6

Automation ideas

What you can build with Pinch Payments and Paywhirl

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

  • Bank Results Event in Pinch Payments creates Cancel Subscription in Paywhirl

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

  • Bank Results Event in Pinch Payments creates Create Customer in Paywhirl

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

  • Bank Results Event in Pinch Payments creates Get Customers in Paywhirl

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

  • Payer Created in Pinch Payments creates Cancel Subscription in Paywhirl

    Triggers when a new payer record 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 Paywhirl, 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.