Skip to content
ChargeKeep logoPinch Payments logo

Connect ChargeKeep to Pinch Payments

Move data between ChargeKeep and Pinch Payments 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.

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

Automation ideas

What you can build with ChargeKeep and Pinch Payments

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

  • New Lead in ChargeKeep 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 in ChargeKeep

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

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

    Triggers when a new lead is created

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

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

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

    Triggers when a new lead is created

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

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

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 ChargeKeep and acts in Pinch Payments, 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.